RandProof20. Multi-Chain Architecture
All EVM chains share a single Solidity implementation. Fee settlement uses native assets or USDC via CCTP V2.
20.1 EVM-Compatible Chains
All EVM chains share a single Solidity implementation. Fee settlement uses native assets or USDC via CCTP V2.
20.2 Non-EVM Chain Implementations
| Chain | Contract Language | Keeper Runtime | Stake Asset | Fee Asset | Entropy Source |
| Solana | Rust / Anchor | Rust binary | SOL | SOL / SPL USDC | DRAND + NIST + slot VDF |
| TON | Tact | Node.js + TON SDK | TON | TON / jUSDT | DRAND + NIST + masterchain hash |
| Cardano | Plutus V3 | Haskell runtime | ADA | ADA | DRAND + NIST + Ouroboros Praos VRF |
| Sui | Move | Move module | SUI | SUI | DRAND + NIST + sui::random |
| Polkadot | ink! / pallet_revive | Substrate runtime | DOT | DOT / USDC via Asset Hub | DRAND + NIST + BABE VRF |
20.3 Cross-Chain Fee Settlement
-
Native settlement: Fees stay in chain's native asset
-
USDC settlement: Native USDC via CCTP V2 where available. On chains without native CCTP V2 USDC, RandProof settles in the chain's native asset rather than bridged USDC (AV-49 policy, see Section 32.10.1 for the per-chain table)
-
Protocol treasury: 20% accumulates in chain-native assets or native USDC, depending on chain. Funds bridge to Base only where the chain has native (non-bridged) USDC support; on chains without it, treasury holds the native asset on-chain rather than bridging (AV-49 policy)
20.4 BIT5050: The Genesis Client - BIT5050 deployments on 17+ chains: Ethereum, Base, OP, ARB, Linea, Polygon, World Chain, Solana, Sui, HyperEVM, TON, Cardano, BNB, Avalanche, Moonbeam, Polkadot, Bittensor.
19. KeeperCoordinator.sol: The On-Chain Core
KeeperCoordinator.sol is implemented and tested as an MVP, deliberately scoped narrower than the full design described in the rest of this section, wi
21. Node Operator Economics
RandProof employs a low-stake, high-decentralization model. Unlike traditional Proof-of-Stake systems where staking secures consensus, RandProof’s sec