Quote from: BlackHatCoiner on Today at 04:26:45 PM

Breath!

Quote from: jennamarble on Today at 01:51:45 PM

this is understandable I will use 132 bits of entropy as a string plus the increments for extra security and uniqueness plus it would be deterministic for me if whenever I forget I can recover it however the big number is just hard to recover if lost so the point stands that I will use string, not my name as I gave that just as an example I will use a string with 132 bits of entropy as that is strong and used by electrum as well plus by using GPU I don't want to save all those billions of addresses so i will only save the addresses that match the pattern but with my method of string+n increments and for this increments are necessary if you use same string billions of times it will generate the same address but if you add the needed numbers/increments it will fulfil the task of pattern and uniqueness since using 132 of entropy for single address is not very economical I would say.

Quote from: jennamarble on Today at 01:51:45 PM

this is understandable I will use 132 bits of entropy as a string plus the increments for extra security and uniqueness

Wait, do you mean that you'll hash that entropy or that you'll use it directly for the addresses? There's no need to hash anything neither to take any extra security measures; if you randomly generate 256 bits, they're fine to perform ECDSA, SHA256, RIPEMD-160, SHA256 and then the final base58 encoding.

Quote from: jennamarble on Today at 01:51:45 PM

it will fulfil the task of pattern and uniqueness since using 132 of entropy for single address is not very economical I would say.

You may have misunderstood the procedure. Every address is an encoded RIPEMD-160 hash along with a version byte in the front and with a checksum in the back. [Useful link]

There are no 132 bits of entropy. You may have confused it with the BIP39 in which you use 128 bits of entropy along with 4 bits of hash for the seed generation. Then, after some PBKDF2 and HMAC-SHA256/512 rounds, you end up with the derived addresses. But, that's just a proposal for generating deterministic keys. If you want to go with the standard way, you'll need 256 bits.

the string does not have to bip39 to be secure is just needs to be long enough i think you are misunderstanding or trying to twist my words or maybe trying to change the topic you think i dont know about those procedures you talk about you are clearly not very claver regarding this

jennamarble

Posts

Merits