Node-capacity network

The responsibility network behind Accessura Protocol.

In Accessura Protocol, node roles are functional capacities rather than fixed identities. The network needs market support for thin books, operational verification for daily trading, distribution and routing for biding requests, formal challenge and Jury Review for contested cases, and slow-variable governance around the shared rules.

Early on, the platform and selected partners may carry several of these capacities at once. As the market matures, eligibility, service bonds, conflict screening, and reputation separate sensitive actions at the case, route, or transaction level. Red-corridor policy enforcement remains outside ordinary network adjudication.

Node capacities
6

Market support, verification, routing, dispute, governance, boundary

Responsibility assets
3

Stablecoin bond, native token, reputation

Launch path
Staged

Managed Launch, Agent-Assisted, Open Market

Staking & Incentives

Responsibility capital, not brochure APRs.

Responsibility layer

Market Support Node

  • Stake
    IllustrativeLiquidity-support bond + bounded inventory commitment
  • Yield
    IllustrativeCold-start liquidity incentives + starter-quote support
  • Slash
    Spoofing, wash volume, unsupported quote withdrawal
  • Notes
    Backs starter quotes, RFQ quote support, and PMM-side continuity while organic depth is thin.

Commerce settles in USDC. Token and reputation sit on top as accountability and governance layers rather than replacing stablecoin-denominated market flow.

Responsibility layer

Verification Service Node

  • Stake
    IllustrativeQualified service bond
  • Yield
    IllustrativeService fees + governed incentives
  • Slash
    Conflict breach, negligent checks, service-policy breach
  • Notes
    Backs source, ownership, freshness, schema, duplicate-risk, and delivery-readiness checks.

Commerce settles in USDC. Token and reputation sit on top as accountability and governance layers rather than replacing stablecoin-denominated market flow.

Responsibility layer

Challenger / Jury Service Node

  • Stake
    IllustrativeChallenge bond or qualified adjudication stake
  • Yield
    IllustrativeCase fees + valid-challenge redistribution
  • Slash
    Frivolous challenge, conflict violation, poor case handling
  • Notes
    Makes contestability real and resolves escalated cases inside bounded question sets.

Commerce settles in USDC. Token and reputation sit on top as accountability and governance layers rather than replacing stablecoin-denominated market flow.

Final thresholds, yield formulas, and access rules are governed variables. The durable point is structural: stablecoin bond protects the trade, native token carries broader service accountability, and reputation remembers behavior the market should not forget. Market support incentives are cold-start-only and should shrink as organic orderbook depth grows.

Trade-level seller stake (separate from node stake)

Per-trade deposit + fraud penalty.

Every trade locks a seller-side Deposit (D_j), sized proportionally to predicted quality (δ · p · q · θ̂). It releases with payout on successful delivery. Confirmed fraud claws back the Deposit and triggers a hard reset on the seller's Reputation (r_u); normal misses only dampen it via EMA decay. This sits on top of whatever node-operator stake the seller may also hold — seller stake scales with trade flow, node-capacity stake is set by service role.

Asset architecture

Three-layer asset structure.

1

Stablecoin Layer

USDC bond and settlement collateral. The first-line safety asset for payout, refund, and dispute resolution.

2

Native Token Layer

The accountability and governance asset. Used for network participation, longer-horizon alignment, and governed incentives rather than day-to-day commerce.

3

Reputation Layer

Non-transferable and non-purchasable. Accumulates through accurate service, valid challenge behavior, and reliable delivery, and cannot be bought around with stake.

Role incentives

Six behaviors the network wants to reward.

Market Support Node

Supports thin books and lane formation while organic depth is still growing.

Verification Service Node

Supplies daily source, ownership, freshness, schema, and delivery-readiness checks.

Distribution / Routing Node

Improves RequestBrief routing, buyer matching, and route-time quality scoring.

Challenger / Jury Service Node

Posts bonded disputes and resolves escalated cases under conflict rules.

Governance Participant

Tunes slow variables such as corridor thresholds, eligibility, incentive budgets, and bond rules.

Platform Boundary Operator

Handles Red-corridor hard stops that ordinary network governance cannot decentralize.

Trust governance

Decentralized where claims are contestable, bounded where law is not.

The node-capacity network decentralizes challenge, verification service, Jury Review, market-support parameters, and slow-variable governance. It does not decentralize irreducible boundary decisions or let ordinary voting override case evidence.

Assertion Oracle

The bounded question-set layer for contestable claims.

Operated by: Verification service under governed rules

  • Turns listed or delivered objects into machine-readable, challengeable assertions.
  • Question-set versions are governed standards; they are not rewritten mid-case to force an outcome.

Challenge

A bonded public process for disputing listings and response offers.

Initiated by: Any qualified Challenger

  • A challenge must point to a concrete alleged defect rather than vague dissatisfaction.
  • Successful challenge returns the bond plus a bounty; failed challenge loses bond and bandwidth.

Quarantine

Temporarily isolates disputed or boundary-sensitive objects from ordinary routing and settlement.

Triggered by: Challenge thresholds or boundary actions

  • Quarantined objects are removed from ordinary routing until trust review or boundary handling resolves them.

Jury Review

Case-specific adjudication by qualified verifier capacity.

Panel drawn from: eligible service capacity

  • Panels apply bounded question sets to evidence in scope and do not rewrite global policy mid-case.
  • Verdicts are timestamped, logged, and feed later routing, bond, and precedent decisions.
Hard boundary

What ordinary governance cannot do.

Ordinary trust governance may tune:corridor thresholds, challenge-bond ranges, node eligibility, market-support budgets, fee bands, question-set versions, and other slow variables.

Ordinary trust governance may NOT:decide a live case by sentiment, erase a settlement record, convert Red-corridor material into normal market inventory, or grant any seller permanent non-challengeable status.

Case resolution stays inside the dispute path. Red-corridor enforcement stays with the platform boundary layer.

Governance architecture

Four layers of final-form trust governance.

1

Boundary Layer

Platform-held Red-corridor lines: sanctions, MNPI, rights blocks, restricted-party handling, and emergency restriction. These boundaries do not decentralize into ordinary trust voting.

2

Assertion Layer

Every object generates a standardized assertion at listing time, with level-specific question sets. Listing is assertion — assertion is challengeable.

3

Dispute Layer

Bonded challengers surface specific defects. Challenger / Jury Service Node capacity adjudicates contested claims under corridor-specific rules.

4

Governance Layer

Token + reputation governance changes slow variables: bond ranges, corridor thresholds, node eligibility, incentive budgets, fee bands, and question-set versions. It does not decide live disputes by popularity.

Next step

Inspect the trust stack behind the market.

This page shows the node-capacity network in product terms. For the mechanism narrative, read how matching, market support, delivery, verification, and settlement fit together. For builder-facing surfaces, inspect the protocol reference.

Read the mechanismReview protocol layers