Skip to main content
The tables below list the deployed vault proxies backing gtokens. Call each vault at its proxy address; Etherscan exposes the verified implementation ABI and read methods through the proxy page. For gtoken sources enabled through the public API, use GET /v2/gvaults/yield-sources as the environment-specific integration manifest. The contract directory is broader than the set of gtoken sources currently returned by that endpoint.

​
Production gtoken contracts

​
Sandbox gtoken contracts

​
Fee-wrapper infrastructure

Ground provisions each fee wrapper as a separate proxy. The contractAddress returned by the fee-wrapper API is the address your integration reads from and transacts with. Production fee-wrapper factory infrastructure is not currently deployed. Ground will add the verified addresses here when production provisioning is enabled.
Never copy contract addresses between sandbox and production. Resolve the backing vault from the yield-source response and resolve a provisioned fee wrapper from its API response before constructing a transaction.