GRAVFI · The liquidity gravity layer for Robinhood Chain.
CAPITALHASGRAVITY.
Pull assets into Robinhood Chain.
Verify the backing.
Put capital to work.
Live finance factsRobinhood Chain · connectingBridge · native · trusted relayerSwap · router configuredData · no simulated numbers
Network
Robinhood Chain
chain id 4663 · connecting
Block
Source
Ethereum
connecting
Assets
1 / 5
active in registry
Reserves
none flagged
Token
$GRAV
The contract address is published here and on @GravFinanceRH only. Until it appears in both places there is no official $GRAV.
Price, liquidity, volume and holders are read from GeckoTerminal and Blockscout; supply and launchpad-curve reserves are read on-chain. A source that does not answer shows a dash. Nothing is estimated.
G
$GRAV token · Robinhood Chain
GravFi Token
Price
reading GeckoTerminal
- Symbol
- —
- Decimals
- —
- Total supply
- —
Supply is read from the contract; market values from GeckoTerminal, Blockscout and DexScreener every minute. Only this address is official.
03Gravity flow
Liquidity has a destination.
Capital enters on Ethereum, is locked, verified, and lands on Robinhood Chain as a GravFi representation. The diagram is a walkthrough of the mechanism, not a live transaction.
- 1EthereumSource asset leaves the user's wallet.
- 2GravFi VaultCollateral locked in a single-asset vault.
- 3VerificationThe messenger delivers the lock proof; the bridge checks eid, nonce and route.
- 4Robinhood ChainThe gToken is minted to the recipient, 1:1 with the vault.
- 5DeFi LiquidityThe representation trades, pools, and routes on Robinhood Chain.
Worked exampleIllustration · not a transaction
01
1,000 USDC
02
Vault locked
03
gUSDC minted
04
Available on Robinhood Chain
Real wraps happen in the application, produce on-chain events, and are tracked by contract state — see /app/bridge.
04Proof of Gravity
Every unit should have a home.
Each gToken is compared against the collateral its vault actually holds, read from both chains at a pinned block. When contracts are not deployed, that is what you see.
05Supported assets
Pull assets in.
Stablecoins, bitcoin and gold with canonical Ethereum contracts. A gToken appears only when its vault and token are deployed; nothing is listed as live before that.
06Gravity Router
Route capital.
Pick a source asset and a target gToken; the router quotes the bridge leg and the swap leg from live contracts. It never claims atomicity: two chains means two transactions, and it shows both.
01
USDC
Ethereum
02
GravFi Bridge
lock → message
03
gUSDC
Robinhood Chain
04
DEX pool
router configured
05
gWBTC
Robinhood Chain
Open Gravity RouterTwo transactions · not atomic · every fee quoted on-chain
07Liquidity
Backed on-chain.
Pools are enumerated from the configured router's factory and read at one block. TVL comes from reserves quoted in USDG through the on-chain WETH/USDG pool; volume needs an indexer and is omitted.
08Integrators
Verify, don't assume.
Everything the interface knows is readable by anyone: asset registry, contract addresses, ABIs, and a reserve engine you can run yourself.
Contract registry7 / 15 configured
- GravRelayMessenger0xecC3bb…
- GravRelayMessenger0xB98527…
- GravBridge0xEaab9A…
- GravBridge0x82efb3…
- GravVault · USDCNot deployed
- GravToken · gUSDCNot deployed
// Verify a reserve yourself — same reads the interface performs
const collateral = await eth.readContract({
address: USDC, abi: erc20Abi,
functionName: "balanceOf", args: [GRAV_VAULT_USDC],
});
const supply = await robinhood.readContract({
address: gUSDC, abi: erc20Abi, functionName: "totalSupply",
});
const backingBps = collateral * 10_000n / supply; // ≥ 10_000 → FULLY BACKED09Security
Contract architecture.
Role separation, pause switches, rate limits and reentrancy protection across four small contracts. The bridge does not invent a messaging protocol; it plugs into one.
GravVault
- Single-asset custody
- BRIDGE_ROLE-only deposit and withdraw
- Rolling withdrawal limit
- Pausable · ReentrancyGuard · SafeERC20
GravToken
- ERC-20 with source decimals
- Mint and burn only through BRIDGE_ROLE
- No public mint function
- Pausable transfers
GravBridge
- Messenger-agnostic transport
- Inbound only from the configured messenger
- Nonce replay protection
- Route registry per asset
Messenger
- IGravMessenger boundary
- LayerZero OApp or native messenger pluggable
- Not deployed yet — bridge stays inert
- Fee quoted by the messenger itself
Contracts are experimental until independently audited. · Foundry test suite: 43 tests incl. 3 invariants.