MSDPhase 1

Demo mode — this is a demonstration build running on mock data. Nothing you load, query, or share is persisted to a live backend or written on-chain, and the closets, drawers, and grants shown are illustrative, not real records.

MSD partnership view

anchor0x6d73…0000

Sign in to your palace

MSD identifies the subject via a signing key. In Phase 1, sign-in uses a deterministic test wallet (same value as mech/dev_boot.py). Phase 2 swaps in MatchID SSO without changing this surface.

Phase-1 test wallet

Click below to sign in as the Phase-1 test subject. Your palace is local to this browser — closet-cache (localStorage) holds the metadata for every closet you absorb.

  • wallet: same deterministic privkey as mech/dev_boot.py
  • durability: browser localStorage (cleared on sign-out)
  • Phase 2: MatchID SDK swap, no UI change

Four storage gates protect every read

  • Engine allowlist

    Only allow-listed engines can ever ask.

  • Cap-ref recency

    Your grant must be fresh, not stale.

  • Query alignment

    The question must match what you granted.

  • Block timestamp

    Anchored on-chain, no time-travel.

Every read must clear all four. Phase-1 today: the engine decrypts using your per-drawer key inside a mock secure enclave. Phase-2 ratchet — when shipped — removes that mock entirely. We don’t pretend Phase-2 ships today.

What MSD is, and what it never becomes

  • No backdoor — not even “lawful access”.
  • Your identity is yours, never state-revocable.
  • We strengthen local currency, never substitute it.
  • Russia and the ruble are excluded, permanently.

Compliance by architecture, never by backdoor.