Skip to main content
The tables below list the deployed vault addresses backing gtokens. Use the linked explorer to inspect each contract and its verified ABI. For proxies, use the proxy address with the implementation ABI. 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.