About

A focused lab for authorized work.

NUR Recovery Lab exists so operators can investigate public chain data and recover from owner-held backups without inventing balances, bypassing MFA, or turning the product into a cracking service.

Mission

Give authorized operators a single, auditable workspace where live research and recovery tooling share the same case model, the same security gates, and the same expectation of provenance.

Every result should answer three questions: what network, what data mode, and what authority allowed this action.

What it is

  • A case-based recovery workspace with encrypted artifact intake.
  • A six-network research surface with explicit LIVE / RECORDED / SIMULATED modes.
  • A gated toolkit for key export, funded-address discovery, sweeps, and fee-bumps.
  • An MFA-protected application with role-scoped access and append-only audit history.

What it is not

  • Not a public registration product or consumer wallet app.
  • Not a service that breaks secp256k1, guesses unknown seeds, or attacks third-party wallets without authorization.
  • Not a place where simulated or recorded fixtures are labelled as live balances.
  • Not a substitute for legal ownership documentation — operators remain responsible for authorization evidence.

Who it is for

Owners set workspace policy, provider configuration, and operational limits. Administrators manage users and case sharing. Operators run intake, verification, research, and recovery on cases they own or are granted. Auditors review history and reports without mutating recovery state.

Design principles

  1. Fail closed. Gates, capacity, and authorization must be satisfied before privileged work runs.
  2. Show provenance. Research responses name their provider, mode, and coverage limits.
  3. Keep secrets scarce. Passwords and private keys are used ephemerally; exports are one-time reveals where possible.
  4. Stay scoped. Cases, permissions, and reports never imply system-wide access or hidden data.