Replies: 1 comment
|
One-tx-per-session pooled settlement is a sensible optimization on gas, but the failure mode we saw running escrow-settled agent tasks is dispute granularity: when funds are pooled, a single contested task freezes or fragments the whole session's settlement. What worked for us: lock the budget per task at publish time and release only on the publisher's explicit acceptance against pre-stated, verifiable acceptance criteria. Pooled settlement then works great as the rail — the money can still net through one tx — as long as per-task receipts are individually signed and dispute-arbitrable. So +1 to the idea, with the caveat: keep the accounting per-task even if the money moves per-session. We've been iterating on exactly this escrow model here: https://github.com/houdaguang/actn-agent-network |
Uh oh!
There was an error while loading. Please reload this page.
Opened an issue proposing a Concord payment scheme beside the x402 plugin from #32576 — pooled settlement, one tx per session, spend capped by an account policy: #32896. Would value a maintainer's read before I open a draft PR.
All reactions