Your contracts.
No borrowed addresses.
Public deployment is not configured. Local deployments appear below only when the disposable devnet is running on this computer.
Configured deployments
What is checked
Before enabling a deployment, the client checks the RPC chain ID, non-empty contract bytecode, configured runtime code hashes and core contract wiring. A matching hash identifies the configured build; it does not prove the code has no vulnerabilities.
What is not deployed
This package does not configure Pairhouse public-chain contracts, a treasury, public synthetic-asset price feeds or a production indexer. The source includes local-only deployment automation and a preparation checklist. Never send funds to old, copied or unverified addresses.
Roles and custody
The deployment's owners and configurable fees are visible in the Solidity source and must be reviewed before public use. Production administration should use separately reviewed controls and an approved owner. The development wallet and mock oracle owners are disposable local test accounts, not production operators.