AllSet Portal

AllSet coordinates supported movements between Fast and external chains. Its source repository documents separate deposit, withdrawal, and revoke workflows. The AllSet SDK exposes supported application entry points, but it does not make cross-network completion synchronous or automatic.

Deposit and withdrawal

A deposit starts with a transaction to the configured bridge contract on the source chain. AllSet services observe and verify the event before the corresponding Fast-side balance is credited. Merely sending funds to an auto-linked EVM address is not a bridge deposit and produces no deposit event.

A withdrawal starts with a Fast-side transfer and intent. Relayers and destination contracts perform the external-chain leg later. The source transaction may be final while delivery is still pending, failed, or unknown. Track both sides with their transaction identities; do not make a new withdrawal just because the first acknowledgement was lost.

The source tree includes generator, verifier, relayer, block-hash, and cross-sign components. Their deployments, chain contracts, token mappings, and route availability vary by environment. A chain being recognized by the SDK is not proof that all services for that route are active.

Revoke and recovery

Revoke is a separate protocol operation with preconditions; it is not an automatic refund for every failed or delayed withdrawal. Check the revoke workflow and the current transaction state before attempting it. For an uncertain submission, preserve its exact identity and seek reconciliation rather than assuming funds can safely be resent.

AllSet's design aims to maintain backing between bridge-held assets and Fast representations. That invariant depends on the configured contracts and verification process; it is not evidence that a particular user transfer has reached its destination. Use source- and destination-network records for that conclusion.