All wallet software that I know of has migrated from JBOK to some form of deterministically derived keys. The first wallet with deterministic key derivation that I know was Armory around 2011-2012, and its scheme inspired BIP32, which formed the basis of many key generation standards that followed. Obviously, software that predates these schemes did use JBOK ...
Before opening the thread, I had already tried to import a wallet on Bitcoin Core using the Master Private Key previously extrapolated with dumpwallet. In summary I had done:
Then trying to import the newly created wallet again:
Make Blank Wallet > Yes
The steps you described is for a single private key, not a BIP32 wallet. If you are looking to back-up your HD seed (master key) in bitcoin-core you should use the dumpwallet command.
It doesn't. You read it wrong, first snippet shows you account key for m/44'/0'/0'/0 derivation path, second snippet for m/44. As the derivation paths are different - obviously the accounts' keys are different too.
bip39-lib.js works along with bip32-lib.js AND bitcoinjs-lib.
BIP39 is strictly regarding the mnemonic phrase and HD seed.
In order to derive child keys from an HD seed you'll also need to use BIP32.
BUT... BIP32 has no concept of addresses either so ultimately you'll also need bitcoinjs-lib.
In other words you need to use all three libraries to go from ...
What was the motivation to move 8 bits to the end and use 2^11 possible words instead of move no bits and use 2^8 words with a 32 word mnemonic resulting in a bijective correspondance between the set of permutations of words and the set of possible 256 bit sequences.
Typical word lists are 2048 entries, and that seems to be well established as usable. Using ...