Skip to main content

Constants and network reference

This page collects high-frequency values that developers should not have to rediscover in several repositories. Values are taken from current V3 authority and source-backed implementations.

Network

PRESS

The planned supply is not a complete tokenomics manifest. Allocation, vesting, treasury routing, validator rewards and burn policy still require formal approval before mainnet.

Capsule metadata

Evidence

Current V3 evidence status enum: Reserved dispute evidence type:
The contract maintains a separate finalized boolean, so consumers should not assume status enum value 5 is the only way to identify finalization.

Contributor roles

These are Capsule contributor roles, not protocol role IDs: Maximum combined active share:

Fee classes

API defaults

PressKey

Current inspected extension:

Treat this page as a convenience, not a deployment manifest

Contract addresses are intentionally absent unless they are part of an approved current deployment authority set. Copying an address from an old script is more dangerous than requiring developers to load the actual deployment manifest. When a value changes through approved authority, the reference should change with it.