Private pre-testnet

Current validation boundary
← Home

Native assets

ZNA: provenance, attestations and selective disclosure as protocol state.

Native assets

ZNA Native Assets

Zeqron keeps provenance as protocol-native asset state: lineage, attestations and selective disclosure. The integrity of that provenance depends on authenticated attestations at the source and on lineage rules the protocol enforces.

Sequence

Provenance sequence

  1. 01IssueRegister the asset as native state
  2. 02AttestAuthenticated source attestation
  3. 03TransferCustody change under protocol rules
  4. 04Selectively discloseProve an attribute without the full record
  5. 05Verify lineageCheck consensus-anchored history

Off-network: physical custody, ERP records, and human processes remain outside the ledger.

What the protocol covers: lineage rules the libraries check, and verification of the authenticated attestations that were submitted. It cannot make the physical world unforgeable.

Why protocol-native assets

In many smart-contract systems, asset-specific rules are implemented and maintained at the application layer. ZNA targets assets as first-class protocol state with shared invariants — efficiency claims are design aims under library validation.
Contract

Asset in a smart contract

Where the rules liveApplication layer
  • Application-layer executionLogic runs in a VM / contract runtime above the base protocol
  • Per-app security surfaceCorrectness depends on each contract's implementation quality
  • Fragmented stateProvenance patterns reimplemented per deployment
Protocol

Asset in the protocol

Where the rules liveProtocol state
  • Assets as protocol stateTyped asset rules and invariants at the protocol layer (libraries)
  • Protocol invariantsAsset rules checked by nodes at execution; enforcement by consensus is a design target
  • Genealogy indexProvenance and disclosure rules designed to travel with the asset

Internal build · RFC-ASSET-002 · under validation