dogecoin VS bips

imho you need to know the tx size and then calculate it: https://github.com/dogecoin/dogecoin/blob/master/doc/fee-recommendation.md

This effects us right now see https://github.com/dogecoin/dogecoin/discussions/2264 where the dogecoin devs are proposing 1.21 as a softfork upgrade. Not only do softforks in general have the risks I just mentioned, but the devs are intending to introduce segwit either in 1.21 or subsequently. Segwit can and will be gamed just like taproot has been. IMO we need to set dogecoin on a straightforward path of casting aside segwit and lightning and pursuing transaction throughput by reducing blocktime and increasing blocksize. Let the devs know how you feel about segwit and following bitcoin's (risky) development path in general, in the github link above.

Probably this depends on what you want to do. It is my understanding that the devs use regtest to check all functions after changing some of the core wallet's code (all local). This will create a new blockchain where you can do all the test from (https://github.com/dogecoin/dogecoin/tree/master/src/test). But I am also not sure about this (;

Absolutely, because what we're doing is trying to catch up on 4 years of very intensive Bitcoin development. Recent Bitcoin Core versions (such as the base we use for 1.21) are really good software and per the small discussion we had on GitHub, we would ideally wish this to become a stable base for Dogecoin to build further upon in the future. This is good because once that is done, contributors will no longer see all their work deleted with every major release.

Anyway, to give a recent and practical example: when I was re-testing Victor's wallet compatibility fix that we merged last week, I found that the regtest network in 1.21 was much more incompatible with 1.14 than I expected based on comments made in previous PRs and we cannot automatically test for regressions cross-version until it is fixed.

Unfortunately I hadn't thought this through when we worked on 1.10 back in 2015 (I too am a dumb) so now we're having it custom for dogecoin... Many wallets however are suspected to NOT implement Dogecoin's prefixes and just use Bitcoin prefixes, which should work fine.

I think the last time I saw Comic Sans used in any software as a main font was when I compiled dogecoin[1]. Can't remember any before that.

[1] https://github.com/dogecoin/dogecoin

After that - anything. I promised before that as we get closer to a release, I will re-propose a softfork plan and I intend to keep that. It will NOT be the same plan that I posted 16 months ago because reality has changed quite a lot since then, but I will try to make it a good and open plan, that - in the tradition of the plans I've been putting out since a year or so now - furthers decentralization and operator freedom.

Look-up "BIP32", "BIP39" and "BIP44", those will point you to documents describing precisely how seed phrases are converted into crypto keys.

What I'm trying to illustrate here is that a passphrase can really be thought of as a 25th word, except the 25th word isn't one from the BIP39 word list. (https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt)

And then the entropy is discarded, and the seed is generated from the words, not from the entropy. The seed is not the entropy https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

If you’ll be able to remember at least some of words, looking at wordlist, that dramatically improves the chances of guessing, making possible to recover the phrase.

> It's worth reminding any readers that what3words is a horrible coordinate system for human usage due to its unreliability. The key flaw is the choice of words that are easily confused by humans such as including both the singular and plural of the same word (e.g. likely.stage.sock and likely.stages.sock are on the opposite sides of a river) which are easily mixed up both when spoken/heard and when remembered/repeated, and also many words which sound similar e.g. 'innocence' and 'innocents', 'wants' and 'once', etc.

This is already an issue that is easily resolvable: Instead of 3 words, use 5 words from BIP 39's far less ambiguous list of 2048 words.

https://github.com/bitcoin/bips/blob/master/bip-0039/english...

If i18n is a requirement, the development of translation tables would be needed. BIP39 already has that for 8 other languages, but there's still a lot of other languages that could be added in.

https://github.com/bitcoin/bips/tree/master/bip-0039

I'm guessing that it can't be resolved due to legacy reasons, but that's just all the more reason for an open service to take over what3words' job. There's also the debate of length-vs-ambiguity, but the scenarios where the addition of 2 words will make a major difference are few & far between.

Hey - if your Ledger device is not giving you the word after entering the first three letters then it is possible you may have noted down it incorrectly. All the words belong to BIP39 list, so make sure your words are available in the list below. We hope this helps clarify. https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt