Web3

The SEC Rewrote the Crypto Whitepaper. Now Design It.

The SEC published its crypto offering rules on August 18. Most of the coverage went straight to the money: \$5 million under one exemption, \$75 million a year under the other. Fair enough, those are the numbers a founder checks first. But proposed Rule 103 carries a requirement that lands on a completely different desk. If you use either exemption, your disclosures have to be public, free of charge, and hosted on a website you name in a filing with the Commission. Lawyers do not build that. Somebody has to design the page, ship it, and keep it current after the raise closes.

ClefDev Studio
ClefDev Studio
August 31, 2026 6 min read
The SEC Rewrote the Crypto Whitepaper. Now Design It. cover

What the proposal actually does

Regulation Crypto Assets is file S7-2026-27, issued August 18 and published in the Federal Register on August 21. Comments close October 20. It is the SEC's first real rulebook for token offerings after roughly a decade of guidance letters and enforcement actions, and it landed without warning. CoinDesk noted the agency had cancelled the August 14 meeting that was meant to put it to a vote, then issued the proposal anyway four days later.

There are two exemptions from Securities Act registration. A startup exemption covers up to $5 million over a four-year period, once. A fundraising exemption covers up to $75 million in any twelve months, structured in two tiers, with unaudited financial statements at the $20 million tier and audited statements above it. Both require what the Commission calls principles-based disclosure. Chairman Paul Atkins framed the goal as giving builders "clear pathways to raise capital under the federal securities laws." Commissioner Hester Peirce, who has been arguing for a token safe harbor since a 2020 speech about a New Jersey gas station, wrote that the aim is rules that are "sensible, clear, and enforceable."

The proposal also preempts state registration requirements for offerings made under it, and it builds on the joint SEC and CFTC interpretation from March 17 of this year. That simplifies the legal position and considerably enlarges the publishing job.

That phrase, principles-based, is doing a lot of work. The Commission lists what you have to cover and says close to nothing about how it should look.

Ten topics, no template

Rule 103 sets out around ten disclosure areas. The investment contract and the managerial work the issuer promises to do. Terms of the offering. The crypto asset itself. Management and conflicts of interest. Plans for developing the network. Security and source code. Token economics and allocations. Governance. The surrounding ecosystem. Risk factors.

Read that as a content brief and it is already large. Read it as an information architecture problem and it gets harder, because nobody is handed a template. The predictable result is thirty screens of legal prose with the token allocation buried in a paragraph instead of shown as a chart. Some teams will produce something a normal person can read. Plenty will produce a wall and call it compliance.

The whitepaper stops being a document

The bigger shift is time. Under the fundraising exemption an issuer files annual reports within 120 days of fiscal year end, semiannual reports within 90 days, and current reports within four business days of certain events. Sidley's read of the proposal states the hosting condition plainly: the Rule 103 disclosures have to be publicly available, free of charge, on a website identified in the notice of reliance.

Four business days is a product requirement, not a legal one. It means the disclosure site cannot be a PDF exported from a Word file and pinned in a Discord channel. It needs a content model, an owner who is not a lawyer with FTP access, a review path, version history, and a layout that survives a fresh paragraph of risk language being added on a Thursday afternoon.

That is unglamorous infrastructure work. It is also the difference between a disclosure site that stays accurate and one that quietly rots six months after the raise, which is roughly when someone notices the team page still lists two people who left.

Put the load-bearing facts where the decision happens

Almost nobody reads a disclosure site before buying a token. They read the buy screen.

So the design job is not only the disclosure page. It is deciding which four or five facts out of those ten topics have to appear inside the product at the moment somebody commits money. How much of the supply the team holds. When it unlocks. Who can mint more. What the issuer has publicly promised to build and has not built yet. The complete record lives on the disclosure site and you link to it. The facts that change the decision live in the flow. This is where most of our time goes with Web3 teams, and it is nearly always an argument about how much one screen can carry.

The SEC is not asking for that. It is asking for the site. But the antifraud and antimanipulation provisions still apply as usual, which is Peirce's way of noting that a technically complete disclosure page will not help you if the interface tells a different story.

A token's status is a state, not a fact

The proposal includes a conditional safe harbor. If an issuer completes, or permanently ceases, the essential managerial efforts it said it would perform, the crypto asset can be treated as no longer subject to that investment contract.

Think about what that does on screen. The same token can be one thing in year one and something else in year three, and its legal character depends on work the team said it would do. Most crypto interfaces present a token as a fixed object with a price and a chart next to it. Under this proposal it behaves more like a state machine, and the roadmap stops being marketing. It becomes the condition the safe harbor turns on.

Designing that honestly is hard. A roadmap with legal weight cannot be four vague quarters on a landing page, and it cannot quietly change when a milestone slips.

Before October 20

None of this is law yet. Sixty days of comments, then a final rule that may look different, then whatever Congress does or does not do about market structure. Proposals die all the time.

The direction still looks set. Token disclosure moves from a document you publish once to a public interface you maintain. If you are building in this market, the useful move this month is to file a comment while the format question is genuinely open, and then start treating the disclosure page as part of the product rather than something the lawyers will sort out later. Teams that start now will build it properly. The ones that wait will retrofit it against a deadline.

Sources

  1. U.S. Securities and Exchange Commission, "SEC Proposes New Regulation Crypto Assets", August 18, 2026sec.gov
  2. U.S. Securities and Exchange Commission, "Regulation Crypto Assets" (proposed rule, File No. S7-2026-27), August 18, 2026sec.gov
  3. Commissioner Hester M. Peirce, "Filling the Regulatory Tank: Regulation Crypto Assets Proposing Release", August 18, 2026sec.gov
  4. CoinDesk, "U.S. SEC proposes first major crypto rule in surprise announcement", August 18, 2026coindesk.com
  5. Sidley Austin, "The Wait is Over: SEC Proposes 'Regulation Crypto Assets,' A Bespoke Offering Regime for Crypto Investment Contracts", August 20, 2026sidley.com
  6. Morrison Foerster, "SEC Proposes New Regulation Crypto Assets", August 19, 2026mofo.com
ClefDev Studio

ClefDev Studio

Design team · Riga, Latvia

We are a design studio working with iGaming, Web3 and fintech brands. Notes from the studio are written by the people working on the projects, not by a content team.