Topic: What exactly is the relationship between private and public keys on the blockcha (Read 94 times)

Do you mean generating random 256-bit or 512-bit of data using certain number as basis of the RNG?


In general, public key is just 256-bit of data (512-bit if you use uncompressed public key).

Maybe I don't understand, but your example shows you getting 5 public keys (both compressed and uncompressed versions) from 5 different private keys.

Hey, is it something amazing when I can linearly get as many uncompressed public keys as I want with only 1 uncompressed public key as a generator?

PRIVATE KEY
0000000000000000000000000000000000000000000000000000000000000005
------------------------------------------------------
PUB Uncompressed
042f8bde4d1a07209355b4a7250a5c5128e88b84bddc619ab7cba8d569b240efe4d8ac222636e5e 3d6d4dba9dda6c9c426f788271bab0d6840dca87d3aa6ac62d6
------------------------------------------------------
RIPEMD-160 hash40
8eab8f2151da240474bf7cdd2d9065f7dcd3602e
------------------------------------------------------
Bitcoin Address Uncompressed
1E1NUNmYw1G5c3FKNPd435QmDvuNG3auYk
------------------------------------------------------
PUB Compressed
022f8bde4d1a07209355b4a7250a5c5128e88b84bddc619ab7cba8d569b240efe4
------------------------------------------------------
RIPEMD-160 hash
4747e8746cddb33b0f7f95a90f89f89fb387cbb6
------------------------------------------------------
Bitcoin Address Compressed
17Vu7st1U1KwymUKU4jJheHHGRVNqrcfLD
------------------------------------------------------


PRIVATE KEY
0000000000000000000000000000000000000000000000000000000000000006
------------------------------------------------------
PUB Uncompressed
04fff97bd5755eeea420453a14355235d382f6472f8568a18b2f057a1460297556ae12777aacfbb 620f3be96017f45c560de80f0f6518fe4a03c870c36b075f297
------------------------------------------------------
RIPEMD-160 hash40
0524e15415f8e038071bf6d0f0d5aa2b44bf6ced
------------------------------------------------------
Bitcoin Address Uncompressed
1UCZSVufT1PNimutbPdJUiEyCYSiZAD6n
------------------------------------------------------
PUB Compressed
03fff97bd5755eeea420453a14355235d382f6472f8568a18b2f057a1460297556
------------------------------------------------------
RIPEMD-160 hash
7fda9cf020c16cacf529c87d8de89bfc70b8c9cb
------------------------------------------------------
Bitcoin Address Compressed
1Cf2hs39Woi61YNkYGUAcohL2K2q4pawBq
------------------------------------------------------


PRIVATE KEY
0000000000000000000000000000000000000000000000000000000000000007
------------------------------------------------------
PUB Uncompressed
045cbdf0646e5db4eaa398f365f2ea7a0e3d419b7e0330e39ce92bddedcac4f9bc6aebca40ba255 960a3178d6d861a54dba813d0b813fde7b5a5082628087264da
------------------------------------------------------
RIPEMD-160 hash40
73ab19930b7c023b0c7e17da43649ca58a419999
------------------------------------------------------
Bitcoin Address Uncompressed
1BYbgHpSKQCtMrQfwN6b6n5S718EJkEJ41
------------------------------------------------------
PUB Compressed
025cbdf0646e5db4eaa398f365f2ea7a0e3d419b7e0330e39ce92bddedcac4f9bc
------------------------------------------------------
RIPEMD-160 hash
5dedfbf9ea599dd4e3ca6a80b333c472fd0b3f69
------------------------------------------------------
Bitcoin Address Compressed
19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
------------------------------------------------------


PRIVATE KEY
0000000000000000000000000000000000000000000000000000000000000008
------------------------------------------------------
PUB Uncompressed
042f01e5e15cca351daff3843fb70f3c2f0a1bdd05e5af888a67784ef3e10a2a015c4da8a741539 949293d082a132d13b4c2e213d6ba5b7617b5da2cb76cbde904
------------------------------------------------------
RIPEMD-160 hash40
be5fdeb54c869d582cf796c34e28b4d21813ffa6
------------------------------------------------------
Bitcoin Address Uncompressed
1JMcEcKXQ7xA7JLAMPsBmHz68bzugYtdrv
------------------------------------------------------
PUB Compressed
022f01e5e15cca351daff3843fb70f3c2f0a1bdd05e5af888a67784ef3e10a2a01
------------------------------------------------------
RIPEMD-160 hash
9652d86bedf43ad264362e6e6eba6eb764508127
------------------------------------------------------
Bitcoin Address Compressed
1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
------------------------------------------------------


PRIVATE KEY
0000000000000000000000000000000000000000000000000000000000000009
------------------------------------------------------
PUB Uncompressed
04acd484e2f0c7f65309ad178a9f559abde09796974c57e714c35f110dfc27ccbecc338921b0a7d 9fd64380971763b61e9add888a4375f8e0f05cc262ac64f9c37
------------------------------------------------------
RIPEMD-160 hash40
808dc34fd51c936e2db7c702745228b5a6a53d55
------------------------------------------------------
Bitcoin Address Uncompressed
1CijKR7rDvJJBJfSPyUYrWC8kAsQLy2B2e
------------------------------------------------------
PUB Compressed
03acd484e2f0c7f65309ad178a9f559abde09796974c57e714c35f110dfc27ccbe
------------------------------------------------------
RIPEMD-160 hash
b46abf4d9e1746e33bcc39cea3de876c29c4adf3
------------------------------------------------------
Bitcoin Address Compressed
1HSxWThjiwbC4dJbXHMpBfwRenB12UguG5
------------------------------------------------------

It works exactly like the basics above. But without the private key.


I have done testing in the last few months and the results show 99.99% accuracy. And there is only one error in the first private key which is the point generator itself in the ECC.

The biggest question is how is that possible? How can a public key be created without a private key? Isn't this something that is almost impossible for most people?

Yes of course, but that's the reality, although I don't know enough about it because I'm not an expert.

Let's see what actually happens!

What I know is that ECC works by representing a binary value (the private key) to get certain coordinates on a curve. That's the brief description that I understand.

It is very clear to me that something is wrong, please someone here if anyone understands what is actually happening?