Skip to main content
gtokens give applications access to Ground RWA yield through tokens held in their users’ wallets. Users deposit a supported asset into the corresponding Ground vault contract and receive receipt tokens. Your application can integrate the contract directly or use a fee wrapper for revenue sharing.

​
Choose an integration path

Use a direct gtoken integration when users should deposit into the backing Ground vault and hold gtokens in their current wallets. Your backend uses the Ground API only to manage deposit access. Deposits, withdrawals, and share accounting happen onchain. Use a fee wrapper when your application needs a performance fee, designated fee recipient, or a customer allowlist isolated from the underlying vault. Ground provisions the wrapper, but the underlying vault already exists.
POST /v2/fee-wrappers provisions a fee wrapper over an existing backing vault. It never creates the underlying vault.

Integrate directly onchain

Allowlist EVM addresses and interact with a gtoken’s backing Ground vault.

Configure revenue sharing

Provision a fee wrapper around a gtoken’s backing vault and configure its performance fee.

​
Start building

gtoken quickstart

Complete a sandbox integration from discovery through the first deposit.

Understand the model

Learn how gtokens, backing vaults, fee-wrapper shares, and API resources fit together.
If you need Ground to provision wallets, manage allocations across several yield sources, or automate rebalancing, use Portfolio Wallets instead.