Network costs and reserves.
Native network costs and token-denominated customer charges use separate amounts and exact conversion. Operator policy governance is implemented; live withdrawal quotes and payouts remain in progress.
01Policy controls
An exact chain/asset policy specifies a native reserve ceiling, customer charge ceiling, buffer, freshness windows, workspace scope and effective period. Draft values are immutable.
02Manual scenarios
Recent admin MFA is required. Owner and finance operators can save cost/conversion/refund scenarios, submit them and obtain approval from a different operator. Every scenario is labelled manual; it cannot create funds, reserves or a withdrawal.
03Exact conversion
Record complete native components and a rational conversion. Add costs before rounding into the charge asset. Native charges require 1:1 parity. Conversion rate precision can exceed the token balance precision.
04Refunds and replacements
The shared calculation retains the agreed conversion, returns unused reserves and caps customer charges when actual native cost overruns. Future policy replacements close the previous effective period atomically. Receipt-based refund posting and actual outgoing execution remain pending.
GET /v1/admin/network-fee-policies
POST /v1/admin/network-fee-policies
GET /v1/admin/network-fee-policies/{id}/simulations
POST /v1/admin/network-fee-policies/{id}/simulations
POST /v1/admin/network-fee-policies/{id}/submit
POST /v1/admin/network-fee-policies/{id}/approve
// All paths require an independent operator session and recent MFA.
// Manual scenario: 0.002 ETH estimate + 25% buffer = 0.0025 ETH reserve.
// At a manual 2,500 USDC/ETH rate: reserve 6.25 USDC.
// Actual-cost scenario 0.0015 ETH: charge 3.75 USDC, return 2.50 USDC.
// No actual quote, ledger reservation or payout is created by this simulator.Open your workspace