Methodology
Every number needs a model. Every procedure needs a boundary.
Plentropy separates exact specification facts, simplified teaching models, implementation-specific procedures, and operational judgment.
Never enter a real seed
Plentropy never needs your secret. Do not paste, type, photograph, upload, validate, repair, or generate a recovery phrase or passphrase here—or on any educational website.
The site has no accounts, wallet connections, uploads, clipboard tools, camera or microphone access, analytics, or backend secret processing. Demonstrations use numbered tiles, invalid labels, and prepared fictional scenarios.
What “plenty” means
- Name the failure or attacker.
- State what they know, control, and can test.
- Use a conservative lower bound for source uncertainty.
- Cross the modeled guessing risk with room to spare.
- Stop adding entropy when custody, recovery, or another cryptographic limit becomes the bottleneck.
There is no universal magic number independent of source quality, leakage, wallet construction, and recovery design.
Evidence labels
| Class | Used for | Review rule |
|---|---|---|
| Specification | Exact BIP, SLIP, RFC, and NIST mechanics | Review when revised or status changes |
| Implementation guidance | One wallet’s documented generation or recovery path | Review quarterly and show the applicable version/date |
| Incident | A historically documented failure mode | Preserve the dated scope; do not generalize beyond evidence |
| Teaching model | Transparent hypothetical attacker rates and simplified diagrams | Show every assumption beside the output |
Core evidence
- BIP39 for mnemonic, checksum, and passphrase mechanics.
- BIP32 for hierarchical seed-to-key derivation.
- NIST SP 800-90B for entropy-source modeling and conservative estimation.
- RFC 4086 for security-randomness requirements and failure patterns.
- NIST SP 800-57 Part 1 Rev. 5 for comparable classical security strengths.
Privacy and local progress
Only explanation depth and guide progress may be saved in local browser storage. Opening answers and all demonstration state remain in memory. The settings page lets visitors inspect or erase the saved profile.