CyberTemple

CyberTemple / Contracts

Primary-source registry

CyberTemple provably fair raffle contract addresses

These mainnet contracts are the primary evidence behind CyberTemple’s world-first documented combination: one NFT per wallet address on the Ethereum ownership trust layer, LayerZero owner verification and matching Monk IDs on the Base and Arbitrum execution layers. Verify the full address, bytecode, current roles, live settings and events on the relevant explorer before signing a transaction.

Configured production deployments

Network Role Address Chainlink VRF Subscription ID Deploy block
Ethereum
Chain ID 1		 ERC-721 Monk NFT and L1 owner-sync sender 0x10E4c5372c4ec298DfC62caF7d1c2826a7E0B6C3 Not applicable 25,360,127
Base
Chain ID 8453		 L2 donation rounds, VRF settlement and claims 0xeB1ed6A08f0b5B2D0F8c9Bf59a709724Afb722E6 23727093601249171064293419895154375795114731829270869307648413283655113293111 47,596,911
Arbitrum One
Chain ID 42161		 L2 donation rounds, VRF settlement and claims 0xf27D50AeFa26c43A98Fa9bceAEDDD8DE4A30836e 76581714941238331768160035708390348930510642838267292453887356462367935787401 475,564,352

Do not verify an address by its first and last characters alone. Compare all 42 characters and confirm the wallet is on the intended chain. Testnet addresses are intentionally not presented as production deployments on this page.

Contract verification checklist

  1. Confirm the chain. Ethereum, Base and Arbitrum use different chain IDs and independent state even when an interface looks identical.
  2. Inspect the contract. Review the explorer’s contract, code and read tabs. Do not infer source verification or proxy status from this website alone.
  3. Read current controls. On an L2 donation contract, check multisigAddress, active signers, devAddress, VRF settings, LayerZero peer settings, donation unit, payout basis points and claim windows.
  4. Verify NFT utility rules. On Ethereum, inspect the ERC-721 _update override that limits an address to one CyberTemple NFT at a time and the holder-only writeSlogan function. Ethereum is the ownership trust layer; LayerZero currently mirrors owner state to the Base and Arbitrum execution layers. On either L2, inspect ownerClaimWindow, nftOwnerBp, nftOwnerFallback and the ownership mirror used for settlement.
  5. Read the round snapshot. Live global defaults may differ from values already snapshotted for an active or completed round.
  6. Separate policy from enforcement. The configured developer address can withdraw its allocation. Any return of operating surplus uses a voluntary topUpCarryOver transaction, so verify actual top-up events rather than assuming a schedule.
  7. Review the event sequence. The Safe cannot choose or modify a VRF random word, but any pending-request recovery is public. Include requests, retries, clears, fulfillments and aborts when verifying the round lifecycle.

Why role addresses matter

The Ethereum NFT owner and each donation contract’s configured Safe are separate administrators. The frontend cannot turn these roles into a single owner, and a block explorer link does not by itself show whether a Safe’s owners or threshold have changed. Read the full governance and cross-chain trust model.

As checked onchain on July 30, 2026, both production donation contracts return 0x686EA1196a7c809F73A7a9Df0DEDeF13C252a527 from multisigAddress(). Verify the current value directly from each donation contract before relying on this registry.

Base Safe dashboard Base Safe onchain Arbitrum Safe dashboard Arbitrum Safe onchain Understand round mechanics Review risks and permissions Read the FAQ Open the dApp