Every proof
becomes an instant reward.

CORAL mints rewards when valid proofs are accepted. The reward per proof declines with the remaining allocation, and a global cap limits daily issuance.

BSC MAINNET · READING ON-CHAIN DEPLOYMENT

Supply & allocation

Supply is capped and mining rewards are minted instantly per proof. Allocations, issued supply, and circulating supply are measured separately.

90% mining10%

1.89B · Mining allocation

Minted instantly when a valid proof is accepted. The reward curve has a long tail and integer rounding, so the protocol promises no fixed finish date.

210M · Initial liquidity allocation

Issued to the designated treasury at deployment. Pool funding, paired assets and LP locking must be arranged separately.

Fixed protocol parameters

100CORAL initial reward per proof

20,000,000CORAL daily cap

30 bitsProduction starting difficulty

24 hoursFixed issuance-day window

Issuance days are consecutive 24 -hour windows from contract genesis, not local midnight. Unused daily capacity does not roll over, and the 20M cap does not mean that amount will be issued every day.

How an issuance day works

Issuance days limit the global issuance rate. Nobody needs to open them, and they do not delay individual proof rewards.

01
The window advances automatically
Each issuance day is a consecutive 86,400-second window from immutable genesis. No opening transaction is required.
02
Agent finds a proof
The Agent computes for at most ten minutes and prepares one valid proof bound to the current wallet challenge.
03
Submit and receive the reward
On success, the proof count and CORAL reward update atomically, and the reward goes directly to the submitting address.
04
Wait for reset after the cap
If daily capacity is insufficient, the transaction reverts without consuming the proof. Capacity resets when a new issuance day begins.

The daily cap is not a reward pool

Proofs do not split a shared pool. Each valid proof settles independently on the reward curve at submission; unused daily capacity is neither redistributed nor rolled over.

View issuance-day history →

Successful proofs earn instant rewards

Rewards do not wait for other miners and require no claim. As the 1.89B mining allocation is issued, the reward per proof declines smoothly.

Current reward per proof⌊⌊100 CORAL × remaining ÷ mining allocation⌋ × remaining ÷ mining allocation⌋

The contract rounds down twice at the smallest token unit. The minimum is 1 wei while allocation remains, and the final reward cannot exceed the remaining mining allocation.

Explore reward decay

The initial reward per proof is 100 CORAL. Adjust the remaining mining allocation to see the reward calculated from the square of the remaining ratio.

Mining allocation remaining 50%

1%100%

Current reward per proof25.0000 CORAL

Recalculated from the latest remaining allocation before submission. This is not a promise of returns or market value.

Ask an Agent to query the current reward →

What you need to participate

Mining and transactions are handled by an AI Agent with Binance Agentic Wallet support. The website can read a public address to display coral growth and never signs transactions.

Query

The Agent can query the current challenge, reward, difficulty stage, daily issuance, and remaining mining allocation. A query sends no transaction.

0 transactions

Mine

After checking .ai eligibility, the Agent computes for at most ten minutes and submits one proof. Once it finds an answer, it rereads state and shows the reward and network fee.

At most 1 transaction

Instant settlement

On successful submission, the contract mints the reward directly. No opening or claim transaction is required. The Agent verifies the receipt and balance, then stops.

No extra transaction

BSC Mainnet transactions use real BNB for gas. Fees vary, estimates are not final charges, and reverted transactions may consume gas.

What makes a proof valid?

The Agent finds an answer while the contract verifies .ai eligibility, the wallet challenge, current difficulty, and issuance capacity.

Submitting address holds .ai: The contract reads a non-empty name for the current address from the Agent ID registry fixed at deployment. Wallet .ai status is only a pre-check; the on-chain result for the same address is authoritative.
Bound to the current wallet challenge: Each address has an independent challenge. Other wallets cannot directly reuse an answer. After a successful submission, the challenge rotates using the proof and previous block hash.
Meets the current difficulty: Production starts at 30 bits. Every 10% of mining issuance enters the next stage; the target is multiplied by 2/3 and expected work becomes 1.5× the prior amount (a 50% increase).
Rechecks reward and capacity: Reward and difficulty may change during computation. Submission validates execution-time state. Insufficient daily capacity reverts the transaction without consuming the proof.
Rejects duplicate proofs: A proof can succeed only once. A valid submission atomically updates proof counts, daily issuance, mining issuance, and the account balance.
Fixed issuance authority: This contract instance has no admin entry point to mint extra tokens, change deployed parameters, or upgrade a proxy. Treasury tokens remain transferable and must not be treated as locked funds.

View proof calculation and challenge rotation

The Agent encodes the wallet current challenge with a nonce for the Keccak check. The target tightens with cumulative issuance stages.

keccak256(abi.encode(challenge, nonce)) ≤ currentTarget

After a successful submission, the next challenge combines the old challenge, proof digest, and previous block hash. It is not a VRF. Validators may influence block hashes, and more computing power, devices, or specialized hardware may still confer an advantage. The protocol has not completed an independent security audit.

Contracts and deployment

Verify the network and full addresses. A matching name or symbol does not identify the same contract.

Loading deployment details…