Skip to content
Optivalux

Trust

How Optivalux earns trust.

A conceptual overview for partners who want to understand what Optivalux checks, what it records and what it will not do.

The Production V2 protocol implementation is complete. Public-network validation is in development and the physical pilot is preparing; the capabilities described here are not yet live.

  1. 01

    Physical authentication

    Each product carries a secure authenticator registered by the brand. Each check produces fresh cryptographic evidence from that authenticator, which is checked against the product’s registered identity. A result states what was verified and when.

    Technical detail

    Two kinds of authenticator are supported. A symmetric NFC authenticator produces a new, single-use cryptographic message on each tap; it is checked by the Optivalux verification service, which holds the keys in secure hardware, so this kind of check relies on that service. An asymmetric secure element signs a fresh challenge with a key that never leaves the chip, and the signature is checked directly against its registered key. A QR code only locates a product’s record; it is never evidence of possession.

  2. 02

    Product certificate

    The brand issues a certificate for the specific product. Its standing is Active, Suspended or Voided. Suspension is reversible; voiding is permanent.

    Technical detail

    Standing is an independent field on the certificate record. VOID is terminal in the state model.

  3. 03

    Owner-authorized transfer

    Only the current owner can start a transfer of an owned certificate.

    Technical detail

    A normal transfer begins with the current owner’s authorization.

  4. 04

    Recipient acceptance and possession

    The recipient must accept, and the product must be verified in the recipient’s possession, before ownership moves. Nobody receives a product they did not agree to take.

    Technical detail

    Acceptance and a fresh physical-possession verification are both required to complete a normal transfer.

  5. 05

    Controlled recovery

    If an authenticator is lost or damaged, access can be restored through brand-assisted recovery or with the owner’s own Recovery Authenticator. Recovery restores access; it never changes ownership, and a suspended certificate stays suspended.

    Technical detail

    Recovery Authenticator recovery has a 14-day maturation period during which the request can be challenged.

  6. 06

    Protocol evolution

    Ownership is designed so later protocol software cannot silently reassign an already-owned certificate. Software can improve; what you own stays yours.

    Technical detail

    Upgrades are constrained so they cannot change the owner of an existing certificate without the owner’s participation.

  7. 07

    Protection Mode

    If the software or verification a certificate depends on stops working, the owner can start Protection Mode. After a minimum 14-day protection period, the certificate can move to its protected, non-operational state, and the owner can cancel while the process is pending. Ownership does not change.

    Technical detail

    An owner-initiated protection process with a minimum period of 14 days. Completion is subject to the protocol’s protection checks: while the process is pending, a fresh, trusted check of the product’s current authenticator can stop it. Ownership and certificate standing are preserved.

  8. 08

    Security restrictions

    Sensitive actions are limited to the parties entitled to take them: brands manage certificate standing; owners manage transfer, recovery and protection. Optivalux never asks users for recovery phrases.

    Technical detail

    Role separation between issuer actions (standing) and owner actions (transfer, recovery, protection).

  9. 09

    Long-term ownership continuity

    Core certificate state, ownership and recorded provenance are anchored in the underlying record rather than existing only in an Optivalux database or application. Authentication availability and certificate ownership are separate concepts: if verification is temporarily unavailable, ownership and certificate standing are unaffected.

    Technical detail

    Ownership and standing are recorded independently of the verification service that reports authentication availability. Other parts remain operated services, including checks of symmetric authenticators, product details and the applications themselves; recovery and Protection Mode exist for when a service or authenticator fails.

Language we use, and language we don’t.

Optivalux is infrastructure that provides verifiable evidence. It does not make impossible guarantees.

We say

  • verified
  • registered
  • certificate active
  • authenticity evidence
  • authenticator verified
  • matches the registered identity
  • ownership history

We don’t say

  • Avoided: guaranteed genuine
  • Avoided: 100% authentic
  • Avoided: unclonable
  • Avoided: counterfeit-proof
  • Avoided: tamper-proof
  • Avoided: guaranteed value
  • Avoided: fully trustless

Review the architecture with us.

We are happy to walk technical partners through the model in more depth.