Skip to main content
Skyzai

DEX Settlement Badges

info

Active portfolio classification — 2026-07-25 [D]. DEX Settlement Badges is a pre-launch settlement-evidence capability inside Skyzai Work, not an independent SKU, package, exchange, settlement rail, insurer, or authority source. Product, pricing, commercial-page, and standalone-launch language below is preserved design history; route names and local fixtures do not prove external replayable settlement.

note

Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system. A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer. AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt. Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt. Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.

Scope: capability inside the two buyer products (Skyzai Personal / Skyzai Work ✱) — not a standalone SKU. See The Product Family.

Surface: dex.skyzai.com (declarative) Catalog route: skyzai.com/products/dex-settlement-badges/ Status: SPEC Evidence tier: [D] — badge taxonomy ratified; first external counterparty verification is the proof gate (re-tiered [B]→[D] 2026-07-03 per TIER_MERGE_GATE: a spec/draft is not an observed run; [B] requires a dated reproducible receipt) Source canon: 02_SKYZAI/02_ORGANISM_COMMONS/NOOSPHERE/03_PRODUCTS/dex_settlement_badges/WEBSITE.md

What DEX Settlement Badges Are​

DEX Settlement Badges are verifiable status indicators for settlement legs. A badge is:

  • Evidence-based — derived from on-chain or adapter proof, not reputation
  • Replayable — can be re-verified against current chain state
  • Tier-tagged — evidence tier visible, no claim above proof
  • Non-attestational — we verify what happened, not what will happen

Critical boundary: We do not guarantee settlement, insure against failure, or replace legal contract enforcement. We verify evidence.

Badge Types​

BadgeMeaningEvidence Required
SETTLEDDLT-confirmed, replayable[B] On-chain receipt with ≥12 confirmations
CONFIRMEDAdapter-confirmed, not yet DLT-settled[E] Provider receipt, pending chain finality
PENDINGAwaiting confirmation[I] Submitted, no receipt yet
FAILEDReverted or invalid[B] Revert receipt or failure proof
DISPUTEDChallenge raised, under review[I] Dispute filed, review pending

No badge upgraded without proof. SETTLED requires [B] receipt with replayable chain evidence.

Verification Architecture​

┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│  Settlement │────▶│  Receipt    │────▶│  Verifier   │────▶│   Badge     │
│  Request    │     │  Capture    │     │  Engine     │     │   Issued    │
└─────────────┘     └─────────────┘     └─────────────┘     └─────────────┘
                                              │
                    ┌─────────────────────────┼─────────────────────────┐
                    ▼                         ▼                         ▼
              ┌─────────┐              ┌─────────┐               ┌─────────┐
              │   DLT   │              │ Adapter │               │  Replay │
              │  Chain  │              │ Receipt │               │  Check  │
              │ Verify  │              │ Verify  │               │         │
              └─────────┘              └─────────┘               └─────────┘

Verification Process​

class SettlementVerifier:
    def verify(self, receipt: SettlementReceipt) -> Badge:
        # 1. Receipt integrity
        if not receipt.verify_signature():
            return Badge.FAILED("invalid_signature")

        # 2. Chain state verification
        if receipt.chain_receipt:
            tx = self.w3.eth.get_transaction(receipt.tx_hash)
            if tx.blockNumber and self.confirmations(tx) >= 12:
                return Badge.SETTLED(receipt)
            elif tx.blockNumber:
                return Badge.CONFIRMED(receipt, confirmations=self.confirmations(tx))

        # 3. Adapter verification
        if receipt.adapter_receipt:
            adapter = self.get_adapter(receipt.adapter_id)
            if adapter.verify(receipt.adapter_receipt):
                return Badge.CONFIRMED(receipt)

        # 4. Pending
        return Badge.PENDING(receipt)

    def replay(self, badge: Badge) -> Badge:
        """Re-verify a badge against current chain state."""
        return self.verify(badge.receipt)

Settlement Receipt Schema​

{
  "settlement_id": "set_2026_abc123",
  "type": "dex_swap",
  "status": "settled",
  "badge": "SETTLED",
  "evidence_tier": "B",

  "trade": {
    "from": {"asset": "USDC", "amount": "1000.00"},
    "to": {"asset": "ETH", "amount": "0.5"},
    "rate": "2000 USDC/ETH"
  },

  "chain_evidence": {
    "tx_hash": "0x...",
    "chain": "base",
    "block_number": 12345678,
    "confirmations": 15,
    "timestamp": "2026-05-09T12:00:00Z",
    "receipt_verified_at": "2026-05-09T12:05:00Z"
  },

  "adapter_evidence": {
    "adapter_id": "uniswap_v3",
    "adapter_receipt": "0x...",
    "adapter_verified": true
  },

  "replay": {
    "replayable": true,
    "last_replay": "2026-05-09T12:10:00Z",
    "replay_result": "confirmed"
  },

  "ofn_receipt": "ofn:2026:set_abc123...",
  "authorization_receipt": "receipt:..."
}

The active schema uses a typed authorization_receipt; a public-DAV consequence requires at least two natural-person councilors to bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies only; agents stage unsigned proposals, whose IDs cannot substitute for the receipt; deterministic settlement is limited to that exact receipt-bound consequence.

The exact superseded compatibility statement follows as dated K3 provenance.

The k2_signature field is a legacy field name retained for schema backward compatibility. It carries K2 signatures for envelopes ratified pre-2026-05-09 and PRISM council proposal IDs post-transition (per K2_DEPRECATION.md).

API Specification​

POST /v1/verify​

Submit settlement for verification.

Request:

{
  "tx_hash": "0x...",
  "chain": "base",
  "expected_trade": {
    "from": "USDC",
    "to": "ETH",
    "amount": "1000"
  }
}

Response:

{
  "badge": "SETTLED",
  "settlement_id": "set_2026_abc123",
  "evidence_tier": "B",
  "chain_confirmations": 15,
  "replayable": true,
  "ofn_receipt": "ofn:2026:..."
}

POST /v1/replay​

Replay a settlement verification.

POST /v1/batch​

Batch verify multiple settlements.

GET /v1/badges/{id}​

Retrieve badge status and history.

GET /v1/export​

Export settlement proof for regulatory/compliance use.

Adapter Support​

AdapterTypeChainsStatus
Uniswap V3DEXEthereum, Base, ArbitrumPlanned
CurveDEXEthereum, BasePlanned
1inchAggregatorMulti-chainPlanned
Circle CCTPBridgeEthereum, BasePlanned
CustomGenericAnyEnterprise

Evidence Tiers​

TierClaimRequired Evidence
[I]Badge architecture is definedDesign document
[B]Verification stub + badge taxonomy ratifiedInternal stub-test green
[E]Live settlement verified and replayedMainnet receipt, replay proof
[A]Settlement badges used in audited financialsExternal audit report

Current status: [B] — verification stub exists; first external counterparty verification is the proof gate.

What This Service Is NOT​

  • Not a DEX operator
  • Not custody — no funds, tokens, or assets held at any point
  • Not a settlement guarantee — we verify rail evidence; we don't coordinate via AIA/AMMs settlement
  • No finality claim before the source rail's evidence resolves
  • No compliant badge before replay passes against source data

Regulatory Export​

Settlement proof can be exported in regulator-ready format:

{
  "export_type": "regulatory_settlement_proof",
  "period": {"from": "2026-05-01", "to": "2026-05-09"},
  "settlements": [...],
  "audit_trail": "...",
  "attestation": {
    "signed_by": "0x...",
    "timestamp": "...",
    "tier": "B"
  }
}

η = 0 Compliance​

ChargeableNot Chargeable
Verification API callsSettlement itself
Replay toolingChain state access
Dashboard and analyticsBadge claim (truth is free)
Regulatory export packageExport format itself

Zero-Sum Resolution Equation

K3 public-DAV authority history — 2026-07-12​

K3 historical reference — not active authority
note

Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.

The active schema uses a typed authorization_receipt; a public-DAV receipt must identify at least two natural-person PRISM councilors and cannot be an unsigned proposal ID.

APU · local guide, not live AI DEX Settlement Badges

Context: DEX Settlement Badges. Local guide only. Messages are not sent or saved.

Skyzai

Explore the protocol map Development & availabilityContact Skyzai

Your world. Better connected.
A Skyzai experience, with APU.

Skyzai is coming together.

The shared app at skyzai.com is in development. Explore the website while we build the connected experience.