Fee-wrapper lifecycle
Allowlist and fee-update lifecycle
Mutation responses useconfirmed when the requested state is already effective
and submitted when Ground broadcast an onchain transaction. Webhooks report
the terminal confirmed or failed result.
Do not convert submitted to confirmed based only on time elapsed. Read the
resource, observe the transaction receipt, or process the confirming webhook.
gVault webhook event types
Every delivery uses
{ id, type, createdAt, data }; the fields above are inside
data. Treat identifiers and the current resource read as authoritative;
webhook arrival order is not guaranteed.
Delivery status
The event-feed API describes delivery to your registered endpoint:
Delivery status is not business-operation status. For example, a successfully
delivered
status: failed fee-update event has delivery status completed and
payload status failed.
See Integrate gVault webhooks for receiver setup and
Handle asynchronous gVault operations for the
full reconciliation model.