Avalanche Community Proposal Meeting 06-05-2024 (ACP-83) #96
meaghanfitzgerald
started this conversation in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
ACP-83 Meeting 06-05-2024
Meeting Date/Time: 06-05-2024, 15:30 UTC
Meeting Duration: 1 hour
Moderator: Meaghan FitzGerald
Purpose of the Meeting
In this meeting, we will discuss and determine the desired approach for an intended multidimensional fee scheme to be implemented for the P-Chain and X-Chain on Avalanche's Primary Network as proposed in ACP-83.
Who is invited?
Any protocol developer, ACP author, researcher, or Avalanche community member is invited to attend this meeting.
Links
Sign Up Form: Google Form
Youtube Link: video
Preparation Material
To ensure a high-quality discussion, please review the following materials prior to the meeting:
Mandatory
ACP-83 ReadMe
ACP-83 Discussion
Dominant Resource Fairness
Highly Encouraged
Dynamic Pricing for Non-fungible Resources
Approaches to Charging and Rate Control
Vitalik blog post on MDF
Agenda
Protocol engineers will present the research and experimentation that has thus far influenced the approach outlined in the ACP's ReadMe (linked above). Motivation for adding multidimensional will be explained, and an open discussion on this aspect of the protocol's design will be open for discussion.
Open Questions
With multiple dimensions, if one dimension changes it alters the fee paid by each transaction in the mempool and changes the amount leftover for the priority fee. How will the mempool maintain the ordering dictated by priority fees?
How will block building work in the new paradigm?
Notes
Meeting Notes Summary
ACP-83 will be divided to clarify validator signaling and network specifications.
Complex block-building features associated with multidimensional fees will be detailed in a separate ACP.
Building blocks based on Snowman++ raises questions about BFT’s necessity if mempool views vary.
Blocks should not only be accepted but also validated to ensure they don't violate resource constraints.
In the multidimensional fee case, blocks built by malicious clients with minimal transactions are valid but not optimal and could slow down the network.
Focus should be on preventing clients from building valid but inefficient blocks.
Such attacks should not be economically feasible by transactors.
Calculating priority fees is challenging due to the structure of UTXO chains (X/P-chains are UTXO based).
A base fee could be used, but priority fees can’t be calculated until a transaction is included in a block, this poses a challenge in a multidimensional fee environment.
An update mechanism based on an exponential curve allows oscillation around the target rate.
Larger forks will see more dramatic adjustments when resources (block space) are underutilized.
Dynamic fee would focus on tracking excess fees and applying them appropriately.
Useful Resources on dynamic fees based on external research
Action Items
Beta Was this translation helpful? Give feedback.
All reactions