The Story Behind This Site

The Setup

The Bitcoin System Constitution is a CC0-licensed standard for what it means to be Bitcoin-aligned. It has no token. No company. No founder allocation. No donations. It is published openly and intentionally written to outlast its author.

When it went online, two domains were registered defensively to keep the namespace from being grabbed by someone hostile: the canonical site at bitcoinsystemconstitution.org, and a shorter alias at bitcoinconstitution.org. The alias was never connected to anything. It had no DNS records. It had never resolved to any IP. It had never served a single byte of content. It existed only to hold the name.

The Complaint

Five days after the defensive .org was registered, an unsubstantiated phishing complaint reached the registrar. Within hours, Tucows applied a five-day clientHold on the domain, and the upstream reseller suspended the entire customer account: every unrelated domain, the VPS hosting this site at the time, and access to support reduced to ticket-only.

The complaint was factually impossible. A domain that has no DNS records cannot resolve. A domain that doesn't resolve cannot serve content. A domain that doesn't serve content cannot host a phishing page. This is not a matter of opinion — it is how the public DNS works, and any first-year systems engineer can verify it from the public record. Independent investigation confirmed: zero archived snapshots in the Wayback Machine, no public DNS record at any major resolver, no nginx server block on the VPS, no traffic in any access log.

But the policy at the reseller was simple: any domain complaint, anywhere, suspends everything. There was no per-domain blast radius. There was no investigation step. The customer was taken offline and asked to prove a negative through a ticket queue.

We pushed back. The clientHold was lifted three days later. But the pattern was the lesson — a single anonymous email had cost several days, several domains, and a publicly visible service. There was no plausible defense that scaled.

The Pattern Underneath

Investigation surfaced a few facts that, taken together, form a context but not a proof:

• A .com of the same name had been parked at GoDaddy since 2020 by an unrelated party, never used.
• A .xyz of the same name had been registered eleven days before our .org and was listed for sale on Afternic at $999 USD by a seller with no other Bitcoin-related history.
• We displaced no one when we registered the .org — but five days later, an unsubstantiated complaint arrived.

These facts are circumstantial. They do not name anyone. They do not prove bad faith. But they form a pattern that anyone watching the domain market recognizes: registrant gets a name, an unsubstantiated abuse report arrives, the registrar reflexively suspends, the registrant is pressured to release the name. Whether or not it was deliberate here, the system is structured so that it works that way.

The Migration

The decision was clear: separate every service across different providers. One vendor with an "any complaint equals full suspension" policy is one anonymous email away from total outage. The lesson cost time, but it was the right one to learn early.

The plan was straightforward, and most of it could be executed immediately:

• Registrar. Move domains away from the original reseller. The first attempted move ran into ICANN's 60-day post-registration transfer lock — a rule designed to prevent fraudulent transfers, but here it functioned as an unintended cage. A secondary plan was needed.
• DNS. Separate from the registrar, so a registrar-level suspension cannot also break name resolution.
• Hosting. Move the VPS to a different jurisdiction and a different vendor.
• Email. Already separate (ProtonMail).
• Source. Already separate (GitHub, CC0).

The most time-sensitive piece was getting new domains registered fast. A second registrar, paid in good faith, took payment for two new registrations and then sat on the order for over twelve hours without provisioning. WHOIS confirmed both names were still publicly available — sitting in the open, exposed to anyone monitoring the namespace.

So we asked the community for help.

The Community

A response came back within minutes. A community member offered to register the names and hold them, no questions asked, before knowing who they were helping. They moved the registrations to a working registrar in under a minute, pointed them at a new VPS, and went to bed. No payment was requested. No conditions were attached.

This is what worked when vendors did not. It is the difference between a system that runs on contracts and a system that runs on principle. The Constitution is not just a document about Bitcoin — it is a document for anyone who has decided to do honest work in a world that does not always reward it. The community member who responded to the call understood that without being told.

The only request: do not name them. Some people prefer to do the right thing quietly, and that preference deserves to be honored.

In thanks, the remaining domains in our collection — the ones still trapped under the original registrar's transfer lock — will be transferred to that community member as soon as they are free. They may be worth something one day if this work continues to matter. They may be worth nothing. Either way, they belong to whoever stepped up when it counted. We trust that they will do the right thing with them. If not, the community will figure it out.

What This Site Runs On Now

• Domains: registered through a community ally, with WHOIS privacy on by default.
• DNS: at the registrar level for now, with delegation to a third party planned.
• Hosting: a fresh VPS at a privacy-respecting host in Iceland — chosen specifically because it is a different jurisdiction, a different vendor, and a different account from the registrar.
• Email: ProtonMail, separate from everything.
• Source code: GitHub, under CC0.
• Evidence record: a public log at github.com/SatNohashi/bitcoinconstitution-org-evidence, updated as events occur.

If any single one of these is attacked, the others remain. That is the lesson.

What Did Not Change

Everything that mattered. The Constitution itself. The principles. The license. The intent. The fact that this work has no token, no presale, no founder allocation, no monetization plan, and no purpose other than to define honestly what it means to be Bitcoin-aligned.

If anything, the experience clarified the work. The Constitution was written, in part, because trusted intermediaries can be coerced into acting against the people who depend on them. That hypothesis — abstract when written — was tested in practice within weeks of publication. The system behaved exactly as the document predicted. The fix was exactly what the document recommended: keep no single intermediary in a position of total leverage.

A Note to Whoever Is Watching

If the abuse report against the original .org was accidental — a user clicking the wrong button on the wrong domain — the public record now exists, and the matter is closed.

If it was deliberate — a squatter trying to free up a name they could resell — the new domains are registered, the site is live, and the namespace is held. The cost of trying again has gone up, and the next attack hits a more distributed system. The Constitution does not go away because a registrar is uncomfortable.

Either way, the work continues. The pattern is on record. The community responded.

Nothing in life goes according to plan. The plan that survives is the one that keeps moving.