EVM-Compatible · Chain ID 77117002
Build on the
journalism layer
PressChain is an EVM-compatible L1 with a journalism-specific protocol on top. If you know Solidity, ethers.js, and REST APIs, you already know 80% of what you need.
What You Are Building On
PressChain runs full EVM execution. Contracts govern Capsule publishing, role bonding, acceptance voting, and court resolution. The Bridge API is a REST middleware layer that normalizes chain data for outlet and dApp integrations. PressKey handles all signing and identity.Four Rules Before You Write a Line of Code
WordPress and outlet apps never touch RPC
Your application calls the Bridge API. The chain is accessed through API Gateway - Bridge - Protocol API. This is non-negotiable.
PressKey signs everything
Every write action - voting, publishing, role purchases, court participation - requires a PressKey-signed nonce. You never handle raw private keys in your app layer.
The Bridge is your stable surface
Chain data can change shape between protocol versions. Build against
bridge.presschain.io routes, not raw RPC, unless you are building validator or node tooling.Quick Environment Setup
ethers v6 Provider
Runtime Ports (Operators)
Public apps
presschain-next@portal3010
presschain-next@outlet3011
presschain-next@court3012
presschain-next@proposals3013
presschain-next@ads3014
presschain-next@status3015
presschain-next@docs3016
presschain-next@faucet3017
Internal services
gateway46100
protocol-api46101
indexer46102
court-engine46103
media-engine46104
burn-engine46105
Chain RPC (internal only)
Mainnet HTTP8545
Mainnet WS8546
Testnet HTTP9545
Testnet WS9546
Where to Go Next
Quickstart
Deploy a contract call and read your first Capsule in under 10 minutes.
Architecture Overview
Domain separation, service topology, and why the stack is built this way.
Contract Registry
All deployed addresses with descriptions and ABI references.
Bridge API
Full route reference. The primary integration surface for everything.
