bips VS dogecoin

Bitcoin transactions involve locking funds in scripts, which can only be spent if those locking conditions are met. The part of the script that expresses these locking conditions are called ScriptPubKeys. On the other hand, the part that provides unlocking scripts to satisfy the locking conditions is referred to as ScriptSig for legacy transactions, and ScriptWitness for SegWit Transactions. These scripts are evaluated by a stack-based language called Script. This article will mainly focus on ScriptPubKeys.

Here’s the reference https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

There are 5 271 537 971 301 488 476 000 309 317 528 177 868 800 possible permutations of the bip39 wordlist found here: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt when using 12 word seeds. You probably have better change to win the lottery every week for the rest of your life than cracking a 12 word seed in correct order

No one controls Bitcoin, because it's a protocol. Bitcoin Core is the reference implementation, but there are others, and anyone can create new implementations if they wish. Also, the Bitcoin Core maintainers can't just change something on a whim, because users would then switch to another fork. Maintainers (or miners or other groups) can't force their changes on users, because everyone can decide on their own which version they want to use.

The protocol development happens through BIPs (Bitcoin improvement proposals): https://github.com/bitcoin/bips

BIPs are discussed for years, before (and if) they are implemented, and basically everyone needs to agree on them, because no one wants to fork the blockchain, which could be devastating.

All the seeds generated from the CoolWallet (Number / Word) adhere to the BIP-39 protocol.

> users would be required to hand over control of their wallet to actually manage the massive proliferation of addresses needed

BIP32 solved this in 2012, and is used by basically all self-custodial wallets these days. https://github.com/bitcoin/bips/blob/master/bip-0032.mediawi...

> Which policy are we referring to?

* BIP 141 version bits and BIP 148 as a voting mechanism: https://github.com/bitcoin/bips/blob/master/bip-0141.mediawi... and https://github.com/bitcoin/bips/blob/master/bip-0148.mediawi...

* core developer votes: https://en.bitcoin.it/wiki/Segwit_support

* posturing and maneuvering: https://cointelegraph.com/news/samourai-wallet-intends-to-ru...

> It evolves in a decentralized and organic manner, devoid of any formal political process or voting.

Just because its voting mechanisms are informal, that doesn't make them not voting mechanisms.

Have you checked the 1.14.7-dev branch on GitHub? https://github.com/dogecoin/dogecoin

🧾 Whitepaper

It already has the "fix" inherited from the Bitcoin code they reuse. Though you shouldn't count on that feature to not have bugs: the Dogecoin codebase is old and poorly maintained. If you run it on a cloud service, always turn on billing limits. https://github.com/dogecoin/dogecoin/blob/master/doc/reduce-...

Here's the release tracker for 1.14.7. We've been a little bit backed up with some work to migrate the testing system to a supported version of Ubuntu in GitHub, as well as a need for more people to do good code reviews.

read this dogecoin issue for more info (it also works with doge) https://github.com/dogecoin/dogecoin/issues/3243