How protocol actions are protected
ARBOR is bought through its verified ODYS market route. Staking writes target Arbitrum One, validates exact addresses, simulates before submission, prevents duplicates, and never reports success when support contracts are absent. Newly received stake receipts mature through an immutable onchain cooldown before they can be redeemed or transferred.
ARBOR is acquired from the verified locked-liquidity pool. This terminal never mints a second ARBOR.
Your staked-ARBOR position grows only after real ARBOR inventory is funded and distributed. No fixed APR is invented.
USDC or reviewed current-generation wrapped xStocks can be claimed from immutable allocations after eligibility review.
Verified xStocks metadata appears here when the provider is available.
Display metadata only—not a reserve holding, reward promise, eligibility approval, or executable quote.
DexScreener data is indicative and may be delayed. This chart is not an executable quote, protocol NAV, reserve proof, or promise of liquidity.
Connected protocol position
MODULE STATUS · CHECKINGTechnical receipt shares: —
Connect an EVM wallet to view the protocol position.
Epochs appear only after the complete reward inventory and proofs are published.
A listed allocation is an ARBOR protocol distribution, not a guaranteed return or issuer stock dividend. Always verify token, root, funded amount, snapshot block, and deadline.
This calculator assumes the displayed wallet and total vault shares remain unchanged until distribution. The actual result changes with deposits, withdrawals, rounding, and the amount genuinely funded onchain.
+0.00% measured from this server session open
equal-weighted session normalization
| # | ASSET | PRICE | CHANGE | SESSION | ARBITRUM CONTRACT | PROVIDER | FRESHNESS |
|---|---|---|---|---|---|---|---|
| Market data will appear when a verified source is available. | |||||||
Reserve composition
| SLEEVE | VALUE | WEIGHT | SOURCE |
|---|---|---|---|
| No verified reserve composition is configured. | |||
- No indexed protocol activity yet.
ARBOR programs
ODYS Market
Buy and sell the canonical fixed-supply ARBOR through its verified ODYS/Uniswap market route.
PRELAUNCH · PROJECT URL REQUIREDARBOR Staking
Stake ARBOR for verifiable, fully funded protocol distributions. Receipt shares remain a technical accounting detail and new deposits use a 24-hour cooldown.
SUPPORT CONTRACT REQUIREDStock Token Rewards
Claim funded USDC or reviewed wrapped xStocks from immutable Merkle epochs. Raw rebasing assets are not accepted by policy.
DISTRIBUTOR + PROOF SERVICE REQUIREDRWA Sleeve
A separate Safe can custody eligible xStocks. The sleeve is disclosed independently and is not guaranteed redemption backing.
SAFE + ELIGIBILITY REVIEW REQUIREDARBOR Seasons
Non-wagering campaigns can award points for verified staking longevity, learning quests, and transparency participation.
PROPOSED · NO CASH WAGERINGTransparency Desk
Publish contract reads, treasury custody, reward funding, market provenance, and every unresolved production blocker.
DISCLOSURE · ACTIVEARBOR tokenLaunch address pending
Market routeProject and pair pending
Treasury SafeMultisig pending
ARBOR stakingDeployment pending
Funded rewardsDeployment pending
RPC redundancySecond provider pending
Event ledgerCheckpoint pending
Audit & legalIndependent completion required; never auto-approved
Reserve and risk report
| CONTROL | STATUS | PRODUCTION REQUIREMENT |
|---|---|---|
| Canonical token boundary | IMPLEMENTED | ARBOR launched through ODYS is canonical; support contracts cannot mint a replacement. |
| Funded reward epochs | IMPLEMENTED | Use wrapped, eligibility-reviewed assets and publish allocation proofs. |
| Independent audit | REQUIRED | Audit every contract and exact deployment parameter. |
| Legal and eligibility review | REQUIRED | Determine licensing, KYC, jurisdictions, and tokenized-stock eligibility. |
| Market-data licensing | VERIFY | Confirm production display, caching, and redistribution rights. |
| Solidity product naming | ARBOR | ARBOR/sARBOR metadata and deployment identifiers are canonical; audit exact bytecode before testnet rehearsal. |
The reserve should be legible.
A financial interface should never make users guess which numbers are onchain, externally sourced, stale, or illustrative.
- Every dashboard number identifies its source.
- Tokenized-stock exposure remains an explicit, bounded sleeve.
- Redemption, transferability, and legal eligibility are disclosed separately.
- Production requires audit, legal review, monitored governance, and incident procedures.