- Job 1: Ensure Relayers have Sufficient Crypto
- Steps
- Job 2: Check the LINK balance of the various VRF subscriptions
- Links
- Schedule
- Historic
Job 1: Ensure Relayers have Sufficient Crypto
We use OpenZeppelin Defender to automate transactions. In particular, the awarding of prize pools and pod batching.
Defender has two concepts: Autotasks and Relayers. Relayers are essentially EOA wallets that are stored securely in AWS. Autotasks are essentially lambdas that run periodically. The Autotasks use the Relayer API to trigger transactions.
The Relayer wallet addresses need to be stocked with crypto in order to run transactions.
Polygon Bridge: You can bridge MATIC over with Polygon: https://wallet.matic.network/
Binance Bridge: You can bridge BNB with the bridge: https://www.binance.org/en/bridge
| Network | Currency | Address |
|---|---|---|
Ethereum | ETH | |
Polygon | MATIC | |
Binance | BNB | |
Celo | CELO |
Steps
- Click the above addresses. For each one, ensure it has enough native crypto to function.
- Ethereum relayers should have at least 1 ETH
- Polygon relayers should have at least 1 MATIC
- Binance relayers should have at least 0.5 BNB
Job 2: Check the LINK balance of the various VRF subscriptions
Mainnet subscriptions:
Testnet subscriptions:
Subscriptions should be stocked with a minimum of 20 LINK tokens at all times to avoid our requests being sent in a pending state.
More info here: https://docs.chain.link/docs/chainlink-vrf/#subscription-limits
The contracts that use Chainlink VRF 2 are listed below:
| Name | Network | Address |
|---|---|---|
DrawBeacon | Ethereum |
| Name | Network | Address |
|---|---|---|
DrawBeacon | Ethereum Goerli |
Links
Schedule
- Brendan
- Pierrick
- Ryan
- Tuna
