Solana ships technical capabilities that older law did not anticipate. A program can be upgraded after deployment. A token can carry a confidential balance, an interest-bearing display, a permanent delegate, or a transfer fee. A non-fungible asset can be compressed into a Merkle leaf for a fraction of a cent. A validator could be penalized by a future protocol rule. This paper puts one question to each mechanism: what legal consequence does the on-chain fact create, and under which regulator? It answers under the law of the United States, the European Union, and Brazil, together with the gaps that none of those regimes closes, current as of June 2026. One finding organizes the rest. Authority on Solana is legally legible yet not legally dispositive. A retained upgrade, mint, or freeze authority is strong qualitative evidence of the managerial efforts that can render a token a security, but no court or regulator has fixed a numeric threshold at which decentralization defeats that conclusion.

1. EXECUTIVE SUMMARY

The legal status of a Solana product follows from two reads, not from the name of a feature. The first read is the on-chain control surface: who can still upgrade the program, mint supply, or freeze accounts, and whether those authorities have been renounced. The second read is the off-chain promise, meaning what the issuer told the market it would do. United States securities law, the EU’s MiCA regime, and Brazil’s virtual-asset framework converge on a functionally identical efforts-of-others test, and each declines to set a numeric decentralization threshold. That shared silence is the sharpest cross-jurisdiction finding in this paper. Renouncing an administrative authority is the strongest and most verifiable defense a builder has, yet it operates as evidence, not as a safe harbor.

Two instruments reshaped the United States analysis in the year before this writing. The March 2026 SEC interpretive release recast the inquiry around “essential managerial efforts” and placed SOL among network assets outside the security definition, while framing the moment a token leaves an investment contract as a separation keyed to the issuer’s own representations (SEC Release Nos. 33-11412; 34-105020, 91 Fed. Reg. 13714 (Mar. 23, 2026)). The GENIUS Act set an issuer-level, reserve-backed regime for payment stablecoins (Pub. L. 119-27, 139 Stat. 419 (July 18, 2025)). Neither ties a specific on-chain key to a securities outcome, so the paper treats the architecture-defeats-securities thesis as commentator inference throughout.

The Solana-specific surface then divides into clean problems. Each Token-2022 extension carries its own classification risk. A compressed NFT tests the boundary of the MiCA unique-asset exclusion and the U.S. copyright writing requirement. Liquid staking sits inside a 2025 SEC staff safe harbor whose carve-outs decide most real cases. Interface and governance liability turns on a narrow Fifth Circuit holding and an unresolved criminal docket. Stablecoins, grants, validator economics, and account-closure mechanics each carry a distinct tax or licensing footprint. The paper closes by turning the analysis into a tool, a skill that reads the on-chain control surface and emits graded, counsel-gated risk signals rather than verdicts.

2. INTRODUCTION AND METHODOLOGY

This paper builds the legal foundation for a production-grade skill for Solana builders, an agent skill that reads the on-chain control surface and emits graded risk signals. The skill integrates with the Solana AI Kit and runs independently of it. The object of study is the set of Solana-native technical mechanisms that carry legal weight. The subject is how those mechanisms are classified under securities, payments, privacy, tax, and intellectual-property law, across the United States, the European Union, and Brazil. The method is doctrinal. Each mechanism is traced to the primary instruments that govern it.

Two conventions run through the analysis. First, United States securities treatment is bifurcated by date, because the March 2026 SEC release changed the controlling framework; claims are pinned to the version in force as of June 2026. Second, each substantive claim carries a confidence label. HIGH marks black-letter law with aligned regulator guidance. MEDIUM marks a rule whose interpretation is still moving. LOW marks an active split or regulatory silence. STUB marks a question on which no primary authority exists, where the law has not yet spoken. Much of the Solana-specific surface sits at MEDIUM or below, and the paper says so plainly rather than manufacturing certainty.

This is informational analysis, not legal advice, and it creates no attorney-client relationship. A builder should retain qualified counsel in the relevant jurisdiction before acting on anything below.

3. ON-CHAIN AUTHORITY AND THE HOWEY TEST

When a Solana builder retains the power to upgrade a program, mint new supply, or freeze a holder’s account, does that retained power make the token an investment contract? The question lives almost entirely in one part of the Howey test, and the law that answers it is qualitative. No U.S. court and no SEC release has set a numeric decentralization threshold as of June 2026, and no foreign regulator has done so either.

Figure 3.1. On-chain control feeds the Howey efforts-of-others element.

The test and where on-chain authority fits

Howey defines an investment contract through a four-element inquiry: an investment of money, in a common enterprise, with a reasonable expectation of profits, derived from the essential managerial or entrepreneurial efforts of others (SEC v. W.J. Howey Co., 328 U.S. 293, 298-99 (1946)). The fourth element does the work here. The Ninth Circuit long ago read “solely from the efforts of others” to mean efforts that are “undeniably significant” and affect the enterprise’s success (SEC v. Glenn W. Turner Enters., 474 F.2d 476, 482 (9th Cir. 1973)). On-chain authority is a factual input to that element. Whether an active party can still mint supply, freeze balances, or rewrite program logic is direct evidence of whether holders depend on someone’s continuing efforts.

The March 2026 SEC interpretive release does not enumerate upgrade, mint, or freeze authority as discrete factors, and nothing in it ties those on-chain powers to a labeled “prong four” (SEC Release Nos. 33-11412; 34-105020 (File No. S7-2026-09), 91 Fed. Reg. 13714 (Mar. 23, 2026), FR Doc. 2026-05635).1 The authority analysis reaches Howey only through the general standard of essential managerial efforts, and the mapping below is reasoned inference, not black-letter holding.

Retained authority as evidence of managerial efforts

A retained, non-renounced program upgrade authority held by an active team is the strongest single on-chain fact pointing toward an investment contract. The team can unilaterally rewrite the program at any time, so a holder’s return stays tethered to ongoing development. That pattern tracks the cases. LBRY found that capital-raising to develop and operate a network created a reasonable expectation of profit from the issuer’s efforts (SEC v. LBRY, Inc., 2022 WL 16744741, at 5-6 (D.N.H. Nov. 7, 2022)). Coinbase* held, at the pleading stage, that an issuer’s ongoing protocol development and ecosystem promotion adequately alleged reliance on managerial efforts (SEC v. Coinbase, Inc., 726 F. Supp. 3d 260, 296-310 (S.D.N.Y. 2024)). A live loader-v3 upgrade authority paired with a public roadmap is close to the fact pattern those courts found sufficient. Confidence here is MEDIUM. No court has adjudicated upgrade authority as such, and Coinbase spoke only to the sufficiency of pleadings.

Renouncing the authority cuts the other way. Setting the upgrade authority to None via the BPF Loader Upgradeable SetAuthority instruction (the --final flag) makes a program permanently immutable and removes the lever (Solana Program Library documentation, BPF Loader Upgradeable, set-upgrade-authority --final, as of June 2026). Mint and freeze authority behave the same way under the SPL Token and Token-2022 programs: SetAuthority to None irreversibly disables minting or freezing (Solana Program Library, SPL Token SetAuthority semantics, as of June 2026). A retained mint authority lets an active party dilute holders without limit; a retained freeze authority lets it immobilize any account. Both are managerial powers in substance. The treatment is unsettled. No court has individually adjudicated mint or freeze authority under Howey, so the linkage is reasoned rather than holding-backed, and the confidence on this specific mapping is LOW.

A caution that the entire article carries: the thesis that renounced authority or decentralization defeats securities status is commentator inference, not a regulatory holding. No primary authority states that immutability is per se dispositive. Renouncement is the strongest available defense and, because it is verifiable on-chain, the most objective one. It is not a safe harbor.

The 2026 release and the separation framework

The March 2026 release withdrew and superseded the 2019 FinHub Framework and established a token taxonomy. It also named SOL among network or digital-commodity assets whose value derives from programmatic operation rather than managerial efforts (SEC Release Nos. 33-11412; 34-105020 (File No. S7-2026-09), 91 Fed. Reg. 13714 (Mar. 23, 2026)). For a Solana-issued SPL token, the operative question is no longer whether the token sits on Solana. It is whether the issuer retains managerial authority and made promises tying the token’s value to its own efforts.

The release reframes when an asset stops being subject to an investment contract. Rather than the older open-ended rhetoric of “sufficient decentralization” associated with the 2018 Hinman remarks (now superseded), the analysis follows a separation framework keyed to the issuer’s own representations. Separation can occur through fulfillment, where the issuer completes the developmental efforts it promised, or through failure to satisfy, where the issuer publicly abandons or fails to deliver them (SEC Release Nos. 33-11412; 34-105020 (File No. S7-2026-09), 91 Fed. Reg. 13714 (Mar. 23, 2026)). Decentralization is assessed against the issuer’s stated definitions, not a market consensus. This is a MEDIUM-confidence reading of the release. Renouncing on-chain authorities operationalizes the milestone in a verifiable way, which strengthens a separation argument without guaranteeing it.

The secondary-market split

A builder should understand that the same SPL token can carry different risk at primary issuance and on secondary trades, and that the controlling rule is contested. Ripple held that anonymous programmatic sales on an exchange were not investment-contract sales, because blind bid-ask buyers could not know they were funding the issuer’s efforts (SEC v. Ripple Labs, Inc., 682 F. Supp. 3d 308, 327-30 (S.D.N.Y. 2023)). Binance applied that reasoning to dismiss the SEC’s secondary BNB-sales claim (SEC v. Binance Holdings Ltd., 2024 WL 3225974, at 18-22 (D.D.C. June 28, 2024)). Terraform* rejected the manner-of-sale distinction, holding that Howey draws no line between institutional and secondary purchasers (SEC v. Terraform Labs Pte. Ltd., 684 F. Supp. 3d 170, 195-96 (S.D.N.Y. 2023)). On Solana the seller’s identity is typically invisible in AMM-pool swaps and CEX order books, which cuts against an investment-contract finding on secondary trades under Ripple and Binance. Retained upgrade or mint authority keeps the issuer’s efforts live and feeds Terraform’s contrary view. The split is unresolved as of June 2026; a builder facing it should engage qualified securities counsel before relying on either line.

Multisig and DAO control

Who holds the authority changes the analysis qualitatively, and the law here is the thinnest. A small, team-controlled multisig over upgrade, mint, or freeze authority is functionally equivalent to unilateral team control and supports a managerial-efforts finding. A broadly governed DAO holding the same authority weakens that finding, because the persons exercising the power are more dispersed and the control is harder to reverse unilaterally. It does not eliminate the inquiry. Founders frequently retain outsized voting weight, and the SEC has historically treated nominal token-holder governance with skepticism, finding in The DAO that voting did not negate reliance on the managerial efforts of the promoter and curators (SEC, Report of Investigation Pursuant to Section 21(a): The DAO, Exchange Act Release No. 81207 (July 25, 2017)).

The point can only be stated qualitatively. No regulator or court has set an M-of-N multisig size or a token-distribution percentage that defeats the managerial-efforts element. This is a genuine gap (STUB confidence). The unresolved legal question is how distributed and how credibly irreversible control must become before the efforts of others stop being the efforts of others. Any builder structuring around it should treat the answer as undecided and obtain counsel.

Cross-jurisdiction comparison

The substantive test converges across the legal systems a Solana builder is most likely to touch, while each lacks a numeric threshold. The contrast below pairs each jurisdiction’s framing of the efforts element against how on-chain authority feeds it.

Table 3.1. Howey-equivalent tests across the United States, the European Union, and Brazil, and how retained on-chain authority enters each.

The practical takeaway is bounded. As of June 2026, retained on-chain authority is the strongest fact pushing a Solana token toward investment-contract or security treatment across these jurisdictions, and renounced authority is the strongest verifiable defense. Neither is dispositive in any of them. Because the secondary-market split remains open, every builder weighing these structures should retain qualified counsel in each jurisdiction of offering. This section is informational analysis, not legal advice.

Figure 3.2. No covered jurisdiction fixes a numeric decentralization threshold.

4. TOKEN-2022 EXTENSIONS AS A LEGAL SURFACE

Token-2022 (the SPL Token Extensions program) lets an issuer bolt discrete, composable features onto a single mint. Each extension changes what the token does on-chain, and each therefore carries its own legal exposure under securities and anti-money-laundering law, and under data-protection law where personal data is touched. The disciplined question is never “is a Token-2022 token a security?” It is narrower: which on-chain control lever does a given extension hand the issuer, and which off-chain promise sits behind it? Classify by the lever and the promise, not by the extension’s name.

Figure 4.1. Classify a Token-2022 extension by its on-chain lever and the off-chain promise behind it.

A threshold technical fact drives the whole analysis and is easy to get wrong. The interest-bearing extension mints nothing. InterestBearingConfig stores a rate that amount_to_ui_amount applies, through continuous compounding, to the displayed figure only; no new tokens are created and no transferable value accrues on-chain (SPL Token-2022 InterestBearingConfig documentation). Because the extension creates no payment obligation, a display-only counter almost certainly fails the threshold “note or obligation” inquiry under the family-resemblance test of Reves v. Ernst & Young, 494 U.S. 56 (1990). The four Reves factors (the seller’s and buyer’s motivations, the plan of distribution, the reasonable expectations of the investing public, and the presence of a risk-reducing factor) all presuppose a genuine promise to repay. A cosmetic UI number promises nothing (confidence: MEDIUM, as of June 2026). The legal hook lives off-chain. Where issuer documentation or marketing represents that the displayed rate corresponds to a real, issuer-funded yield, the wrapper around the token (that promise) may itself be a Reves note or a Howey investment contract, even though the extension is inert.

That relocation matters because of who holds the rate. InterestBearingConfig carries a rate_authority the issuer can retain and exercise at discretion. Howey asks whether there is an investment of money in a common enterprise with a reasonable expectation of profit derived from the essential managerial efforts of others (SEC v. W.J. Howey Co., 328 U.S. 293 (1946)). A retained rate_authority, paired with marketing that presents the accrual as a real return, supplies on-chain evidence of exactly the “essential managerial efforts” the federal market regulators flagged in their March 2026 interpretation as the trigger that overlays investment-contract treatment onto an otherwise non-security token (SEC Release Nos. 33-11412; 34-105020 (File No. S7-2026-09), 91 Fed. Reg. 13714 (Mar. 23, 2026), FR Doc. 2026-05635).2 The same logic reaches the transfer-fee extension. TransferFeeConfig withholds a basis-point fee on each transfer into a withheld-amount field, redeemable by the withdraw_withheld_authority, typically the issuer (SPL Token-2022 TransferFee documentation). Protocol revenue routed to a central party for the benefit of holders is probative of horizontal commonality and of profit derived from others’ efforts (Howey, 328 U.S. 293). The weight of that evidence varies with where the fee goes. Revenue funding an active team’s discretionary treasury is stronger evidence than revenue that is burned or that funds automated operations. This is evidentiary, not dispositive (confidence: LOW; no court or regulator has ruled on a Token-2022 fee as Howey evidence as of June 2026).

A recurring move in commentary deserves caution. Several analysts infer that renouncing on-chain authorities, or holding them through a sufficiently dispersed multisig or DAO, defeats securities characterization. That inference is reasonable and worth raising with counsel, but it is commentator gloss on Howey’s managerial-efforts element, not settled law. Treat any authority-control analysis qualitatively. Ask whether discretionary control over the token’s economics in fact persists, not whether some numeric signer threshold has been crossed.

The remaining extensions each open a distinct surface. The transfer-hook extension is the on-chain enforcement primitive for transfer restrictions: Token-2022 issues a cross-program invocation into the configured hook program’s Execute instruction on every non-self transfer, observing post-transfer state, and the hook can fail the instruction to block the move (SPL transfer-hook-interface documentation). A hook enforcing allowlist, KYC, or accredited-investor gating is consistent with Reg D and Reg S resale-restriction compliance for a token that already is a security (Securities Act of 1933, Rule 502(d), 17 C.F.R. 230.502(d); Regulation S, 17 C.F.R. 230.901–905). The hook does not make a token a security. Two residual risks remain: investor-eligibility gating signals that the issuer itself treats the instrument as restricted, and an upgradeable hook program is one more discretionary control lever relevant to the managerial-efforts inquiry (confidence: LOW).

Confidential transfers create the sharpest AML and privacy tension, and the precise mechanic narrows it. The extension encrypts transfer amounts using ElGamal ciphertext with zero-knowledge range and equality proofs, while account addresses and the initial public deposit stay visible (SPL confidential-transfer documentation). Amount-blindness defeats structuring analytics and threshold-based suspicious-activity reporting; address visibility preserves Specially Designated Nationals screening. So the impairment is amount-level monitoring, not identity screening. After Van Loon v. Department of Treasury, 122 F.4th 549 (5th Cir. 2024), which held immutable smart contracts are not sanctionable “property,” and Treasury’s subsequent delisting of the Tornado Cash addresses, an immutable, uncontrolled confidential-transfer primitive is likely not itself OFAC-sanctionable. Any regulated intermediary in the path keeps its full risk-based obligations regardless (31 U.S.C. 5318(h); 31 C.F.R. 1010.230) (confidence: MEDIUM).

The same encryption raises a data-protection question that encryption mitigates without extinguishing. On-chain ciphertext can still be “personal data” where re-identification is reasonably possible, and persistent public addresses plus the public first deposit supply that linkage (GDPR Arts. 4(1), 5; Recital 26, Regulation (EU) 2016/679). The EDPB’s draft guidance on blockchain, currently a consultation document and not final adopted text as of June 2026, recommends encrypting personal data before on-chain storage and designing so that deletion of off-chain keys renders on-chain records effectively anonymized (EDPB Guidelines 02/2025 on processing of personal data through blockchain technologies (consultation draft, Apr. 2025)). On-chain immutability still collides with the erasure and rectification rights (GDPR Art. 17; Lei 13.709/2018 (LGPD) Art. 18), so a deployment touching identifiable persons needs the off-chain key architecture the draft endorses (confidence: MEDIUM).

The permanent-delegate extension is a custody red flag in plain terms. Initialized at mint creation and updatable via SetAuthority, it confers mint-wide authority to transfer or burn tokens from any holder account with no per-holder approval, except for balances moved into confidential state (SPL Token-2022 PermanentDelegate documentation). Holders lack exclusive control of their assets. That undercuts any self-custody marketing and can support custodial or fiduciary characterization, and it is a deceptive-practices exposure if not disclosed clearly and conspicuously (15 U.S.C. 45; 12 U.S.C. 5531, 5536). No FTC Act or UDAAP action has yet tested permanent-delegate dispossession in a crypto context (confidence: LOW, as of June 2026).

The non-transferable extension cuts the other way. NonTransferable blocks all transfers and forces immutable ownership, eliminating the secondary market and the resale-profit expectation central to Howey (SPL Token-2022 NonTransferable documentation). A soulbound token maps onto the non-security “digital tool” category the March 2026 interpretation describes for memberships and credentials such as identity badges (SEC Release Nos. 33-11412; 34-105020, 91 Fed. Reg. 13714 (Mar. 23, 2026)). Risk returns only where the token still confers revenue or profit rights. The documented pairing with a permanent delegate yields a DAO-revocable, non-tradable credential, which reads as governance infrastructure rather than an investment, though the delegate’s revocation power reimports the custody concern above (confidence: MEDIUM).

The comparative picture sharpens two of these surfaces. The interest-bearing extension is most dangerous abroad, and the transfer-fee revenue question turns on Brazilian classification.

Table 4.1. Token-2022 extensions and their classification exposure under United States, European Union, and Brazilian law.

Two cross-jurisdiction points need flagging. The MiCA interest prohibition is the only HIGH-confidence claim in this section because the prohibition is black-letter and in force (MiCA Arts. 40, 50, in force since 30 June 2024). Whether ESMA or the EBA would read it to reach a purely cosmetic, clearly disclosed display where no real remuneration is paid is unsettled; the HIGH confidence assumes the accrual is marketed as real yield. And Brazil’s dual track sorts the token by its economic rights: features that create on-chain participation or remuneration rights pull toward CVM securities jurisdiction, while their absence leaves the token a virtual asset under the BCB Resolutions, which are VASP-focused rather than a direct regulation of self-issued token features (confidence: MEDIUM). Confidential transfers add the LGPD erasure tension to any Brazilian deployment, mirroring the EU analysis.

Nothing here is settled Solana law. No court or regulator has ruled on a specific Token-2022 extension as of June 2026, so every U.S. claim above except the MiCA prohibition reasons by analogy from Howey and Reves to novel on-chain mechanics. A builder should flag the retained authorities (rate_authority, withdraw_withheld_authority, permanent_delegate, an upgradeable transfer-hook program) as the concrete managerial-efforts evidence and treat issuer-captured fees as common-enterprise evidence. Confidential transfers are a separate flag for any intermediary in the path, under AML and sanctions law and under data-protection law. Any concrete deployment should be run past qualified securities and AML counsel in each target jurisdiction before launch.

5. COMPRESSED NFTS AND THE UNIQUE-ASSET BOUNDARY

A compressed NFT (cNFT) on Solana raises a deceptively simple legal question: is it a “unique” asset that escapes crypto-asset regulation, or a standardized series wearing a unique label? The answer turns on a fact most builders overlook. A cNFT’s only on-chain artifact is a 32-byte hash inside a concurrent merkle tree, while the rights a holder actually buys live off-chain, resolved by an indexer. Everything downstream follows from that split: EU classification, US copyright title, royalty enforcement, and intermediary liability all flow from it.

The mechanic that drives the law

Metaplex Bubblegum mints cNFTs as leaves under a single concurrent merkle root, and one tree can hold on the order of a billion leaves (Solana Foundation, State Compression and Compressed NFTs (2024); Helius, All You Need to Know About Compression on Solana (2024)). The chain stores the root and a changelog, nothing more. There is no SPL token account per asset. To read any attribute of a cNFT, such as owner, metadata URI, or license terms, a client must call a Digital Asset Standard (DAS) API, which reconstructs state from ledger transactions and returns a merkle proof. The cryptographic uniqueness sits in a leaf hash. The transferable rights sit in off-chain JSON. As of June 2026, that structural reliance on an off-chain intermediary is the single most decision-relevant fact for the analysis that follows.

The MiCA unique-asset exclusion

Article 2(3) of MiCA excludes crypto-assets that are “unique and not fungible” from the bulk of the regime (Regulation (EU) 2023/1114, art. 2(3)). A naive reading says every cNFT qualifies, because each leaf carries a distinct asset_id. That reading fails on the text itself. Recital 10 states that the mere attribution of a unique identifier is not, in and of itself, sufficient to classify an asset as unique and non-fungible; the assessment looks to the asset’s de facto features (Regulation (EU) 2023/1114, recital 10). Recital 11 adds that crypto-assets issued in a large series or collection may be considered fungible despite a label of uniqueness (Regulation (EU) 2023/1114, recital 11). ESMA’s qualification guidance applies the same substance-over-form logic, directing classification by economic function rather than by the form or origin of the instrument (ESMA, Final Report on the Guidelines on the Qualification of Crypto-Assets as Financial Instruments, ESMA75453128700-1323 (Dec. 17, 2024)).

That standard maps onto the cNFT data model with uncomfortable precision. The unique on-chain object is a hash, not a distinct token account, so EU classification cannot rest on the leaf’s cryptographic uniqueness. It must turn on the off-chain rights bundle. A content-licensing marketplace that mints a large Bubblegum collection, where every leaf grants the same template license terms and the leaves trade actively on secondary venues, presents exactly the standardization-plus-market-behaviour pattern that ESMA flags. Such a series can fall back into MiCA scope as an in-scope crypto-asset rather than an excluded unique item (MEDIUM confidence as of June 2026).

One caution limits this conclusion. No national competent authority, whether BaFin, the AMF, or any other, has published an applied position treating a particular large Bubblegum collection as in-scope. The support here is the ESMA general test, not a cNFT-specific ruling. Builders facing real EU exposure should retain qualified counsel rather than treat the classification as settled.

Table 5.1. Compressed-NFT design assumptions tested against their likely legal treatment.

US copyright: the chain-of-title gap

On the copyright question the law is black-letter, and it cuts against the intuition that owning the token means owning the work. Ownership of a copy is distinct from ownership of the copyright in the underlying work (17 U.S.C. 202). Any transfer of copyright ownership requires a signed writing (17 U.S.C. 204(a)). A cNFT leaf points to an off-chain metadata URI and content; transferring the leaf via a Bubblegum instruction moves the token, not the intellectual property. The merkle leaf cannot satisfy the signed-writing requirement of Section 204(a) on its own. For a content-licensing marketplace the operative license must therefore live in linked terms, whether a metadata-referenced license or the marketplace terms of service, and the buyer receives only the license those terms grant (HIGH confidence as of June 2026). Resale compounds the problem: each downstream transfer moves a token whose chain of title to any actual license depends on off-chain terms the leaf does not carry.

US securities risk stacked on top

A cNFT can also be an investment contract. Under Howey, an investment contract exists where a person invests money in a common enterprise with an expectation of profits derived from the essential managerial efforts of others, a four-element test in which the efforts-of-others element does the work for cNFT analysis (SEC v. W.J. Howey Co., 328 U.S. 293 (1946)). The SEC has applied that framework to NFT collections in two settled administrative orders. In Impact Theory, the Commission treated the issuer’s marketing of buyer profit tied to the team’s ongoing development as evidence of reliance on the efforts of others (In re Impact Theory, LLC, Securities Act Release No. 11226 (Aug. 28, 2023)). In Stoner Cats, the Commission pointed to a built-in 2.5% secondary-market royalty as evidence that the issuer retained a continuing incentive to drive resale value, reinforcing the managerial-efforts element (In re Stoner Cats 2, LLC, Securities Act Release No. 11233 (Sept. 13, 2023)).

The Solana fact pattern lines up closely. A Bubblegum collection where the team keeps the tree’s update and collection authority, and configures a Metaplex secondary royalty, reproduces the Stoner Cats posture: an ongoing managerial role joined to a royalty-driven incentive to promote resale. Two qualifications matter. These are settled orders, not litigated court holdings, and they carry a noted dissent from Commissioners Peirce and Uyeda disputing the limiting principle (In re Stoner Cats 2, LLC, Securities Act Release No. 11233 (Sept. 13, 2023) (Peirce & Uyeda, Comm’rs, dissenting)). Whether the post-2025 SEC, under its current leadership and crypto task force, still treats royalty-as-efforts-of-others as live policy is unclear as of June 2026. A retained-authority, royalty-configured collection should consult securities counsel (MEDIUM confidence as of June 2026).

Royalty enforceability: a contract problem, not a token feature

Secondary-market royalties on Solana are not legally self-enforcing. No binding US or EU statute or case mandates NFT resale royalties; the question falls under general contract law (see Holcomb, The Paradoxical Solution to Enforce Resale Royalties, Wash. J.L. Tech. & Arts (2025)). Standard SPL and Bubblegum transfers carry no enforced payment. Royalty fields in Metaplex metadata are advisory. A direct wallet-to-wallet transfer, or a transfer through a non-cooperating marketplace, bypasses the royalty unless the transfer is gated by a Token-2022 transfer hook or program-level enforcement. For a cNFT specifically, the leaf transfer is a Bubblegum instruction the indexer records; it is not a payment-gating mechanism. A content-licensing marketplace that depends on royalty revenue must secure it by contract through its terms of service, or by on-chain enforcement primitives, rather than relying on the NFT standard to collect (LOW confidence as of June 2026, reflecting the absence of on-point authority). This sits directly on top of the securities caution above: the same royalty configuration that strengthens a Howey argument is also the one the marketplace cannot enforce by default.

DAS-indexer liability: an unaddressed gap

Indexer reliance is structural, and the law has not caught up. To read any cNFT attribute a DAS API call is required; the indexer reconstructs tree state and serves a proof a buyer cannot independently verify without replaying the tree. If the indexer returns a stale proof, the wrong owner, a wrong metadata URI, or some other erroneous attribute, the buyer relying on a license delivered off-chain has no way to detect the error from the leaf alone. No on-point case law or regulator guidance addresses civil liability of a DAS API or RPC provider for serving an erroneous or stale proof (STUB). Exposure would be analyzed under general tort and contract theories, including negligent misrepresentation (see Restatement (Second) of Torts § 552 (1977)) and contractual service-level terms, and under applicable national tort law in the EU. The exposure is heightened for a licensing marketplace precisely because the license terms a buyer relies on arrive through the indexer, not from the chain. Builders should obtain counsel before relying on any allocation of this risk.

Brazil: virtual asset or security

Brazilian law treats a cNFT first as a “virtual asset” under the Marco Legal dos Ativos Virtuais (Lei No. 14.478/2022). It becomes a “valor mobiliário” only if its economic substance gives holders a profit expectation from a third party’s efforts, the Brazilian Howey-equivalent the CVM applies through its orientation opinion (CVM, Parecer de Orientação No. 40, de 11 de outubro de 2022; Lei No. 6.385/1976, art. 2). A pure content-license cNFT, delivered as a per-leaf off-chain license URI without investment-return features, points toward the virtual-asset lane supervised under the Banco Central framework. A collection marketed with resale-value upside and issuer-driven royalties risks classification as a contrato de investimento coletivo, a security (MEDIUM confidence as of June 2026). The boundary between BCB and CVM supervision for NFTs is contested.

GDPR and the off-chain layer

The privacy exposure attaches off-chain, which is where the architecture helps. State compression keeps only the 32-byte root and changelog on-chain. Metadata, content, and any personal data identifying licensees live off-chain on Arweave, IPFS, or HTTP and are mutable at the source. The marketplace and indexer act as controller or processor for that off-chain data (Regulation (EU) 2016/679, art. 4(1)). Because the off-chain layer is mutable, the right-to-erasure obligation under Article 17 is achievable there (Regulation (EU) 2016/679, art. 17), a posture the EDPB has examined in its draft guidance on blockchain processing (EDPB, Guidelines 02/2025 on Processing of Personal Data through Blockchain Technologies (consultation draft, Apr. 2025)). The design holds only if no personal data is ever committed into a hashed leaf or a ledger log, since the on-chain root and changelog are immutable (LOW confidence as of June 2026). For a Brazil deployment, the LGPD analysis (Lei No. 13.709/2018) should mirror this structure.

The practical takeaway for a content-licensing marketplace is concrete. Build the license and the royalty mechanism off-chain and by contract, and keep the chain-of-title record and the personal-data store off-chain as well, because the leaf carries none of them. Treat the EU and securities classifications as open questions for counsel rather than as resolved by the cNFT’s unique label.

6. STAKING, LIQUID STAKING TOKENS, VALIDATORS, AND SLASHING

When a Solana builder lets users stake SOL, mint a liquid staking token, run a validator, or buy “slashing protection,” each act sits at a different distance from a securities, tax, or contract-law line. The governing US materials are not Commission rules. They are two 2025 staff statements from the Division of Corporation Finance, each expressly non-binding and fact-dependent, each drawing a dissent from Commissioner Crenshaw. Treat everything below as informational analysis calibrated to that ceiling, not legal advice, and retain qualified counsel before relying on any classification.

The base layer: protocol staking

Native Solana staking, whether solo, delegated to a validator, or custodial, is most likely outside the federal securities laws. Staff reasoned that protocol staking rewards flow from the staker’s own act of helping secure the network, so the “efforts of others” element of Howey is not met (SEC Div. of Corp. Fin., Statement on Certain Protocol Staking Activities (May 29, 2025)). The mechanic supports the reasoning. A stake account delegates to a validator’s vote account, and the protocol credits inflation rewards algorithmically each epoch in proportion to stake; the validator’s commission is a fee for ministerial node operation, not discretionary asset management. Confidence here is MEDIUM, not higher, as of June 2026. A staff statement binds no court, and the Crenshaw dissent signals real disagreement inside the agency. The analysis is also fact-specific by its own terms.

Liquid staking tokens against the staff exclusions

A plain SOL-backed receipt token follows the base layer. Staff treated the issuance and redemption of a “Staking Receipt Token” as administrative, with value derived from the underlying SOL rather than from a provider’s managerial efforts; because SOL itself is not treated as a security in the staff’s analysis, the token is also not a “receipt for a security” (SEC Div. of Corp. Fin., Statement on Certain Liquid Staking Activities (Aug. 5, 2025)). The mSOL and bSOL receipt model fits that description: an SPL token minted on deposit at an exchange rate to a stake pool, appreciating as the pool’s stake accounts accrue epoch rewards, with the holder bearing SOL price and reward risk directly.

The same statement places a token outside the favorable reading where a provider can “decide/select whether, when, or how much” to stake, where it guarantees or sets reward amounts, or where the token “provides returns in addition to” evidencing depositors’ ownership (Aug. 5, 2025 statement). Two textual points matter for Solana builders. The statement expressly carves restaking out of its scope (id. fn.4). It does not mention MEV at all. That silence governs the JitoSOL question below.

Table 6.1. Liquid-staking architectures and their distance from the 2025 SEC staff exclusions.

JitoSOL bundles an off-protocol return on top of protocol inflation. Jito’s MEV layer runs an off-chain block-space auction; tips land in a per-epoch TipDistributionAccount, a merkle root is posted on-chain, and stakers claim the distribution. Whether that added stream is “administrative” or an entrepreneurial effort generating a return beyond ownership is unresolved, and the staff did not address MEV bundling, so any conclusion is analogical reasoning from the exclusion text (id.). LOW confidence. The Sanctum router raises a parallel question from a different direction. Its automated validator selection and reserve management are discretion in substance even if executed by smart contract, and whether contract automation negates the managerial concern animating the exclusion is untested. LOW confidence, and no authority addresses router-pool aggregators.

A separate theory survives all of this. The August statement reasons only that an LST is not an investment contract and not a receipt for a security; it does not foreclose a “note” characterization under the family-resemblance test (Reves v. Ernst & Young, 494 U.S. 56 (1990)). Industry counsel argues LSTs rebut Reves because the holder bears full upside and downside of the underlying SOL with variable, non-guaranteed rewards, an equity-like profile rather than a promise to repay a fixed sum with interest. No court has applied Reves to a Solana LST. LOW confidence on that point.

Validators and the tax line

Two tax questions face validator operators, and neither has on-point authority. First, character of income. All Solana staking and MEV rewards are includible in US gross income at fair-market value when the taxpayer gains dominion and control, generally when the reward is credited and freely claimable, regardless of later sale (Rev. Rul. 2023-14, 2023-33 I.R.B. 484 (IRS, Aug. 2023)). That ruling is the binding IRS position as of June 2026, though it is under active challenge (Jarrett v. United States (M.D. Tenn., complaint filed Oct. 10, 2024)). Its application to value-accruing LSTs is genuinely uncertain. Where rewards compound into an exchange rate rather than arriving as distributed tokens, a credible argument holds that nothing is “received” until the LST is redeemed or sold, a question Rev. Rul. 2023-14 does not directly answer. For Jito MEV, dominion and control arguably arises only when the merkle root is posted and the airdrop becomes claimable, splitting the taxable event from mid-epoch value capture. MEDIUM confidence on the live rule, lower on these applications.

Second, self-employment tax. Whether a validator’s rewards are passive investment income or trade-or-business income is fact-dependent and unsettled (IRC § 1402). A validator runs continuous equipment-intensive infrastructure and signs vote transactions across roughly 432,000 slots per epoch while charging commission, which pushes a regular, profit-motivated operation toward Schedule C and self-employment tax; a passive delegator’s rewards are ordinary income without it. The line has not been tested by the IRS or courts for Solana validators. Any specific percentage threshold a practitioner offers is assertion, not authority. LOW confidence, and counsel should price that exposure conservatively.

Slashing: indemnifying a risk the protocol does not yet impose

Solana has no live protocol-enforced slashing as of mid-2026. SIMD-0204 only logs verifiable evidence of slashable behavior on-chain without imposing any stake penalty, and the enforcement mechanism, SIMD-0212, is not activated (SIMD-0204; SIMD-0212; Anza/Solana technical documentation, 2025-2026). The legal consequence is concrete. A provider’s “slashing protection” fund, common on Ethereum, currently maps onto no Solana penalty, so today’s indemnification clauses cover operational faults such as downtime and validator key compromise, not protocol slashing. Once SIMD-0212 activates, projected post-Alpenglow and not before roughly Q2 2026, delegated stake at most validators becomes at risk and these indemnities turn economically live. The technical state is MEDIUM confidence. The enforceability and tax character of any specific indemnity payment, whether return of capital or taxable income, insurance or indemnity, is a contract-law question no authority resolves.

Comparative posture

Outside the US, classification turns on different tests and remains open. Under MiCA, the token and the staking service are analyzed separately. A plain SOL-backed LST is unlikely to be an asset-referenced or e-money token because it references a single pooled crypto-asset rather than a fiat peg or a basket, sitting more plausibly as an “other crypto-asset” under the white-paper regime; a synthetic LST without 1:1 reserves, or one marketed as yielding an investment return, risks classification as a MiFID II financial instrument (Regulation (EU) 2023/1114 (MiCA), Arts. 3(1)(6)-(7); ESMA Guidelines on the classification of crypto-assets as financial instruments (2025)). Classification is delegated to national competent authorities, and no authority has publicly classified a specific Solana LST as of June 2026. LOW confidence. In Brazil, a staking arrangement or LST is a valor mobiliário under CVM jurisdiction only if it meets the collective-investment-contract test, a public offer conferring remuneration rights where income arises from the efforts of a third party (Lei 6.385/1976, art. 2; CVM Parecer de Orientação no. 40/2022). Plain protocol delegation, where rewards come from the algorithm, parallels the SEC’s “efforts of others” failure; a marketed yield product over pooled SOL with provider-driven returns leans the other way. Either way, the operator is a VASP under Lei 14.478/2022 and the BCB regime regardless of securities status. LOW confidence, with no CVM decision specific to staking or LSTs.

The through-line for builders: the favorable staff reading protects passive, mint-and-hold, ownership-evidencing LSTs and expressly excludes provider discretion, guaranteed rewards, and returns layered on top of ownership. bSOL and mSOL sit closest to that protection, while JitoSOL is exposed through MEV. The Sanctum router is exposed through routing discretion. None of this is settled law. Each LOW and MEDIUM label above is a direction to obtain qualified counsel before launch, not a clearance.

7. INTERFACE, ROUTING, GOVERNANCE, AND OPERATOR LIABILITY

A single Solana swap interface can sit atop a non-custodial router, a hosted relayer, a fee account, a multisig treasury, and a governance token, and each of those layers attracts a different liability theory under a different regulator. The legal question is narrow and practical. Where, across the interface-router-governance stack, does a builder’s conduct convert protected software publication into an exercise of “control” or “operation” that the law can reach? The answer in mid-2026 is mostly unsettled, and the few fixed points are narrow.

The property holding and its limits. The one piece of black-letter law here is also the most cabined. The Fifth Circuit held that immutable, self-executing smart contracts are not “property” within the meaning of the International Emergency Economic Powers Act, because no person owns or can control them, so the Office of Foreign Assets Control exceeded its statutory authority when it added the Tornado Cash immutable pool contracts to the SDN List (Van Loon v. Dep’t of the Treasury, 122 F.4th 549 (5th Cir. 2024)) (HIGH). The Solana translation is precise. A program account whose upgrade authority has been revoked to null is immutable; no party can alter it or withdraw from it, and none can set its parameters. Under Van Loon’s reasoning, such a program is not blockable property. A router program whose upgrade authority remains with an active team is a different object. It is controllable, and that retained control likely makes it an interest of the controlling team rather than ownerless code.

What Van Loon does not do is the part founders most need to hear. It decided a property question and little else; it did not immunize human operators, a DAO, a front-end, or a relayer service (Van Loon, 122 F.4th 549 (5th Cir. 2024)) (MEDIUM). Treasury removed Tornado Cash from the SDN List on March 21, 2025 rather than continue litigating, but a discretionary delisting is not a concession that interface operators sit beyond reach (OFAC SDN removal, Tornado Cash (Mar. 21, 2025)) (MEDIUM). The court appears to have reached only the property question, and the precise scope of its reasoning on the DAO-as-entity and on any front-end or relayer liability remains unsettled as of June 2026. An operator who retains program upgrade authority, runs hosted relayer infrastructure, controls a fee account, or curates a token and pool list exercises ongoing control that distinguishes them from the ownerless Tornado Cash contracts, and that retained control is the hook that keeps a “person” within OFAC’s reach after Van Loon.

Publishing or forking the code is a separate matter. Interacting with, copying, teaching, or republishing open-source Solana router code is not by itself a sanctioned transaction; liability attaches to a prohibited transaction with a blocked person, not to code as such (OFAC Tornado Cash FAQs 1076, 1078, 1079 (Sept. 13, 2022); FAQ 1095 (Nov. 8, 2022)) (MEDIUM). Forking an Anchor or SPL AMM program and republishing a routing SDK do not constitute prohibited dealings with a blocked person; the prohibited act is signing a transfer that moves value to or from a blocked program or wallet. Receipt of an unsolicited nominal “dust” transfer to a U.S. wallet was treated as a non-priority for enforcement (id.) (MEDIUM). Note that the general virtual-currency FAQs (559-561, 646) are distinct from the Tornado-Cash-specific guidance cited here.

Money transmission and the non-custodial defense. The strongest structural defense for a Jupiter, Raydium, Orca, or Meteora-style interface is non-custody. A purely non-custodial aggregator that never takes control of user funds is not a money transmitter under FinCEN guidance, because it supplies software or a forum rather than accepting and retransmitting value (FinCEN Guidance FIN-2019-G001, Secs. 4.2, 4.5.1 (May 9, 2019); 31 C.F.R. 1010.100(ff)(5)(ii)(A)) (MEDIUM). The Solana mechanic is the linchpin. A Jupiter Ultra request returns a base64 VersionedTransaction that the user signs in their own wallet; the swap executes atomically across the underlying pools in one instruction set, and the aggregator never holds the user’s keys or takes “total independent control over the value.” That is a software supplier under FIN-2019-G001, not a money transmitter. The exemption fails the moment an operator takes custody or independent control, so a hosted relayer that receives, holds, and re-broadcasts funds could fall inside the definition.

The defense is contested, and the contest is criminal. A U.S. operator can face exposure for conspiracy to operate an unlicensed money-transmitting business under 18 U.S.C. 1960 even without taking custody, where a jury finds the operator built and ran a service used to transmit others’ value with knowledge of illicit use. A New York jury returned a partial verdict against Roman Storm on August 6, 2025, convicting on the Section 1960 conspiracy count while deadlocking on the money-laundering and sanctions counts (United States v. Storm, No. 1:23-cr-00430 (S.D.N.Y.)) (MEDIUM). That verdict is not final. Storm’s Rule 29 motion for a judgment of acquittal was argued on April 9, 2026, taken under advisement, and remains undecided as of June 2026; the deadlocked counts have not yet been retried. The Section 1960 rule for non-custodial operators is therefore not yet settled, and “we never had custody” is not a categorical shield. A Solana front-end team that markets a swap or mixing interface, runs relayer infrastructure, controls a fee account, and retains upgrade authority resembles an “operation” more than passive code-publishing; pure non-custodial routing with revoked upgrade authority and no relayer sits closer to the theory on which the jury did not convict.

The CFTC facilitation theory. A U.S. interface that merely facilitates access to leveraged or derivative trading can be charged for failing to register as a designated contract market, swap execution facility, or futures commission merchant, even if it neither offers nor promotes the product itself (In re Opyn, Inc.; In re ZeroEx, Inc.; In re Deridex, Inc., CFTC Release 8774-23 (Sept. 7, 2023)) (MEDIUM). A Solana perps front-end, or an aggregator routing into a leveraged-product pool, that surfaces and enables margined positions could be deemed to facilitate off-exchange leveraged retail commodity trades, triggering registration and Bank Secrecy Act duties regardless of non-custody. Two limits matter. The 2023 orders all involved leveraged or derivative products, leaving the reach into a pure spot aggregator like Jupiter undrawn, and two Commissioners dissented from a related settlement, so the facilitation theory is contested rather than affirmed.

LP-token classification. This is genuinely unsettled, and the analysis should say so plainly. No regulator or court has squarely ruled on the securities status of any LP token (LOW). The 2026 interpretive turn makes a securities characterization of a bare, receipt-style LP token less likely where value derives from the deposited assets and protocol-defined mechanics rather than a promoter’s essential managerial efforts (SEC Release Nos. 33-11412; 34-105020 (File No. S7-2026-09), 91 Fed. Reg. 13714 (Mar. 23, 2026), FR Doc. 2026-05635; SEC v. W.J. Howey Co., 328 U.S. 293 (1946)).3 Pool type drives the analysis. A fungible constant-product LP token is a pro-rata receipt whose return is algorithmic fees and impermissible loss, closer to a receipt evidencing ownership that the staff treated as a non-security in the liquid-staking context. A concentrated-liquidity position recorded as an NFT or bin requires active range management. A vault or manager that actively rebalances LP positions for depositors reintroduces the “essential managerial efforts” element of Howey, because the depositor relies on another’s ongoing decisions for profit. Where decentralization or renounced control is invoked to argue a token is not a security, that remains a commentator inference rather than a holding of the cited release, and it should be stated qualitatively. As of June 2026, qualified securities counsel should review each LP-token design individually.

Market manipulation and MEV. Two regimes reach maximal-extractable-value conduct, and both reach it imperfectly. Under EU law, sandwiching and reordering are reachable under MiCA’s market-manipulation prohibition, but front-running and validator transaction reordering are not enumerated in Article 91, so coverage rests on the catch-all “false or misleading signals” and “fictitious device” limbs and is legally uncertain (Regulation (EU) 2023/1114, Arts. 91-92, applicable from Dec. 30, 2024) (LOW). On Solana, MEV is captured mainly through Jito bundles and priority-fee ordering rather than a public mempool; a sandwich inserts buy and sell legs around a victim swap. Whether a validator or searcher is a “person professionally arranging or executing transactions” obliged to detect and report abuse under Article 92 is unresolved and awaits the final ESMA regulatory technical standard. Under U.S. securities law, a manipulation theory against a Solana interface proceeds under Exchange Act Section 10(b) and Rule 10b-5 only if the routed asset is a security and the interface is a person engaged in a manipulative device (Securities Exchange Act 10(b); 17 C.F.R. 240.10b-5) (LOW). Because the 2026 interpretation treats many Solana network and utility tokens as digital commodities rather than securities, a sandwich on a SOL/USDC pool likely falls outside Rule 10b-5 and into the CFTC’s commodity anti-manipulation authority, which requires scienter and a manipulative device (Commodity Exchange Act 6(c)(1); 17 C.F.R. 180.1) (LOW). Whether automated searcher reordering meets that intent standard is untested as of June 2026.

Governance: the partnership-by-default problem. The most consequential governance exposure for a Solana DAO is structural. A DAO with no incorporated entity is, by default, exposed to treatment as an unincorporated association or general partnership, which exposes active governance participants to joint and several personal liability for the DAO’s debts and regulatory violations (CFTC v. Ooki DAO, No. 3:22-cv-05416-WHO (N.D. Cal. June 8, 2023)) (MEDIUM). Token holders who cast on-chain governance votes through SPL Governance, Realms, or a Squads config vote are the “voluntary group of persons” treated as members; the act of voting, not mere holding, is the participation hook. Ooki was a default judgment with no adversarial defense, so its precedential weight is limited.

The theory has migrated from commodities into securities. A motion to dismiss survived against active institutional governance participants in a suit treating a DAO as a California general partnership, confirming that active participation can constitute being a partner with attendant joint-and-several liability (Samuels v. Lido DAO, No. 3:23-cv-06492-VC (N.D. Cal. Nov. 18, 2024)) (MEDIUM). The court distinguished passive token holders, who were insufficient, from members who combined holdings with active participation. For Squads, a multisig member with permissions to propose, vote, or execute who actively steers treasury or protocol decisions maps onto the active-participant category; passive observers do not. A surviving motion to dismiss is not a merits ruling, so the risk is real without being settled.

Treasury token sales. Selling or distributing a DAO governance token can be an unregistered offer and sale of securities, and the on-point authority here is Solana-native. The SEC entered a settlement concerning the Mango Markets governance token, MNGO, an SPL token, treating the token sale itself as the securities violation (In re Mango DAO, Blockworks Found., Mango Labs LLC, SEC Press Release 2024-154 (Sept. 27, 2024); SEC v. W.J. Howey Co., 328 U.S. 293 (1946); SEC, Report of Investigation: The DAO (July 25, 2017)). That matter resolved as a persuasive civil settlement, entered without admission and subject to court approval; it is not a binding judicial precedent and did not announce a general SEC finding about Solana or the SPL standard as such (MEDIUM). Treasury managers who sell SPL governance tokens to fund operations create primary Section 5 exposure regardless of the multisig custody mechanics used to hold proceeds.

Multisig signers and the load-bearing on-chain fact. Who can move the money is the question that drives both money-transmitter and control-person analysis. Squads v4 signers with executor permission who meet the approval threshold exercise direct control over treasury funds, and that control, not nominal entity ownership, is the predicate for control-of-funds and control-person arguments (FinCEN Guidance FIN-2019-G001 (May 9, 2019); 31 C.F.R. 1010.100(ff)(5)) (LOW). The config_authority field is decisive. Where it is set to Pubkey::default(), the multisig is “autonomous”: all configuration changes require member voting, and no single signer has total independent control, which weakens a money-transmitter theory. Where config_authority is set to a key, that key holder is closer to independent control and to the controlling position that supports a control-person claim. Signers and large governance-token holders who control the DAO can be control persons under Securities Act Section 15 or Exchange Act Section 20(a) regardless of any operating-agreement fiduciary waiver (15 U.S.C. 77o, 78t(a)) (MEDIUM). No regulator has applied FIN-2019-G001 squarely to multisig signers, so this is unsettled as of June 2026.

A time-lock is a signal, not a shield. A non-zero time_lock on a Squads multisig delays execution after threshold approval and can support a reduced-control narrative, but the signers retain the power to approve and ultimately execute, and no court or regulator has held that a time-lock alone negates control or managerial-efforts liability (Squads Protocol v4 program account model; SEC v. W.J. Howey Co., 328 U.S. 293 (1946)) (STUB). Treat it as argument, not authority.

The entity wrapper and its untested edges. Forming a Wyoming DAO LLC converts the DAO into a limited-liability entity and is the strongest available structural mitigation against the partnership-by-default exposure for U.S.-nexus DAOs; the statute also lets the operating agreement and smart contracts define or reduce member fiduciary duties, and even eliminate them (Wyo. Stat. Ann. 17-31-101 to 17-31-116; id. 17-31-110) (MEDIUM). A Squads multisig or Realms governance can be named as the algorithmic management mechanism in the articles. Two cautions limit the comfort. The shield is untested against an out-of-state plaintiff in a forum such as California that may decline to recognize it and apply general-partnership law instead. And the fiduciary-duty modification cuts both ways: it can immunize signers from intra-DAO fiduciary claims, but it does not displace federal securities or commodities duties, and it does not bind token-buyer plaintiffs who never agreed to the operating agreement (Wyo. Stat. Ann. 17-31-110; Securities Act 15, Exchange Act 20(a) (15 U.S.C. 77o, 78t(a))) (MEDIUM).

The following table sets the load-bearing Solana configuration against the liability theory it most affects.

Table 7.1. On-chain configuration choices and the operator-liability posture each one signals.

Comparative perimeter. Outside the United States, the picture is a gap rather than a safe harbor. Under MiCA there is a structural mismatch: the regulation grants DAOs no legal personality and excludes services provided in a fully decentralised manner without an intermediary, yet its custody regime presumes an identifiable legal person able to contract with clients and established in the EU (Regulation (EU) 2023/1114, Recital 22, Art. 75, applicable from Dec. 30, 2024) (MEDIUM). A Squads multisig with no controlling legal entity may fall outside the CASP perimeter if fully decentralised, but once identifiable signers exercise threshold control and provide custody-like services to others, national regulators may assert obligations the DAO cannot structurally satisfy. In Brazil, operating a Solana DEX or aggregator interface for third parties can trigger virtual-asset service-provider authorization and AML duties even where the protocol is non-custodial, because the statutory definition reaches participation in services related to the offer or sale of virtual assets, beyond custody alone (Lei nº 14.478/2022, arts. 1, 3, 5; Resoluções BCB nº 519/520/521 (Nov. 10, 2025); Res. BCB nº 561 (eFX)) (LOW). An LP token that confers a right to profit or a dividend, or voting rights, could be recharacterized as a valor mobiliário and pulled under CVM authority, splitting one interface across the central bank and the securities regulator (CVM Parecer de Orientação 40/2022) (LOW). No Brazilian authority has applied this to a non-custodial router or a DAO multisig. Brazilian framework as of June 2026 contains no DAO-specific provision and no DAO legal personality.

The actionable rule for a builder is narrow and defensible. Never treat a multisig time-lock or a “decentralization” label as defeating liability on its own. The defensible posture pairs an entity wrapper with on-chain configuration that genuinely removes unilateral and admin-key control, and even that posture rests on theories that no adversarial merits ruling has yet confirmed. Qualified counsel should review any specific structure before launch.

8. CROSS-JURISDICTION MAP: STABLECOINS, GRANTS, IP, AND TAX

A Solana builder touching dollars, ecosystem money, code ownership, and a tax return confronts four bodies of law that do not align cleanly across the United States, the European Union, and Brazil. The recurring lesson is that the chain is rarely the operative legal fact. Obligations attach to an off-chain issuer entity, a grant agreement, a license, or a taxpayer, and the Solana mint is a downstream representation of a claim that lives somewhere else.

Stablecoins: the obligation runs to the issuer, not the chain

Start with the controlling US statute. The GENIUS Act (Pub. L. 119-27 (July 18, 2025)) governs “payment stablecoins” such as USDC and PYUSD, and its core duties attach to the issuing entity rather than to any ledger (GENIUS Act, Pub. L. 119-27, Secs. 4(a)(1)-(3), 4(a)(11)). Reserves must be held one-to-one in cash and short-dated Treasuries and may not be rehypothecated, with monthly reserve-composition disclosure subject to CPA examination and CEO/CFO certification, an enforceable holder redemption right, and a bar on paying yield to holders (id., Sec. 4(a)). The chain of issuance is legally irrelevant. USDC on Solana and USDC on Ethereum impose one undivided set of obligations on Circle, because on-chain the SPL token is a claim and the redemption duty runs to the off-chain issuer (HIGH confidence, as of June 2026).

That single-obligor design has a practical edge for Solana holders. Native USDC across all chains is backed by one undivided reserve pool, with no per-chain apportionment; Circle moves supply between chains by burning on the source chain and minting native on the destination via CCTP, so cross-chain transfer creates no new redemption obligor (GENIUS Act, Pub. L. 119-27, Sec. 4(a)(1); Circle CCTP burn-and-mint design documentation (2026)) (MEDIUM confidence). Bridged USDC.e is a different legal animal. It is a third-party wrapped mint collateralized by USDC locked in a bridge, carrying no direct Circle redemption right, so a holder of the native Solana mint and a holder of the bridged variant hold materially different claims even though both circulate on Solana. As of June 2026 it remains unresolved whether bridged USDC.e could itself trigger Circle issuer liability or sits entirely outside Circle’s GENIUS obligations; qualified counsel should be consulted before relying on either reading.

Two supervisory mechanics deserve attention because they aggregate across chains. Supervision bifurcates by size: a state-qualified issuer may operate under a Treasury-certified state regime only while consolidated outstanding issuance stays at or below USD 10 billion, above which it must transition to OCC oversight within 360 days or obtain a waiver, while federal-qualified issuers and IDI subsidiaries are federally supervised from the outset (GENIUS Act, Pub. L. 119-27, Secs. 2(23), 4(c)-(d)) (HIGH confidence). The threshold is computed on total supply attributable to the issuer’s mint authority across every chain, so a multi-chain Solana deployment accelerates crossing the federal trigger. The second mechanic is extraterritorial. A foreign issuer’s stablecoin may be offered or sold in the US only under a Treasury-determined comparable foreign regime, with OCC registration and US-held reserves sufficient for US-customer liquidity (GENIUS Act, Pub. L. 119-27, Sec. 18(a)-(c)) (MEDIUM confidence). Permissionless SPL transfers make “offered or sold in the US” hard to contain. An offshore mint reaches US wallets without the issuer’s volition, and absent a Token-2022 freeze or permanent-delegate control the issuer cannot geofence, which raises enforcement exposure under Section 18.

A timing caveat governs all of this. No final federal rule exists as of June 2026; only OCC and FDIC notices of proposed rulemaking have issued (OCC Notice of Proposed Rulemaking implementing the GENIUS Act, 91 Fed. Reg. 10202 (Mar. 2, 2026)). The effective date is the earlier of roughly January 18, 2027 (18 months post-enactment) or 120 days after final rules, so absent earlier final regulations the operative date is approximately January 18, 2027. Whether the statute reaches secondary-market trading and custody on Solana, beyond issuance, is not resolved on the face of the statute and turns on its Section 3 scope provisions.

PYUSD shows what enforceable redemption looks like on-chain. Paxos Trust Company, a New York limited-purpose trust supervised by NYDFS, issues PYUSD on Solana using Token-2022, and the permanent-delegate extension lets Paxos freeze and seize tokens (NYDFS Guidance on the Issuance of U.S. Dollar-Backed Stablecoins (Industry Letter, June 8, 2022); GENIUS Act, Pub. L. 119-27, Sec. 4(a)(1)(B)) (HIGH confidence). That delegate authority is the concrete primitive operationalizing NYDFS-required redemption enforcement and court-ordered seizure, and it also serves OFAC freezes for the Solana-resident supply, and NYDFS has proposed (2026) updating its regime to align with GENIUS while preserving the 2022 reserve and redemption standards.

The EU classifies by peg, not by chain. Under MiCA (Regulation (EU) 2023/1114), a single-fiat-referenced stablecoin like USDC is an e-money token under Title IV, while a basket- or other-value-referenced token is an asset-referenced token under Title III, and EMT issuers must be authorized credit or e-money institutions granting a redemption-at-par claim (Regulation (EU) 2023/1114 (MiCA), Arts. 3(1)(6)-(7), Titles III and IV) (HIGH confidence). USDC is authorized as an EMT through Circle’s EU-licensed entity, Circle SAS in France, and no ART has been authorized to date given Title III’s heavier prudential burden. Solana-resident USDC carries the same EMT status as the Ethereum mint because the redemption claim sits with the licensed issuer. A second MiCA mechanic bites hardest on a low-fee chain. A significant non-euro EMT used as a means of exchange in the EU faces a hard usage cap: issuance and use are restricted once it reaches one million transactions per day or EUR 200 million in daily transaction value, at which point the issuer must stop issuing until usage falls back (Regulation (EU) 2023/1114 (MiCA), Art. 23(1) (transaction-limit mechanism applied to EMTs via Art. 58(3) for non-Member-State-currency tokens)) (MEDIUM confidence). Solana’s sub-cent fees make per-transaction counts the binding constraint, so high-frequency micro-payments of a USD EMT can hit the one-million-transaction cap far faster than on a high-fee chain even at modest notional volume.

The decentralized case falls through every perimeter. USDS (Sky, formerly MakerDAO) has no corporate issuer and no redemption obligor, and is crypto-overcollateralized through on-chain governance, so it likely fails the GENIUS definition of a permitted payment stablecoin (which presupposes a regulated issuing entity) and almost certainly cannot meet MiCA’s EMT requirement of an authorized institution (GENIUS Act, Pub. L. 119-27, Sec. 2(23); Regulation (EU) 2023/1114 (MiCA), Arts. 48-49) (LOW confidence). On Solana, USDS is an SPL mint controlled by executive votes with no off-chain redeeming entity. It has no permanent delegate acting for a regulated issuer and no fiat reserve to attest, so the hooks built for issuer-backed stablecoins have no addressable counterparty. Whether such a token is best read as outside the payment-stablecoin definition, an unlawful unpermitted issuance, a security, or a commodity is genuinely unsettled as of June 2026 and depends on forthcoming guidance. Qualified counsel is warranted.

Brazil treats fiat-pegged crypto movement as foreign exchange. The November 10, 2025 package reclassified stablecoin transactions as FX operations and integrated VASPs into the BCB’s FX regime, with per-transaction limits of roughly USD 100,000 for VASPs and USD 500,000 for FX-authorized financial institutions (Resoluções BCB Nos. 519, 520, 521 (Nov. 10, 2025); Lei No. 14.478/2022) (MEDIUM confidence). A later instrument tightens the regulated cross-border channel: BCB Resolution 561 (published April 2026, effective October 2026) restricts settlement between regulated eFX providers and overseas counterparties to traditional FX or non-resident BRL accounts, curtailing direct stablecoin settlement of the offshore leg while licensed VASPs retain a narrower pathway (Resolução BCB No. 561 (Apr. 2026)). A Solana USDC or PYUSD transfer that crosses the Brazilian border is an FX operation regardless of the on-chain mechanic, and because SPL transfers settle peer-to-peer without a Brazilian intermediary, compliance requires a licensed VASP or eFX provider to wrap the on-chain leg.

There is no legally recognized chain-specific reserve audit for native USDC or PYUSD. Attestations (Deloitte for USDC, Paxos monthly for PYUSD) cover total reserves against total issuer-wide outstanding supply, because the pool is undivided and supply is fungible across chains via burn-and-mint (GENIUS Act, Pub. L. 119-27, Sec. 4(a)(1)(C), 4(a)(3); NYDFS Industry Letter (June 8, 2022)) (MEDIUM confidence). A statement that “Solana USDC has its own audited reserve” is not supported by current regulatory practice, because no on-chain quantity maps to a ring-fenced Solana reserve.

Table 8.1. Stablecoin treatment under the GENIUS Act and MiCA, mapped to the Solana control primitive that carries it.

Grants, IP, and tax: the deliverable carries the law

Grant money is income. A Solana Foundation grant paid to a US for-profit builder is taxable gross income at fair market value on the date of receipt, not an excludable gift, and tokens received (USDC-SPL or SOL) are property, so FMV at receipt is ordinary income and any later sale is a separate capital event (26 U.S.C. Sec. 61(a); IRS Notice 2014-21 (2014-16 I.R.B. 938); Commissioner v. Glenshaw Glass Co., 348 U.S. 426 (1955)) (HIGH confidence). The gift exclusion does not rescue the builder, because the Foundation funds the work to advance the network, which is a quid-pro-quo inducement rather than the detached and disinterested generosity a gift requires (26 U.S.C. Sec. 102(a); Commissioner v. Duberstein, 363 U.S. 278 (1960)) (HIGH confidence). Nor does the capital-contribution shelter apply: post-TCJA, Section 118 excludes governmental or civic contributions from “contribution to capital,” and it never reached anything but corporations anyway, so a private-foundation grant to a founder or LLC member sits outside it (26 U.S.C. Sec. 118(b)(2), as amended by Pub. L. 115-97, Sec. 13312) (HIGH confidence).

Hackathon prizes follow the same logic. Colosseum prizes are USDC-SPL awards (the Grand Champion award is USD 50,000) taxable as prizes under Section 74(a), with the Section 74(b) recognition-award exclusion unavailable because entrants take action and render services by building (26 U.S.C. Sec. 74(a)-(b); Solana Breakout Hackathon Official Rules 2025 (Colosseum), Secs. 14-15) (HIGH confidence). A structural wrinkle: the prize lands in a single Team-Leader wallet, so a multi-member team faces a downstream assignment-of-income and allocation problem with no IRS guidance on point for on-chain team prizes.

Colosseum entrants retain all IP in their project code and submission; the Administrator expressly disclaims ownership of any Project Submission and keeps rights only in narrowly defined “Creative Materials,” meaning contest marketing content, not the codebase (Solana Breakout Hackathon Official Rules 2025 (Colosseum), Secs. 9-10) (HIGH confidence). A deployed program or repo remains the team’s, so a later token launch or equity raise is not encumbered by a hackathon assignment, though entrants must still clear third-party and open-source code under Section 9. Governing law is Florida with ICC arbitration in Florida.

Open-source licenses bind the funded code by their own terms, independent of the funder, and they diverge in ways that matter for a later closed-source product. Permissive MIT and BSD demand only notice and attribution. Apache-2.0 adds an express patent grant and requires stating modifications and preserving the NOTICE file. GPL and AGPL copyleft force derivative works, and for AGPL network-served code, to ship under the same license (MIT License; Apache License 2.0, Secs. 3-4; GNU GPL v3, Sec. 5; GNU AGPL v3, Sec. 13) (HIGH confidence). Solana programs lean on Apache-2.0 and MIT crates such as Anchor, SPL, Metaplex, and Pyth, and GPL is rare on-chain, but a single GPL or AGPL dependency in grant-funded code can pull the whole program into copyleft and collide with a Foundation grant’s frequent open-sourcing requirement, constraining a future upgrade-authority-controlled closed deployment.

The securities exposure is real but unsettled, and it concentrates at one moment. A convertible grant that converts to equity or a token-warrant on a priced round or milestone is, on conversion, the offer and sale of a security that must fit a Securities Act exemption (typically Rule 506(b) or 506(c), or the Section 4(a)(2) private-placement exemption), and the convertible instrument is generally itself a security until conversion (Securities Act of 1933, Sec. 5 (15 U.S.C. 77e); Sec. 4(a)(2) (15 U.S.C. 77d(a)(2)); 17 C.F.R. 230.506; SEC v. W.J. Howey Co., 328 U.S. 293 (1946)) (MEDIUM confidence). Whether a token issued on conversion is itself a security turns on Howey’s four-element test keyed to an expectation of profit from the essential managerial efforts of others. Where the team retains program upgrade authority and mint authority and continues active development, that managerial-efforts element is more readily satisfied, pushing the token toward security status. This is a commentator inference about how retained on-chain authority bears on the analysis, not a settled holding, and the SEC’s posture on a conversion-issued Solana token where the team keeps upgrade and mint authority is in flux with no on-point guidance as of June 2026. Sequencing compounds the risk: a convertible-grant conversion firing on the same priced round a founder closes can be integrated with that financing, and public Colosseum demo-day pitching can amount to general solicitation that taints a contemporaneous Rule 506(b) raise, with Rule 152 the controlling integration framework rather than a guarantee (17 C.F.R. 230.152; 17 C.F.R. 230.506(c)) (MEDIUM confidence). Qualified securities counsel should review any convertible structure before signing.

The EU and Brazil add their own overlays on the token deliverable. Under MiCA, a Foundation grant denominated in tokens is unlikely to qualify as a “free” distribution exempt from Title II public-offer duties, because Art. 4(3) treats a distribution as not free where the offeror receives a non-monetary benefit, and building ecosystem tooling for the network is plausibly such a benefit; whether white-paper duties bite then depends on the token’s classification and on the EUR 1 million and qualified-investor thresholds (Regulation (EU) 2023/1114 (MiCA), Art. 4) (MEDIUM confidence). No ESMA or national-competent-authority interpretation of the non-monetary-benefit test for a grant-for-build arrangement has been published, so the reasoning is structural. In Brazil, grant tokens and prizes received by a resident are taxable: tokens earned as compensation for development are ordinary income at progressive IRPF rates up to 27.5 percent, and a later disposal is capital gains taxed at 15 percent to 22.5 percent above the monthly R$35,000 exemption, with reporting duties under IN RFB 1.888/2019 as modernized by IN RFB 2.291/2025 (Lei 14.478/2022; IN RFB 1.888/2019; IN RFB 2.291/2025; Lei 14.754/2023) (MEDIUM confidence). On-chain receipt into a self-custody wallet triggers self-reporting, and a token the CVM functionally classifies as an investment token can additionally pull the offering into CVM securities jurisdiction.

A builder reading this map should take away a single coordinating principle and several unresolved edges. The coordinating principle is that legal character attaches to the entity, the agreement, the license, or the taxpayer behind the Solana token, and the chain mostly determines how a control primitive (a Token-2022 permanent delegate, a freeze authority) is exercised, not whether the duty exists. The unresolved edges, each flagged LOW or MEDIUM, are the regulatory status of decentralized stablecoins, the securities treatment of a conversion-issued token under retained on-chain authority, the application of MiCA’s non-monetary-benefit test to grants, and the precise scope and effective date of US final stablecoin rules. On each, the law is genuinely open as of June 2026, and a builder should obtain jurisdiction-specific counsel before relying on any single reading.

9. FROM ANALYSIS TO TOOLING: RUNTIME CAVEATS

A skill that reads Solana accounts and emits a legal-risk signal inherits a set of runtime traps that have nothing to do with classification doctrine and everything to do with how the chain actually settles and stores state, then discards it. The legal question for this section is narrow but unavoidable. When tooling converts an on-chain read into a compliance or risk signal, which runtime facts can the signal rely on, and where must it stop short and flag uncertainty rather than assert a conclusion?

Figure 9.1. Read-only on-chain agents that turn verifiable chain facts into confidence-labeled risk signals through the kit’s MCP servers.

Start with finality, because most settlement assumptions break there. A Solana transaction at confirmed commitment carries optimistic confirmation at roughly 66% stake-weighted vote and arrives in about 0.6 seconds, yet it remains theoretically reversible on a minority fork; only finalized commitment, reached after maximum vote lockout (32 votes, 31 or more subsequent confirmed blocks, roughly 13 seconds), approximates irrevocable settlement under Tower BFT (Solana Docs, Commitment Levels (processed/confirmed/finalized); Tower BFT lockout). No United States statute fixes the legal moment of finality for a transfer on a permissionless chain. The European designated-system regime does not reach Solana either; the Settlement Finality Directive applies only to systems formally designated by a Member State, which a permissionless validator set is not (EU Settlement Finality Directive 98/26/EC, Art. 3 (designated-system scope)). The settlement question is therefore probabilistic rather than deterministic, and the residual reversal risk is allocated by private agreement rather than by black-letter law (Nabilou, Probabilistic Settlement Finality in PoW Blockchains: Legal Considerations, SSRN No. 4022676 (2022)). This is a MEDIUM-confidence reading as of June 2026, and the practical instruction follows from it directly: a tool must not label a confirmed transaction as “settled.”

What happens when a relying party acts on a transfer that later disappears in a reorganization is genuinely untested. The most likely resolution would draw on general contract and negligence principles together with UCC Article 12, the 2022 amendments enacted in the District of Columbia and more than twenty-five states as of 2024 to 2025, which grant a qualifying good-faith purchaser of a controllable electronic record a take-free right once that purchaser obtains control (UCC Article 12 (2022 Amendments), §§ 12-104, 12-102 (controllable electronic records; take-free rule)). Article 12 protects the qualifying purchaser. It does not define when an on-chain transfer becomes irreversible, so it cannot supply the finality rule the runtime omits. No litigated case allocating loss from a chain reorganization to a relying party exists as of June 2026, which is why this allocation question sits at LOW confidence and warrants qualified counsel before any tool encodes a recovery assumption.

The second trap is treating live account state as the system of record. Closing a Solana account returns its rent lamports to a destination and deallocates and zeroes the account data; the SPL token close_account instruction is the common path (Solana Docs, Close Account & Rent Reclamation). United States Bank Secrecy Act recordkeeping places the retention duty on the regulated institution, not on the chain, and requires that records be retained and produced on request (31 C.F.R. § 1010.430(d); FFIEC BSA/AML Examination Manual, App. P). The baseline retention period is five years, and Treasury’s March 2025 final rule extended the period for sanctions-compliance records to ten years (Treasury Final Rule, Extension of Recordkeeping Period for Certain OFAC Records (Mar. 21, 2025)). That obligation runs to the entity and cannot be discharged by pointing at chain state that the account holder is free to close. Standard RPC nodes prune historical state, and only archival nodes serve older slots, so “data availability for compliance reconstruction” depends on archival indexing the institution controls rather than on a live account query. This is HIGH-confidence law on the retention duty itself; the architectural consequence, that the ledger is an unreliable system of record for reconstruction, follows at MEDIUM confidence as of June 2026.

A precise mechanic does the load-bearing work here, and it cuts in two directions at once. Closing an account reclaims rent and erases live state, which breaks naive audit reconstruction because balances and account data are gone. The same closure does not erase the finalized historical instructions that created and funded the account, which persist in append-only ledger history replicated across validators. So the institution loses the live state it might have queried while the historical record it might have wanted erased survives. The table below maps each runtime mechanic to the assumption a tool must refuse.

Table 9.1. Runtime mechanics and the faulty assumption each one forces a tool to reject.

The third trap is privacy. Where a wallet address functions as an identifier or where a memo or metadata field carries identifiable data, European data-protection law is engaged even though Solana cannot rewrite finalized history. The EDPB has taken the position that technical immutability cannot be invoked to excuse non-compliance with the rectification and erasure rights of Articles 16 and 17, so the compliant pattern is to keep identifiable and indirect-identifier data off-chain, where it can be erased to render the on-chain remainder anonymous (GDPR Arts. 5(1)(c), 17; EDPB Guidelines 02/2025 on Processing of Personal Data Through Blockchain Technologies (consultation draft, Apr. 2025)). One caution on that source. Guidelines 02/2025 were issued for public consultation in draft form, and no final adopted text exists as of June 2026, so a tool should treat the exact phrasing as provisional and re-verify against the adopted version before relying on it. The erasure conclusion is sharp regardless of phrasing: account closure does not satisfy a Brazilian or European erasure request, because closure deletes live state while the original instructions and addresses, along with any embedded memo data, remain in the immutable ledger (Brazil LGPD (Lei No. 13.709/2018), Art. 18(VI); GDPR Art. 17). A tool that reported account closure as “deletion” would misstate the runtime’s actual erasure capability. The controller-attribution question is harder and remains unresolved; the draft Guidelines give limited guidance on identifying a controller or processor on a permissionless chain and discourage placing personal data there at all, leaving dApp operators, validators, and RPC providers and indexers in an ambiguous allocation of liability for non-erasable records (GDPR Arts. 4(7), 26; EDPB Guidelines 02/2025 (consultation draft)). That ambiguity is LOW-confidence territory and a matter for qualified counsel, not for a tool to resolve by assertion.

Brazil’s regime reinforces the same off-chain discipline. Lei No. 14.478/2022 brought virtual-asset service providers within the anti-money-laundering framework by amending Lei No. 9.613/1998, subjecting them to COAF reporting and customer-identification duties, and the Banco Central do Brasil resolutions of November 2025, effective 2 February 2026, require AML and counter-terrorist-financing controls together with Travel Rule data accompanying transfers (Lei No. 14.478/2022 (amending Lei No. 9.613/1998); BCB Resoluções 519/520/521 (10 Nov. 2025, eff. 2 Feb. 2026)). The compliance consequence parallels the United States rule: originator and beneficiary data must be retained off-chain, because a closed account yields no live state and reconstruction depends on the provider’s own archival capture. This is MEDIUM-confidence as of June 2026.

One timing mechanic rounds out the runtime picture and corrects a common conflation. A Solana epoch spans roughly 432,000 slots, about two to three days, and governs stake activation and deactivation along with reward-distribution boundaries, but transaction finality operates per-block through Tower BFT lockout and is decoupled from epoch boundaries (Solana Docs, Epochs and Staking (epoch length; stake warmup and cooldown)). Audit work tied to staking rewards or stake-account state must align to epoch boundaries. Audit work tied to settlement or AML timing must align to commitment level. The unifying instruction for the skill is plain. Read the chain and grade the signal, and never let a runtime read assert more certainty than the mechanic supports.

10. CONCLUSION

The through-line is a discipline, not a verdict. Classify a Solana product by its control surface and its promises, and resist the temptation to read a single key or a single label as decisive. The on-chain facts are unusually legible. Anyone can verify whether an upgrade authority is renounced, whether a mint authority survives, or whether a freeze authority remains. That legibility is the builder’s opportunity and the analyst’s anchor. It does not, on the current record, convert into a bright-line rule in any of the covered jurisdictions.

The same discipline shapes the tool. A skill built on this analysis should read the control surface, weigh it against the issuer’s representations, return a graded and source-cited risk signal, and attach an explicit escalation flag. It should never assert that renouncement, a time-lock, a threshold multisig, or a decentralization label is dispositive, because no primary authority supports that claim as of June 2026. Where the law is unsettled, the right output is a labeled uncertainty and a pointer to counsel, not a confident answer. That posture is what separates a useful legal skill from a liability.

DISCLAIMER

This document is informational and does not constitute legal advice. It does not create an attorney-client relationship and is not a substitute for qualified counsel in the relevant jurisdiction. Statutes, regulations, guidance, and case law change; every substantive statement is pinned to June 2026 and should be checked against the primary source before any reliance. The author is a researcher, not a licensed attorney. Retain counsel before acting.

TABLE OF AUTHORITIES

Cases

1. CFTC v. Ooki DAO, No. 3:22-cv-05416-WHO (N.D. Cal. June 8, 2023)

2. Commissioner v. Duberstein, 363 U.S. 278 (1960)

3. Commissioner v. Glenshaw Glass Co., 348 U.S. 426 (1955)

4. In re Impact Theory, LLC, Securities Act Release No. 11226 (Aug. 28, 2023)

5. In re Mango DAO, Blockworks Foundation, and Mango Labs LLC, SEC Press Release 2024-154 (Sept. 27, 2024)

6. In re Opyn, Inc.; In re ZeroEx, Inc.; In re Deridex, Inc., CFTC Release No. 8774-23 (Sept. 7, 2023)

7. In re Stoner Cats 2, LLC, Securities Act Release No. 11233 (Sept. 13, 2023)

8. Jarrett v. United States, No. 3:24-cv-01209 (M.D. Tenn., complaint filed Oct. 10, 2024)

9. Reves v. Ernst & Young, 494 U.S. 56 (1990)

10. Samuels v. Lido DAO, No. 3:23-cv-06492-VC (N.D. Cal. Nov. 18, 2024)

11. SEC v. Binance Holdings Ltd., No. 23-cv-1599, 2024 WL 3225974 (D.D.C. June 28, 2024)

12. SEC v. Coinbase, Inc., 726 F. Supp. 3d 260 (S.D.N.Y. 2024)

13. SEC v. Glenn W. Turner Enterprises, Inc., 474 F.2d 476 (9th Cir. 1973)

14. SEC v. LBRY, Inc., No. 21-cv-260, 2022 WL 16744741 (D.N.H. Nov. 7, 2022)

15. SEC v. Ripple Labs, Inc., 682 F. Supp. 3d 308 (S.D.N.Y. 2023)

16. SEC v. Terraform Labs Pte. Ltd., 684 F. Supp. 3d 170 (S.D.N.Y. 2023)

17. SEC v. W.J. Howey Co., 328 U.S. 293 (1946)

18. United States v. Storm, No. 1:23-cr-00430 (S.D.N.Y.) (partial verdict Aug. 6, 2025; Rule 29 motion undecided as of June 2026)

19. Van Loon v. Department of the Treasury, No. 23-50669, 122 F.4th 549 (5th Cir. Nov. 26, 2024)

Statutes and Regulations

1. 7 U.S.C. 9(1); 17 C.F.R. 180.1 (Commodity Exchange Act, Sec. 6(c)(1))

2. 12 U.S.C. 5531; 12 U.S.C. 5536 (Consumer Financial Protection Act, UDAAP authority)

3. 15 U.S.C. 45 (FTC Act, unfair or deceptive acts or practices)

4. 15 U.S.C. 77e; 15 U.S.C. 77d(a)(2) (Securities Act of 1933, Secs. 5, 4(a)(2))

5. 15 U.S.C. 77o; 15 U.S.C. 78t(a) (Securities Act of 1933, Sec. 15; Securities Exchange Act of 1934, Sec. 20(a))

6. 15 U.S.C. 78j(b); 17 C.F.R. 240.10b-5 (Securities Exchange Act of 1934, Sec. 10(b); Rule 10b-5)

7. 17 C.F.R. 230.502(d) (Securities Act of 1933, Regulation D, Rule 502(d))

8. 17 C.F.R. 230.506; 17 C.F.R. 230.152 (Regulation D)

9. 17 C.F.R. 230.901-230.905 (Regulation S)

10. 17 U.S.C. 202 (2024)

11. 17 U.S.C. 204(a) (2024)

12. 26 U.S.C. 61(a)

13. 26 U.S.C. 74(a)-(b)

14. 26 U.S.C. 102(a)

15. 26 U.S.C. 118(b)(2), as amended by Pub. L. No. 115-97 (Tax Cuts and Jobs Act of 2017), Sec. 13312

16. 26 U.S.C. 1402

17. 31 U.S.C. 5318(h)

18. 31 C.F.R. 1010.230

19. 31 C.F.R. 1010.430(d)

20. Directive 98/26/EC (Settlement Finality Directive), Art. 3

21. Directive 2014/65/EU (MiFID II), Annex I, Section C

22. FinCEN Guidance FIN-2019-G001, Application of FinCEN’s Regulations to Certain Business Models Involving Convertible Virtual Currencies (May 9, 2019); 31 C.F.R. 1010.100(ff)(5)(ii)(A)

23. GENIUS Act (Guiding and Establishing National Innovation for U.S. Stablecoins Act), Pub. L. No. 119-27, 139 Stat. 419 (July 18, 2025)

24. OCC Notice of Proposed Rulemaking Implementing the GENIUS Act, 91 Fed. Reg. 10202 (Mar. 2, 2026)

25. Regulation (EU) 2016/679 (General Data Protection Regulation), 2016 O.J. (L 119) 1

26. Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on Markets in Crypto-Assets (MiCA), 2023 O.J. (L 150) 40

27. SEC Release Nos. 33-11412; 34-105020 (File No. S7-2026-09), 91 Fed. Reg. 13714 (Mar. 23, 2026)

28. Wyo. Stat. Ann. 17-31-101 to 17-31-116 (Decentralized Autonomous Organization Supplement)

29. Lei No. 6.385, de 7 de dezembro de 1976 (Brazilian securities law)

30. Lei No. 13.709, de 14 de agosto de 2018 (Lei Geral de Proteção de Dados Pessoais, LGPD)

31. Lei No. 14.478, de 21 de dezembro de 2022 (Marco Legal dos Ativos Virtuais)

32. Lei No. 14.754, de 12 de dezembro de 2023

33. IN RFB No. 1.888/2019

34. IN RFB No. 2.291/2025 (DeCripto) (Brazil)

35. Resolução BCB No. 519 (Nov. 10, 2025)

36. Resolução BCB No. 520 (Nov. 10, 2025)

37. Resolução BCB No. 521 (Nov. 10, 2025)

38. Resolução BCB No. 561 (2026)

Official Guidance and Releases

1. Comissão de Valores Mobiliários, Parecer de Orientação No. 40, de 11 de outubro de 2022 (Braz.)

2. Commissioner Caroline A. Crenshaw, Response to Staff Statement on Certain Liquid Staking Activities: Caveat Liquid Staker (Aug. 5, 2025)

3. European Data Protection Board, Guidelines 02/2025 on Processing of Personal Data Through Blockchain Technologies (consultation draft, Apr. 2025)

4. European Securities and Markets Authority, Guidelines on the Conditions and Criteria for the Qualification of Crypto-Assets as Financial Instruments, ESMA75453128700-1323 (final report Dec. 17, 2024; guidelines Mar. 19, 2025)

5. IRS Notice 2014-21, 2014-16 I.R.B. 938

6. OFAC, Tornado Cash FAQs Nos. 1076, 1078, 1079 (Sept. 13, 2022); FAQ No. 1095 (Nov. 8, 2022)

7. Rev. Rul. 2023-14, 2023-33 I.R.B. 484 (Aug. 14, 2023)

8. SEC, Division of Corporation Finance, Statement on Certain Liquid Staking Activities (Aug. 5, 2025)

9. SEC, Division of Corporation Finance, Statement on Certain Protocol Staking Activities (May 29, 2025)

10. SEC, Framework for “Investment Contract” Analysis of Digital Assets (Apr. 3, 2019) (withdrawn and superseded Mar. 17, 2026)

11. SEC, Report of Investigation Pursuant to Section 21(a) of the Securities Exchange Act of 1934: The DAO, Exchange Act Release No. 81207 (July 25, 2017)

Other Sources

1. Circle, Cross-Chain Transfer Protocol (CCTP) burn-and-mint design documentation (2026); Deloitte monthly USDC reserve attestations

2. FFIEC BSA/AML Examination Manual, Appendix P

3. Helius, All You Need to Know About Compression on Solana (2024)

4. Katelyn Holcomb, The Paradoxical Solution to Enforce Resale Royalties, 20 Wash. J.L. Tech. & Arts (2025)

5. MIT License

6. Apache License 2.0, Secs. 3-4

7. GNU GPL v3, Sec. 5

8. GNU AGPL v3, Sec. 13

9. Hossein Nabilou, Probabilistic Settlement Finality in Proof-of-Work Blockchains: Legal Considerations, SSRN No. 4022676 (2022)

10. NYDFS, Guidance on the Issuance of U.S. Dollar-Backed Stablecoins (Industry Letter, June 8, 2022); NYDFS proposed payment-stablecoin rules (2026)

11. OFAC, Tornado Cash SDN removal / delisting (Mar. 21, 2025)

12. Restatement (Second) of Torts Sec. 552 (Am. Law Inst. 1977)

13. SIMD-0204 (slashable-evidence logging) and SIMD-0212 (proposed slashing penalty, not activated), Anza/Solana technical documentation (2025-2026)

14. Sky (formerly MakerDAO), USDS governance and collateral documentation

15. Solana Breakout Hackathon Official Rules 2025 (Colosseum), Secs. 9, 10, 14, 15

16. Solana Docs, Close Account and Rent Reclamation (SPL close_account instruction)

17. Solana Docs, Commitment Levels (processed / confirmed / finalized); Tower BFT vote lockout

18. Solana Docs, Epochs and Staking (epoch length ~432,000 slots; stake warmup and cooldown)

19. Solana Foundation, State Compression and Compressed NFTs (2024)

20. Solana Program Library, SPL Token and Token-2022 SetAuthority documentation (SetAuthority to None for mint/freeze); Solana BPF Loader Upgradeable, set-upgrade-authority –final (as of June 2026)

21. Solana Program Library, Token-2022 extension documentation: InterestBearingConfig, TransferFeeConfig, transfer-hook-interface, confidential-transfer, PermanentDelegate, NonTransferable

22. Squads Protocol v4 program account model (Multisig struct: config_authority, threshold, time_lock; Proposer / Voter / Executor permissions)

23. U.S. Department of the Treasury, Final Rule Extending Recordkeeping Period for Certain OFAC Sanctions-Compliance Records to Ten Years (Mar. 21, 2025)

24. UCC Article 12 (2022 Amendments), Secs. 12-102, 12-104 (controllable electronic records; take-free rule), enacted in D.C. and 25+ states (2024-2025)