#market-structure

A useful policy pack needs one regulator hub, one public-interest research archive, one market-structure explainer, and one open technical document set. Without all four, the conversation usually collapses into slogan warfare.

The kinds of materials worth saving in this space:
- plain-language explainers of proposed legislation
- agency material that shows enforcement posture over time
- operator notes on how policy changes affect real product decisions

Read:
- SEC crypto assets hub: sec.gov/crypto-assets
A practical way to follow official statements, alerts, and enforcement-adjacent materials.
- Coin Center research archive: coincenter.org/research/
Useful for plain-language policy analysis and legislative interpretation.
- EU crypto asset rules overview: finance.ec.europa.eu/digital-finance/eu-rules...
Helpful for comparing US uncertainty with a more formal legislative framework.

Documents and downloadable guides:
- FATF virtual assets guidance: fatf-gafi.org/en/publications/Fatfrecommendat...
Still one of the key references for travel rule and risk-based compliance conversations.
- FinCEN guidance library: fincen.gov/resources/statutes-regulations/gui...
Useful when readers need the U.S. guidance record instead of secondhand summaries.

Watch:
- Coin Center video archive: youtube.com/@coincenter/videos
A useful complement when policy readers want public explainers and hearings context.

Build or inspect:
- Ethereum Improvement Proposals: github.com/ethereum/EIPs
Primary-source technical documents that often sit underneath policy claims.
- OpenZeppelin contracts: github.com/OpenZeppelin/openzeppelin-contracts
Useful when policy questions touch real smart-contract patterns and controls.

Image references:
- FATF virtual assets topic page: fatf-gafi.org/en/topics/virtual-assets.html
A compact jumping-off point for policy diagrams, updates, and linked guidance.

One common mistake is treating every speech as if it were binding policy. Another is talking about stablecoins, exchanges, and developer infrastructure as if they all live under the same policy logic.

Common traps to watch:
- treating every speech as binding policy
- ignoring how rules differ across stablecoins, exchanges, and wallets
- waiting for certainty before planning operational responses

References that help correct the drift:
- Coin Center research archive: coincenter.org/research/
Useful for plain-language policy analysis and legislative interpretation.
- FATF virtual assets topic page: fatf-gafi.org/en/topics/virtual-assets.html
A compact jumping-off point for policy diagrams, updates, and linked guidance.

This folio post is meant to be saved and revised. Add examples from your own work whenever one of these mistakes keeps resurfacing.

A useful workflow starts with the specific asset or service, then maps the agencies, lawmakers, jurisdictions, and technical assumptions that matter to that product. That is slower than reacting to headlines and much better than building a policy memo around vibes.

A sequence I would actually hand to a teammate:
1. Map the policy issue to the specific asset, actor, and jurisdiction involved.
2. Track which agencies or lawmakers can actually change outcomes on the timeline that matters.
3. Translate policy movement into operational scenarios for products, treasury, and go-to-market choices.

Useful operating references:
- Coin Center research archive: coincenter.org/research/
Useful for plain-language policy analysis and legislative interpretation.
- Ethereum Improvement Proposals: github.com/ethereum/EIPs
Primary-source technical documents that often sit underneath policy claims.

If your team has a better workflow, post it with the context around team size, constraints, and exactly where the process tends to break.