Weekly Development Updates (5/10/24)

[CodesMcCabe]

• Pausing our community calls:

  • Thank you for everyone that has contributed to the ERC-6900 community calls! We will be pausing our community calls in preference to focusing more on building out the standard with the current working group of developers. However, we will still be posting notes from these discussions in the erc6900 GitHub. https://github.com/erc6900/resources/tree/main/community-calls
  • If you would like to get involved contributing to the standard, feel free to comment on any of our outstanding improvement proposals or submit your own https://github.com/erc6900/resources/issues
  • If you're interested in more active participation with the working group discussions, comment on the issue listed below so we can chat further! Want to get more actively involved in development? #39

• We’ve started addressing the security considerations section of the standard, with help from @0xrubes! Security considerations ERCs#8

• Account storage and manifest declarations for hooks have been re-organized to be much simpler: feat: [v0.8-develop] Simplify hook declaration and storage reference-implementation#51.

• We are exploring ways to be able to compose validation: https://github.com/erc6900/validator-experiments

  • Scenarios that we think would be great to support:

    • A multi-owner validation where different owners use different kinds of cryptographic signatures, e.g. ECDSA vs whatever passkeys use.
    • A multisig validation where different signers use different validation schemes, including some of those schemes possibly being multi-owner or multisig validation in themselves.
    • A multisig validation where an individual owner has the ability to change their validation scheme independently of the others.

  • This is difficult with the way we have been writing plugins so far. But we can potentially adopt a pattern similar to the above to be able to support composable validation without spec changes.

    • However, we may need to make standard improvements to support validation with side-effects, to be able to authorize writes from the account.
    • An idea was proposed to maybe utilize executeFromPlugin to make calls to IValidator instances from the account instead of the plugin.

  • More work to be done here, but this is an area that we’re excited about researching further!