Deploying to Mercury Retroshades

Compiling with the Mercury flag

Before delpoying to the Retroshades network, you need to build the binary that holds retroshades logic:

cargo build --release --target wasm32-unknown-unknown --features mercury

Deploying

mercury-cli --jwt $MERCURY_JWT --mainnet TRUE_OR_FALSE retroshade --project "project-name" --contracts "CONTRACT TO TRACK1" --contracts "CONTRACT TO TRACK2" --target BINARY

Your jwt token will be provided for the moment by the Mercury team.

One thing to keep in mind, is that the retroshade smart contract will be executed in real time when --contracts are executed too. You can target one or more smart contract for a single retroshade contract.

Catchups

To perform the events data backfill and populate tables with past data just run a regular catchup with the --retroshades true flag:

mercury-cli --jwt $MERCURY_JWT --local false --mainnet true/false catchup --retroshades true --contracts "YOUR_CONTRACT" --project-name "YOUR_PROJECT_NAME"