Operate
Mainnet readiness
Where Bashard stands relative to BNB Smart Chain mainnet, and what a launch involves.
BNB Smart Chain mainnet, chain id 56, is the target network. Nothing is deployed there.
Already in the code
- Mainnet rules: no faucet, ownership and supply moved to the treasury, nodes and indexer reading only finalized blocks, explorer links pointing at BscScan.
- Deployment tooling refuses mainnet without explicit owner and treasury addresses and an explicit epoch length. It validates addresses only; it does not enforce multisig wallets.
Deferred
All contract deployments, testnet included, are deferred until the original token exists. No token will be deployed by this project's tooling in the meantime.
Network-mode configuration
In network mode the host runs the web apps and indexer; nodes run elsewhere. Configuration is by environment, set by the operator in their hosting secrets, never committed:
| Variable | Purpose |
|---|---|
BASHARD_MODE=network | Serve web apps and indexer against BNB Smart Chain |
NETWORK | Named network the deployment file belongs to |
RPC_URL | JSON-RPC endpoint; a paid provider is recommended |
OWNER, TREASURY | Owner and treasury addresses supplied at deploy time (multisig recommended, not enforced) |
EPOCH_SECONDS | Epoch length, explicit on mainnet |
Launch order
- Original token exists; audit completed and findings addressed.
- Public testnet with outside operators and a bug bounty.
- Mainnet contract deployment with owner and treasury roles set (multisig recommended), verified on BscScan.
- Indexer and web apps switched to network mode with durable storage and backups.
- Independent operators register nodes; committee fills.