Platform gas funding.
Private operator APIs separate platform capital from customer deposits. These testnet workflows do not enable automated funding or spendable gas.
01Provision dedicated custody
Owner or finance operators request a labelled source with an Idempotency-Key and audit reason. A different operator approves it. The isolated custody service derives its address in a dedicated treasury vault; caller-supplied addresses, derivation paths and key references are rejected. Current admin role and recent passkey verification are required for writes.
02Review an immutable funding plan
Select a ready source, check a customer custody wallet on the same chain, and enter a positive native amount, reference and validity of 1, 6 or 24 hours. A different operator approves while the finalized indexer is current and caught up. Full source and destination addresses remain visible for review.
03Record the original transaction
Bind its hash to the approved plan. This records a permanent reference; it does not send funds. Repeat the same hash after an interrupted response. A committed hash cannot be replaced or cancelled. Never send another funding transfer just because a reference response was lost.
04Wait for finalized accounting
Quorum-validated native transfers from registered sources first enter pending gas and unallocated funding accounts. An exact preapproved source, target, amount, hash, timing and custody match reclassifies the funding as platform-owned gas capital. Customer liabilities and deposit fee revenue do not change. Unmatched or late events remain pending or in review.
05Inspect readiness honestly
Gas positions distinguish recorded owned gas, pending funding and spendable gas. Spendable gas remains zero and executionReady remains false until source inventory, reservations, distribution and spend reconciliation are implemented and verified. Operator views use private no-store responses and cursor pagination. These APIs use admin sessions, not merchant API keys.
GET /v1/admin/treasury/sources
POST /v1/admin/treasury/sources
Idempotency-Key: <request-id>
{ "chainKey": "ethereum:sepolia", "label": "Platform gas", "reason": "Dedicated platform capital" }
POST /v1/admin/treasury/sources/{id}/approve
{ "reason": "Independent custody review" }
GET /v1/admin/treasury/funding-targets?chainKey=ethereum:sepolia&walletId=<uuid>
GET /v1/admin/treasury/funding-plans
GET /v1/admin/treasury/funding
GET /v1/admin/treasury/gas-positionsOpen your workspace