Start simple. Drill down when you need to.
Distribrute lets independent machines test password candidates without giving those machines the wallet. These docs explain the full path, the wallet-specific safety mechanisms, and the limits of the current system.
- 01
Extract
Create a small, non-spendable safe test piece.
- 02
Search
Operators test assigned password ranges.
- 03
Verify
A reported match is checked against wallet ground truth.
- 04
Recover
The owner completes wallet-side recovery and settlement.
Start with the system architecture and what is available today.
System architecture
The components that move a recovery case from secure intake to distributed search, verification, and wallet-side recovery.
Implementation status
A precise view of which capabilities are implemented in code and which remain planned, independent of deployment or general availability.
Follow a case from intake through verification and recovery.
End-to-end recovery
What happens from the first recovery request through distributed password testing, verification, and settlement.
Custodial vs non-custodial
How wallet custody changes intake, verification, the guided recovery session, and the trust placed in Distribrute.
What we cannot recover
Cases that are outside password recovery because key material is missing, the target is not an encrypted wallet, or the wallet format is not supported.
Examine the software that authorizes, distributes, and executes recovery work.
See exactly what is extracted and tested for each supported wallet.
Safe test pieces
The narrow wallet-derived artifacts operators use to test passwords without receiving a spendable wallet.
Blockchain.com wallet engine
How the one-block Blockchain.com/info safe test piece is constructed, tested, and verified.
Bitcoin Core wallet engine
How Distribrute derives a non-spendable wallet-encryption-key test from an encrypted Bitcoin Core wallet and verifies it against a real key.
Understand the trust boundaries, guarantees, and honest limits.