ACP-275: L1 Trust Profile Framework#275
Open
iJaack wants to merge 3 commits intoavalanche-foundation:mainfrom
Open
ACP-275: L1 Trust Profile Framework#275iJaack wants to merge 3 commits intoavalanche-foundation:mainfrom
iJaack wants to merge 3 commits intoavalanche-foundation:mainfrom
Conversation
Contributor
Author
|
Sorry, I was 100% sure that this had to be ACP-274 but it seems like I got it wrong, so the name of the ACP is still 275, but the branch is |
Nuttymoon
reviewed
Feb 19, 2026
Contributor
There was a problem hiding this comment.
As I have expressed in a previous discussion, my stance is that having L1 stages and a logical progression between them would be best.
I also fear that the 4x4 profile proposed would be hard to reason about for both L1 teams and users.
At Suzaku, we've been working internally on gathering data about all L1s and classifying them following the criteria and stages I laid out in the comment linked above. We'll share the results soon.
Comment on lines
+90
to
+93
| | **SP** | Single-Party | One entity | | ||
| | **MP** | Multi-Party | Small known group (2–5) | | ||
| | **MS** | Multi-Stakeholder | Broad community / many parties | | ||
| | **OP** | Open | No human gating; protocol-determined | |
Contributor
There was a problem hiding this comment.
IMO there is a problem with the labels:
- The difference between
Muti-PartyandMulti-Stakeholderlooks subjective. It is complicated to reason about it if the threshold depends on each dimension - A network could be
Openand yet beSP,MP, orMSat a given point
…dd Censorship Resistance, relabel SP/MP/MS/OP, add Board bootstrap, change-triggered review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This ACP proposes a standardised, neutral methodology for describing the trust characteristics of Avalanche L1 blockchains across four independent dimensions:
Each dimension is scored using four labels — SP / MP / MS / OP (Single-Party, Multi-Party, Multi-Stakeholder, Open) — all describing the same axis: who holds effective authority over that dimension, from most concentrated to fully open.
The framework produces a 4-dimensional profile per L1. No composite score, no ranking, no prescription. Different L1s have different goals; the framework describes, it does not judge.
Board & Process
Governance and scoring is coordinated by an L1 Trust Profile Board (5–7 members), with explicit conflict-of-interest disclosure rather than exclusion. A bootstrapping process is defined: the Avalanche Foundation nominates the initial Board within 30 days of adoption, with community ratification via Snapshot within 60 days.
Reviews are both annual (full re-assessment of all active L1s) and change-triggered (expedited within 30 days when an L1 makes a material change to validator policy, operator composition, bridging, or governance).
Track Note
This ACP is filed as Best Practices to reflect its non-protocol-changing, informational nature. Given its methodological and procedural scope, the community may wish to consider whether Standards Track is more appropriate.
Credits
Thanks to the AVAX Economics Working Group, especially to @Nuttymoon and @selim5335