Skip to main content
Most FlowGuard contract addresses are deployment-specific. Always verify the address you are interacting with against the stored deployment metadata and current artifact check.

​
How Addresses Are Derived

FlowGuard contracts compile to BCH script addresses. Each unique set of constructor parameters produces a different deployed address. Two vesting contracts with different totals, recipients, or schedule parameters do not share the same address. The backend DeploymentRegistryService tracks deployments created through FlowGuard together with:
  • contract type
  • network
  • deployment metadata
  • constructor parameters
  • artifact match status
  • optional on-chain verification data

​
Use the Registry

GET /api/deployment/registry
GET /api/deployment/registry?network=chipnet
GET /api/deployment/registry?network=mainnet
Because most covenants are parameterized at deploy time, there is no single canonical address for streams, recurring payments, airdrops, grants, bounties, rewards, proposals, or vote locks. Use the deployment registry to inspect the addresses your deployment actually created.

​
Verify One Address

GET /api/deployment/verify/:address
This route returns:
  • current balance
  • UTXO set summary
  • confirmation status
  • network
  • explorer link

​
Networks

The registry supports:
  • chipnet
  • mainnet
  • testnet3
  • testnet4
Use the network query parameter when you need a specific deployment set.