PHMcDonaldTrump
Enthusiast
Ako po ay isang BSIT 3rd Year student.. Since its Lock'down pagbasasa ang kadalasang libangan ko. then i stumbled upon an article that a h@cker group called BlockchainBandit manage to s†éál worth hundred million USD of ethereum tokens from a rich ethereum wallet.. Basi sa naging invistigation ng mga Crypto'forensics hindi raw vulnerability ng ethereum main-net ang naging cause kundi yung mismong coding ng paggenerate ng ethereum wallet..
Since i am a also big fan of cryptocurrency, i was amazed and i want to dig deeper.
-First my attention was turned to how an ethereum wallet address is created: And after a couple of minutes of googling
I learned the proccess..
Basic understanding nalang para madaling e explain..ROFLMAO:
PrivateKey ==> PublicKey ==> Ethereum Wallet
PrivateKey - Randomly generated Hex string using SHA256, 64characters string from 0-9 or a-f..
PublicKey - Derived from PrivateKey using secp256k1 encryption, 128characters string from 0-9 or a-f..
Ethereum address - Derived from PublicKey using keccak256 encryption, 40characters string from 0-9 or a-f..
So itong PrivateKey ang dapat nating itago kac yan ang susi para buksan ang wallet natin.. pwede siyang iimport sa kahit anung wallet(metamask,myetherwallet etc..)..
-Next a Spark in my mind was created:
Is ethereum realy safe??
Since private key is ramdomly generated, what are the odds that my privateKey was also ramdomly generated by someone in some other part of the world??
Then i ended up deciding to treat myself a challange.. To cr@ck a privateKey from a wallet address..
And Yes this is my Lock-Down challange..
UPDATE:
So after reading and reading and reading.. I found out that it is barely impossible to reverse the encryption process since secp256k1 is an elliptical curve cryptography.. No more explanations!! the simplest way to describe this is secp256k1 is a one'way encryption (it means you can go through but you cant go back)..
Since privateKey is nothing but a 64chars hex string what if i generate all private'keys from 0x000..000 to 0xffff...ffff??
So i calculated the total combinations of 0-f in 64 digits with repetitions and the result is huge(2^(8x32))!!
Hmmn.. Kahit meron akong Processor na kayang mag generate ng 10 trillion PrivateKeys per second aabotin parin to ng siyam siyam.
at kakailanganin ko ng 7.8TB na storage para lang dito.. So kung paplanohin natin egenerate lahat ng wallet addresses, with nowadays computing power kahit ipunin natin lahat ng computer sa buong mundo aabotin parin tau sa pag puti ng kalabaw..
I needed another approach:
And here is the plan. To test my luck with whatever is available and whatever i can do with my noobie understanding.
==> randomly generate an ethereum address with tied privatekey
==> checking the balance of the generated address if theres something i can s†éál
==> store in disc if i got the hit..
Will be updated Soon..
Bashes, suggestions are accepted
Since i am a also big fan of cryptocurrency, i was amazed and i want to dig deeper.
-First my attention was turned to how an ethereum wallet address is created: And after a couple of minutes of googling
I learned the proccess..
Basic understanding nalang para madaling e explain..ROFLMAO:
PrivateKey ==> PublicKey ==> Ethereum Wallet
PrivateKey - Randomly generated Hex string using SHA256, 64characters string from 0-9 or a-f..
PublicKey - Derived from PrivateKey using secp256k1 encryption, 128characters string from 0-9 or a-f..
Ethereum address - Derived from PublicKey using keccak256 encryption, 40characters string from 0-9 or a-f..
So itong PrivateKey ang dapat nating itago kac yan ang susi para buksan ang wallet natin.. pwede siyang iimport sa kahit anung wallet(metamask,myetherwallet etc..)..
-Next a Spark in my mind was created:
Is ethereum realy safe??
Since private key is ramdomly generated, what are the odds that my privateKey was also ramdomly generated by someone in some other part of the world??
Then i ended up deciding to treat myself a challange.. To cr@ck a privateKey from a wallet address..
And Yes this is my Lock-Down challange..
UPDATE:
So after reading and reading and reading..
I found out that it is barely impossible to reverse the encryption process since secp256k1 is an elliptical curve cryptography.. No more explanations!! the simplest way to describe this is secp256k1 is a one'way encryption (it means you can go through but you cant go back)..Since privateKey is nothing but a 64chars hex string what if i generate all private'keys from 0x000..000 to 0xffff...ffff??
So i calculated the total combinations of 0-f in 64 digits with repetitions and the result is huge(2^(8x32))!!
Hmmn.. Kahit meron akong Processor na kayang mag generate ng 10 trillion PrivateKeys per second aabotin parin to ng siyam siyam.
at kakailanganin ko ng 7.8TB na storage para lang dito.. So kung paplanohin natin egenerate lahat ng wallet addresses, with nowadays computing power kahit ipunin natin lahat ng computer sa buong mundo aabotin parin tau sa pag puti ng kalabaw..I needed another approach:
And here is the plan. To test my luck with whatever is available and whatever i can do with my noobie understanding.
==> randomly generate an ethereum address with tied privatekey
==> checking the balance of the generated address if theres something i can s†éál
==> store in disc if i got the hit..
Will be updated Soon..
Bashes, suggestions are accepted