Inspectable
by design.

Identity & eligibility

Identity is chain ID + registry address + Agent ID token number. A .ai name is display information only. Registry ownership is required. Its real owner can explicitly authorize one additional wallet in PROOF, and can revoke or replace that delegate. This does not change the official Agent ID. A registry-specific agent-wallet method is used only if separately verified and enabled.

Login uses an expiring EIP-712 signature tied to the site origin, chain, wallet and one-time nonce. Private keys never go to the platform. The current native balance development threshold is 0.001 BNB, read at a confirmed block inside the challenge window and rechecked before authorization. It is not a continuous-balance lock.

Tasks, vouchers & rarity

First-version tasks are bounded SHA-256 chains with random per-attempt inputs. There is no mint-failure fine. The 10-minute limit, two authorizations and four starts per rolling 24 hours are development defaults. The service verifies the answer and current eligibility before signing.

Vouchers expire after 24 hours and allow one mint. Rebinding is limited to one transaction, to a wallet currently authorized for the same ID. Project delegation can be set only by the actual ID owner, not by dev, Guardian or the delegated wallet. A delegation is valid only while its authorizing owner matches the registry owner. If a registry permits transfers away and back, an unrevoked delegation can become valid again; the current Agent ID registry documents soulbound ownership. Old signer versions retain their issuance window after rotation; explicit revocation can invalidate outstanding vouchers.

Rule versions and rarity thresholds are immutable once registered. Mint rule 1 is registered on BNB Smart Chain: one Pass per voucher, a 24-hour lifetime and rarity weights 1 / 2 / 4 / 8. Duration and task-type hashes influence the deterministic rarity seed; this is not a fair randomness claim. Minting pauses independently from NFT transfers.

Funding & hourly settlement

The target holder reserve is 25% of final $PROOF supply. Distribution starts only after the required tokens have really entered the vault. Flap tax allocation settings do not create a free 25% supply reserve; acquisition and funding must be verified separately.

Development release schedule: 180 days / 4,320 hourly epochs. Rarity weights are 1 / 2 / 4 / 8. Holding factor rises linearly from 1× to 3× over 30 days and caps. Every parameter must be locked against the deployment manifest before launch.

Buy and sell tax are each 2%. All tax actually received by the project after Flap protocol fees is allocated to NFT holders, with no separate project commission. No same-tax buyback or challenge-prize allocation is promised. Tax is credited in the asset actually received.

The UTC-hour calculation integrates actual ownership time. An hour with no eligible score carries its budget forward; an indexing or RPC failure remains an error and cannot be treated as an empty hour. Integer rounding remainder is carried. Merkle roots are published by an administrator; a root verifies membership, not the correctness of an off-chain score calculation.

Claims stay with the original earning wallet after an NFT transfer. Relayers can pay gas but cannot choose a different recipient. Claimed assets are outside the vault and outside its rescue function.

Administrator & rescue authority

All unclaimed rewards are revocable. Dev and the Flap Guardian have direct administrative powers. They can pause claims, publish reward roots, change supported configuration, upgrade contract behavior, and withdraw the full balances of unclaimed assets to the configured dev address.

This includes the unvested 25% reserve, unsettled tax and amounts already settled into published hourly claims. Rescue closes the entire reward generation before funds move. Its unclaimed records become invalid; later revenue or reopening cannot revive them. This is withdrawal with revocation, not a migration that preserves claims.

Only dev or Guardian can call rescue, and its recipient is the configured dev. Dev changes follow a two-step acceptance process. Guardian rights remain available under the Flap contract. Unlimited upgrade powers mean function-level checks must not be presented as protections administrators can never change.

No wallet can sign for another user or take assets already claimed into a user wallet through these contracts. NFT transfer/approval and user wallet signatures remain separate permissions.

Deployment state

Network target

BNB Smart Chain · 56

Proof Pass

0x344BFeecefaDA80d8B63C9D93b854a4cB878ec43

NFT implementation

0xCE37A2337093097ceBf508F10d84BE18E0969b33

NFT authorization signer

0x881c0496F0E5775E45B7d6c51e472e5e44EAB416

Vault implementation

0x5DfddA6da5A34a6c8370C43A3B4B427105B0A523

Vault factory

0x3078c820161591E9a709679822167A17D47E9AB2

Reward vault

—

PROOF token

—

Dev

0x73bf133C3f6E8FEd577e032988a73C90cb758cD3

Guardian

0x9e27098dcD8844bcc6287a557E0b4D09C86B8a4b

A dash means no verified address has been supplied for that field. Live balances and rewards appear only after their source is available. A website or source repository is not an independent contract audit.