Prerequisites
You need a Ground sandbox API key, an EVM address controlled by your user or application, and enough of the listed deposit token and native gas token to submit sandbox transactions.1. Discover a gtoken source
The gtoken API uses the/v2/gvaults namespace. Use the returned source ID as
gVaultId.
id, contractAddress, asset, and interface.
Resolve these values independently in sandbox and production.
Set GVAULT_ID to the selected row’s id:
2. Authorize the address
200 response is already confirmed. A 202 response means the authorization
transaction was submitted. In that case, poll the allowlist state until
allowed is true:
3. Read the contract configuration
At the returnedcontractAddress, call asset() to resolve the ERC-20 deposit
token. Treat the catalogue’s interface as the selector for the correct vault
interface; not every backing vault has the same synchronous or asynchronous methods.
4. Submit the deposit
For a synchronous USTB-style backing vault, approve the exact asset amount and call:5. Record the result
Store the environment,gVaultId, contract address, chain ID, transaction hash,
asset amount, share amount, and receiving address. Treat the transaction as
complete only after the required chain confirmations.
Direct integration guide
Build the complete direct access flow.
Configure revenue sharing
Have Ground provision a fee wrapper over the selected gtoken’s backing vault.