← Work/CASE · 01 STATUS: SANITIZED CASE STUDY

Trust architecture for a Bitcoin-adjacent launch

A contentious chain split was being explained ten different ways at once. We mapped the confusion, scored the risk, and rebuilt the story into one system the community could actually argue about — correctly.

DOMAINBitcoin-adjacent / chain split TYPETrust system + visuals OUTPUTStrategy · confusion map · launch kit DURATION3 weeks
CONTEXT

A real project, an unreadable story

The technology was sound. The communication wasn't. After a chain split, the public couldn't tell which chain was which, whether their funds were safe, or who was actually in charge — and every channel answered differently.

Sentiment dashboards said “negative.” That wasn't useful. The real problem was structural: a tangle of overlapping questions with no canonical answer anywhere.

AT INTAKE
Dated public captures32
Findings documented47
Contradictory “official” answersSEVERAL
Canonical “is it safe?” answerNONE
METHOD APPLIED
01 Collect 02 Normalize 03 Map 04 Score 05 Synthesize 06 Translate
CONFUSION MAP · AT INTAKESANITIZED
FALSE / HIGH RISK CONTESTED UNANSWERED VERIFIED
Which chain is the real one? “Is it Bitcoin or not?” Replay-attack risk? Who controls supply? “Is my money safe?” Is the team the same? Exchange support

A field of confusion points, one missing center. No surface answered “which chain is real?” the same way — so every other question inherited the ambiguity.

FINDINGS

Three things the map made obvious

01

The center was empty

There was no single canonical answer to the question every other question depended on.

02

Safety read as evasion

The “is my money safe?” answer was technically true but phrased like a dodge — so people assumed the worst.

03

FUD filled the vacuum

Every unanswered node became a place for a confident wrong answer to take hold.

THE REFRAME

From ten stories to one system

BEFORE
“It's the real Bitcoin, basically.”
“Don't worry, your coins are fine” (no how).
“The team moved on” / “same team.”
Five docs, three timelines, zero canon.
AFTER
One canonical “which chain” explainer, linked everywhere.
A claim/proof table: every claim, its evidence, its status.
A plain “is my money safe?” answer with the exact steps.
Open questions labeled open — not hidden.
ACTION PLAN

What we handed over, ranked

P0

Publish the canonical “which chain” explainer

One page, linked from every surface, that fills the empty center.

DAY 1
P0

Rewrite the safety answer in plain language

Exact steps, no hedging, with the “why it's safe” spelled out.

WEEK 1
P1

Ship the claim/proof table

Every public claim, its evidence, and an honest status flag.

WEEK 2
P2

Stand up a confusion-watch

Lightweight monitoring so new misreadings get caught early.

ONGOING
WHAT THEY IMPLEMENTED

They shipped four of four within a month

Canonical explainer published and pinned everywhere
Plain-language safety answer in the FAQ & docs
Claim/proof table live and maintained
Confusion-watch handed to the community team
“Which chain” repeat-asks↓ sharply
Docs “clarity” rating
Canonical answer coverage1 → every surface

Directional, sanitized outcomes · rigor & clarity signals, not market metrics.

“We thought we had a sentiment problem. We had a missing diagram. Once the center existed, the arguments got smarter.”

— CORE CONTRIBUTOR · SANITIZED