Protocol Guild primary sources
Collected: 2026-05-10 UTC
Primary sources reviewed
- https://www.protocolguild.org/
- Official landing page
- Used as the canonical project identity and public-facing funding surface
- https://protocol-guild.readthedocs.io/en/latest/index.html
- Official documentation homepage
- Key points used: defines the three-part mechanism as eligibility framework, member registry, and onchain donation contracts; frames Protocol Guild as collective funding for Ethereum layer-1 R&D maintainers
- https://protocol-guild.readthedocs.io/en/latest/01-membership.html
- Membership and eligibility docs
- Used to confirm the category structure (wayfinding, governance, client implementations, upgrade delivery), the self-curated contributor model, and the fact that registry maintenance follows roadmap and working-group evolution rather than static project labels
- https://protocol-guild.readthedocs.io/en/latest/02-onchain-architecture.html
- Smart-contract architecture docs
- Used to confirm the modular funding stack: immutable vesting contracts → pass-through wallets → split contracts → DAO ratification / multisig operations
- https://github.com/protocolguild/documentation
- Canonical docs repository
- Used to confirm that the documentation surface itself is maintained as a living mechanism reference and has been materially updated for newer PG versions
- https://raw.githubusercontent.com/protocolguild/documentation/main/README.md
- Repo-level overview of the docs project
- Used for provenance and current-maintenance signal
- https://raw.githubusercontent.com/protocolguild/documentation/main/docs/01-membership.md
- Raw markdown source for membership rules and active working-group structure
- Useful because it exposes the practical registry-maintenance logic directly rather than only through rendered docs
- https://raw.githubusercontent.com/protocolguild/documentation/main/docs/02-onchain-architecture.md
- Raw markdown source for contract architecture, DAO, and multisig details
- Useful for verifying where authority sits across vesting, pass-through, split, DAO, and multisig modules
Notes
- Protocol Guild’s real mechanism is not “donations for core devs”; it is an evolving contributor-legibility system that decides which labor qualifies and how that labor receives durable funding rights.
- The most important control surface is the registry and its update process. Immutable vesting minimizes donor-side redirection risk, but mutable membership and weight updates still determine who actually gets paid.
- The architecture matters because it separates irreversible donation flow from governance-over-registry: vesting contracts constrain redirection, while split weights, DAO procedures, and multisig operations still shape operational control.
- This entry belongs in the corpus because it is a clean comparison class for curated contributor funding, especially against Moloch-style treasury governance, Drips-style flow-based distribution, and grants-program application systems.