Tokenomic Alignment with L1 Growth and Architecture #246
Replies: 3 comments 2 replies
-
|
Regarding (3) above: Note that the for the 0.000001% of total C-Chain Stake weight multiplier for fee basis, although seems to be a good approximation, this could be further refined from a linear multiplier to something that more formulaically approximates the marginal benefit to base chain security/value of adding the additional validation/stake weight at scale , such that marginal increases in total stake weight have a diminishing effect at scale. An asymptotic or logarithmic function likely best approximates marginal value at scale. |
Beta Was this translation helpful? Give feedback.
-
|
As this progresses, it is likely best to focus first on a simplified version of this ACP that moves forward parts (1) and (3), or to even break those up for separate consideration also. So in its minimal prioritized form, I believe (1) (fees directed to validator/stake rewards) is the simplest and most essential starting point. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, thanks for taking the time to write this up. I would like to better understand how you imagine some of the details working in practice. Regarding (1), the shift from burning fees to directing them to validator rewards, I think your logic broadly holds at the system level: if governance can dial down inflationary emissions as L1 fee flows grow, the net effect can absolutely be neutral or even deflationary. The challenge I see is less about the mechanics and more about the narrative and game-theory for non-validating AVAX holders. Today the “AVAX burn” story is extremely simple and powerful from a market perspective. Replacing a significant portion of that with rewards that end up as sellable tokens in validator hands will inevitably be perceived by some as structurally more inflationary, even if the macro accounting is more subtle. Have you thought about preserving a guaranteed, non-trivial burn floor that is harder to change via governance, and only redirecting the marginal portion of L1 fees to validators as in (1)? That could help reconcile the “sound money / deflation” crowd with your goal of tying L1 activity directly to staking rewards. Some simple numeric scenarios “before vs after” (net issuance, burn, validator APR) under different L1 volume regimes would probably help a lot to make (1) more digestible. A second concern touches both (1) and your general framing of how this evolves over time. You are implicitly assuming a trajectory where L1s grow strongly, so that their fees become an increasingly large share of validator rewards, which in turn allows emissions to be reduced. I agree this is the ideal path. But what happens in less optimistic scenarios where L1 growth is slower, more cyclical, or where a non-trivial share of important L1s end up with disjoint validator sets and low on-chain activity from the point of view of AVAX fee flow? If we have already reduced burn and redirected fee flows along the lines of (1), but L1 volume does not materialise as hoped, we could end up in an awkward situation: lower burn than today, similar or higher emissions because governance is slow to cut, and not enough L1-based rewards to compensate. Do you imagine any guardrails or thresholds here, such as only increasing the share of fees going to validators once certain L1 revenue or activity metrics are sustainably reached? On (3), the idea of changing from a static baseline fee (like 1.33 AVAX) to a fee set as a percentage of total main-chain stake weight is conceptually very elegant. L1s pay more as the security they are effectively “buying” improves, and less when the quality of security decreases. That is a clean mental model. In practice, though, there are a few potential pitfalls that might require more explicit treatment. If fee levels and baseline are tied too directly to total stake, L1 cost structures might fluctuate for reasons that have nothing to do with their own usage or behaviour, such as a large validator entering or leaving, or market cycles affecting staking behaviour. That introduces volatility that is difficult to plan around for serious builders. There is also a possible feedback loop: if fees from L1s become a big component of validator rewards and stake declines, security drops, L1s pay less by design, rewards shrink, and that can further discourage marginal validators. Finally, the more tightly fees are coupled to stake as in (3), the stronger the incentive for large stakers to push the parameters in directions that benefit them through governance. You mention hysteresis, which is the right instinct, but I would be interested in how concretely you imagine that meta-layer being implemented for (3): for example, updates only every N epochs, caps on how fast the fee baseline can move, and using moving averages of stake instead of raw snapshots. Your points on validator specialisation and L1s directing fees to a subset of main-chain validators chosen from the AVAX-staked set (and then optionally adding their own emissions on top, as described later in your text and in (5)) are, à mon sens, some of the most powerful parts of the proposal. This gives L1s a proper market mechanism to attract validators that match niche requirements in terms of uptime, hardware, geography, compliance constraints, or even “soft exclusivity” (main chain plus only a limited set of L1s). At the same time, this also opens the door to a more stratified validator landscape where well-capitalised, compliant, institutional operators systematically capture the richest reward streams and progressively accumulate more influence. That may be a necessary trade-off if Avalanche wants to be truly “institutional-grade”, but I would be curious whether you see this outcome as acceptable, or whether you think it should be counterbalanced by transparency and soft guardrails, for example via public metrics on income distribution per L1 and per validator, or some attention to concentration risks. It would be interesting to know how you view these second-order effects around (5) and its variants. On the idea you sketch about requiring the additional incentives in (5) to be provided as LP pairs (for example, native gas token plus USDC or AVAX), I think there is a lot of potential but also quite a bit of complexity. It is attractive in that it could help turn the main chain into a stronger liquidity hub and further align AVAX holders with the success of individual L1s and their tokens. On the other hand, it adds another layer of design choices for L1 teams, who must now think about pools, impermanent loss, and which pairs to use, on top of everything else. I would be interested to hear whether you see the LP-pair variant as a strong recommendation, a soft “nice to have”, or something that should be kept out of the MVP scope you mention at the end in order not to overload the initial ACP. The PAYG degressive structure you propose toward the end, where the marginal validator fee decreases as the size of an L1 validator set increases, is a very neat way to incentivise decentralisation without making large sets prohibitively expensive. It fits nicely with the rest of the design. That said, here too, I think the community will want a bit more clarity on how you picture the shape and governance of that curve. Do you imagine the form of the PAYG curve (how fast costs per validator decline, where it asymptotes) to be fixed or configurable, and what “target region” in terms of validator counts do you have in mind for more public L1s versus explicitly private ones? Since this is partly meant to change behaviour, a simple example or even just an order-of-magnitude sketch would really help others understand what (in practice) you are trying to nudge L1s toward. Stepping back from the individual points, one last aspect concerns the overall complexity of the full package formed by (1), (3), (5) and the other refinements you mention. For advanced or institutional L1s, this “menu” of options is probably ideal: dynamic fees as a function of security, routing choices between burn and validator rewards, specialisation of validator subsets, optional additional emissions in different asset forms, and a PAYG curve aware of validator set size. For many teams, though, this is a lot to absorb and reason about. It might be useful to explicitly distinguish a simple “default mode” from an “advanced mode”: a base configuration with opinionated, safe defaults where an L1 can essentially plug in and go without deep economic design work, and then a second, opt-in layer where all the knobs from (1), (3), (5) and the PAYG refinements become available for sophisticated projects. You already hint at splitting parts (1) and (3) into separate ACPs; sharpening that into a clear layering strategy would probably make it easier for the community to evaluate and iterate. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been working on a much more comprehensive set of ACPs around AVAX tokenomics (and specifically, its alignment with L1 ecosystem) which I plan to introduce when ready at MVP level, but separately want to propose a few related ideas to improve the alignment of the $AVAX token value:
Note: Current validator count (and weight) has fallen from a peak of over 1,860 to under 800 (weight from over 230M AVAX to apx. 150M AVAX) recently, and has been trending down, which is a concern for security and ecosystem health. By directing the growing fees from L1 adoption to reward the main validator set, we create a market/natural incentive mechanism for validators (and stakers) to participate in the health of the network.
A more nuanced version of this would allow the allocation of L1 fees to be split (and governance configurable, subject to hysteresis dynamics) between burn and direct validator incentivization. However, this may not be necessary/beneficial, since total emissions is already governable, and L1 fees can be an input to that governance decision.
Change from the current statically-determined fee mechanism (e.g., 1.33 AVAX, etc.) to instead be set (again, subject to some hysteresis meta-configuration dynamics) dynamically as a percentage of the total validator stake weight on the main chain. This now directly aligns the L1s with the quality of security (a mutual benefit/goal) they are receiving by participating in the Avalanche ecosystem, via simple market dynamics. For example, current total stake weight of C-Chain is apx. 150M AVAX. If we say that the baseline L1 fees are to be 0.000001% of total C-Chain Stake weight, this results in a 1.5 AVAX baseline fee by current metrics. If main chain security/quality decreases because we lose stake weight, then L1s pay less for the lower quality product. But as C-Chain stake weight increases, they pay more for the better quality network. (We would also keep, in tact, the current mechanism to scale fees formulaically from this baseline, based on L1 scale thresholds.) This mechanism works in conjunction with (1) above (fees going to validators), so as to keep rewards proportional to overall main chain validation growth to avoid reward dilution.
If we want to be truly institutional-grade, our main chain should aspire to this growth. The current decline in main-chain validation and stake weight needs to be reversed.
Note that more nuanced discussion can occur around other variables/dynamics that could enhance token/value alignment with L1 fee structure (and I have draft ACPs on this topic, not yet published), but this above dynamic can be introduced as a component independently and separately.
A final note: There are variants of the above dynamics, as well as a lot more detail (much of which I am drafting separately), but the intent of the above is to provide a minimum-viable introduction appropriate for this "ideas" phase of the ACP process, erring on the side of brevity to facilitate community discussion.
Beta Was this translation helpful? Give feedback.
All reactions