Wormhole Foundation primary-source snapshot

Fetched: 2026-08-11 UTC

1) Wormhole Foundation homepage

Source: https://wormhole.foundation/

Selected excerpts from the site:

The Wormhole Foundation is dedicated to supporting open-source, decentralized technologies that securely and seamlessly connect Web3.

We support the development of Wormhole, the world’s leading blockchain interoperability platform.

We offer grants, research, and ecosystem programs to help a decentralized community of individuals and teams build the connective fabric of the new web.

Wormhole Foundation hosts one of the largest bug bounty programs in all of software development.

Additional signals from the site:

  • The Foundation presents itself as an active ecosystem steward with grants, research, and security-program responsibilities rather than as a thin legal shell
  • The homepage makes the Foundation the natural note for the ecosystem-program and bug-bounty boundary around Wormhole
  • This is useful taxonomy because those functions are organizational control surfaces that are not cleanly described by the protocol note alone

2) Wormhole protocol security docs

Source: https://wormhole.com/docs/ai/pages/protocol-security.md

Selected excerpts from the docs:

Governance is the process through which contract upgrades happen. Guardians manually vote on governance proposals that originate inside the Guardian Network and are then submitted to ecosystem contracts.

A two-thirds supermajority of the Guardians is required to pass any governance action.

All governance actions and contract upgrades have been managed via Wormhole’s on-chain governance system.

Wormhole Foundation GitHub organization

Additional signals from the docs:

  • The security docs are valuable because they separate Guardian signing authority from Foundation stewardship instead of treating Wormhole as a single undifferentiated actor
  • At the same time, the docs route readers to the wormhole-foundation GitHub organization, which shows that the Foundation is part of the canonical public implementation and documentation shell
  • The combination means the Foundation note should clarify the boundary rather than overstate admin-key control it does not appear to hold directly

3) Wormhole Guardian docs

Source: https://wormhole.com/docs/ai/pages/protocol-infrastructure-guardians.md

Selected excerpts from the docs:

Wormhole relies on a set of 19 distributed nodes called Guardians that monitor the state on several blockchains.

The current Guardian set can be seen in the Dashboard.

Security through reputation, not tokens: Wormhole relies on a network of established validator companies instead of token-based incentives.

Additional signals from the docs:

  • The Guardian docs make clear that operator trust sits partly in a named set of validator companies rather than in an abstract bridge mechanism
  • They also point readers to a Foundation-linked dashboard, reinforcing the Foundation’s role in publishing and framing the public operator picture around the protocol
  • This strengthens the case for a separate Foundation note whose job is to distinguish Guardian authority from foundation-hosted stewardship and presentation layers

4) Foundation-hosted core repository

Source: https://raw.githubusercontent.com/wormhole-foundation/wormhole/main/README.md

Selected excerpts from the repository:

This monorepo contains the reference implementation of the Wormhole protocol.

See operations.md for node operator instructions.

Additional signals from the repository:

  • The Foundation-branded GitHub organization is not just a brochure site; it hosts the reference implementation and operator-facing repository materials
  • That makes the Foundation note useful for questions about repo gravity, source-of-truth software distribution, and where builders will naturally look for canonical implementation guidance
  • Together with the Foundation homepage and protocol docs, the repo confirms that the Foundation boundary matters even though Guardian signatures remain the live governance threshold

Notes

  • This pass did not try to map Wormhole Foundation’s incorporation or board structure; the more useful result was clarifying the foundation-versus-Guardian boundary in primary materials
  • The strongest taxonomy value here is separating public stewardship, repo/docs authority, and ecosystem/security programs from the Guardian signer threshold that controls upgrades
  • The Foundation appears best categorized as the stewardship and ecosystem shell around Wormhole rather than as a synonym for the Guardian network itself