I agree with the point the author is making and generally am just as annoyed by arbitrary password rules; nevertheless:
> chili dog monkey nutso
Is definitely not 18 quintillion years at best it's approximately 250000^4 which is 2^72.
A good (though still requiring some memorizing effort approach) would be something along the lines of https://github.com/bitcoin/bips/blob/master/bip-0039.mediawi...
which uses a standard dictionary of 1626 easily memorable english words with each password being a 12 word mnemonic phrase. 1626^12 ~= 12^128
In Stop forcing arbitrary password rulesbitcoin
bips
Wikitext2013–2026
bitcoin / bips
bips
Bitcoin Improvement Proposals
104Distinct people
124Mentions
0Explicit recommenders
11KGitHub stars
What to know before exploring
What it is
Bitcoin Improvement Proposals
GitHub
Where it is used
- Ledger Wallet (Ledger Live) — Ledger Wallet uses the BIP32, BIP39 and BIP44 standards to manage seeds and derivation paths for generating keys and addresses. Source
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- bcoin-org/bcoin · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:53 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year124 dated mentions
Observed mentions: 2013-12-10 19:15:46 UTC to 2026-09-13 15:23:25 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 12 | 1 | 11 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 15 | 0 | 15 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 17 | 0 | 17 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 13 | 0 | 13 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 4 | 1 | 3 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
People wishing to submit a BIP should first describe their idea to the bitcoindev@googlegroups.com
mailing list to gather feedback on viability and community interest before working on a
formal description. Please open a pull request to this repository only when substantial progress on the draft has been
made, preferably when the draft is nearing completion. Authors do not assign a number to their own proposal.
After a proposal meets the editorial criteria, a BIP Editor will assign a number to it and publish the proposal by
merging the pull request to the repository. Please see BIP 3: Updated BIP Process for the full process.
The BIPs repository serves as a publication medium and archive. Having a BIP published here indicates that the proposal
is in scope and has met other formal criteria for this repository, but does not indicate that it is a good idea, has
community consensus, or that it is about to be adopted. The BIP Editors are expected to be liberal with publishing BIPs
and to try not to be too involved in decision-making on behalf of the community. Beyond the formal criteria, evaluation of
the proposals is left to the audience of the repository. When a proposal is controversial and it cannot be agreed upon
whether it should be published, the conservative option will always be preferred: the proposal will be closed.
Those proposing and opposing changes should consider that ultimately acceptance and adoption rests with the Bitcoin
users (see also: economic majority).
Number
Layer
Title
Owner
Type
Status
1
BIP Purpose and Guidelines
Amir Taaki
Process
Closed
2
BIP process, revised
Luke Dashjr
Process
Closed
3
Updated BIP Process
Murch
Process
Deployed
8
Version bits with lock-in by height
Shaolin Fry, Luke Dashjr
Informational
Complete
9
Version bits with timeout and delay
Pieter Wuille, Peter Todd, Greg Maxwell, Rusty Russell
Informational
Deployed
10
Applications
Multi-Sig Transaction Distribution
Alan Reiner
Informational
Closed
11
Applications
M-of-N Standard Transactions
Gavin Andresen
Specification
Deployed
12
Consensus (soft fork)
OP_EVAL
Gavin Andresen
Specification
Closed
13
Applications
Address Format for pay-to-script-hash
Gavin Andresen
Specification
Deployed
14
Peer Services
Protocol Version and User Agent
Amir Taaki, Patrick Strateman
Specification
Deployed
15
Applications
Aliases
Amir Taaki
Specification
Closed
16
Consensus (soft fork)
Pay to Script Hash
Gavin Andresen
Specification
Deployed
17
Consensus (soft fork)
OP_CHECKHASHVERIFY (CHV)
Luke Dashjr
Specification
Closed
18
Consensus (soft fork)
hashScriptCheck
Luke Dashjr
Specification
Complete
19
Applications
M-of-N Standard Transactions (Low SigOp)
Luke Dashjr
Specification
Closed
20
Applications
URI Scheme
Luke Dashjr
Specification
Closed
21
Applications
URI Scheme
Nils Schneider, Matt Corallo
Specification
Closed
22
API/RPC
getblocktemplate - Fundamentals
Luke Dashjr
Specification
Deployed
23
API/RPC
getblocktemplate - Pooled Mining
Luke Dashjr
Specification
Deployed
30
Consensus (soft fork)
Duplicate transactions
Pieter Wuille
Specification
Deployed
31
Peer Services
Pong message
Mike Hearn
Specification
Deployed
32
Applications
Hierarchical Deterministic Wallets
Pieter Wuille
Informational
Deployed
33
Peer Services
Stratized Nodes
Amir Taaki
Specification
Closed
34
Consensus (soft fork)
Block v2, Height in Coinbase
Gavin Andresen
Specification
Deployed
35
Peer Services
mempool message
Jeff Garzik
Specification
Deployed
36
Peer Services
Custom Services
Stefan Thomas
Specification
Closed
37
Peer Services
Connection Bloom filtering
Mike Hearn, Matt Corallo
Specification
Deployed
38
Applications
Passphrase-protected private key
Mike Caldwell, Aaron Voisine
Specification
Deployed
39
Applications
Mnemonic code for generating deterministic keys
Marek Palatinus, Pavol Rusnak, Aaron Voisine, Sean Bowe
Specification
Deployed
40
API/RPC
Stratum wire protocol
Marek Palatinus
Standard
BIP number allocated
41
API/RPC
Stratum mining protocol
Marek Palatinus
Standard
BIP number allocated
42
Consensus (soft fork)
A finite monetary supply for Bitcoin
Pieter Wuille
Specification
Deployed
43
Applications
Purpose Field for Deterministic Wallets
Marek Palatinus, Pavol Rusnak
Specification
Deployed
44
Applications
Multi-Account Hierarchy for Deterministic Wallets
Marek Palatinus, Pavol Rusnak
Specification
Deployed
45
Applications
Structure for Deterministic P2SH Multisignature Wallets
Manuel Araoz, Ryan X. Charles, Matias Alejo Garcia
Specification
Complete
46
Applications
Address Scheme for Timelocked Fidelity Bonds
Chris Belcher, Thebora Kompanioni
Specification
Draft
47
Applications
Reusable Payment Codes for Hierarchical Deterministic Wallets
Justus Ranvier
Specification
Deployed
48
Applications
Multi-Script Hierarchy for Multi-Sig Wallets
Fontaine
Specification
Deployed
49
Applications
Derivation scheme for P2WPKH-nested-in-P2SH based accounts
Daniel Weigl
Specification
Deployed
50
March 2013 Chain Fork Post-Mortem
Gavin Andresen
Informational
Deployed
52
Consensus (hard fork)
Durable, Low Energy Bitcoin PoW
Michael Dubrovsky, Bogdan Penkovsky
Specification
Closed
53
Consensus (soft fork)
Disallow 64-byte transactions
Chris Stewart
Specification
Draft
54
Consensus (soft fork)
Consensus Cleanup
Antoine Poinsot, Matt Corallo
Specification
Complete
60
Peer Services
Fixed Length "version" Message (Relay-Transactions Field)
Amir Taaki
Specification
Closed
61
Peer Services
Reject P2P message
Gavin Andresen
Specification
Deployed
62
Consensus (soft fork)
Dealing with malleability
Pieter Wuille
Specification
Closed
63
Applications
Stealth Addresses
Peter Todd
Standard
BIP number allocated
64
Peer Services
getutxo message
Mike Hearn
Specifi
Read the full README on GitHubWhat Hacker News says
8 sourcesThis incident had nothing to do with zero-conf txs. In fact okpay did wait for multiple confirmations, and was still hit by this $10k double spend!
This whole thing was possible because of an accidental fork of the chain which lasted a few hours. This is the only accidental fork that occurred in the last 3 years.
Details: https://github.com/bitcoin/bips/blob/master/bip-0050.mediawi...
In OneBit – Mastercard PayPass Integrated Bitcoin Wallet> Someone submitted a Bitcoin transaction which did, in fact, exhaust the number of locks available to the Berkeley DB.
You really need to get up to speed with the event before commenting on it, there's a very good writeup in the form of BIP50.
https://github.com/bitcoin/bips/blob/master/bip-0050.mediawi...
The issue has nothing to do with a particular transaction or block, it was going to fail anyway and just happened to be triggered by a large block. The oversight meant that all 0.7 clients were inconsistent with one another depending on the history of the node and how long it had been operating.
> No sane person says "An important feature of the Bitcoin Protocol is that conforming clients MUST REJECT any Bitcoin transaction which would exhaust the default number of locks available to the Berkeley DB."
Nobody did say that, the failure w
Read the rest
as implicit not explicit.
> Several hours of transactional history got wiped out.
No it didn't, it was replaced with a slightly different history, or history remained the same, depending on which side and which client you happened to be running at the time.
https://github.com/bitcoin/bips/blob/master/bip-0032.mediawi...
I think the main advantage to a blockchain solution is the cryptographic verifiability. Not only is the accounting accurate, but the funds cannot be forged or hidden. Also the rules for managing funds can be programmatically encoded using a series of technologies such as multi-sig keys, pay-to-script-hashes, and HD Keys.
In What's the use for Bitcoin?The "Open Wallet" link has a bitcoin URI. If you have a wallet installed, it'll pop open that wallet. More here: https://github.com/bitcoin/bips/blob/master/bip-0021.mediawi...
Stripe doesn't have a Bitcoin wallet for consumers.
In Stripe: BitcoinDisappointed to see that they don't appear any PaymentProtocol[1] integration.
[1] https://github.com/bitcoin/bips/blob/master/bip-0070.mediawi...
In Stripe: BitcoinThere are two similar methods for generating addresses for a recipient.
Hierarchical deterministic wallets (HD wallets, BIP 32): https://github.com/bitcoin/bips/blob/master/bip-0032.mediawi...
Stealth addresses: http://sx.dyne.org/stealth.html
The former is more broadly supported.
In Bitstamp Accounts Frozen> You should STOP SENDING bitcoin deposits to your Bitstamp account IMMEDIATELY as private keys of your deposit address may be lost.
I read this as wallet file(s) having been corrupted. The way to avoid this is to use deterministic[1] wallets
However...
> We have reason to believe that one of Bitstamp’s operational wallets was compromised on January 4th, 2015.
makes it sound like one would be wise to short sell btc immediately.
[1] https://github.com/bitcoin/bips/blob/master/bip-0032.mediawi...
In Bitstamp Accounts Frozen