search

erc6900 / resources

18 stars 4 forks source link

Community Call #5 #26

Closed jaypaik closed 4 months ago

jaypaik commented 5 months ago

Request a calendar invite

Previous call recap

Meeting Info

Agenda

  1. Ecosystem developments
  2. ERC-6900 updates
  3. Research and development

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

jwindawi commented 5 months ago

Thanks to everyone who joined for Community Call 5!

A recap of the call:

  1. A discussion of ecosystem developments
    1. Following up on last week’s comments from the 4337 team about the v0.7 update to that standard, @jaypaik walked through the 6900 team’s analysis of the update and its implications for ERC-6900:
      1. Required 6900 change: update UserOperation references with PackedUserOperation
      2. Optional change: New methods support like executeUserOp()
    2. More broadly, for ERC-6900 Accounts & Plugins Migrations:
      1. New EntryPoint (v0.7) reference.
      2. All UserOperation needs to be refactored to PackedUserOperation . Multiple field decoding updates are necessary.
      3. [Optional] New method support for executeUserOp()
      4. User accounts migration with active plugins may need extra care on handling Plugin state data for accounts.
  2. ERC-6900 updates
    1. The team continues to build in dialogue with the community
    2. @jaypaik presented v0.7, the most recent update to the 6900 spec, which is now incorporated (EthMagicians, Github). The update is part of an ongoing process of streamlining the standard while maintaining its security, and grew out of community conversations on calls and on Github around:
      1. The removal of permitted call hooks and injected hooks during plugin installation
      2. Disallowing use of hooks as dependencies
      3. The full changelog is here
  3. ERC-6900 research and development
    1. @dlim-circle joined the call to discuss Circle’s experience in working with the standard, and in particular on gas optimization as a motivation to work with semi-modular accounts.
    2. @adam-alchemy presented a pull request focused on clarifying the behavior of hooks that interact with account state.
  4. Next steps
    1. The next call will be in four weeks, on February 22, 2024 - details and links to follow.