erc6900 / resources

18 stars 4 forks source link

Community Call #8 #30

Closed CodesMcCabe closed 2 months ago

CodesMcCabe commented 3 months ago

Calendar invite

Previous call recap

Meeting Info

Agenda

  1. Ecosystem developments
  2. ERC-6900 update
  3. Open Discussion

To add or request a topic that you'd like to discuss, please comment in response to this Issue below!

CodesMcCabe commented 2 months ago

Thanks to everyone who joined for Community Call 7!

Recording

A recap of the call:

6900 ecosystem development

  1. @dphilipson walked through a demo of the newly release Cold-Storage plugin for modular accounts. (Github / Demo)
  2. X Spaces - The Future of AA and Security: Spearbit + Alchemy with Noam from Alchemy and Hari & Omar from Spearbit.
  3. Showcased 3 articles released by the 6900 and 7579 working teams. @jaypaik commented:
    • There is currently active collaboration between both teams to build towards solutions where plugins/modules are compatible across both standards.
    • These discussions are seen as beneficial towards pushing the space forward as we discuss security and implementation details.
    • It should be possible at this time to have alignment on execution and validation though some more work to be done there.
    • 7579 team is working towards an implementation with validation hooks. Great to see a convergence here.

Working towards compatible standards articles

ERC-6900 updates

  1. @jaypaik walked through the 6900 roadmap draft mentioning he's happy to discuss priorities with the community. Any community member is able to take on these items if they would like!
  2. @adam-alchemy talked about an experimental feature for v0.8 - signature validator interface. This change bakes in the 1271 standard, signature validation, and explains a specific way for plugins to implement it. Prior to this, it was up to plugins to treat this as any other execution function on the account but in practice we noticed this could cause issues around conflicting plugins. This brings it roughly to the same level as validation functions in that there is an expected interface that plugins have to implement. For now capped at 1 implementation per account but working towards multiple plugins at once.
  3. @jaypaik responded to the closed PR for adding a replace plugin by the Decipher team. Discussion will continue as we work towards a viable implementation solution.