Connect to PressChain
A PressChain integration begins with two different connections: a read connection to JSON-RPC and a user authorization connection through PressKey. Keeping them separate makes the application easier to secure and easier to operate. For reads, use the canonical V3 RPC endpoint:77117002, or 0x498B64A in hexadecimal.
Web application setup
A browser application can read through JSON-RPC directly and use PressKey only when the user needs to authorize an action.Detect PressKey
window.ethereum when another provider has not already claimed that name, but PressChain-native applications should prefer window.presschain explicitly.
Backend setup
Backends that only read network state do not need a wallet at all.eth_call operations. It is not the correct place for storing user signing keys.
Configuration you should keep together
Treat network and deployment values as a coherent environment package:First health checks
Before building product features, verify these conditions:eth_chainIdreturns the expected testnet ID.eth_blockNumberadvances over time.- Your application can perform
eth_callagainst a known deployed contract. - PressKey can be detected on an allowed PressChain domain.
- Account and network change events update application state.