Skip to content

ACP-275: L1 Trust Profile Framework#275

Open
iJaack wants to merge 3 commits intoavalanche-foundation:mainfrom
iJaack:acp-274
Open

ACP-275: L1 Trust Profile Framework#275
iJaack wants to merge 3 commits intoavalanche-foundation:mainfrom
iJaack:acp-274

Conversation

@iJaack
Copy link
Contributor

@iJaack iJaack commented Feb 18, 2026

Summary

This ACP proposes a standardised, neutral methodology for describing the trust characteristics of Avalanche L1 blockchains across four independent dimensions:

  1. Validator Control — who decides validator entry and exit
  2. Validator Distribution & Bridged Asset Security — how concentrated validator operation is, and what that means for bridged asset risk under ICM's 67% BLS threshold
  3. Censorship Resistance — whether a controlling party can selectively exclude or delay transactions
  4. Governance Transparency — how visible and predictable upgrade processes are

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

@iJaack iJaack closed this Feb 18, 2026
@iJaack iJaack deleted the acp-274 branch February 18, 2026 23:46
@iJaack iJaack changed the title ACP-274: L1 Trust Profile Framework ACP-275: L1 Trust Profile Framework Feb 18, 2026
@iJaack iJaack restored the acp-274 branch February 18, 2026 23:48
@iJaack iJaack reopened this Feb 18, 2026
@iJaack iJaack closed this Feb 18, 2026
@iJaack iJaack deleted the acp-274 branch February 18, 2026 23:48
@iJaack iJaack restored the acp-274 branch February 18, 2026 23:50
@iJaack iJaack reopened this Feb 18, 2026
@iJaack
Copy link
Contributor Author

iJaack commented Feb 18, 2026

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 acp-274..

Copy link
Contributor

@Nuttymoon Nuttymoon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO there is a problem with the labels:

  • The difference between Muti-Party and Multi-Stakeholder looks subjective. It is complicated to reason about it if the threshold depends on each dimension
  • A network could be Open and yet be SP, MP, or MS at a given point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants