Attack-time estimator
Combine source-labelled device models with uniform passphrase or dice assumptions, then change the candidate rate to see how the result moves.
No code. Written to be actionable.
This estimator turns the site's static attack-cost tables into an interactive sensitivity model. It keeps each published device scenario separate, because Block, Coinkite, LLFOURN and otaliptus make different assumptions about UID, timer, RTC and attacker knowledge. Selecting a model does not endorse it or establish that it applies to a particular device.
Interactive sensitivity model
Build an attack scenario
Select descriptions of how secrets were generated. Do not enter wallet-specific data. The estimator script does not transmit inputs or write them to browser storage; current selections remain in page memory.
Illustrative result
Choose a published device scenario to calculate the search time.
How to read the result
- Half-space is a sensitivity convention. The estimator uses half the enumerated space, with a minimum of one check. This assumes a uniformly positioned target and no better search ordering; it is only a large-space approximation.
- The rate is not a hardware claim. A candidate check must reach the available address, public key or xpub target. Raw device-state enumeration and BIP39 PBKDF2 plus wallet derivation may run at very different rates.
- Combined mode is conditional. Device and passphrase bits add only when both independent factors must be searched together. If other wallet data lets the attacker identify the mnemonic separately, use passphrase-only mode for that case.
- Mixed dice is output-capped. Fair, independent and secret rolls can add a separate term to a device candidate space, but a 12-word mnemonic carries at most 128 bits of entropy and a 24-word mnemonic at most 256 bits.
- Pure dice replaces the device model. The result is bounded by the smaller of roll entropy and mnemonic output size. It assumes accurate entry and no disclosure of the roll sequence.
- BIP39 output has a 512-bit ceiling. Passphrase-only and combined results cannot exceed the number of distinct BIP39 seed outputs. A particular wallet-data target can impose a lower effective collision boundary.
A long displayed time is not a recommendation to delay. Published scenarios remain unverified for an individual wallet, compute rates can change and a passphrase or mixed-dice term does not repair the original mnemonic. Use the model to understand sensitivity, then follow the migration guidance for decisions about funds.