№ 08·0408 · Proof of Business2 min read · Section 4 of 6
8.4 Verification process
From submission through evidence, review, and Reconciliation to a Verification Node — with the states Verified, Sealed, and Settled, and a Verdict for disputes.
Updated
8.4 · Verification process
Happened is not confirmed. A result enters the Proof Ledger only after Reconciliation, when it becomes a long-term value input.
Onchain consensus confirms a transaction sequence and a state transition. PoB confirms whether a thing happened in the business world as claimed. The verification process compresses a subjective narrative into a reviewable workflow: material completeness, time consistency, attribution coherence, and a check against the exclusions of 8.3.
What this page doesSets out the verification steps, the record states, and the review function
Core themesBurden of proof, review, Reconciliation, Verdict
Reading highlightsSupplement, rejection, dispute; the states a record can hold
The verification steps
Each step carries the burden of proof on the submitting party. Material an independent reviewer cannot examine does not advance.
Event submission
Generate a unique event number for the result and bind the Deal, the task, the related nodes, and the closed-loop type. The submitter carries the burden of proof: any gap in material must be filled within the time limit.
Evidence package
Submit contracts, onchain references, bank or escrow paths under compliance, correspondence, and acceptance records per the template. The material must let an independent party re-review the conclusion, not merely trust the applicant.
Review queue
The reviewer checks authenticity, completeness of the closed loop, time sequence against backdating, the attribution boundary of 8.5, and the exclusions of 8.3. Multi-signature, rotation, or sampling can apply.
Reconciliation
The Project, Capital, and Proof ledgers are matched line by line to remove discrepancy. The outcome is one of: passed, supplement required, rejected, or dispute. Supplements carry a frequency and time limit; an objection is recorded so nothing passes by silence. A contested case ends in a Verdict.
Verification Node
A passed record writes its conclusion hash, key metadata, and version, producing a Verification Node — the single anchor any party can check. The record is marked Verified. It anchors later settlement, reputation, and re-review.
A miner proves computing power. PoB review proves the consistency of material and fact. A reviewer's identity does not replace the evidence package — the material still has to hold.
The states a record can hold
Once a Verification Node exists, the record moves through defined states. Each state is precise, and none is reversible past Sealed.
VerifiedThe record passed Reconciliation across the three ledgers. The result is recognized and anchored to a Verification Node.
SettledThe Capital ledger completed clearing for the transaction. Distribution against the record is done.
SealedThe record is locked in a final state that can no longer change. It stands as a permanent anchor.
VerdictA dispute or audit reached a conclusion that cannot be appealed. The Verdict closes the contest and binds attribution.
Where anti-cheating sits in the process
The process resists distortion through cross-checks and mutual-exclusion rules, not through trust in a name.
Cross-checkOnchain time, the counterparty email domain, and the contract number are matched against public disclosure.
Mutually exclusive eventsOne financing round or acceptance target allows one Sealed lead chain, unless a Verdict splits it.
Cooldown and frequencyAbnormal frequency or templated material triggers manual or algorithm-assisted review.
Evidence chain availableThe chain stays available for external audit and regulatory review — examinable, not self-attested.
The verification process moves WCN from "who is loudest" to "whose material holds." Without it, PoB is no better than off-chain bookkeeping, and easier to tamper with.
