Docs · Network
Transfers
Moving an asset, and what happens when the asset is gated.
Ungated transfers
An ordinary asset moves like any Cosmos balance: the holder signs, the chain checks the balance, the transfer lands.
Gated transfers
When an asset is Trust gated, a movement must additionally carry an authorization artifact signed by a key in the asset's gate. The chain verifies the signature, the nonce and the window.
An authorization is a capability, bound to one movement, with a nonce that is spent when it is used and a short window. It is not a payment instruction and it moves nothing on its own.
From the Console
The asset's page shows whether the asset is gated and, when it is, the gating organization, the policy version, and how many keys may authorize a movement — a count, never the keys themselves.
READ ONLY See whether an asset is Trust gated — /projects/[projectId]/assets/[assetId]
Where: Console → Assets → an asset
The Console shows the gating organization, the policy version and how many keys may authorize a movement. It does not issue authorizations: one is issued per movement by the organization that opened the gate, so moving a gated asset from the Console is refused by the chain.
Requires: ADMIN, AUDITOR, APPROVER, POLICY_AUTHOR
The Console does not issue authorizations. A gated transfer attempted from it is refused by the chain, which the screen says before you try. The transfer is still offered rather than hidden: the chain is the authority on whether a movement is authorized, and a form that decided for it would be guessing at state it cannot see.
An ungated transfer touches nothing outside the chain. It needs no Trust authorization, no control plane and no network call to Bengar — a transfer commits with the Gateway switched off, which is the property the separation exists for.