Skip to main content
The gVault allowlist applies to direct access to an existing gVault. The subject is an EVM address, not necessarily a wallet: it can be an EOA, multisig, smart account, or another contract.

​
Add an address

Call from your backend with the id returned by the gVault catalogue:
The operation is idempotent for the desired allowlisted state:
  • 200 with status: confirmed means no further state change is pending.
  • 202 with status: submitted and transactionHash means Ground broadcast the update, but it has not necessarily confirmed.

​
Verify the effective state

Do not enable deposits until allowed is true. A transaction hash proves submission, not confirmation or effective authorization.

​
Remove an address

Removing your organization’s grant blocks future deposits after the effective allowlist state becomes false. It does not seize shares or block redemption of an existing position. If another authorized organization still grants access, the effective state may remain true.

​
Handle failures

Treat 404 as an unknown gVault or unavailable organization resource, 409 as a conflicting in-flight state change, and 503 as a temporary submission failure. Before retrying an uncertain request, read the effective state. API reference: add, get, and remove.