When a Crypto Foundation Is a Central Party

Video transcript

Can a crypto foundation be a central party? In the SEC staff's view, yes, under footnote 4 to FAQ 1.4, added November 2, 2026.

A foundation housing broad-based governance could itself be a central party if it has operational, economic or voting control over another crypto system, like setting parameters for applications built on it.

In contracts, operational means upgrades, pauses, listings and oracles. Economic means fees, risk parameters and treasury spending. Voting means proposal and veto roles.

Look for keys a foundation can use without a vote: risk and listing setters, oracle admins, fee switches, treasury multisigs, emergency guardians, and proxy and role admins.

A timelock gives users time to exit, but the decision stays with the multisig. If every signer is a foundation affiliate, the power has not moved.

The hand-off starts with an inventory of every role. Classify each one, and remove what needs no decision. Move discretion to the governance timelock in one proposal, then publish and monitor.

Funding is separate from control. Under FAQ 2.3, paying for security after launch is not essential managerial effort. Use a governance-approved budget and keep vendors off the role list.

This is the technical side, not legal advice, so confirm with counsel. Read the full article, or book a system review to find the keys your foundation still holds.

Since November 2, 2026, the crypto foundation central party question has a footnote.

FAQ 1.4 says broad-based governance participants are generally not a group that could be a central party, even when governance sits inside a foundation. Footnote 4 then turns to the foundation itself.

A foundation may sign for a treasury, set parameters, approve grants or hold emergency keys. This post sorts those powers and sets out a hand-off plan.

This article explains the technical and security side of SEC Division of Corporation Finance FAQ 1.4 and its footnote 4. It is not legal advice; confirm how it applies to you with counsel.

What FAQ 1.4 and Footnote 4 Say

FAQ 1.4 says governance participants generally are not a group if they are unaffiliated and have no agreement to act in concert outside governance.

The answer is the same where governance is part of a foundation and participation is based on holding the native crypto asset. Footnote 4 is attached to that sentence.

Such an organization, association, or foundation itself could be a central party where it has operational, economic, or voting control over another crypto system.

For example, it might set the operational parameters for one or more crypto applications deployed on the functional crypto system.

Four points of reading:

• Such means the foundation that houses governance, not the token holders who vote through it.
• Another crypto system points to control beyond the system the foundation governs, such as an application.
• Could be sets no bright line. It is facts and circumstances.
• Left open: what operational parameters are, and whether control over an application affects the base asset.

If a foundation directly controls the functional system itself, the ordinary central party definition already applies.

These are staff views with no legal force or effect. They interpret the Commission's March 17, 2026 interpretive release, Release No. 33-11412.

The SEC's example in practice

In contract terms, picture a chain's foundation holding listing, fee or cap roles on a lending market, exchange, bridge or staking product built on that chain.

On the footnote's reasoning, that foundation could be a central party for the application, even if the chain's own governance is broad-based.

The Canton Coin request letter of October 30, 2026 shows one foundation as described to the staff. It said the Canton Foundation is only one of the 13 Super Validator Node Operators, and its committees cannot dictate protocol changes.

The staff's November 3 response relied on the letter's representations, including that the network has no central party. See our Canton Coin explainer.

Operational, Economic and Voting Control

The three kinds of control come from the release's central party definition. In contracts, each maps to functions you can name.

These are role definitions from public code. Who holds a role in a given deployment must be read from the chain.

They line up with the four powers in FAQ 1.5, which our central party explainer covers function by function.

The Foundation Keys to Look For

Look for keys a foundation can use without a governance vote.

• Risk and listing setters. Collateral factors, borrow caps, liquidation incentives and listed assets.
• Oracle admins. Whoever controls the oracle controls every liquidation that depends on it.
• Fee switches. In Uniswap v3, only the factory owner can set and collect the protocol fee.
• Treasury and grant multisigs. Funding work is not the problem; unilateral spending keys can be.
• Emergency guardians and cancellers. A foundation that can cancel a passed proposal can veto governance.
• Proxy and role admins. They can upgrade the code or grant any role above, including to themselves.

What Makes a Foundation Key Unilateral

Where a foundation key sits in a multisig, four facts matter.

1. Signers. If every signer is a foundation director, employee or contractor, it is the foundation's key.
2. Modules. Safe's docs say modules have unlimited access to a Safe. Each is a path around the threshold.
3. Timelocks. A delay gives users time to exit. That is notice, not independence.
4. Pairing. A key that cannot act without an independent party is a different fact.

Optimism's docs give a paired example: the L1 Proxy Admin owner is a 2-of-2 of an Optimism Foundation 5/7 multisig and the Security Council multisig.

For how roles like these are held across live protocols, see our admin keys census of 25 of the largest protocols.

A Hand-Off Plan for Foundation Keys

1. Inventory. Every role the foundation, its directors and contractors hold, on every contract and chain.
2. Classify. Operational, economic or voting; automatic, discretionary or emergency.
3. Remove what needs no decision. Renounce it, hard-code bounds, or replace a setter with a formula.
4. Move discretion to governance. Grant the role to the governance timelock and revoke the foundation's copy in one proposal.
5. Narrow what must stay fast. Make emergency roles pause-only, let only governance unpause, and add an expiry.
6. Remove bypasses. Disable modules on Safes governance relies on; make the timelock every role admin.
7. Separate funding from control. Pay for audits, bounties and monitoring from a governance-approved budget.
8. Publish and watch. Publish each change with transaction hashes, then monitor for new grants.

Funding is a different question from holding keys. Under FAQ 2.3, once a system is functional, services to secure, maintain, improve or enhance it would not involve essential managerial efforts.

Keep vendors off the role list. See our post on security work after launch.

Then give counsel one row per role, read from the chain and dated.

How Guardian Helps

A system review call is an hour with a Guardian engineer on what you actually run, and who holds the keys that can change it.

For the full record, our regulatory and compliance work maps every privileged role with its holder, threshold and timelock, read from deployed contracts.

Your counsel owns the legal reading.

Frequently Asked Questions

Can a crypto foundation be a central party under the SEC FAQs?

Yes, in the staff's view. Footnote 4 to FAQ 1.4 says a foundation housing broad-based governance could be one where it has operational, economic, or voting control over another crypto system.

Does housing governance in a foundation make token holders a group?

Generally not, if participants are unaffiliated and do not act in concert outside governance. FAQ 1.4 gives the same answer where governance sits in a foundation and participation is based on holding the native asset.

Is a timelock on a foundation multisig enough?

A timelock gives users notice and time to exit, but the decision is still the multisig's. If every signer is a foundation affiliate, the power has not moved.

Can a foundation keep funding security after a hand-off?

Under FAQ 2.3, once a system is functional, services to secure, maintain, improve or enhance it would not involve essential managerial efforts. Pay through a governance-approved budget and keep vendors off the role list.

Sources

• SEC Division of Corporation Finance: Frequently Asked Questions on the Application of the Federal Securities Laws to Certain Types of Crypto Assets (issued Sept. 25, 2026; updated Nov. 2, 2026)
• Federal Register: Release No. 33-11412, Application of the Federal Securities Laws to Certain Types of Crypto Assets, 91 FR 13714 (Mar. 23, 2026)
• SEC (incoming letter): Request on behalf of Digital Asset Holdings, LLC regarding Canton Coin (Oct. 30, 2026)
• SEC Division of Corporation Finance: Canton Coin, no-action letter (Nov. 3, 2026)
• Aave: aave-v3-core ACLManager.sol
• Uniswap: v3-core UniswapV3Pool.sol
• Compound: Comptroller.sol
• OpenZeppelin Contracts: TimelockController.sol
• Safe: IModuleManager.sol
• Optimism Docs: Privileged Roles in OP Stack Chains