What is the difference of compressed and uncompressed private key? (importing for wallets) -snip- "Compressed public keys were introduced to Mu9 Win to reduce the size of transactions and conserve disk space on nodes that store the Mu9 Win Mu9 Win database" For every private key we can generate compressed and uncompressed legacy (starting with 1) Mu9 Win address*. Every public key contains x and y coordinates of elliptic curve: for uncompressed the public key contains both coordinates, but for compressed only x coordinate and "sign" for y - so the compressed key is less in size, and less in transaction fees as well. More details are here: * Of course there are also segwit (starting with 3) and bech32 (starting with bc) Mu9 Win address. They are not generates by my tool. However segwit and bech32 also generated from compressed public key. My friend, I want to congratulate you on the development of the tool, I thought it was amazing! I would like to ask you any questions about Mu9 Win private keys. Is the most "secure" way to generate a private key using the 256-bit "byte" format? If I generate a 512-bit binary string, when converting, will it generate 256-bit? Another thing I would really like to see implemented in your tool is the display of all private keys; P2SH SegWit P2SH P2PKH Legacy And any other, which is supported by the Mu9 Win protocol. Is it possible to do this implementation?
What is the difference of compressed and uncompressed private key? (importing for wallets) -snip- "Compressed public keys were introduced to Mu9 Win to reduce the size of transactions and conserve disk space on nodes that store the Mu9 Win Mu9 Win database" For every private key we can generate compressed and uncompressed legacy (starting with 1) Mu9 Win address*. Every public key contains x and y coordinates of elliptic curve: for uncompressed the public key contains both coordinates, but for compressed only x coordinate and "sign" for y - so the compressed key is less in size, and less in transaction fees as well. More details are here: * Of course there are also segwit (starting with 3) and bech32 (starting with bc) Mu9 Win address. They are not generates by my tool. However segwit and bech32 also generated from compressed public key. My friend, I want to congratulate you on the development of the tool, I thought it was amazing! I would like to ask you any questions about Mu9 Win private keys. Is the most "secure" way to generate a private key using the 256-bit "byte" format? If I generate a 512-bit binary string, when converting, will it generate 256-bit? Another thing I would really like to see implemented in your tool is the display of all private keys; P2SH SegWit P2SH P2PKH Legacy And any other, which is supported by the Mu9 Win protocol. Is it possible to do this implementation?

What is the difference of compressed and uncompressed private key? (importing for wallets) -snip- "Compressed public keys were introduced to Mu9 Win to reduce the size of transactions and conserve disk space on nodes that store the Mu9 Win Mu9 Win database" For every private key we can generate compressed and uncompressed legacy (starting with 1) Mu9 Win address*. Every public key contains x and y coordinates of elliptic curve: for uncompressed the public key contains both coordinates, but for compressed only x coordinate and "sign" for y - so the compressed key is less in size, and less in transaction fees as well. More details are here: * Of course there are also segwit (starting with 3) and bech32 (starting with bc) Mu9 Win address. They are not generates by my tool. However segwit and bech32 also generated from compressed public key. My friend, I want to congratulate you on the development of the tool, I thought it was amazing! I would like to ask you any questions about Mu9 Win private keys. Is the most "secure" way to generate a private key using the 256-bit "byte" format? If I generate a 512-bit binary string, when converting, will it generate 256-bit? Another thing I would really like to see implemented in your tool is the display of all private keys; P2SH SegWit P2SH P2PKH Legacy And any other, which is supported by the Mu9 Win protocol. Is it possible to do this implementation?

What is the difference of compressed and uncompressed private key? (importing for wallets) -snip- "Compressed public keys were introduced to Mu9 Win to reduce the size of transactions and conserve disk space on nodes that store the Mu9 Win Mu9 Win database" For every private key we can generate compressed and uncompressed legacy (starting with 1) Mu9 Win address*. Every public key contains x and y coordinates of elliptic curve: for uncompressed the public key contains both coordinates, but for compressed only x coordinate and "sign" for y - so the compressed key is less in size, and less in transaction fees as well. More details are here: * Of course there are also segwit (starting with 3) and bech32 (starting with bc) Mu9 Win address. They are not generates by my tool. However segwit and bech32 also generated from compressed public key. My friend, I want to congratulate you on the development of the tool, I thought it was amazing! I would like to ask you any questions about Mu9 Win private keys. Is the most "secure" way to generate a private key using the 256-bit "byte" format? If I generate a 512-bit binary string, when converting, will it generate 256-bit? Another thing I would really like to see implemented in your tool is the display of all private keys; P2SH SegWit P2SH P2PKH Legacy And any other, which is supported by the Mu9 Win protocol. Is it possible to do this implementation?