Skip to main content

​
Economic principles

The V3 economic policy begins with a simple rule: every public state-changing economic action must have an explicit cost, bond, funded value or approved premium usage charge. Governance-only configuration is treated separately. This makes economic behavior inspectable. A client can explain why an action costs something and which class applies without embedding business logic in every button.

​
Six fee classes

PressChain V3 defines:
  • none
  • bond
  • micro
  • standard
  • elevated
  • funded
These are semantic classes. Mainnet amount tables can be approved independently.

​
Why classes are better than scattered constants

Imagine three clients hard-code a publication fee in separate repositories. When economics change, one client updates, another does not and the third rounds the token amount differently. A canonical action rule avoids that drift:

​
Bonded actions

Role activation and top-up are bond actions. The value is not simply spent like a fee. It represents protocol stake subject to bond rules. Withdrawal has its own cooldown and micro fee semantics.

​
Funded actions

Bounty creation is funded. The creator must supply funding for the bounty itself. Treat that funded amount separately from transaction gas and any protocol fee. A review screen might show:
Use actual approved values for the active network rather than the illustrative numbers above.

​
Premium actions

trust.analysis.request is defined as a premium economic action with identity, standard fee, premium access and project-plan quota requirements. If an application integrates such a service, it should preserve the boundary between protocol economic semantics and the separate analytics implementation.

​
Governance is different

governance.configure and ownership.transfer are non-public governance actions with no public fee class. Do not expose internal administrative operations as ordinary paid user features merely because they change state.

​
Security controls around economics

Current policy requires controls including treasury floors, automatic bounty budget caps, maximum active bounties, role and bond validation at settlement, pause capability, replay prevention, deterministic idempotency and immutable settlement audit events. Economic code should fail safely when these controls cannot be evaluated.

​
Mainnet amounts are not documentation guesses

Where final mainnet amounts have not been approved, the docs state the class and requirement without making up a number. This lets developers build durable interfaces now while preserving the governance boundary for final economics.