How to use a proposed US framework without lying

There is a useful fact and a dangerous one, and they travel together. Useful: founders, counsel and boards are planning around a proposed US framework for crypto-asset offerings. That planning is demand. Dangerous: people speak as if the proposal were already the path. A proposal can change, stall, be replaced, or issue in a form that does not match the deck.

Permitted public language, if any, is small: that the team is watching a proposed framework; that any US offer will follow counsel and live rules; that this communication is not an offer. Prohibited: “Reg CA-compliant,” “the new Reg A,” “retail-ready in the US,” “waiting on the exemption” as if the wait were a queue with a number.

Operationally, use the attention to professionalise. Claims, geographies, providers, a desk. Those artefacts remain if the proposal dies. The artefacts we refuse to produce are the ones that only work if a specific final rule arrives: a public sale page, an allocation waitlist, a creator script that tells a general US audience they can participate. Those are a different business.