Fees & finality
Separate proving latency, relayer reimbursement, and base-chain settlement.
Protocol behavior is proposed. This release is an interface preview; no funds or wallet signatures are accepted.
Cost components
| Component | Purpose |
|---|---|
| Base-chain gas | Pays for public transaction execution |
| Relayer allocation | Reimburses the submitting party |
| Deposit escrow | Covers admission processing where enabled |
| Swap price impact | Depends on the external liquidity route |
Estimation
The reference wallet path estimates operation gas using recent successful usage or a default, with a 1.25× buffer. Its app selects shielded ETH for fees even though lower-level components can support other fee assets. This is not a Jammer fee quote.
A Jammer release must show the maximum authorized charge, selected fee asset, and handling of unused value. No live gas or fee estimate is available in this preview.
Completion is not one timer
Proof generation, relayer submission, block inclusion, finality, and scanner synchronization are distinct stages. The UI should report the current stage instead of promising a universal completion time.
Reorgs, congested blocks, stale roots, unavailable relayers, and fragmented notes can increase latency. Performance targets must be tied to a specific release and measurement environment.