KY / BOUNDARY RIG
Wallet protocol
User-controlled software requires a key, signing and recovery boundary test.
- P0OPEN
Scope
Application, platform, version and date
ARTEFACTS / Official application, platform, release and date records
PASS WHEN / The exact wallet build and research period are fixed. - P1OPEN
Boundary
Key, device and service control
ARTEFACTS / Technical documentation and safe key-creation observations
PASS WHEN / Key access and provider boundaries are supported for the stated version. - P2OPEN
Action
Signing, route and telemetry parameters
ARTEFACTS / Versioned signing, permission and warning tests on disposable accounts
PASS WHEN / Observed approval information and blind spots are documented. - P3OPEN
Failure
Recovery and distribution cases
ARTEFACTS / Recovery documentation and safe failure-path tests with no real assets
PASS WHEN / Recovery dependencies and irreversible loss states are explicit. - P4OPEN
Limit
Document versus runtime evidence
ARTEFACTS / Release provenance, audit scope, privacy limits, conflicts and QA sign-off
PASS WHEN / Critical unknowns are resolved or stop publication.