CoralReef| ★Price (USDT) | Amount (REEF) | Total |
|---|
| Price (USDT) | Qty (REEF) | Time |
|---|
Move internal liquid CORAL into the isolated trading ledger. CORAL has no chain deposit or withdrawal.
When admission is paused, new deposits and orders stay blocked; existing trading CORAL can still be returned after open orders are cancelled.
| Market | Side | Price | Qty | Filled | |
|---|---|---|---|---|---|
| connect to view | |||||
| Market | Side | Price | Qty | Filled | Status | Time |
|---|---|---|---|---|---|---|
| connect to view | ||||||
Perpetual contracts on REEF first, CORAL and more to follow — funding every 8h, cross and isolated margin, the same exact-decimal ledger underneath. The perps engine lands after deposits and withdrawals go live; the spot book you're trading today is the price source it will index against.
New projects launching on Reef raise here: fixed-price and auction sales settled by the venue's ledger, allocations weighted by CORAL holdings and lock-ups. Building on Reef and want to raise on the launchpad? Get in touch.
Keep CORAL's internal rewards clearly separate from native-chain staking. Compare Reef validators now; future validator changes will use a reviewed chain adapter and require a fresh wallet signature every time.
A trading market never enables staking by itself. Each network needs its own reviewed state reader, transaction builder, wallet method, finality checks, and explicit action gate.
Validator information can refresh in the background. Adding, removing, or replacing a native nomination target will always show the complete proposed list and require the user's wallet signature.
Fearless's browser extension uses the standard Substrate injected signer. It can sign in, link a Reef account, sign CORAL proofs, and approve server-prepared Reef payloads without exposing a private key.
Direct WalletConnect v2 support is mapped to Reef, but remains off until the same transaction payload passes real Fearless Android and iOS compatibility tests. Pairing alone will never count as login or transaction approval.
Chain identity loading...
Compare aggregate public signals before spreading your nominations. Individual staker addresses are not shown.
| Validator | Network status | Total stake | Nominators | Commission | Era points | Est. APY |
|---|
Exact finalized entitlements already imported for this account.
Exact imported rewards not yet moved to liquid; claims may be paused.
Internal CORAL available to stake.
Locked across active positions.
In the 28-day exit queue.
Your effective share after lock multipliers.
Only finalized entitlements imported into Coral Reef can become claimable. Estimates and uncalculated eras never enter this balance.
LP staking and boosted market-making rewards are planned, but no pool accepts CORAL today.
Future launchpad access may use CORAL weight. No allocation or reservation is active today.
Each position keeps its own term, multiplier, unlock and exit state.
Starting an exit stops the position’s active lock state. When the countdown completes, withdraw moves it back to liquid internal CORAL—not to a token wallet.
Estimates, uncalculated history and exact claimable entitlements remain visibly separate.
No server-produced estimate has been supplied. This does not mean zero.
No program boundary, proven first validator era or calculated-through era has been published.
Connect the account to read exact imported entitlements.
Estimated is a server-produced preview and is not spendable or claimable.
Not calculated means no result was published for that range; it never means zero.
Calculated, not imported is still not claimable until an exact entitlement is separately imported.
Claimable is an exact finalized entitlement imported into Coral Reef while claims are armed.
Connect an account to compare its verified Reef wallets with the published calculation.
| Era | Linked wallet | Memeparadox | Network | BP boost | Total |
|---|---|---|---|---|---|
| Connect an account to view its calculated era history. | |||||
Only rows below have crossed the separately audited import boundary. They remain distinct from the calculation above.
| Era / date | Reward source | Attribution | Amount | Status |
|---|---|---|---|---|
| Connect an account to view reward history. | ||||
See how finalized Reef staking history is allocated under the current formula.
This view changes only when a verified calculation is published. It has not been imported into account balances, is not claimable, and remains a shadow calculation.
Checking published coverage and updater status.
Rows are derived from public Reef staking exposure, but only masked account identifiers are published here. This table shows theoretical allocation, not a wallet or claimable balance.
| Rank | Staking account | Total CORAL | Memeparadox | Network | BP boost | Eligible eras |
|---|---|---|---|---|---|---|
| Open this tab to load the current public calculation. | ||||||
Formula and snapshot details load with the distribution.
One internal claim, explicit states, and no promise of a wallet token before launch.
Eligible activity is attributed as unclaimed CORAL by the rewards service.
Claiming moves the exact amount into your liquid internal CORAL balance.
Choose a server-published term. Longer locks increase reward weight; they do not create rewards without a separately funded epoch.
Begin unstaking, wait 28 days, then move the position back to liquid internal CORAL.
Multipliers below are loaded from the server and are display-only in this client. The server remains authoritative when a stake is created.
Each finalized era schedules at most 15,000 CORAL: 60% for Memeparadox-validator stakers, 15% for eligible wider-network stakers, 5% reserved for future signed BP-support voting, and 20% reserved for separately approved rewards such as staking or LP programs. Allocation uses exact integer units and deterministic largest-remainder rounding. Displayed amounts are not claimable until an audited import is approved.
CORAL on this page is an internal claim. A future contract launch requires a separate, explicit migration and claim process; this interface does not imply that process is live.