Create a delegation session
Let another address act for you within limits on actions, time, spend and counterparty, using the Developer Portal.
A delegation session lets another address, the delegate, act for you within limits you set: which actions, for how long, with how much, and with whom. You remain the root. Delegations → New in the Developer Portal walks you through creating one.
Implementation candidate
Creating a session is an on-chain transaction on the network named in the header. The root can revoke a session later. A session cannot be edited.
Before you start
- Sign in with the wallet that will be the root. See the quickstart.
- Your wallet must be on the same network as the portal header and hold a little of the network's native coin for gas.
- Have the delegate's address ready. It must differ from yours.
Step 1: Terms
| Group | What you choose |
|---|---|
| Who | The delegate, the side the session acts on (buyer or seller), and the settlement token it applies to. |
| Permitted actions | Tick only what the delegate needs. On the buyer side: create and escrow Atoms, accept revisions, confirm completion. |
| Lifetime | When the session stops working: after its first action, at a time you set (one day is the default), or never. |
| Spending caps | The most one Atom may escrow, the most per period, and the most over the whole session. Leave a cap empty for no limit. A seller-side session also sets the minimum value it may accept. |
| Scope | Optional restrictions: one counterparty, object, asset or profile, and the dispute setting of the Atoms the delegate may form. Empty means any. |
Things to know when you set limits:
- Only creating an Atom spends. It counts against the caps when the Atom is created.
- A refund does not give the cap back. If an Atom is cancelled or expires, the amount it used stays used.
- Confirming completion releases escrow to the seller. Grant it only to a delegate you trust with that decision.
What a delegate can never do
Whatever you tick, a delegate cannot:
- open or settle a dispute,
- file anything in a dispute case,
- sign consensus for a settlement,
- cancel an Atom,
- act beyond the caps, outside the scope, or after the session ends.
The panel on the right of the form lists these limits.
Step 2: Review
The review states in sentences who may act for whom, what the delegate may and may not do, how long the session lasts, the caps and the scope. Technical details shows what your wallet will be asked to send and the predicted session id. A highlighted note appears when a choice is broad, for example when the delegate may confirm completion.
Step 3: Simulate
The server runs the exact call against the latest block. You can continue only when it succeeds. If it fails, the portal says why and what to change.
Steps 4 and 5: Send and read the outcome
Choose Send, read the confirmation, and approve the transaction in your wallet. The portal checks first that your wallet is on the right network and that the transaction is the one it prepared.
The portal then reads the result from the chain and compares the created session with the predicted id. A transaction that succeeded but created something else is shown as an error, not as a success.
When the session exists, open it from the link, or find it under Delegations, where its remaining lifetime and what it has spent are shown. You can also paste its id into Lookup.
When sending is turned off or unavailable
Where the portal operator has turned sending off for the network, the last step is Export instead of Send. Copy or download the prepared transaction and send it with your own wallet or tools. The same conditions that block sending apply as when you create an Atom: a Sinera account session, a network that is not deployed, or a wallet on the wrong network.