Models & verifiers
AI-assisted document checks, verifier work and credential processing occur outside the consensus-critical execution environment. Outputs can be signed and linked to registered model hashes.
The whitepaper’s verification market combines AI-assisted checks with verifier selection, cryptographic commitments, quorum decisions and bonded disputes.
Issuer DID, schema and salted credential commitment are recorded; the document itself stays off-chain.
A signed attestation identifies the registered model hash, committed input and structured result.
Verifiers are selected, submit hidden commitments, reveal outcomes and aggregate results.
A challenge window follows finalization, providing an accountability path for contested decisions.
The chain is designed to verify signed evidence and apply deterministic state transitions. AI models do not become consensus validators, and model inference is not presented as an on-chain VM.
AI-assisted document checks, verifier work and credential processing occur outside the consensus-critical execution environment. Outputs can be signed and linked to registered model hashes.
Requests, allotment, commitments, reveals, aggregation and challenges are protocol transactions processed through deterministic native modules.
Not specified for launch. The research explicitly defers a general-purpose virtual machine and smart contracts. Xenorra’s first proposed release uses a constrained native-module execution environment to reduce consensus and security complexity.
Accounts and transfers; staking; governance; cryptographic suite registry; decentralized identifier registry; credential registry; and the verification market. State transitions are deterministic and consensus-verifiable.
The whitepaper evaluates WebAssembly with metering and floating-point disabled, a RISC-V interpreter, or a resource-oriented language such as Move. No virtual-machine choice, launch date or smart-contract API is finalized.
The design prioritizes an auditable consensus core. General-purpose contracts can expand application capabilities, but also introduce new execution costs, exploit surfaces and resource-metering requirements.
Credential registration, revocation, staking, governance and verification-market calls have specified state-transition rules. They are native protocol functions—not arbitrary user-deployed smart contracts.
Any future VM would need a deterministic execution specification, bounded resource accounting, mature Rust support and isolation so contract faults cannot compromise consensus-critical modules.