Full analysis selected. Choose Quick brief to read the key points first.
WFN QUICK BRIEF · UNDER 1 MIN
The short version
MODE 2 OF 2
What a verifier checks
BIP 322 defines a generic signed-message format. The verifier constructs virtual transactions from the message and evaluates a spending proof against the target script. This allows verification for script types beyond the legacy compact-signature convention. Compatibility depends on the signing and verification software and the chosen proof format. BIP 322 · Generic signed message format ↗
Give the proof a narrow purpose
A service verifying control of an address can include its domain, a fresh challenge, the address and an expiration time in the message. A valid proof establishes that the script requirements were satisfied for that challenge. The service needs separate evidence for the user’s legal identity, the origin of funds or ownership of any balance beyond what it explicitly verifies.
Handle reuse and compatibility
Display the full message before signing and verify its exact bytes. Reject stale or previously used challenges and keep the network, address and proof format with the record. Test both a supported address and one your verifier cannot validate, so compatibility errors are visible to the user.
Quick Brief is a reading aid. The full article and source trail stay on this page.
01 · VERIFIED RECORD
What a verifier checks
BIP 322 defines a generic signed-message format. The verifier constructs virtual transactions from the message and evaluates a spending proof against the target script. This allows verification for script types beyond the legacy compact-signature convention. Compatibility depends on the signing and verification software and the chosen proof format. BIP 322 · Generic signed message format ↗
02 · WFN EDITORIAL ANALYSIS
Give the proof a narrow purpose
A service verifying control of an address can include its domain, a fresh challenge, the address and an expiration time in the message. A valid proof establishes that the script requirements were satisfied for that challenge. The service needs separate evidence for the user’s legal identity, the origin of funds or ownership of any balance beyond what it explicitly verifies.
03 · REVIEW POINTS
Handle reuse and compatibility
Display the full message before signing and verify its exact bytes. Reject stale or previously used challenges and keep the network, address and proof format with the record. Test both a supported address and one your verifier cannot validate, so compatibility errors are visible to the user.
Original WFN vector illustrationWFN · 9 November 2026
Reading tools and source notes
WFN STORY COMPASS
Choose your reading angle
Switch between the reported record, market context and open questions. Status labels distinguish claims from findings.
All context layers are visible. Choose a lens to jump to that part of the story.
Editorial noteSource-based explanation with original WFN analysis. Historical records retain their dates; numerical examples are illustrative. The original vector illustration is conceptual and is not documentary evidence.
WFN REALITY LEDGER
What is on the record?
Primary-source explainer
Primary-source explainer
Primary record / reference periodBIP 322 · Generic signed message format
