RedStone CLI

RedStone CLI is a tool that helps to deploy all necessary contracts for the RedStone Push Model and run the relayer responsible for pushing prices on-chain

Instruction

1. Install RedStone CLI in the separate folder (there will be a few files autogenerated)

npm i @redstone-finance/cli

2. Run initialization script which will prepare files for CLI and run it afterwards

npx redstone-cli init

3. Contracts deploying can be done right after initialization or later by running the command below to start CLI

npx redstone-cli

4. Deploy all necessary RedStone contracts responsible for updating prices on-chain and interfaces for reading prices by selecting Deploy contracts option in the CLI menu. Then pass proper values for parameters which will be displayed

| Param | Description | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | Network name | Network name on which contract will be deployed, also basic name for all files autogenerated (needs to be used the same through whole process) | | Network RPC URL | RPC URL used to deploy contract | | Proxy Admin Owner | Wallet Address that will be used to run contract upgrade (contracts are deployed behind a proxy to make them upgradable) | | Private key | Wallet private key used for deployment |

5. When all contracts are deployed start the relayer by running CLI using the command below and select the Run relayer option in the CLI menu. Then pass proper values for parameters which will be displayed. Relayer will run straight away in the same process as CLI. Currently default update conditions are deviation - 0.5%, heartbeat - 6h, adjusting them will come in the next release

npx redstone-cli

| Param | Optionality | Default value | Description | | -------------------------------------------------- | :---------: | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Network name | required | | Network name on which contract will be deployed, also basic name for all files autogenerated (needs to be used the same through whole process) | | Network RPC URL | required | | RPC URLs used to send update transactions, can be multiple to increase robustness, comma-separated e.g. https://rpc-url-1.com,https://rpc-url-2.com | | Relayer iteration interval | optional | 5000 | Time interval in which the relayer tries to update prices if update conditions are met | | Expected transaction delivery time in milliseconds | optional | 5000 | Time in which it is expected that valid transaction can be mined, typically 2x avg block time | | Are fees two dimensional | optional | yes | Yes if network has two dimensional fees (like Arbitrum or ZKSync based networks), more info here | | Gas limit for update transaction | optional | 750000 | Gas limit used for update transaction | | Private key | required | | Wallet private key used for updating prices on-chain |