HyperEVM Contract Addresses and Verification
The project documentation points to the published runtime deployment descriptor as the canonical source for active-chain contracts and instruments.
Official Papertrade documentation · Updated November 5, 2026 · Canonical domain: papertrade.finance
Canonical deployment source
The browser release embeds the active deployment fingerprint. The project documentation treats the published deployment descriptor as the authoritative deployment record.
Contract profiles
The relayer-only, open and session-fee profiles share most interfaces but differ in submitter permissions and PAPER transfer or staking rules.
Verification note
No contract address is invented on this mirror page. Use the current published deployment descriptor and the live application release when verifying an address before an onchain action.
Contract verification workflow
Use this page as the official address index, then verify the network, contract type and expected relationship before interacting directly. A token address, staking address and deposit-proxy component have different roles even when they are part of the same Papertrade deployment.
Static addresses vs runtime state
An address reference proves where a deployed component lives; it does not describe every active limit or protocol parameter. Trading minimums, market configuration, relayer permissions and other runtime values can change through the deployed control model, so integrations should read current state where the protocol exposes it.
Related Papertrade Guides
Frequently Asked Questions
What addresses are listed here?
This page is intended to reference deployed Papertrade contracts such as Exchange, PAPER, staking, tokenomics and session-key components.
Should I verify contract addresses before signing?
Yes. Contract addresses are security-sensitive and should be checked against the current trusted deployment reference before interacting.
Are frontend URLs the same as contract addresses?
No. Frontend domains and HyperEVM contract addresses are separate resources with different security roles.