In regards to the output of dumpwallet, that is the most effective reply:
dumpwallet output documentation & clarification?
About your questions:
Why does a non-public key tackle correspond to 2 fee addresses?
Addresses are directions out of your pockets to the paying pockets.
These directions are divided in 2 components: a prefix and a few string.
If the prefix is:
- “1” this implies your pockets needs the receiving cash to be locked in a P2PKH script (Pay To Public Key Hash), and the hash of your public key is the string a part of the tackle;
- “3” this implies your pockets needs the receiving cash to be locked in a P2SH script (Pay To Script Hash), and the hash of the script is the string a part of the tackle;
- “bc1q” this implies your pockets needs the receiving cash to be locked in a Segwit script, and the hash of the script is the string a part of the tackle;
- “bc1p” this implies your pockets needs the receiving cash to be locked in a Taproot script, and the hash of the script is the string a part of the tackle.
So, the identical actual non-public key can originate 4 totally different addresses.
Within the 1.txt file, the receiving tackle starting with 3 is adopted by 00…… This code shouldn’t be a non-public key. What’s it?
It is the P2SH tackle for that personal key.