🎁 [Feature Request]: Smart Accounts enhancements

[brozorec]

What is the feature you would like to see?

This is issue is to keep track of proposals for new features, interface modifications and any other enhancements and proposals not related to the smart contract modules that has the potential to contribute to a broader adoption of smart accounts.

Core Contract

1. Refactor Delegated signers to take advantage of the changes proposed in CAP-71 (given this proposal gets approved and included in a next protocol upgrade)
2. Adopt an approach where expired context rules are automatically pruned (e.g. using temporary storage by following the pattern in fungible token approvals)
3. SDK streamlining the interactions with smart accounts on the client side (similar to what's previously done in passkey-kit)
4. Increase the max cap of context rules in a smart account (set to 15 atm)

Verifiers

1. Add a new function to query metadata on verifiers. This will be helpful on the client side by improving auditability. The External signer contains the verifier contract and key data bytes, but how those bytes are to be presented by clients depends on off-chain logic (app-specific or indexing).
2. Modify the reference webauthn (passkey) verifier to account for credential id.

Policies

1. Policies are the most opinionated piece of the framework so some guidelines of how to implement new policies might be useful

---

Resources:

• Smart Accounts Documentation

[kalepail]

• CallContract to accept a Vec<Address> vs just Address. Many protocols have many contracts in their call stack and you'll want to be able to approve them all for any single tx to pass
• CreateContract to accept a Vec<BytesN<32>> vs just BytesN<32>. Maybe not as important but would be nice to approve the deployment of several wasms vs just one per context rule

[kalepail]

• At least one example utilizing an indexer (like https://goldsky.com/) to showcase reverse lookup from passkey credential id to contract hash. This is especially important in cases where the context rule the signer was added to wasn't the credential id used to derive the contract hash

[kalepail]

• Support updating context rules in one shot vs piecemeal. If I want to add/remove signers and add/remove policies or update the name or expiration I have to do all of that as it's own transaction. It would be nice to combine these into one super update

[kalepail]

• support adding/removing mutliple signers and policies at a time vs one by one

[kalepail]

• it doesn't seem policies have a concept for updating things like params, so updating would required full removal and re-add, which isn't ideal. I'd like to see an official update method supported for policies

[kalepail]

• allow the selection of a specific context rule to match against. The current structure can get very expensive and entirely needlessly so. This would allow removing the 15 context rule limitation as well which would also be very nice and I would argue essential for my primary use case of per dapp signers