[CAP-90] Custom signature payload for account contracts #2049
Replies: 4 comments 10 replies
|
Supportive of this. We're working on spending policies for agents paying via x402 on Stellar, and committing to a policy rule id in the custom payload, plus account-managed nonces, would make enforcement in One note: the x402 Stellar exact scheme currently only accepts |
|
One case the Security Concerns section might name. The CAP rules out an account that doesn't support custom payload accepting one unnoticed. The opposite case is left to the account: a 4-argument Take the CAP's own example, an account that enforces strict ordering with a sequential nonce in the custom payload. If its A sentence would cover it: an account whose authorization depends on its custom payload MUST reject the empty vector rather than fall back to a default. SDK support for the fourth argument, when it lands, could make that choice explicit for account authors. On the x402 point above: while the exact scheme accepts only Douglas |
Given that the use case is to address the gap in Open Zeppelin's use case that was supposed to have been covered by CAP-71, but then they discovered during implementation the gap. Can we do some early prototyping with this solution with the expected use case to confirm it definitely fills the gaps and there are not other surprises? I think if we can spike a core + env, and a soroban-sdk, we could share a working quickstart running those components to test adoption within the OpenZeppelin contracts before accepting this CAP. We might need updates to another sdk, and rpc too. We can probably use @sisuresh's spike harness. |
|
Thanks for drafting CAP-90 🙏 it gives us a lot more room in how the OZ smart account handles authorization and most importantly, it solves the problem from my earlier comment. This lets us move delegated signers from
But there's one concern I'd like to raise: with
A treasury lists Alice's account as a delegated signer. When the treasury pays a vendor, Alice's With the current delegation flow in the OZ accounts, the delegate sees So the proposal is to add a host function to CAP-90 that returns the delegator inside
Thanks again for the work on CAP-90 and looking forward to your feedback about the proposal. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is a discussion thread for CAP-90: Custom signature payload for account contracts.
This CAP aims at closing the gap in the Soroban custom account design: it allows every custom account to authenticate an arbitrary, custom payload in addition to the fixed, protocol-defined context that Soroban host currently provides. That increases the flexibility of custom accounts and allows implementation of new functionality from custom nonce policies to policy rules in modular accounts that utilize delegation. The latter custom policy use case was the main driver for this CAP.
All reactions