spin-operator reference
Environment Variables
Data Availability
We currently use AWS S3 as a DA placeholder solution. There's roadmap in the future to setup interface for DA, so that DA will be separate from operator-tasks.
Fill in the AWS credential with permission to write to S3 buckets.
AWS_ACCESS_KEY_ID
with S3 bucket write permission
AWS_SECRET_ACCESS_KEY
with S3 bucket write permission
AWS_REGION
with S3 bucket write permission
Blockchain Environments
Specify the blockchain node RPC URL and contract information.
Game contract address can be obtained when deploying the contracts Deploy spin-contracts
Generate an wallet and fill in OPERATOR_ADDRESS and OPERATOR_PRIVATE_KEY this will be your operator's wallets credentials, it will be mainly responsible for settling submissions.
The values in .env.template are working for locally deployed network through spin-contracts.
CHAIN_RPC_URL
The URL of the node RPC
OPERATOR_ADDRESS
The wallet address of the operator
OPERATOR_PRIVATE_KEY
The private key of the operator
GAME_CONTRACT_ADDRESS
The SpinOPZKGameContract contract address
GAME_STAKING_CONTRACT_ADDRESS
The StakingContract contract address
Operator Config Environments
ALLOW_INVALID_SUBMISSION
Checking player submission, 0 means do not allow
0
AUTO_STAKING_SUBMISSION_COUNT
Number of submissions to stakes at once when needed
100
PORT
The port of the express server
8001
HOST
The host of the express server
0.0.0.0
Last updated