The SEC Central Party Test: Which Admin Powers Count
Quick answer. Under SEC staff FAQ 1.5 (November 2, 2026), a central party oversees participation when it has unilateral authority over access, voting processes, consensus or code. Those powers sit in pause, blacklist, upgrade, validator and forced transfer roles.
Video transcript
Four admin powers can make a crypto protocol a central party under the SEC's new staff FAQ. Each one maps to functions you can read onchain.
The Division of Corporation Finance added FAQ 1.5 on November 2, 2026. It reflects staff views, not a rule, and has no legal force. The legal call belongs to counsel.
A central party has unilateral authority to grant or limit access, change voting processes, control who validates, or modify code and reverse transactions. The test applies at any level, protocol, validator or user.
In code, that means pause roles and blacklists, upgrade keys over the governor or timelock, validator and sequencer sets, and proxy admins, forced transfers, admin burns and rescue functions.
There are two carve-outs. Every material aspect runs automatically by rules-based code, or discretion flows solely through broad-based governance. There is no emergency pause carve-out.
A team multisig is hard to fit within broad-based governance. Its signers are often affiliated, and a timelock in front of it adds notice, not independence.
Under FAQs 2.4 and 2.5, the staff's views on issuer statements and buyback announcements apply only once a functional system has no central party.
Build counsel a record from deployed contracts. Scope every contract, list each power, resolve every holder, mark each bypass of governance, and document the history.
Read the full article for the counsel checklist, or talk to Guardian about mapping your admin powers.
The SEC's March 17, 2026 interpretive release says a functional crypto system has no central party that oversees participation. It did not say what overseeing participation looks like.
On November 2, 2026, the Division of Corporation Finance answered in FAQ 1.5. The answers are staff views, not a rule, and have no legal force or effect.
FAQ 1.5's four examples map to functions you can read from deployed contracts. This post maps them and ends with an inventory for counsel.
This article explains the technical and security side of the SEC Division of Corporation Finance's crypto asset FAQs 1.4 to 1.6. It is not legal advice; confirm how it applies to you with counsel.
The Four Powers, in the SEC's Words
The release defines a central party as a person, entity or group with operational, economic or voting control of a crypto system.
FAQ 1.5 ties oversight to the authority to control access to the crypto system at any level: protocol, validator or user. It then gives four examples.
For example, a central party oversees participation in a crypto system when it has unilateral authority to:
- Grant or limit access to the crypto system;
- Determine or change the voting processes for software upgrades, protocol changes, or distributions of the crypto system's native crypto asset;
- Control who can participate in the consensus mechanism to validate transactions; or
- Modify the crypto system's rules-based code, reverse transactions, or revoke access to the crypto system.
Three phrases do the work.
- For example makes the list illustrative, not complete.
- Unilateral asks whether one person, entity or group can act alone.
- At any level reaches a token blacklist as well as an upgrade key.
Where Each Power Lives in Code
| FAQ 1.5 power | Functions and roles that grant it | Reference implementations |
|---|---|---|
| Grant or limit access | Pause, blacklists, allowlists, identity registries, address freezes | OpenZeppelin Pausable; Circle pauser and blacklister; ERC-3643 agents |
| Change voting processes | Governor settings and upgrade keys; timelock, mint and emission roles | OpenZeppelin GovernorSettings, TimelockController; Circle masterMinter |
| Control who validates | Validator, signer and sequencer sets; proposer and challenger roles | OP Stack Proposer and Challenger; Canton Super Validator admission |
| Modify code, reverse transactions, revoke access | Proxy admins, upgrades, forced transfer, admin burn, recovery, rescue | OpenZeppelin ProxyAdmin, UUPSUpgradeable; ERC-3643 forcedTransfer; Circle rescuer |
Access goes offchain. A relayer, keeper or sequencer the protocol depends on can also refuse a user's transactions.
Voting power sits one layer down. In an OpenZeppelin Governor, settings change only through governance.
But a team multisig that can upgrade the governor, timelock or vote token can change the process.
A team-held PROPOSER_ROLE or CANCELLER_ROLE on the governance timelock can route around or veto the vote.
Distributions count. Check who sets emissions, reward rates, airdrop roots and minter allowances.
Validator sets can be governed. In the Canton Coin request letter, a new Super Validator needs approval from at least two-thirds of the Super Validator node operators.
Meta-powers count too. Role admins can hand any power to anyone, and Safe modules can act without the owners' signature threshold.
The Two Carve-Outs
FAQ 1.5 ends with two cases in which a central party generally does not oversee participation:
- Automatic. Every material aspect runs automatically under rules-based code, without anyone's discretion.
- Governed. Any discretion is exercised solely through broad-based governance whose participants are not a central party.
The first fits an immutable design. It covers every material aspect, so one discretionary lever, such as a fee setter, must qualify under the second.
The second turns on solely: no team multisig with the same role, no outside proposer or canceller, no Safe module, no upgrade key over the governor.
There is no carve-out for emergency powers. A guardian that can pause alone fits the description of unilateral authority to limit access; whether a narrow pause is material is for counsel.
See our post on security work after launch for narrow emergency designs, and our GENIUS Act comparison for freezes the law requires.
Multisigs and Broad-Based Governance
Footnote 2 to FAQ 1.4 defines broad-based governance. Each part of it can be checked onchain.
| Footnote 2 test | What to check onchain |
|---|---|
| Transparent | Public proposals and payloads; verified source; execution linked to the vote |
| Rules-based | Governor, timelock and vote token change only through governance |
| Wide and diverse | Voting power by delegate, including team, investor and foundation delegations |
A team multisig is hard to fit within that definition. FAQ 1.4's group view covers participants who are not affiliated; signers who all work for one team are affiliated.
A timelock in front of a multisig adds notice, not independence. Users get time to exit, but the decision is still the multisig's.
Counsel will ask who the signers are, their affiliations, the threshold, and whether a module or role admin can act without them.
Footnote 4 adds that a foundation could itself be a central party over another crypto system. Our foundation post covers it.
Why It Matters: FAQs 2.4 and 2.5
Two staff views apply only once a functional system has no central party:
- FAQ 2.4: issuer statements likely would not create a new investment contract.
- FAQ 2.5: a buyback announcement would not be a promise to undertake essential managerial efforts.
The staff added the no central party condition to FAQ 2.5 on September 28, 2026.
So a live upgrade key or a team-held pause role is a fact counsel needs before a buyback announcement.
For how live protocols hold these powers, see our admin keys census of 25 of the largest protocols.
An Inventory to Hand Your Counsel
Counsel owns the legal reading; engineering owns the facts. Build the record from deployed contracts, and stamp each item with a block number or date.
- Scope. Every contract on every chain, with verified source, plus offchain dependencies.
- Access powers. Every pause, blacklist, allowlist and freeze, its holder, and who can unpause.
- Voting-process powers. Governor settings, timelock roles, upgrade keys over governance, emission setters.
- Consensus powers. Who can add or remove validators, signers or sequencers, and by what rule.
- Code and reversal powers. Proxy admins, forced transfer, admin burn, recovery and rescue.
- Meta-powers. Role admins, owners that reassign roles, Safe modules and guards.
- Holders. EOA, multisig, timelock or governor; flag every foundation, issuer or affiliate role. Follow nesting to the end.
- Bypasses. Every power one person, entity or affiliated group can use without a vote.
- Governance record. Where proposals, votes and execution are published; how concentrated delegation is.
- History and plan. Role grants and upgrades since launch, and each planned hand-off with a date.
How Guardian Maps Admin Powers
Guardian's regulatory and compliance work produces this record as technical evidence.
Our privileged role and upgrade path map covers every role that can move value, upgrade, pause, freeze or change parameters, with its holder, threshold and timelock.
Contract configuration drift dates every change to roles, parameters and upgrades. After a hand-off, Managed Security watches every block for privileged calls and upgrades.
The legal reading stays with your counsel.
Frequently Asked Questions
What is a central party under the SEC's crypto guidance?
The March 17, 2026 interpretive release defines it as a person, entity or group with operational, economic or voting control of a crypto system. FAQ 1.5 adds four examples of unilateral authority.
Does a multisig make a protocol centralized under FAQ 1.5?
The FAQ does not mention multisigs. One that holds a listed power and can act without a governance vote resembles the unilateral authority it describes, particularly with affiliated signers. Counsel makes the call.
Is an emergency pause a central party power?
FAQ 1.5 has no emergency carve-out, so a pause held by a team or guardian multisig belongs in the inventory. Whether a narrow, time-limited pause is material is a legal judgment.
Are the SEC crypto FAQs binding?
No. They are Division of Corporation Finance staff views, not a rule, regulation or statement of the Commission, with no legal force or effect.
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)
- OpenZeppelin Contracts: Pausable, AccessControl, GovernorSettings, TimelockController, ProxyAdmin and UUPSUpgradeable source
- Circle: FiatToken design (stablecoin-evm)
- Ethereum Improvement Proposals: ERC-3643, T-REX Token for Regulated EXchanges
- Optimism Docs: Privileged Roles in OP Stack Chains
- Safe: IModuleManager.sol
Map your admin powers with Guardian
Guardian reads every privileged role, holder, threshold and timelock from your deployed contracts, so counsel works from a dated record instead of documentation.