Sign
Use Sign when you need a key to create a cryptographic signature for a payload, whether off‑chain or chain‑specific. This can include signing arbitrary data or producing a transaction signature. A signature proves that the key holder approved the exact payload.
What endpoint should I use for my transactions?
IBM Digital Asset Haven supports several signing types, including generic hash signing (32‑byte hashes), EdDSA message signing (arbitrary‑length messages), and chain‑specific formats such as Substrate SignerPayload and Cosmos SignDocDirect. Use a chain‑specific format when you plan to submit the signed data on‑chain. Use hash or message signing for general‑purpose signing or unsupported chains.
- Transfer
-
Use Transfer Asset for native tokens, ERC‑20/721 assets, SPL tokens, Cardano assets, and similar transfers. This endpoint:
- Creates a wallet transfer request
- Requires user‑action signing
- Supports fee sponsorship
- Supports idempotency through
externalId - Enforces policy approvals
- Provides status tracking and indexing (
txHash,dateConfirmed)
- Broadcast (Sign and Broadcast)
- Use Broadcast Transaction when you have created a raw or serialized transaction, or when you need to call smart‑contract functions, mint assets, or deploy contracts. This endpoint signs the transaction with the wallet key and broadcasts it. It also returns the request status and
txHash. - Sign (Generate Signature)
-
Use Generate Signature only when you need an off‑chain signature and do not want to broadcast a transaction. This endpoint is deprecated in favor of the Keys API and does not submit data to the chain.