Payment tabs
A tab puts a ceiling in escrow once; every call then carries a voucher your session key signs for the running total, and closing the tab pays exactly that and returns the rest. Tabs are opened from the SDKs. This page says whether this router has them open and makes the session key that signs for yours.
Tabs on this router
Reading…Reading this router's status…
Your session key
Reading…The key that signs tab vouchers. It is made here with WebCrypto, its private half is non-extractable and stays in this browser's IndexedDB, and only the public key below is shared. It is not a wallet: it holds no funds and cannot move the tab's escrow.
Opening a tab (open_tab), topping it up and reclaiming it are wallet transactions an SDK or script makes with this public key; this page makes none. A voucher is signed for one tab program, one tab and one opening of it (the tab’s created_at, read from the chain once it is open), so a voucher of a closed tab cannot be used on a tab opened again at the same address; what a voucher signs. Clearing site data deletes the key; a tab opened with it can then only be closed by the payee.
What happens, in order
- Make a session key here (or let the SDK make one). Its public key is all you share.
- From the SDK, open a tab: your wallet signs
open_tab(payer, payee, USDC, cap, expiry)once, moving the cap into thetrellis_tabescrow. The expiry is at most 30 days out. - Each call carries a voucher: the session key's ed25519 signature for the cumulative amount used and a sequence number, bound to the tab program, the tab and the moment this tab was opened. No wallet prompt, nothing on chain per call.
- The payee closes the tab with the highest voucher and is paid that amount; the rest of the cap returns to you. If the payee never closes, anyone can reclaim after the expiry plus 24 hours: the payee gets what it posted, you get the rest.
The payee stops serving when unvouched usage exceeds the larger of 25% of the last request's cost and $0.05, so neither side is exposed for long. Read the tab scheme · Read about the facilitator