Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unciphered - Randstorm - BitcoinJS SecureRandom #38

Open
ghost opened this issue Nov 16, 2023 · 0 comments
Open

Unciphered - Randstorm - BitcoinJS SecureRandom #38

ghost opened this issue Nov 16, 2023 · 0 comments

Comments

@ghost
Copy link

ghost commented Nov 16, 2023

Hi Folks,

Given the recent publication

Which goes on to reveal that "Bitcoin private keys should be generated with 256-bits of entropy; unfortunately, affected keys generated with vulnerable BitcoinJS (or dependent projects) often used less entropy than required.... reduces the amount of necessary work anywhere from 32 to 64-bits." due to several potential problems encountered with Random Number Generation in browser-based software used at the time. And that these vulnerable wallets were created between 2011 and 2014.

What modifications would be required to the code to only produce a database of non-zero, dormant wallets generated within a targeted time period - e.g 2011-2012 or 2011-2014?

Appreciate your thoughts, thnaks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants