ProofLease is being integrated as the SLA settlement and marketplace layer for BOT Chain's vCompute — the Verifiable Computation Layer that onboards physical GPU and CPU hardware as DePIN nodes.
Every contract, oracle, and reputation mechanic in ProofLease is designed to plug directly into vCompute's attestation and proof-of-work infrastructure when it ships.
BOT Chain's Verifiable Computation Layer
vCompute is a core pillar of BOT Chain's roadmap. It onboards physical GPU and CPU hardware as DePIN (Decentralised Physical Infrastructure) nodes, issues cryptographic proof-of-work receipts for compute tasks, and provides trusted hardware attestation so that buyers can verify a machine really has the hardware it claims.
vCompute supplies the verification primitive. ProofLease supplies the marketplace and settlement primitive. Together they close the full loop: hardware operators earn BOT for verified compute delivery, and buyers get cryptographically-enforced SLA guarantees — not just trust-me uptime claims.
The settlement agent already calls an LLM to reason about compliance. Adding vCompute proof validation to the prompt is one targeted change — the architecture is already structured for it.
ProofRouter.submitProof() is designed to accept arbitrary proof data. It will receive vCompute execution receipts with no contract changes — just a new caller and a richer proof payload.
vCompute proof submission per epoch and AI settlement calls are economically viable on BOT Chain. On Ethereum mainnet the gas cost per epoch would exceed the payment itself.
ProofLease already runs on BOT Chain Mainnet. Hardware operators register machines as on-chain RWA assets, buyers escrow BOT, and the AI agent settles each epoch by reading heartbeat proofs from AssetRegistry. This is the foundation layer that vCompute will extend.
The current heartbeat mechanism confirms machine liveness but not actual workload delivery. When vCompute ships its cryptographic proof-of-work layer, ProofLease's ProofRouter contract is purpose-built to receive those proofs. The AI oracle will factor verified compute receipts — not just heartbeats — into each settlement decision.
Hardware class and region are currently self-reported by providers. vCompute's trusted hardware attestation layer (TPM or TEE-based remote attestation) will flow into the AssetRegistry hardwareHash field, letting the AI oracle verify that the machine actually has the advertised GPU class — not just that a provider claimed it.
BOT Chain's Compute Node Activation onboards physical GPU and CPU hardware as DePIN nodes. ProofLease becomes the public-facing marketplace for that infrastructure: node operators list capacity, buyers lease it with BOT token, and the AI oracle enforces the SLA end-to-end. ProofLease is the monetisation layer for vCompute's supply side.
AssetRegistryMachine registrationvCompute hook: vCompute attestation service writes hardware proofs into hardwareHash on registration
ProofRouterProof storagevCompute hook: Receives execution receipts from vCompute node layer alongside existing heartbeat proofs
LeaseEscrowPayment settlementvCompute hook: settleEpoch() reads from ProofRouter; vCompute proofs gate compliant vs. breach decision
ReputationProvider scoringvCompute hook: Score reflects full DePIN compliance history — liveness + compute delivery + attestation
The full contract suite and AI agent are deployed on BOT Chain Mainnet and have settled real epochs with verified on-chain transactions. The architecture is deliberately vCompute-shaped: ProofRouter accepts arbitrary proof data, the AI oracle prompt is structured to reason about proof validity, and the Reputation contract aggregates compliance history across the full lease lifecycle. When vCompute ships its attestation and proof-of-work layer, ProofLease plugs in with minimal changes — not a rewrite.