fpo3.franklinwaller2.testnet
. You only need to set up your near account and provider node to be able to start pushing data to it. near-cli
package. (npm i -g near-cli
).AggregatorInterface
and AggregatorV3Interface
for easy integration into existing smart contract infrastructure. There are no limits in how often an answer can be posted to the contract. The contract uses OpenZeppelin's Access Control library to manage roles; by default only the deployer has permission to post data or to grant others permission.FluxPriceFeed.sol
by cloning this repository. For example, the commands to deploy a contract with description ETH / USD
are:12345
.v14.18.1
.DISABLE_ANALYTICS
to false
. No private keys will be submitted.appconfig.json
, each price pair is mapped to a single contract and can have any number of sources. The node will push the result of the last source that returns an answer, throwing out sources that do not respond.appconfig.json
evm
and near
. You can use each network type multiple types to combine for example Avalanche, Polygon and Ethereum.NEAR_ENV=testnet near login
(NEAR_ENV=mainnet
for mainnet). This will store private keys inside the ~/.near-credentials/testnet
(or /mainnet
for mainnet). If for some reason the data is not in those folders please manually copy the private key over from ~/.near-credentials/default
over to the desired network folder.appconfig.json
Make sure if you are using NEAR to change the accountId (containing {{YOUR_ACCOUNT_ID}}
) with your accountId that you just used to login with. Also if you want to deploy for mainnet, make sure the networkType
is set to mainnet and rpc
is set to https://rpc.testnet.near.org
..env
file you just created, change the NEAR_CREDENTIALS_STORE_PATH
to the root of the near-credentials
folder. (For example /home/myname/.near-credentials/
).NEAR_ENV={NETWORK} near login
and following the steps provided by the CLI. This will generate a access keys in ~/.near-credentials/{NETWORK}/{MY_ACCOUNT}.near.json
which can then be copied into any environment. We would also recommend for you to check out batching of transactions, this makes pushing data on chain be done 1 transaction instead of multiple saving you gas. See Batching for more information.privateKeyEnvKey
.env
file). Not required if you are using credentialsStorePathEnvKey
chainId
and rpc
to the desired EVM chain in the appconfig.json file
. Currently it is configured to use the Aurora EVM chain..env
the AURORA_PRIVATE_KEY
to your private key (Not a mnemonic but the key that starts with 0x).env
file)"networks"
configuration.6
"networks"
configuration.Pair[]
Pair
. See above what kind of settings are required for those. Notice that settings like interval
are ignored, since they are part of the batch.