Parties
Both parties are Atlas participants. See Atlas for creating participants and sharing their IDs.
What a delegation contains
vaultUniqueId: the delegator’s vault that holds the delegated assets. Only the delegator sees it.delegatedAssets: one entry per delegated asset holding, with the amount currently delegated. Amounts never include fees. For the delegator, each entry also haswalletUniqueId, the wallet that holds it. The delegatee does not see vault or wallet IDs.sourceAddresseson each asset: the on-chain addresses currently holding it. The delegator always sees them. The delegatee sees them only if the pledgor has opted in to disclosing them. Assets can move between addresses over time, but they stay in the delegator’s wallet. An empty list means the asset has no attributable on-chain address, for example fiat.revokedOn: set once the delegation has ended. Absent while it is active.
Settling assets in and out
Either party can propose moving assets between a wallet its organization owns and the delegation, within the agreement’s settle rights.- Call
POST /atlas/delegations/{delegationId}/settlewith one entry per wallet and asset, plus anidempotentIdso a retried request is not applied twice.clientReferenceIdis an optional memo both parties see. A positive quantity is an asset your wallet receives; a negative quantity is an asset your wallet sends. Every entry in one request points the same way. An asset can be received into only one wallet, but can be sent from several. - The request returns
202with asettlementRequestIdonce it is accepted for processing. Nothing has moved yet. - The delegator approves the settlement, whichever party proposed it. Assets move only after that approval.