Skip to main content
PRESSCHAIN V3 DEVELOPER PLATFORM

​
Infrastructure for journalism that can prove what happened

PressChain is a purpose-built blockchain protocol for publishing records that need more than a timestamp. It gives applications a common way to represent a published work, its author, its outlet, its evidence, revisions, contributors, provenance and protocol-level economic actions. The goal is not to put an article body on a blockchain. The goal is to give important reporting a durable verification layer that independent applications can read, challenge and extend. A Capsule is the center of that model. A Capsule anchors content and metadata hashes to a canonical bytes32 identifier. Related registries can then attach contributors, evidence, revisions and verification activity without forcing every concern into one contract.

Build an application

Connect to the V3 testnet, read chain state and integrate PressKey without taking custody of user keys.

Understand Capsules

Learn how publication records, metadata, evidence, contributors and revisions fit together.

Work with evidence

Model canonical and dispute evidence, inspect tallies and build evidence-aware interfaces.

Integrate PRESS economics

Understand bonds, fee classes, funded actions, rewards and the boundary between testnet facts and mainnet policy.

​
V3 network at a glance

Current deployments and balances are testnet state. Mainnet receives a new PRESS asset and a separately approved deployment manifest. Testnet balances are not represented as automatically migrating to mainnet.

​
What you can build

PressChain is useful anywhere an application needs to answer questions such as: who published this record, what content did they commit to, what evidence supports it, who contributed, what changed later, and which protocol rules governed the action. A newsroom CMS can register a Capsule as the verification record behind a story page. A browser extension can show readers the Capsule and its evidence beside an article. An investigations platform can attach dispute evidence without modifying the original publication. A syndication service can preserve attribution and content hashes as material moves between outlets. A research product can index Capsule events into a query layer without becoming the authority for the underlying facts. The important design choice is that applications do not invent a parallel meaning for protocol data. PressChain keeps semantics in protocol rulebooks, contracts and canonical models. Clients render those semantics.

​
Choose your path

If you want working code first, start with Connect to V3 Testnet, then Read Chain State and Build with PressKey. If you are designing a publishing product, read Architecture, Capsules, Evidence and Provenance. If you are operating infrastructure, start with RPC, Indexing, Security and the Production Checklist.

​
Source authority

These docs follow the current V3 authority configuration and active repositories. Historical specifications are useful for archaeology, but they are not allowed to override the active V3 authority files. Where implementation is intentionally incomplete, the docs say so instead of documenting a planned interface as if it were already live. That distinction matters for API endpoints, economic amounts, contract addresses and mainnet behavior. Developers should be able to build against what exists today and understand what still requires an approved authority manifest.