Proof of Business (PoB)

Only verified outcomes become value.

PoB is WCN's verification layer. It recognizes business outcomes that can be proved, attributed, and audited — so settlement always reflects what actually happened.

PoB turns real, verifiable results into records the system can admit, track, and use as input for settlement. If it cannot be evidenced, it does not count.

What PoB enforces

01

Result threshold

Only verified outcomes enter the PoB record. Activity without a provable result stays outside.

02

Attribution

PoB tracks who led, who collaborated, and what made the result hold — not a flat participation score.

03

Settlement input

Recorded PoB becomes the structured input for allocation, fees, and governance.

04

Network memory

Validated outcomes persist as durable records — not disappearing chat logs or campaign dashboards.

Boundaries

Rewarded vs. rejected

PoB rewards completed outcomes. If it cannot be evidenced and reviewed, it does not enter the record.

What is rewarded
  • Fundraising outcomes (signed, subscribed, transferred)
  • Market outcomes (measurable conversion and retention)
  • Service delivery (onboarded, delivered, accepted)
  • Liquidity provision (depth, spread, stability)
  • Asset lifecycle (design, issuance, distribution)
  • Agent execution (logged work with attributable results)
What is not rewarded
  • Posts, hype, and activity without outcomes
  • Claims without evidence
  • Bot traffic, wash trading, and circular attribution
  • Side deals that bypass system attribution
Verification

From claim to confirmed record

Five steps take an outcome from raw claim to system-confirmed record: submission, evidence, review, conclusion, and archive.

  1. 01

    Outcome registration

    Register the completed deal or task with clear context and a definition of done.

  2. 02

    Evidence upload

    Attach structured proof: contracts, on-chain references, dashboards, or acceptance records.

  3. 03

    Review

    Reviewers check authenticity, completeness, timeline, and attribution.

  4. 04

    Conclusion

    Approve, request more evidence, reject, or route to disputes.

  5. 05

    Archive

    Accepted records enter the PoB ledger as durable inputs for reputation and settlement.

Proof Desk

The verification control center

Proof Desk is where evidence is collected, reviews are queued, disputes are resolved, and final decisions are issued before anything becomes a PoB record.

  1. Intake

    Evidence packages tied to specific deals and tasks

  2. Review

    Authenticity checks, clarifications, and policy compliance

  3. Disputes

    A clear path to contest outcomes or attribution

  4. Conclusions

    Approve, request more info, or reject — every decision is explicit

Scoring

How PoB is calculated

In plain terms: PoB score = how big was the outcome, how important was it, how strong is the evidence, how well did it hold up, minus any risk flags. The formula below makes this precise.

Formula

Effective PoB=Base Value×Business Weight×Quality×Durability×Risk Discount
  1. 01

    Base Value

    How large is the verified outcome.

  2. 02

    Business Weight

    How strategically important this type of outcome is.

  3. 03

    Quality

    Evidence depth, confirmation count, and audit readiness.

  4. 04

    Durability

    How well the outcome holds up over time.

  5. 05

    Risk Discount

    Disputes, anomalies, and flags reduce the score.

Phase 1 focuses on evidence quality and ledger integrity. Token settlement, if approved at all, is deferred to Phase 3 (M24+) and remains compliance-gated.

Attribution

Attribution matters

Without attribution, PoB only proves a result exists. With it, the network sees who advanced the outcome — essential for fair credit and future allocation.

Boundary

Not a substitute for law

PoB is an operational layer inside WCN. It does not replace securities, tax, or licensing obligations — teams still need proper counsel.

Proof boundary

Review public proof before entering the mechanism.