Skip to main content

​
Register a Multisig Wallet

POST /api/v1/auth/multisig/wallets (vendor / admin) The platform supports two registration styles. The right option depends on your onboarding setup:
  • Platform-Managed Multisig - The service provisions and operates the wallet according to your environment. You typically provide a label, network, and policy inputs as returned by onboarding. Follow the fields and enums your registration response documents.
  • Self-Managed (Bring-Your-Own Keys) - You supply multisig_type, signer_addresses, threshold, and any network-specific addresses or URLs your integration package requires (Ethereum vs TRON differ).

​
B2B Execution: Two Patterns

​
Platform-Managed Multisig

For wallets fully operated inside CoinPool’s infrastructure, B2B transfers can complete synchronously (200) once internal approvals succeed. Settlement references and status on the transfers resource reflect what the platform records for tracking.

​
Collaborative Signing (TRON/Ethereum)

For configurations that require co-signing on-chain:
  1. POST /api/v1/auth/transfers/b2b may return 202 with proposal_id.
  2. GET /api/v1/auth/multisig/proposals/{id} returns status and, for TRON, tron_unsigned_tx including rawDataHex and txID.
  3. Authorized signers produce a signature over the agreed payload (commonly signing rawDataHex on TRON).
  4. POST /api/v1/auth/multisig/proposals/{id}/confirm with { "signature": "<hex>" }, or in controlled non-production environments optionally { "signer_private_key": "<hex>" } for server-side signing.
Signatures append until threshold is met. The service then broadcasts and updates linked transfers when reference_type is transfer.

​
Ethereum (Contract Multisig)

When an Ethereum multisig contract is configured, proposal payloads and signing steps follow your deployment. Integrate using GET and POST multisig proposal endpoints only.

​
Security

Do not embed private keys in end-user apps. Prefer hardware or HSM signing and send signature only.