Protocol contracts
Bytecode hashes are computed from the current BNB Chain response.
Contract addresses, immutable dependencies, role boundaries, adapter status, and direct-contract recovery paths in one place.
Each NFT is permanently bound to its primary-screen stock. Catalog presence verifies identity and availability, not an executable route; rewards cannot be redirected to arbitrary tokens or BNB.
Swap code is integrated. Claims open only after the production deployment is verified.
Bytecode hashes are computed from the current BNB Chain response.
Guardian powers are pause-only. Timelock, Guardian, Treasury, and deployer have no selector that can withdraw Machine backing or holder reward reserve.
The adapter address for an ID is immutable once set. Timelock governance can disable an adapter but cannot silently replace it.
——No production security-audit artifact has been supplied. Mainnet launch and reward activation remain release-gated.
Call HardwireController.redeem(tokenId). Redemption remains available while risk actions are paused.
After 24 hours from the latest request, the payer may call retryVRF or cancel.
After fulfillment, anyone may call HardwireController.finalize(intentId).
RewardVault.claimToken(tokenIds, amountBNB, boundToken, minOut, deadline, adapterId, data) is the only reward payout path. If its route is paused, defer the claim; credit is not lost.