Networks and deployment provenance
Discover supported networks from the API and verify the governed active-V2 Sepolia deployment before signing.
Use GET /v1/networks and GET /v1/deployments as the integration source for supported network
and deployment metadata. Do not hard-code an address from an RPC response, a local test run, or an
unversioned source file.
Current hosted development network
| Field | Value |
|---|---|
| Network | Sepolia |
| Chain ID | 11155111 |
| API base URL | https://api.torq.finance |
| Contract registry | @torq-finance/contracts and GET /v1/contracts/{contractName} |
The generated contracts package includes the governed deployment namespace, addresses, ABI event definitions, artifact checksums, and linked-library metadata. Validate the package release and checksum before encoding an external signer transaction.
Signing rules
- Set the wallet or signer to the
chainIdreturned in the prepared transaction intent. - Simulate the exact intent on that chain.
- Submit through the customer-owned signer.
- Register the transaction hash with the workflow and wait for canonical completion.
Torq rejects a mismatched signer chain before a transaction is registered. A mined receipt alone does not prove that indexed state, authority, and postconditions match the prepared workflow.
Local development
Local Hardhat addresses and manifests are development fixtures, not public integration targets. They must never be copied into an application configuration intended for Sepolia or production. Use the API deployment response and governed artifact registry for every customer-facing environment.
No public mainnet deployment namespace is documented by this Developer Preview. Do not infer production availability from a package name, ABI, or Sepolia address.