if you run out you create collisions with all kinds of side affects, like overwriting data, thats why you need to use Collision-resistant ids methods like CUID2.
Some Corrections/Important Points to Note: 1. At 6:00, the problem is that you want to receive payments.. so you ask people to send payments to your address or "the hash of your public key". But if there is another person, who asks me for some money, and I pay to them.. they can see which transaction's outputs(say "T_o") have I used to pay them. Hence, they know that I own the account corresponding to the hash of pubkey that is present in the output T_o. So, they can figure out what all other payments have I received by checking what all transactions have output money to hash of my pubkey. We don't want this.
Every time you want to receive money, you use randomizer to generate a new set of public and secret keys then use the new public key to receive coins and discard the new secret key (or keep it somewhere safe!). This way you can generate billions of public keys and maintain anonymity(privacy) using each public key only once.
Thanks, Tadge! I am loving these classes.
8:27 should be 32 bits not 32 bytes because you tell later that the should be lass than like a billion. Is there any misunderstanding here?
What is meant by "list of addresses can run out"?
if you run out you create collisions with all kinds of side affects, like overwriting data, thats why you need to use Collision-resistant ids methods like CUID2.
Some Corrections/Important Points to Note:
1. At 6:00, the problem is that you want to receive payments.. so you ask people to send payments to your address or "the hash of your public key". But if there is another person, who asks me for some money, and I pay to them.. they can see which transaction's outputs(say "T_o") have I used to pay them. Hence, they know that I own the account corresponding to the hash of pubkey that is present in the output T_o. So, they can figure out what all other payments have I received by checking what all transactions have output money to hash of my pubkey. We don't want this.
Every time you want to receive money, you use randomizer to generate a new set of public and secret keys then use the new public key to receive coins and discard the new secret key (or keep it somewhere safe!). This way you can generate billions of public keys and maintain anonymity(privacy) using each public key only once.
Very good
Very nice class! Thanks guys!
Nice
讲的很好啊！！！
What does Tadge's shirt say??
it says welcome to cuba bitch
fuck authority, get laid, delete facebook
Hold my key LoL