Topic: Super BrainFlayer 2019 - Enormous Blooms, Gigantic Text-Files, all BTC ADDRESSES (Read 1584 times)

Locking this thread so it stops getting bumped and soliciting more suckers.

I will need to try to correct my error of giving merit to op

---

---

https://bitcointalk.org/index.php?action=merit;u=64507


Merit summary for philipma1957

Merit: 1864

Sent in the last 120 days

Today at 07:12:11 PM: 4 to ryanc for Re: Super BrainFlayer 2019 - Enormous Blooms, Gigantic Text-Files, all BTC ADDRESSES


Today at 07:10:38 PM: 4 to btc-room101 for Super BrainFlayer 2019 - Enormous Blooms, Gigantic Text-Files, all BTC ADDRESSES


Today at 07:09:56 PM: 2 to gmaxwell for Re: Super BrainFlayer 2019 - Enormous Blooms, Gigantic Text-Files, all BTC ADDRESSES

Not sure how this occurred.

---

---

---

---

I am the the author of Brainflayer. Please be aware that this poster is violating my copyright, and any software they offer (if it exists at all) may include malware.

Brainflayer is not free (as in speech) software. Distributing modified versions of it (with the sole exception of forked repositories on github) is illegal. Distributing precompiled binaries is illegal without exception.

As gmaxwell pointed out, a lot of what was posted by btc-room101 is "technobable nonsense".

Are you selling software or not?

I think if you bother to read my website www.inflection.top, that all this software has been free since last year to anybody in a 3rd world country, that want's to learn about btc

I think the next gen btc will come from a person who has a DEEP understanding of the failure of bitcoin, and no better way, that studying the bowels of bitcoin, than hacking bitcoin, and learning how to crack it,

In summary 'inflection' is when mining became non-profitable, and scanning became more profitable, IMHO more hw in the future will be deployed to find 'lost coin' than to mine the new, as the mining is now a negative profit


Is it legal to run a computer? Is it legal to add two numbers? 2+2=x, I think there are many control assholes on earth, who have long demanded a license to code, and tax to own a compiler, that a fee be paid if you 'write a program'

don't use this damn word 'wallet' with me, there is no wallet in this scope, were talking raw ECDSA data here that is all gleaned from the public block-chain

I myself don't even own a bitcoin exchange account, I don't care about your US-Dollar, I just care about mathematics

We hack bitcoin because assholes say we can't, that it can't be done, .. blah-blah

I don't care about the price of btc ( eventually going to zero ), I don't care about the people who use btc to 'get rich'

I think crypto-currency's may be useful, if they are truly secure, private,  and safe, ... BITCOIN is NOT.

Here's an overview of the new brainflayer-2019, I wrote much of this code in 2017, but essentially rewrote brain-flayer,

first some terms there are keys ( private keys, usually hex, but often in wif (base58) for humans, there addresses which are public-key, which are frequently hashed and converted to base58 where they become the common btc-address, in 'hacking' its best of course to work in the world of pure-hex for everything,  the WIF both addr/priv/pub keys that display is just for user usage. Of course if your going on line you need to generally use WIF format for most online database's to display history address,
What's new

1.) Full support for 64 bit, that includes the bloom filters, before they were limited to 4gb is which  a search space of about 50 million keys, now with 16gb blooms you can search 200M addresses all at once ( remember here the GOAL of brainflayer is to run through possible key-space and look to see if that key's address is 'hot', but 'hot' I mean containing any value in history

2. Extensive work in addition to new hoptions -H and -P, where -H is for halt, and -P is for private key, the -H option tells brainflayer how long to run in terms of input before it re-cycles, this is important for batch file automated running, where you don't want endless running. -P causes BF to output all private-key information this is very important to to build a database of all Address/Private Key 'Pairing'

Remember what we're doing here is building a database to relate all btc addresses used in history of btc, and they're private-key/public-key information.

Also important is the public-key, as often it is ignored, but for advanced hacking I call 'super-van' because essentially I completely rewrote and gutted vanity gen, and gave it a single purpose of GPU hacking, but it needs the data from super-flayer.

...

Sometimes I will write, brainflayer sometimes 'super-flayer', there are many versions, I think this is the 3rd iteration of the BF re-write, all options have been modified

What's import

-b , the bloom filter your using is very important

-c u,c,x ; u & c of course are common in BTC, but 'x' is very important because that is the raw format, and often the 'raw' is the best information

-t sha256 is is most common a default, most of these are no longer used, the keccak does work, it is possible to hack ethereum using this tool, I did it, but there is so little 'coin' worth finding, its really not worth the bother

-x is very important here we tell SBF ( super BF  ) that the input is 'hex', now what this means is that instead of converting 'passwords' we're passing the 'hex' for the passwords directly, this means you can use your own encoding scheme and then let SBF see if that 'key' was ever used to generate an address. This is very important for hacking the new 2048 scheme where you have 8-words from a dictionary, and they're hashed and combined

-k, -n are useful for baby-step, giant step DLP algos where you have a plan to hack a particular private-key ( address pair )

-B batch say's how many private-keys do I process on every cycle default is 4096 which is fine, if you have a 32GB or larger ram system, then go for 32k o as you wish, when using huge arrays it can make the ESDSA algos more efficient but you need massive memory.

-I I think this is too slow, essentially this is just telling SBF to run from nth private key and increment ( can be controlled ) and see if that priv-key matches anything in the bloom filter ( your list of addresses of value ), super-van is much better than this and 5-10x faster than the CPU


 ./brainflayer3 -h
Usage: ./brainflayer3 [OPTION]...

 -a                          open output file in append mode
 -b FILE                     check for matches against bloom filter FILE
 -f FILE                     verify matches against sorted hash160s in FILE
 -i FILE                     read from FILE instead of stdin
 -o FILE                     write to FILE instead of stdout
 -c TYPES                    use TYPES for public key to hash160 computation
                             multiple can be specified, for example the default
                             is 'uc', which will check for both uncompressed
                             and compressed addresses using Bitcoin's algorithm
                             u - uncompressed address
                             c - compressed address
                             e - ethereum address
                             x - most signifigant bits of x coordinate
 -t TYPE                     inputs are TYPE - supported types:
                             sha256 (default) - classic brainwallet
                             sha3   - sha3-256
                             priv   - raw private keys (requires -x)
                             warp   - WarpWallet (supports -s or -p)
                             bwio   - brainwallet.io (supports -s or -p)
                             bv2    - brainv2 (supports -s or -p) VERY SLOW
                             rush   - rushwallet (requires -r) FAST
                             keccak - keccak256 (ethercamp/old ethaddress)
                             camp2  - keccak256 * 2031 (new ethercamp)
 -x                          treat input as hex encoded
 -s SALT                     use SALT for salted input types (default: none)
 -p PASSPHRASE               use PASSPHRASE for salted input types, inputs
                             will be treated as salts
 -r FRAGMENT                 use FRAGMENT for cracking rushwallet passphrase
 -I HEXPRIVKEY               incremental private key cracking mode, starting
                             at HEXPRIVKEY (supports -n) FAST
 -k K                        skip the first K lines of input
 -n K/N                      use only the Kth of every N input lines
 -B                          batch size for affine transformations
                             must be a power of 2 (default/max: 4096)
 -w WINDOW_SIZE              window size for ecmult table (default: 16)
                             uses about 3 * 2^w KiB memory on startup, but
                             only about 2^w KiB once the table is built
 -m FILE                     load ecmult table from FILE
                             the ecmtabgen tool can build such a table
 -v                          verbose - display cracking progress
 -P                          print private key in output
 -H                          Halt at line
 -h                          show this help


...


Actually using SBF requires that you have built your bloom-filter files, its best to have many blooms, like 100Msatoshi.blm, 10BTC.blm, 1MSatoshi.blm, I think there are 100Million satoshi to a btc, so 0.01btc is 1m-sat, which gets down to almost dust, but I like to go for any address ever used that contained any kind of value, as in fact they do get user again, and over&over,

-w is worth playing around, I think its designed for older pc's with limited memory and power
-m is much the same, when your running SBF for hours like this model is designed, it doesn't matter to pre-compute the tables

Remember the original BF was designed to take a database of passwords, and convert them to hex with SHA, and then to use that as a private key, and look up the address with Ecdsa, and then if an address match is found in the bloom the private-key/address/password is printed to screen that was the original model.

The way that I used SBF is more to generate data, and patterns used for ML ( LSTM/RNN ) where you want to learn about real prior used keys, public-keys, and addresses and look for patterns, cyclic or FFT that can be fed into DLP algo's.

sure  you will always find BTC that has real-value, but IMHO that is not the goal here, this is really about learning the patterns of bitcoin private-key/address pairs

SVM can allow you to catalogue, the different systems to compute private keys, there are many companys that provide 'wallets', and this stuff can be correlated so you start seeing the patterns of different schemes used to generate the private-keys and addresses

Also much can be done with public-keys that are found in the early pre2012 block-chain, and these are the btc of real value on the chain

Why are you giving the tools to hundreds to hack Bitcoin? If you have lost interest then leave it be. You don't need to give tools to the masses which will be used for malicious purposes. It seems that even you were using it for malicious purposes. Counting cards is a little bit different to what you are proposing to give out. Counting cards actually takes a great deal of skill and shouldn't actually be illegal in Casinos. Its just a way of reducing the odds.

Hacking into other peoples wallets though? That is illegal and shouldn't be distributed. Also considering you are a hacker and you've developed this code. Whats to say you aren't spreading malware through this? Sure it could be checked but the first few hundred people excited that they could earn a quick buck could be compromised.

I would say leave it. You don't need to release this. Brain flayer is out there which can be used for educational reasons if people are interested in our unsecure brain wallets can be and how they can be subject to hacks. We don't need you to release something with the sole purpose of reducing the amount of time that a brain wallet could be compromised.

I would disagree about "... can't sell it... its all tracked..." and so on
if you do know how to hack it, you can somehow figure out how to outwit tracking
can you proof by signing a message from one of the addresses that you found with big balance

Share your experience on https://github.com/btc-room101, It will be very interesting to take advantage of your experience.

Brainflayer is 4 years old, hasn't been updated since then,

I totally re-wrote brainflayer from scratch, added dozens of new switches for finding private keys from public keys, I also wrote dozens of new unix like cmd-line utilitys to assist in hacking btc

I also wrote dozens of shell scripts to run 24/7 to automate btc hacking on server startup.

I rewrote vanity-gen, stripped out all the bs, and put in bloom-filters to find private-keys for address databases placed in bloom-filters ( 32gb+), completely re-wrote all the GPU C++ code that run's in opencl so it can run at amd or nvidia

snort block-parser is 2014 doesn't work, and hasn't been maintained, I just posted the code to parse bitcoin blocks and get the addresses yesterday on this forum ( see bitcoin hacking university )

bitcrack I have no idea, but it sounds lke a 'linear collider clone', which means it just linear searchs private-key space 1 to N, where N is 10**77, so maybe if every atom in the known universe ran the software, then in 10k years you might hit that one key you were looking for,

What I do is look  for 200million addreses at once, 150M-keys/sec 1060 class gpu cards, and the search space is based on DLP known working algos, I don't care about any particular address I just want to find their private-keys and store them

Then you running the mining-pool  collector ( I posted yesterday ) run every ten minutes to get new addresses before they make it to the block-chain, and everytime a new address is used, you look to see with a bloom filter whether you have that private key, if you do then you can store, or sweep.

I have lost interest in this subject after 5+ years of hacking btc, so I'm just looking for students interested in this crap. Sort of like Ed Thorpe teaching MIT kids how to count cards.

All tools are already on github:
https://github.com/ryancdotorg/brainflayer
https://github.com/brichard19/BitCrack
https://github.com/znort987/blockparser

Here is where I post the standard warning:

Bitcoin "hacking" tools have frequently been used to spread malware.

We could make some guesses as to why: Someone creating actual hacking tools is likely to be someone with missing or unusual morals-- if they'll hack other people, why not you?  People who want to use hacking tools are also victims that people won't necessarily feel too bad about ripping off.  The greedy impulse of potentially stealing some Bitcoin may also blind people to being properly sceptical about what they're downloading and running.

Whatever the reasons are, it happens.

Often the 'hacking' tools are not just not real, but they're technobable nonsense.  Other-times they are real, but with an unwelcome surprise inside.

In this case the post sets off a number of red-alarms, for example "64gb bloom filters" make no sense at all. There are about 500k unique output addresses, a filter with a one in a million false positive rate is about 2MB in size. The author's other posts are full of other technobabble nonsense, like "ECDSA primes".

Consider yourself forewarned.

Back in 2015 when Brainflayer came out I played around, and over two years I rewrote the core, and raised the bloom filters from 512mb to 64gb, and setup pass-word tables at 512gb, note your need a 4TB hard-disk to pretty much play with this stuff, and 64gb of RAM.

The other thing is putting bloom-filters on GPU cards, with a 1060 you don't really get 3GB of RAM for one allocation, its really like 512mb, same for 1080 card you don't get 8gb you get around 1gb, but once you know the maxes you can put bloom filters on the card;

Another thing is you need to harvest 200million addresses that have had value, and of course the 50k with high-value, and then run 24/7 to get the new addresses out of the mining-pool.

...

What is brain-flayer? Well its a program that was written to crack bitcoin addresses that used test-strings as their private-key, thus if you use say a 512gb text table, which is every possible combination of strings for every language on earth, ... and pass that though a GPU/CPU then run through keys for every possible 'string' then you can find all the bitcoin accounts that used 'brain-wallets' ( another word for using a string to generate a private-key )

The unique thing about brain-flayer is that it used bloom filters to keep track of the addresses of high-value, so this way as it ran and matched an address with a key/pair then the private-key/address/pass-string get printed out, so you can generate 1,000's of private keys that all at one time contained value.

Most of course are all drained, but its still interesting.

There are many parts to this puzzle, if people are interested tell me what parts of the above are interesting and I'll upload the code to github.

github.com/btc-room101

Given there are dozens of 'parts' to this package, I need to know what people need? I also did this stuff for ethereum as well, so that's available.

Just moving on, that's why I'm dumping the code, but I don't want to bother uploading to github.com if there is no interest.


...

The thing is this just isn't about 'test-string', or brain-wallets, there are many tests that can be done, as many people used block-chain 'data' as their private-key, so there are still tons of 'dust' to be found for those who want to bother.

Finally, let me say this I have found lots of BTC, and I just move-on, I'm not interested in collecting btc, as you can't sell it, its not private, it can't be sold, and I would never use it in an exchange, as its all tracked, so what would be the point? In fact I don't even own an exchange account.

I just find that HACKING BTC is very interesting, I have been involved in hacking DES, since the 1980's, and AES, and ESCDSA, so all this stuff is just an interesting hobby for me.