WCNWeb3 Capital Network
v1.0Interface contract · public API boundary pending

Build against the proof boundary.

A compact docs console for developers and operators: quickstart, proof submission, node records, deal tasks, registry lookups, and event webhooks.

Open source libraryOpen wiki

Guide sections

04

Quickstart to proof review

Endpoint families

05

Proof, nodes, deals, registry, webhooks

Languages

03

cURL, JavaScript, Python

01 · Orientation

Docs begin at the boundary, not the pitch.

WCN's public docs define how external builders should think about proof objects, reviewed nodes, and event surfaces without exposing private deal files.

  • Public pages explain concepts and safe fields.
  • Private evidence stays behind permissioned review.
  • API availability is published only after the boundary is approved.

02 · Access

Authenticate every write, review every proof.

The intended API model is scoped access. Writes must be attributable, repeatable, and reversible when a review fails.

  • Use bearer keys only after approval.
  • Send idempotency keys for write operations.
  • Treat public summaries as outputs of review, not raw uploads.

03 · Quickstart

Submit proof, wait for review, then publish safely.

A typical integration creates a proof packet, receives an in-review state, and later listens for a signed event when the summary is approved.

  • Create a proof packet for a known task.
  • Store the returned proof id for reconciliation.
  • Listen for proof.published rather than polling raw evidence.

04 · Review model

The review layer is part of the protocol.

WCN is evidence-first. The useful artifact is not the upload itself; it is the reviewed proof object that can support attribution, settlement, and reputation.

  • Reject unverifiable submissions.
  • Separate private proof from public proof summary.
  • Keep disputes and revocation paths explicit.

API reference

POST/v1/proof

Submit a proof

Create a proof packet for review. Public output stays limited to safe summaries; private evidence remains permissioned.

Parameters

taskstringRequired

The reviewed task or deal-task identifier.

evidenceuriRequired

A private or content-addressed evidence reference.

idempotency_keystringOptional

Prevents duplicate submissions during retries.

Errors

401unauthorizedMissing or invalid API key.
409duplicate_submissionThe idempotency key has already been used.
422validation_errorRequired evidence fields are missing or malformed.

Request

example
curl https://api.wcn.network/v1/proof \
  -H "Authorization: Bearer $WCN_KEY" \
  -H "Idempotency-Key: proof_2026_06_30_001" \
  -d '{ "task": "task_8fK2a", "evidence": "ipfs://bafy..." }'

Response

example
{
  "id": "proof_3xQ",
  "status": "in_review",
  "public_summary": null
}

Source resources

System LibraryOriginal HTML source archive for WCN's 72 systems, design system, and operating documents.Open systems →WikiCanonical knowledge base for WCN concepts, proof logic, node system, governance, and roadmap.Read wiki →DevelopersConservative developer entry point that records the current public API boundary and integration posture.Developer boundary →

Changelog

v1.0

  • Launched native /docs portal.
  • Added proof, nodes, deals, registry, and webhook endpoint contracts.
  • Linked docs to the source system library and wiki.