Skip to main content
If you are using the web3 SDK in JavaScript, signing looks like this:

Step 3: Submit the signed transaction

The returned txId matches what you got in step 1. The transaction is now in the mempool.

Step 4: Check transaction status

Poll this endpoint until type is "Confirmed":
While pending:
Once confirmed:
If not found:
For most use cases 1 confirmation is sufficient. For high-value transfers wait for at least 110 confirmations (~2 hours): this is the Alephium recommendation for exchanges and large amounts.

Sending tokens alongside ALPH

To include a token in the transfer add a tokens array to the destination. Every output on Alephium must include a minimum ALPH amount (dust) even when the primary transfer is a token:
1000000000000000 attoALPH (0.001 ALPH) is the typical dust minimum. The node will reject outputs below this threshold.

Sweep all ALPH from an address

To empty an address completely use the sweep endpoint it automatically calculates the correct amount after gas:
Note that sweep returns an array of unsigned transactions if the address has many UTXOs the node may split it into multiple transactions. Sign and submit each one individually.

Decode a transaction before signing

If you want to inspect what a transaction does before signing it:
Always decode and verify fixedOutputs matches your expectations before signing, especially when building transactions programmatically.

Parameters reference

Next steps

Read a contract

Call view functions on deployed contracts

Error handling

Retry logic and error code reference