SVRN & its Long market
The verified SVRN contract and AI pair, fee beneficiary, token compatibility and remaining service activation.
In this chapter
One canonical token
Serevin (SVRN) launched on Robinhood Chain, chain ID 4663, on 8 September 2026 at 9:11 PM Eastern Time. Its canonical contract is 0x93CEF53FbC2A9244de0bEd8964331f7e1dc21E18. Direct chain reads confirmed 18 decimals and an initial supply of 1,000,000,000 tokens.
The initial market is SVRN/AI. AI is Artificial Inu at 0x2E8c31162b855A2ffa90F6F8634643Ad6F111e18. The creation receipt confirms the Uniswap v4 pool; the source links below identify the exact token and transaction.
An additional SVRN/ETH market would use the same canonical SVRN token and requires separate liquidity. AI’s price can affect SVRN’s quoted market value. This pairing provides no ownership of or redemption right against AI’s NVDA holdings.
Separate a token’s market from its rights
The local design explores reserve redemption and collateral-backed credit. The wider roadmap includes service benefits and protocol participation. Those remain subject to actual implementation and finalized rights.
Launching a tradable token creates a market. It does not by itself deploy a lending protocol, provide liquidity to USDG loan markets, create a reserve claim or grant a share of protocol earnings.
The workspace features the SVRN/AI spot market and reads current supply and pool reference price at one verified Robinhood block. Wallet balances include both canonical tokens. Quote comparisons can request AI/SVRN through Route; availability depends on the provider. The direct Uniswap comparison checks v3 pools and does not represent this v4 pool.
The pool reference is denominated in AI per SVRN. It is not a dollar valuation or an executable quote and excludes price impact and dynamic hook fees. Stale or failed reads are identified. A shared pool-manager balance is not reported as this pool’s liquidity or Serevin’s reserve backing.
In-app swaps for this hook-based v4 market are not enabled. The Long trade link opens Long and uses its own transaction flow. Execution checks and all-in fee presentation must be verified before Serevin can offer native swaps for this exact pool.
What staking currently does
The implemented staking vault is single-token custody. A user stakes tokens and can unstake their recorded quantity under normal operation. It has no reward engine, fee discount, revenue distribution, voting power or slashing. The separate ServiceMembership module implements timed commitments and finite noncash service credits.
Staking alone creates no yield. Any later rewards require an explicit funding source and approved distribution rules. The same admin-recovery policy applies to staked assets.
A separate FundedRewardsCampaign contract draft adds explicitly funded, time-weighted rewards. It does not change the older custody vault and is not deployed on mainnet. The staking and farming workspace explores proposed programs and prepares local campaign drafts; deposits and reward claims are not enabled there.
What the compatibility check established
SVRN’s minimal proxy points to the DopplerERC20V1 implementation published for Robinhood Chain. The observed token has no vesting allocation and no active maximum-balance restriction. Its owner is the Doppler Airlock. Serevin’s two administrators do not gain control of this external token through their Serevin roles.
The token supports burn(amount). Serevin must use its transfer-then-burn reserve mode. A local test copied the observed token bytecode, recreated the relevant launch flags and used synthetic accounts and USDG funding. Staking deposits and withdrawals, reserve redemption, exact supply reduction and exact reserve payouts passed. The burnFrom mode rejected the unsupported call.
This local test is not an external audit or an activated mainnet reserve. It did not execute a Long swap or claim fees. Production contracts, backing assets and service terms still require their own activation checks.
Fees and the next activation steps
The observed pool fee registry gives treasury 0xd427E05687Cd5A84bd4d4A450906eC221c0C936F 95% of its fee shares. The remaining beneficiary has 5%. These are shares of collected pool fees, not percentages of trade volume or a return promised to token holders. The pool uses a dynamic fee hook, so a stored fee value is not a guaranteed execution fee.
The launch allocated its supply to the pool mechanism; it did not create a team vesting allocation or provide USDG lending capital. Fee rights, trading liquidity, reserve backing and operating budgets must each be accounted for separately.
- Complete exact-pool quote and execution checks, including the dynamic hook and trading fees.
- Set membership terms using the service cost and observed token liquidity; no production quantity is implied by the initial supply.
- Fund lending, reserve and operating accounts separately under approved budgets.
- Activate initialized financial contracts with the recorded token and approved two-admin controls.
- Add other pairs only after assessing depth and operational needs. Extra pools can fragment available liquidity.