Skip to main content
The tables below list Ground’s deployed gVault proxies. Call each gVault at its proxy address; Etherscan exposes the verified implementation ABI and read methods through the proxy page. For gVaults 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 gVaults currently returned by that endpoint.

​
Production gVaults

​
Sandbox gVaults

​
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 gVault from the yield-source response and resolve a provisioned fee wrapper from its API response before constructing a transaction.