Meeting Minutes from November 27 WG Meeting

meeting_minutes.md

@@ -1,5 +1,54 @@
 # Meeting Minutes: Technical Specification of General Layer 2 Blockchain Scalability Solutions for EVM-compatible public Blockchains WG
 
+## Meeting Wed, 27 November 2024, 7:00 am PT
+
+Attending: Andreas Freund (EF),  James Harsh, Nikola (Nethermind), Ohad Banta (Starknet), Jan Grozny (Zircuit), Nemanja (Eternal)
+
+Agenda:
+1. Welcome, and a reminder of the WG meeting rule
+2. Selection of scribe
+3. Introduction of new participants
+4. L2 Transaction Fee API spec: Collect PR approvals,
+5. L2 Transaction Statuses: Collect PR approvals. PR is here.
+
+Notes:
+
+Scribe: Andreas (Zoom AI Scribe)
+
+* Introductions:
+  - In the meeting, Andreas led a round of introductions from various team members, including Ohad, James, Jan, Nemanja, Derek, and Nikola.
+* L2 Transaction Fee API Spec
+  - The L2 transaction fee API spec is based on the L2 transaction fee specification, which is already a draft. The chair is seeking approvals and comments for the API spec. 
+  - Andreas discussed the design and implementation of transaction fee estimation endpoints. He explained that the endpoints return HTTP codes and fees are broken down into execution, data, and priority fees. Each fee is further divided into the requested currency value, gas units, and gas price. Andreas also detailed the data schema for the transaction fee estimate, which requires the transaction call and chain ID. He mentioned optional parameters like transaction priority, currency, and transaction ID. The response for a successful request includes objects for execution, data, and priority fees, with each object containing currency, gas, and breakdown values. Andreas raised a question about accounting for different gas prices for blob and L1 call data gas, suggesting the introduction of an additional parameter for L1 blob gas price.
+  - Derek discussed the automatic switching between blob and call data depending on which one is cheaper for Arbitrum One. It was agreed to update the description to be more verbose, depending on whether it's call data or blob data, whichever is cheaper. Nikola brought up the topic of vectorized gas transactions and the potential changes it could bring to the spec. They also discussed the need to differentiate between call data and blob data fees. The conversation ended with the decision to update the description and the need to understand the derivation method for the L2.
+  - Andreas discussed the last endpoint to get a transaction fee after transaction submission, which requires a transaction hash and chain ID as query parameters. He explained the returned data includes transaction status, total fee, and fee breakdowns. Andreas also discussed the requirements for the API endpoints, including the need for a request and response body with an HTTP code. He mentioned the importance of testability and provided testability statements for each endpoint. Andreas also discussed the conformance levels for the specification, with Level 1 requiring all must requirements to be fulfilled, Level 2 requiring must and should requirements, and Level 3 requiring should requirements. He emphasized that for Level 2 conformance, the testing procedures for each requirement must be described.
+* Transaction Statuses Specification Draft Discussion
+  - The L2 transaction statuses spec aims to standardize statuses across different designs to improve the experience for developers, wallets, and end-users.
+  - In the meeting, Andreas discussed the specification draft PR, seeking approval or comments on the proposed statuses. 
+  - Ohad suggested splitting the "drop" status into "reverted" and "rejected" for clarity.
+
+Next steps
+• Andreas to update the L2 Transaction Fee API spec description to clarify that the L1 gas price could be for call data or blob data, whichever is cheaper, from the perspective of the L2.
+• Andreas to explicitly state in the L2 Transaction Fee API spec that L2 client-specific fees are out of scope.
+• Ohad to leave a comment on the PR suggesting splitting the "L2 dropped" status into "reverted" and "rejected" in the L2 Transaction Statuses specification.
+• Andreas to add new participants to the meeting invite and email list.
+• Andreas to seek an L2 representative to serve as co-chair for the working group.
+• Working group members to review and provide feedback on the L2 Transaction Fee API spec and L2 Transaction Statuses specification PRs.
+• Andreas to post meeting minutes and send updates to the Slack channel and email list.
+
+
+## Meeting Wed, 13 November 2024, 7:00 am PT
+
+Meeting canceled since PRs are collecting approvals and Devcon7.
+
+## Meeting Wed, 30 October 2024, 7:00 am PT
+
+Meeting canceled since PRs are collecting approvals.
+
+## Meeting Wed, 16 October 2024, 7:00 am PT
+
+Meeting canceled since PRs are collecting approvals.
+
 ## Meeting Wed, 02 October 2024, 7:00 am PT
 
 Joint Session with RollCall Group as a RollCall Breakout on L2 Transaction Statuses. Canceled due to lack of participation.