Skip to main content

Fee classes

Fee classes describe the economic character of an action. They are useful to application developers because the class can remain stable even when a network-specific amount changes.

Classes

Selected V3 actions

Build a generic cost component

A reusable action-cost component should take semantic policy as input:
This avoids copy such as “All writes cost 1 PRESS,” which becomes wrong as soon as funded or elevated actions are introduced.

Error handling

If the application cannot resolve the current network amount for a fee-bearing action, disable authorization rather than guessing. A missing economics manifest is an operational error, not permission to use a stale cached amount indefinitely.

Economic transparency

Show class and amount before signing. For bonded or funded actions, explain whether value is locked, transferable, refundable or subject to settlement policy. The user should be able to distinguish protocol economics from network gas and from any separate application subscription fee.