Grafana and the explorer are read-only. This console is where the operator changes chain parameters,
collects the gas revenue, and switches validity proving on/off. Every action is enforced on-chain by
role — only the admin wallet can execute.
How the fee works. EIP-1559: each block has a base fee in MIDS that rises when blocks
fill and falls when they empty. You shape it with the gas limit — raise it → cheaper txs under load;
lower it → pricier txs, stronger spam resistance. Typical 60,000,000. Lives in the L1
SystemConfig, so this is a Sepolia transaction.
⚠ Runs on Sepolia (11155111) · admin only
💸 Withdrawal & trading fees
Estate-level fees on the compliant vault & settlement.
Current withdraw feeloading…
Flat fee on withdrawal, in USD, capped on-chain at 1% of the amount. Recipient:
…. This is a Midas Chain transaction.
⚠ Runs on Midas Chain (64327) · admin only
Maker / takerloading…bps · cap 200
Trading fees in basis points (1 bp = 0.01%). Maker provides liquidity, taker fills it.
⚠ Runs on Midas Chain (64327) · admin only
🏦 Gas revenue — fee vaults
Where every transaction fee is collected, on the L2. Sweep it once a vault clears its 10 MIDS minimum.
⚠ Recipient is a lost key. All three vaults currently sweep to
0x69DB…8e4f — the original admin key lost in the MIDS re-genesis, so withdrawn fees would
be unrecoverable. Harmless on testnet (fake MIDS); on mainnet the recipient must be set to your
treasury/multisig at genesis (it’s a genesis constant — already in the mainnet checklist).
🔐 Validity proving (OP-Succinct)
ZK finality — worth turning on only when gas revenue covers the PROVE cost.
Optimisticvalidity proving OFF · no PROVE spend
⚠ Toggle writes the on-chain switch on Midas Chain (64327) · admin only
The break-even. A proof’s cost is ~fixed no matter how many txs it covers, so it only pays
once fees from real volume exceed it. Tune the assumptions below to your numbers:
Break-even volume—txs / day needed
…
Turning validity proving ON starts real $PROVE spend and changes finality. I recommend
keeping the flip human-confirmed (this toggle) rather than fully automatic — a volume spike or an attack
shouldn’t be able to start burning PROVE on its own. The supervisor reads this on-chain switch and never spends
while it’s OFF.
🗂 Contract registry
Deployed contracts this console uses. Admin (testnet): … — on mainnet these roles move to a multisig.
Midas Chain testnet · operator console — actions are role-gated on-chain.
Read-only status loads without a wallet; changing anything requires the admin wallet on the noted network.