Skip to content
VYREN

Lifecycle

Progression by state, not marketing date.

Vyren treats architecture, implementation, production deployment, Genesis and activation as separate states. Each later state requires its own prerequisites and evidence.

  1. 01

    Architecture

    Rev4.6 canonical rules and boundaries are frozen.

    CURRENT
  2. 02

    Implementation

    Canonical implementation has reproducible build evidence.

    CURRENT
  3. 03

    Production Deployment

    Mainnet addresses and runtime equality are not yet bound. Deployment becomes hard where live evidence actually consumes it.

    PENDING
  4. 04

    Genesis

    Participation remains closed until the applicable G-GENESIS legal, safeguarding, settlement, security and public-surface conditions pass.

    BLOCKED
  5. 05

    Activation

    Activation follows QAD, clean-state, R2, G-ACTIVE, ASCF and F3 conditions rather than a marketing date.

    NOT ASSERTED

Genesis

Not a countdown event.

Participation opens only after the applicable G-GENESIS legal, safeguarding, settlement, public-surface and minimum security conditions are current. Production deployment is not treated as a universal legal pre-Genesis requirement.

Activation

Threshold-bound.

Rev4.6 activation uses protocol-defined thresholds including QAD, clean / ABF handling, R2-ACTIVATION, G-ACTIVE, ASCF and F3 rather than a promotional date. MARKET OPEN remains a separate path under P04 + G-MARKET.