Why SignalFire exists

Most conviction online is cheap talk. SignalFire makes commitment expensive — on purpose.

The problem

The internet has a bad memory, and worse, a flexible one. Posts get edited. Predictions get quietly rewritten when they miss. Claims vanish when inconvenient. Track records are optional.

This makes it hard to tell a real position from a confident guess, or a forecaster with a record from someone loud on the last thing they got right.

The idea

SignalFire stands on two commitments that reinforce each other:

A claim is only credible when it has cost. Free statements are noise — and everyone knows it.
A claim only matters if it can be judged. Statements no one can hold you to are performance.

Neither works on its own. Paired, they produce something rare on the modern internet: a cryptographically sealed, economically backed, timestamped claim that reveals automatically and is publicly judged on its own terms.

Examples

Patterns SignalFire is built for:

THE ANALYST'S FORECAST

Put your prediction on record

A forecaster calls a specific outcome: “BTC tops at $140k by Q2 2026.” They burn 10 DGB, lock the signal for 90 days. On day 90 it reveals automatically and readers vote Accurate / Wrong / Debatable. Over time their signals accrue a public track record — the kind you can't edit later.

THE FOUNDER'S DEADLINE

Make a public promise with teeth

A team commits: “We will ship feature X by September 1st.” 100 DGB burned, 60-day lock. On the deadline the commitment reveals, and anyone can judge whether they shipped. The burn is real. The promise is auditable. The track record follows the team.

THE EMBARGOED STORY

Timestamp an investigation

A journalist finishes a sensitive story but isn't ready to publish. They seal it with a 30-day unlock and a 1 DGB burn. On day 30 it reveals byte-for-byte what was sealed — no edits, no rewrites, hash provably unchanged. The on-chain burn timestamps the finding; the IPFS commitment proves nothing was rewritten in transit.

THE PRIORITY CLAIM

Prove you had it first

A researcher has a novel idea but isn't ready to publish. They seal a draft with a 6-month unlock and a 5 DGB burn. Months later, when the work comes out, anyone can verify their idea predates competing publications: hash match, unfakeable timestamp, unbreakable chain of commitment.

Who it's for

Analysts and forecasters who want a provable track record
Journalists with time-sensitive disclosures
Founders making public commitments they want taken seriously
Researchers claiming intellectual priority
Anyone who thinks online memory should be harder to edit

How it works, briefly

Sign in with Digi-ID — no passwords, just your DigiByte address.
Compose your signal. Encryption happens in your browser before anything leaves it.
Choose an unlock time and burn amount. The conviction preview updates live.
Broadcast the burn transaction from any DGB wallet. Sign the Digi-ID confirmation.
The signal sits on the feed with metadata only — no body — until the unlock time.
At unlock, a background job releases the decryption key. The content reveals, integrity-verified.
Readers judge Accurate / Wrong / Debatable.

For the technical details — encryption scheme, burn-address derivation, verification pipeline — see the repo README.

A product of Orange-Hat, LLC. Built on DigiByte.