Pre-production MVPEVM-first · Chain-agnostic · Production network not selectedProduct status

Platform / NovaID

NovaID: Participant state.

A participant-state primitive for representing identity and eligibility outcomes without placing identity documents on-chain.

MVP MOCK

The MVP models participant and verification states using synthetic data so downstream workflow behavior can be evaluated.

Public architecture material

Purpose

Give a transaction workflow a clear, reviewable way to reference who a participant is and whether an external verification requirement has been represented as satisfied.

THE PROBLEM

Real-world asset workflows depend on identity and eligibility checks that occur across different providers, jurisdictions, and systems. The protocol needs a durable state reference without becoming the identity provider itself.

Protocol shape

NovaID in the coordination layer.

A conceptual state path with explicit inputs, outputs, inter-primitive relationships and authority boundaries.

MVP MOCK
NovaID / Participant state

Who is represented?

INPUTSynthetic participant + mock result
  1. 01Referenced
  2. 02Mock checked
  3. 03State recorded
MODELED OUTPUTEligibility-state reference

Trust boundary Not real identity verification

Participant state informs registry and document workflows.

CURRENT MVP

The MVP models participant and verification states using synthetic data so downstream workflow behavior can be evaluated.

FUTURE / CONDITIONAL

A future implementation may integrate qualified identity and compliance providers, subject to jurisdiction, privacy design, contractual controls, security review, and explicit approval.

REFERENCE DATA MODEL

What the state references.

Fields below are illustrative MVP concepts, not an available API or legal determination.

INPUTS
  • Synthetic participant data
  • Mock verification result
  • Policy context
DATA MODEL
  • Participant reference
  • Organization or individual type
  • Verification-state code
  • Attestation reference
  • Issuer/provider reference
  • Validity window and event history
OUTPUTS
  • Identity-state record
  • Eligibility event
  • Workflow decision input
Trust boundary

What the state can—and cannot—mean.

The MVP trusts a mock result supplied by the demonstration. It does not independently identify a person, validate documents, screen sanctions, or determine legal eligibility.

Explicit limitations

Not provided by the MVP.

  • No real KYC or KYB
  • No biometric or identity-document processing
  • No regulated identity decision
  • No production credential issuance
  • No real personal information should be submitted

Composition

NovaID is one primitive, not a closed product suite.

Developer concept

Evaluate the model, not a marketing claim.

Review the shared concepts, architecture, schemas, and current product-status matrix.