Session keys
A session key lets an agent move one of your positions from one Sluice pool to another, in a single transaction, within limits you set. It cannot withdraw, and it cannot send your value anywhere but back to you.
Setting one up is two approvals at two different addresses. The first is the one to read carefully; the second is the one that carries the limits.
Delegation is per wallet, so there is nothing to show or change until one is connected.
My positionsRevocation is two levels. Revoking one agent leaves the router approved for the others; removing the router’s approval stops all of them and needs nothing from the router.
The router is one deployed contract with no owner, no pause and no upgrade path. Changing it means deploying a different address, which you would have to approve deliberately.
The vault behind it is upgradeable, and one governor key can replace its code. That key is a custody key over your position whether or not you delegate anything.
A move is a withdrawal and a deposit in one transaction, and both pay the pool’s fee — an agent moving your position often costs you that, every time. Both ends are priced from a 60-second average of the pool’s own price, and on a pool that has not traded inside that minute the average is simply the current price. That is the common case here.
A dash means we do not have the number, never that it is zero.