LIVE DATAPool and position records follow chain finalityWallet confirmation required for transactions
PROTOCOL REFERENCE

Contracts & Permissions

Follow the contracts, understand the authority
Every role has a defined boundary

Robinhood Chain · Chain ID 4663

RebloomVault

Non-upgradeable deployment · Fixed administrator

Runtime matches build
0x07337e08521b2c6b281e8262cb12c055cdedb21c
Deposits at checkOpen
Project at checkOpen
Administrator typeEOA
Independent auditNot completed
Verified snapshot · Block 61093157 · Sep 12, 2026, 8:20 AM EDTPoint-in-time evidence, not a live status feed

Authority is explicit

These two addresses are immutable in this deployment

Administrator

0x6dF1c936Ada41eb7F1539Cf7f43B9635eEa48023

A single externally owned account, not a multisig

Platform fee recipient

0x6dF1c936Ada41eb7F1539Cf7f43B9635eEa48023

Receives platform fees and recovered surplus assets

Who can do what

Contract permissions apply independently of the website

AuthorityOperationEnforced boundary
AnyoneDeposit admitted assetsdepositRequires one admitted old token and one configured Stock Token, open deposits, token approvals and valid price bounds
ContributorWithdraw unlocked principalwithdrawOnly the recorded contributor can withdraw their position, subject to minimum output amounts and a deadline
AdministratorAdmit or remove old tokenssetOldTokenAdmission pins the current runtime code hash; removal blocks new deposits, not existing withdrawals
AdministratorPause new depositssetDepositsPausedImmediate effect with no timelock; withdrawals and claims remain callable
AdministratorClose the projectcloseProjectIrreversible stop to new deposits; does not unlock permanent positions or disable eligible withdrawals
AdministratorPublish reward allocationspublishEpochChooses the Merkle root and allocation within available community fees; claims open after 48 hours
AdministratorCancel a pending allocationcancelEpochOnly before the 48-hour opening time; reserved funds return to the community fee balance
AdministratorRecover surplus assetsrecoverSurplusToken / recoverNativeUnreserved ERC-20 balances and native ETH go only to the fixed platform recipient; this does not withdraw LP principal
AnyoneCollect position feescollectCredits collected fees to community and platform balances; caller does not receive the fees
AnyonePay accrued platform feespayPlatformPays only the fixed platform recipient, regardless of who submits the transaction
AnyoneSubmit a valid reward claimclaimRequires a valid proof after the delay; funds go to the recipient encoded in the proof, not necessarily the caller
The reward publisher is a trust assumption

The administrator determines reward recipients and amounts through the Merkle root; the contract verifies proofs and budgets, not holder eligibility or fairness The 48-hour delay applies to reward claims, not every admin action

Where the assets go

Liquidity custody and collected fees follow separate paths

Funding wallet

Two ERC-20 assets

The contributor approves and signs the deposit

Uniswap V4

Liquidity position

The pool holds liquidity; the vault owns the position NFT

RebloomVault

Contributor record

The contract records ownership and the permanent lock choice

Principal withdrawal

Only the original contributor can withdraw an unlocked position No administrator unlock or LP transfer function is exposed

Collected fees

90% is allocated to the community and 10% to the platform, with rounding dust retained by the community Collected fees remain in their original tokens

Direct transfers

Sending ETH or tokens directly does not create a position Unreserved assets can be recovered to the platform recipient, not automatically returned to the sender

Inspect the evidence

Public source, deployment transaction and protocol dependencies

Read Solidity source

Deployment transaction

0x6de73f0b20b03af9797aac8467dda0a1b4443e31c3acfac74838022a924b104a

Deployment block 61077243

Build correspondence

Runtime compared with the local compiler artifact, masking immutable slots; deployed addresses are read separately

Explorer source verification: Not confirmed

Bytecode and source fingerprints

Runtime keccak256

0x769e5502c044839f0db9bf966c40789e5ae5bc856e074be874c17977f30bc5c0

Source keccak256

0xf339c3ffc5592ca554aa8a8af90cf7c8da49a20c07bedd658d37f68d67a6bf87

11,331 runtime bytes · Compiler 0.8.37+commit.f401782d.Emscripten.clang

Download evidence JSON ↗
What this page establishes

Publicly inspectable deployment and explicit permissions Code matching is not an independent security audit, a guarantee against loss, or a review of every supported token Reward calculation and claim interfaces are not yet connected

View your positions