Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: TheArchaeologist on July 29, 2018, 08:32:57 AM



Title: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 29, 2018, 08:32:57 AM
Hi,

As been discussed many times before using a Brainwallet is a bad idea. I ran some test myself and found 18.509 BTC-addresses based on a brainwallet which also has been used in the blockchain before.

I tried to compare my results with the results of other researchers but could not find any lists online at all. I found some examples but not a comprehensive list. So I published my own results over here: https://eli5.eu/brainwallet

Please note: all published addresses have a balance of 0 so this is not a list for robbers :). There are also a lot of extra datasets I haven't used this far so I expect the numbers to go up once I use them as well (I'm in the middle of perfecting my own tooling and blockchain parser so this will take some more time first).

I love to get some feedback and if you have results to share which I missed in this round I'm more than happy to hear from you and include them.

TA


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: keychainX on July 29, 2018, 09:22:20 AM
Which dictionary did you use?

One word or multi word attack?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 29, 2018, 10:12:18 AM
I mainly used single words from dictionaries and used passwords from published password dumps.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: keychainX on July 29, 2018, 10:20:21 AM
Did you use block parser to create the list?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 29, 2018, 10:32:09 AM
No, I used my own parser but since it wasn;t/isn't finished yet I got the transactions and balance from using the Blockchain API.

The steps involved for creating such a list:
  • Perform a SHA-256 on the input (word/phrase)
  • Check the generated private key (compressed/uncompressed) against my own databases with successes
  • If Private key is not in database create BTC-address from the key(s)
  • Check if BTC address exists on blockchain based on my own database with all BTC-addresses
  • If address is found store the private key and passphrase in the database and get info on number of transactions and balance from Blockchain API

That's about it.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on July 29, 2018, 10:40:12 AM
Oh wow... more than 18k BTC addresses having used single word passphrases is pretty bad. At least most of them don't seem to have been used since 2013.

Did you look into Brainflayer [1] or did you feel more comfortable using a custom made solution?

[1] https://github.com/ryancdotorg/brainflayer


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 29, 2018, 11:18:05 AM
I did look into Brainflayer and also used it in the process. But you got to keep in mind Brainflayer is not a standalone solution. It depends on creating a Bloom filter based upon all addresses used in the BTC-Blokchain. So you first need to come up with such a list: this is where I used my own parser to create the list. In 2015 when Brainflayer was released there were about 80 Million unique addresses on the blockchain which lead to a lot less false positives than when used on the 400 Million plus unique addresses currently in use. And finally Brainflayer just reports if a match was found it doesn't do any looking into transactions or balances used.

So what I did was make use of Brainflayer to do a very fast scan using a Bloomfilter and I processed the results from there within my own tooling to filter out false positives, duplicates and add extra information on transactions and balances.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: philipma1957 on July 29, 2018, 11:39:37 AM
most of the ones you found  have a 0.00005460 deposit and withdrawal

ie 2 transactions.  so I would adjust the 18,509  down to under 2,000

as it is obvious those addresses where designed and used  to receive then send 0.00005460

0.0000546 seems to start at 899 and end at 18036   that is more then 17,000  where security was basically an

" I don't care do you? "  plan.   But it does interest me  that the first 899  on the list were not like that and used often.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 29, 2018, 01:20:03 PM
I personally believe most of the ones with a 0.00005460 deposit and withdrawal are in there because of some experiment in the past where simple dictionary words were used to see how long it would take for an attacker to grab the funds. I do agree with you the ones with the most transactions are the ones most interesting that's why I sorted the list by number of transactions. I still think the other ones are interesting as well when trying to compose a list of brainwallets which have been used in the past.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: keychainX on July 29, 2018, 01:47:33 PM
What is the biggest transaction on those? Anyone above 10BTC?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 29, 2018, 03:36:29 PM
Biggest is over 500 BTC. As stated on the site (https://eli5.eu/brainwallet/detail/14NWDXkQwcGN1Pd9fboL8npVynD5SfyJAE.html):

General Information
The passhrase below was used as a Brainwallet to generate the given address.

BTC Address: 14NWDXkQwcGN1Pd9fboL8npVynD5SfyJAE
Used passphrase: bitcoin is awesome
Total transactions: 19
Amount received: 501.06500863 BTC
Amount spent: 501.06500863 BTC

Proof
You can check the private key is indeed known by verifying the following signed message when running your own node:

Code:
bitcoin-cli verifymessage "14NWDXkQwcGN1Pd9fboL8npVynD5SfyJAE" "HBi3IJsPku4lbbxJo3KAbghdPUKkpcCkg0E6VqHBDLGoEXvzdcUqI3MLA1bvoe4IcTcB5V4IL+l5XB7YLIchg7E=" "By using a weak brainwallet the private key for address 14NWDXkQwcGN1Pd9fboL8npVynD5SfyJAE has been compromised."


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: keychainX on July 29, 2018, 04:25:09 PM
Cool, thanks!  ;)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on July 29, 2018, 07:38:57 PM
Very interesting data, and proof that we are inherently awful at privacy. I think my personal favorite is number 72, "how much wood could a woodchuck chuck if a woodchuck could chuck wood", which has held over 500 BTC.

You've missed a decimal point at entry 266 - it currently says it has held over 2 billion BTC.  :D


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 29, 2018, 08:47:46 PM
Thanks for pointing out the 2 Billion mistake! I will look into it tomorrow.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: f3tus on July 30, 2018, 07:17:33 AM
This thread might be of interest to you: https://bitcointalk.org/index.php?topic=2488493.0

And I did something similar with Ethereum (only used some ~10,000 most common passwords): https://bitcointalk.org/index.php?topic=2488493.msg42291616#msg42291616


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 30, 2018, 10:14:55 AM
Thanks for pointing out those posts. I was aware of the first one (from Pastebin) but haven't yet made my own dataset with the kind of data decscribed in there like BTC-addresses, transaction-id's, merkleroots, etc.

I will read up on your post about Ethereum brainwallets. I'm focussing on BTC for now but it's always nice to read about other experiences!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 30, 2018, 10:41:47 AM
Very interesting data, and proof that we are inherently awful at privacy. I think my personal favorite is number 72, "how much wood could a woodchuck chuck if a woodchuck could chuck wood", which has held over 500 BTC.

You've missed a decimal point at entry 266 - it currently says it has held over 2 billion BTC.  :D

Fixed some nasty bugs which caused some addresses to stay blank on the overview-pages and fixed some wrong amounts_in and amounts_out which were not properly converted in some cases.

I also added another 60 new entries to the list based on a small sweep I just completed so the list currently contains 18.569 entries.

Finally: I'm always interested in new datasets to try and/or results from other people who conducted this kind of Research. I aim to let this list grow to the best source for compromised brainwallets.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Evil-Knievel on July 30, 2018, 10:50:08 AM
As been discussed many times before using a Brainwallet is a bad idea.

I disagree, I have never lost anything from a brain wallet but I have lost quite a few coins from failing hardware wallets and dying hard drives.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: amaclin1 on July 30, 2018, 10:54:30 AM
Is there there a list of addresses in plain text?
I want to compare your list with mine :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 30, 2018, 10:59:35 AM
As been discussed many times before using a Brainwallet is a bad idea.

I disagree, I have never lost anything from a brain wallet but I have lost quite a few coins from failing hardware wallets and dying hard drives.
I get you stand on this and maybe the introduction was a bit too short on the subject. As always there are exceptions to the rule and if you manage to remember a brainwallet with high entropy and also using some personal knowledge (like a salt) it becomes a lot more secure. Let's just hope you want suffer from a dying brain instead of a dying hard drive! :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on July 30, 2018, 11:07:02 AM
Let's just hope you want suffer from a dying brain instead of a dying hard drive! :)

The human brain is a very fragile thing. There are literally hundreds of completely unpredictable accidents and illnesses that can leave you with profound memory loss. Relying solely on your memory is a bad idea.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 30, 2018, 11:18:48 AM
Is there there a list of addresses in plain text?
I want to compare your list with mine :)
There isn't one yet but I could build it easily. So you are looking for a text file containing 1 BTC address on each line?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: amaclin1 on July 30, 2018, 11:24:29 AM
There isn't one yet but I could build it easily. So you are looking for a text file containing 1 BTC address on each line?
Any format you prefer  :)
I am too lazy to copy-paste 38 pages from https://eli5.eu/brainwallet/  ;D


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 30, 2018, 11:30:47 AM
I am too lazy to copy-paste 38 pages from https://eli5.eu/brainwallet/  ;D

Grab them from this text-file then: https://eli5.eu/brainwallet/btc_brainwallet_v18569.txt

Would be nice if you could share the ones I miss!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Thirdspace on July 30, 2018, 01:26:45 PM
have you checked whether any of them have BCH or BTG balance? :D
or are they old used addresses with no chance of having balance on recent forks?
can you sort the list by the latest date of transaction? might give more insight


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on July 30, 2018, 01:46:46 PM
have you checked whether any of them have BCH or BTG balance? :D
or are they old used addresses with no chance of having balance on recent forks?
can you sort the list by the latest date of transaction? might give more insight

Good thinking! All of these brainwallets seem to have been cleared up a long time ago though, presumably there are multiple people running regular scans on the most common brainwallet addresses as described by OP. At least that was the state of 2015 when Brainflayer was first introduced at Def Con 23.

I'd also love to see a feature for listing the addresses by the latest transaction date though.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 30, 2018, 03:03:39 PM
Forum member amaclin1 did a check and came up with 200 addresses/brainwallets he had which were missing from my list. I just added them to m database and updated the site. My own software indicated two of the entries as a duplicate so the total list now contains 18.767 entries. Thanks for helping/sharing!

To comment on the other request by adding the latest transaction date: This is something I currently do not have present in my database. I will mark is as a future request since I first have to complete/update my own blockchain parser for this. But as mentioned by HeRetiK all of the addresses were emptied a long time ago so way before any fork afaik.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: rpstatic on July 30, 2018, 05:31:18 PM
Did you also find wallets with any balance on it? Would be interesting if people still use them.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on July 30, 2018, 07:27:29 PM
Did you also find wallets with any balance on it? Would be interesting if people still use them.
No I didn't. It seemed to be a lucrative business once so I can imagine lots of time and computing power has been consumed to find private keys for addresses with non zero balances in the past.

Furthermore: I'm just interested in finding as much brainwallets as possible which have been used in the past. I'm not interested in stealing funds which aren't mine.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 26, 2018, 04:33:25 AM
Bumping this thread as I am also doing something similar, and plan to publish my results to increase awareness of the risk of using sha256 brainwallets.

Like the OP, I'm interested in this only for research purposes, so I scanned all known addresses rather than just cherry picking those with a balance. I'm using brainflayer, but as previously noted, the large number of addresses in the blockchain as of 2018 result in a very high false positive rate (currently around 13%) which requires a lot of post processing.

So far I've found 20329 valid keys. The large majority of the keys are based on single English dictionary words, which seem to have been deliberately sent small amounts (for research? for fun?) back in 2013.

This particular brainwallet concerns me, as the transactions are recent (March 2018), and for a large value (0.5 BTC): https://www.blockchain.com/btc/address/1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR

The funds were swept out instantly, which strongly suggests it was a theft by a bot watching that privkey. The passphrase is a song title, with minor mangling.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Thirdspace on September 26, 2018, 01:15:30 PM
This particular brainwallet concerns me, as the transactions are recent (March 2018), and for a large value (0.5 BTC): https://www.blockchain.com/btc/address/1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR

The funds were swept out instantly, which strongly suggests it was a theft by a bot watching that privkey. The passphrase is a song title, with minor mangling.
there were 4 transactions competing to sweep balance from 1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR (https://bitaps.com/1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR)
I found two of them were trying on two different addresses with same balance of 0.5 BTC,
receiver address 17WRjamo... and 1LdUHTEV... (https://bitaps.com/1LdUHTEVxWJhrhKfy4H3VuYDnTHQVjsdBn) competing on utxo of 1GkGD48u... and 152DXcBq...
I think there is more to it than just some bots sweeping some addresses
did you also find private key for 152DXcBqGShpC7mBj4XZHQG9uGY9mUtZ8d (https://bitaps.com/152DXcBqGShpC7mBj4XZHQG9uGY9mUtZ8d) ?
btw, that receiver address 1LdUHTEV... has balance of 50 BTC :o 450+ tx ins without a single tx out


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on September 26, 2018, 01:45:47 PM
[...]

This particular brainwallet concerns me, as the transactions are recent (March 2018), and for a large value (0.5 BTC): https://www.blockchain.com/btc/address/1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR

The funds were swept out instantly, which strongly suggests it was a theft by a bot watching that privkey. The passphrase is a song title, with minor mangling.

It not only suggests bots, it also suggests that these bots iterate through rather impressive lookup tables.

Have you checked whether this particular passphrase has been part of a prior leak? You can check here: https://haveibeenpwned.com/Passwords

It would be interesting to know whether our brainwallet sweepers are using publicly available password lists or have some pimped collections of their own.


there were 4 transactions competing to sweep balance from 1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR (https://bitaps.com/1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR)  [...]

There seem to be quite a handful of bots competing for the most common passphrases. This talk from 2015 estimates them at half a dozen [1], I wouldn't be surprised if matters have gone worse since then.

[1] https://www.youtube.com/watch?v=foil0hzl4Pg (around the 31:30 mark)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 26, 2018, 02:27:43 PM
The funds were swept out instantly, which strongly suggests it was a theft by a bot watching that privkey. The passphrase is a song title, with minor mangling.
receiver address 17WRjamo... and 1LdUHTEV... (https://bitaps.com/1LdUHTEVxWJhrhKfy4H3VuYDnTHQVjsdBn) competing on utxo of 1GkGD48u... and 152DXcBq...
I think there is more to it than just some bots sweeping some addresses
did you also find private key for 152DXcBqGShpC7mBj4XZHQG9uGY9mUtZ8d (https://bitaps.com/152DXcBqGShpC7mBj4XZHQG9uGY9mUtZ8d) ?

Not yet.

It not only suggests bots, it also suggests that these bots iterate through rather impressive lookup tables.

There would be some challenges with maintaining a database that has several billions (maybe even trillions) of records, but it wouldn't be impossible. You would need a BIG bloom filter (to minimise false positives), and a clean and fast key->value database with lots of storage.

Have you checked whether this particular passphrase has been part of a prior leak? You can check here: https://haveibeenpwned.com/Passwords

It would be interesting to know whether our brainwallet sweepers are using publicly available password lists or have some pimped collections of their own.

Oh no — pwned!
This password has been seen 1,164 times before


Turns out it's not such a mysterious password after all; checking further, it appears in the password lists I downloaded. I thought my system had found it through mangling of lyrics (which it may have still done, independently). The password for 1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR is "loveisallyouneed"


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on September 26, 2018, 02:49:06 PM
Have you checked whether this particular passphrase has been part of a prior leak? You can check here: https://haveibeenpwned.com/Passwords

It would be interesting to know whether our brainwallet sweepers are using publicly available password lists or have some pimped collections of their own.

Oh no — pwned!
This password has been seen 1,164 times before


Turns out it's not such a mysterious password after all; checking further, it appears in the password lists I downloaded. I thought my system had found it through mangling of lyrics (which it may have still done, independently). The password for 1GkGD48ucUKCwPkwRyH1bDLJTAdeHVn2xR is "loveisallyouneed"

Alright, that's slightly less worrying then.

I was expecting something along the lines of "l0ve1s4lly0un33d" or a 1337 version of "Hey Jude" which would have implied a far vaster lookup table. (assuming it isn't already. well, probably now it will be.)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 26, 2018, 04:14:07 PM
Turns out it's not such a mysterious password after all; checking further, it appears in the password lists I downloaded.

Alright, that's slightly less worrying then.

I was expecting something along the lines of "l0ve1s4lly0un33d" or a 1337 version of "Hey Jude" which would have implied a far vaster lookup table. (assuming it isn't already. well, probably now it will be.)

I can think of one method to vastly reduce the amount of storage required for a stealer-bot, and I'm sure that people much smarter than I am have come up with a similar idea. So it's not impossible for a setup to be able to include a wide variety of permutations, in the hope of catching something in the future. I'm using a modest 2TB array on my temporary cracking machine and I estimate that could store around 20 to 25 billion candidate addresses.

I had a quick look through the results, and my system has found at least one 8 character password that does not appear in any of the source input files, has zero Google results, and is not on haveibeenpwned. The password evolved by mixing two or more disparate source lines together, and applying some extra mangling (appending, truncating, etc). THAT'S what should scare people off using sha256 wallets: your cool 8 or 10 character "random" password, even one that has no words in it, is not unbreakable.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: vit05 on September 27, 2018, 02:59:34 AM
Let's just hope you want suffer from a dying brain instead of a dying hard drive! :)

The human brain is a very fragile thing. There are literally hundreds of completely unpredictable accidents and illnesses that can leave you with profound memory loss. Relying solely on your memory is a bad idea.

It would be very interesting if someone could find papers with statistical research proving what is safer for a period of time greater than 10 years. A human brain or an HD. Something like this would definitely be very useful for many future applications. The simplest way to think about this is that it is much riskier to store a password in the brain than in a hard drive.

But perhaps the big complicator is not exactly health issues or an accident. It may be that keeping sentences is not the best way to put something in the brain, it's too risky. And many times we look for something simple as in the case of this password that is just a title of a very famous song.

But overall, few people have kept some kind of hard drive for over 10 years.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on September 27, 2018, 09:40:05 AM
It would be very interesting if someone could find papers with statistical research proving what is safer for a period of time greater than 10 years. A human brain or an HD. Something like this would definitely be very useful for many future applications. The simplest way to think about this is that it is much riskier to store a password in the brain than in a hard drive.

I doubt such papers exist.

The answer to the question depends on repetition, though. You can commit a 12 word phrase to memory relatively easily, probably in under an hour. You'll remember it for a day or two, no problem, but you'll have forgotten most of it in a week or two unless you practice it a few times every day. There's no way most people will remember something like that for >10 years unless you are repeating it at least a couple of times a week.

And then, as I mentioned, all you need is a mild blow to the head or a bad infection and you've forgotten it.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on September 27, 2018, 05:04:50 PM
Bumping this thread as I am also doing something similar, and plan to publish my results to increase awareness of the risk of using sha256 brainwallets.
Thanks for bumping. I kind of felt there was not much interest in this before as I expected to get a lot more responses to the list I published. Publishing the results including proof cost me quite some time. But good to see another person with the same interest :)


So far I've found 20329 valid keys. The large majority of the keys are based on single English dictionary words, which seem to have been deliberately sent small amounts (for research? for fun?) back in 2013.
I think your results share a lot of findings in my set. I am very much interested in the ones you found so I can update my list with the ones I missed. Any chance you can share your findings? (a list of found words/sentences you found would be enough)


The funds were swept out instantly, which strongly suggests it was a theft by a bot watching that privkey. The passphrase is a song title, wit
Yes, there are a couple of bots active which monitor the mempool (using a modified bitcoind client) for incoming transactions. Each address found is then matched against a very large set of addresses composed on all kinds of brainwallets. In other words: Just because the brainwallet "Jack" hasn't been used yet doesn't mean it is a safe brainwallet. When you would deposit some coins into the attached address you can be sure they will be stolen within the blink of an eye.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 28, 2018, 06:03:33 AM
Bumping this thread as I am also doing something similar, and plan to publish my results to increase awareness of the risk of using sha256 brainwallets.
Thanks for bumping. I kind of felt there was not much interest in this before as I expected to get a lot more responses to the list I published. Publishing the results including proof cost me quite some time. But good to see another person with the same interest :)

Yes, I can see you've spent some time collecting the data and making a nice interface to present it. Perhaps you should make a way for people to leave comments? For example, to link to a thread discussing that specific brainwallet. I'm thinking about approaching this from another perspective, making a website that displays (well known) passphrases to show how basic some of them are, and how quickly funds sent to those addresses were swept away. May even try sending small amounts to a few of them (like ryanc did live in one of his presentations) to demonstrate that the funds will be stolen within literally seconds.

Obviously, I need to do this in a way that makes it obvious how insecure passphrase brainwallets are, but without making it seem too easy for a would-be thief. (To make it clear: it's NOT easy, and I'd say that in 2018 we'd be beyond the point of diminishing returns.)

I think your results share a lot of findings in my set. I am very much interested in the ones you found so I can update my list with the ones I missed. Any chance you can share your findings? (a list of found words/sentences you found would be enough)

Still collecting, but I'll share at a later date. I forgot to mention that I'm also including Litecoin and Dogecoin, so some of those keys would not be for Bitcoin.

The funds were swept out instantly, which strongly suggests it was a theft by a bot watching that privkey. The passphrase is a song title, wit
Yes, there are a couple of bots active which monitor the mempool (using a modified bitcoind client) for incoming transactions. Each address found is then matched against a very large set of addresses composed on all kinds of brainwallets. In other words: Just because the brainwallet "Jack" hasn't been used yet doesn't mean it is a safe brainwallet. When you would deposit some coins into the attached address you can be sure they will be stolen within the blink of an eye.

Yes, I think that's a point that some people will struggle to grasp, that the very first time they use their new brainwallet phrase the funds could be stolen instantly. And also that brainwallet thieves are not focussing on cracking any specific address; the method of cracking will find ANY insecure wallet. So both these arguments fail:

- I'm the only one who knows my passphrase
- No one cares enough about me to try hacking my wallet

This comment on Hacker News from the owner of 1brain... may provide some insight:

https://news.ycombinator.com/item?id=7368283

(That was the only thing that account posted on HN. No one ever replied to that comment.)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 06, 2018, 01:39:53 AM
Things were getting a bit boring because my system was only finding one or two new wallets per day, but today it suddenly found about 30 new ones.

Here's another (relatively) recent transaction, which was swept out immediately:

https://www.blockchain.com/btc/address/15jG7moSaWgQADbG45cbvc79sHjKBBnxBk

Alternate block explorer showing double spend attempts within the same couple of seconds:

https://bitaps.com/15jG7moSaWgQADbG45cbvc79sHjKBBnxBk

Nearly 1 BTC is not a small amount. Back then it was worth around $15k USD

Password is "letthegoodtimesroll"

---

This one lasted a bit longer, and uses a non english phrase that doesn't appear in my password lists or haveibeenpwned (so I won't reveal it here) : https://www.blockchain.com/btc/address/1AsUMTvY4bRXKXrFZ1tbQ8xi1Lz3DiBNHt

Hopefully the transfer out was by the rightful owner.

---

Some of these brainwallet funding transactions have multiple outputs, often with one large output (change?), so I suspect they're withdrawals from an exchange, and people are sending to this cool wallet thing they can generate safely without needing to install any software........

Don't use SHA256 brainwallets!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: anthonytcm on October 06, 2018, 10:22:08 PM
Hi,

As been discussed many times before using a Brainwallet is a bad idea. I ran some test myself and found 18.509 BTC-addresses based on a brainwallet which also has been used in the blockchain before.

I tried to compare my results with the results of other researchers but could not find any lists online at all. I found some examples but not a comprehensive list. So I published my own results over here: https://eli5.eu/brainwallet

Please note: all published addresses have a balance of 0 so this is not a list for robbers :). There are also a lot of extra datasets I haven't used this far so I expect the numbers to go up once I use them as well (I'm in the middle of perfecting my own tooling and blockchain parser so this will take some more time first).

I love to get some feedback and if you have results to share which I missed in this round I'm more than happy to hear from you and include them.

TA

I went through it and though I don't understand the specifics of how you did it, I am amazed at your findings! Thanks for sharing this!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on October 07, 2018, 09:55:42 AM
Alternate block explorer showing double spend attempts within the same couple of seconds:

https://bitaps.com/15jG7moSaWgQADbG45cbvc79sHjKBBnxBk

Nearly 1 BTC is not a small amount. Back then it was worth around $15k USD

Password is "letthegoodtimesroll"

This is crazy. Within 2 seconds of the Bitcoin being deposited to that address, 3 different people/bots tried to steal it, and 1 was successful. 1 of the failed attempts was to send it to this address:

https://bitaps.com/1GGctqw9UeUd2vUFRdz5fUvHQnmxAEiTAK

Every single one of the 104 transactions to this address is trying to empty another address within a second or two of a deposit being made. A lot of them are unsuccessful due to the funds being cleared by someone else first, but this address has still managed to steal 0.166 BTC. What's worse is you can look at pretty much any of those transactions and see two or three more addresses trying the exact same thing, all with their own extensive histories of clearing out other addresses within seconds a transaction being made.

If ever there was an argument against using a brain wallet, this is it. Your BTC will be stolen before you've even refreshed your browser and seen that your transaction has been confirmed.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 07, 2018, 11:08:02 AM
What's worse is you can look at pretty much any of those transactions and see two or three more addresses trying the exact same thing, all with their own extensive histories of clearing out other addresses within seconds a transaction being made.

Hmm, that gives me an idea. It should be possible to do some basic (automated) analysis on brainwallet transactions, to find common theft destination addresses (such as https://www.blockchain.com/btc/address/1brain7kAZxPagLt2HRLxqyc3VgGSa1GR ) and then work back a level or two to find other potential compromised wallets. This may help flag wallets which were not instantly cleaned out - which is a red flag for sure - but where funds ultimately ended up at the same address as the more blatant thefts.

If ever there was an argument against using a brain wallet, this is it. Your BTC will be stolen before you've even refreshed your browser and seen that your transaction has been confirmed.

I'd say most of the people still using a brain wallet are simply not tech savvy, and see it as a low friction solution for storing their funds. No software is necessary, nor do you need to write down or print out any weird codes.

I've done Google searches for some of the plausible real brainwallets (ie not just dust intending to be found as a challenge) and often the only results are block explorer pages; no specific mention of a theft. Could it be that these non tech savvy users don't know who (or where) to ask about the theft, at least in a public forum, and so simply move on?

I suspect that in the past, and possibly even now, some services such as exchanges, block explorers, and online wallets offer a feature to withdraw directly to a brain wallet. What could be easier than storing your funds "in a password"?

Here's an article from 2013 which shows bots were active even back then: http://cointext.com/2013/11/04/brain-wallet-thefts-increasing/


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on October 07, 2018, 11:20:55 AM
I'd say most of the people still using a brain wallet are simply not tech savvy, and see it as a low friction solution for storing their funds. No software is necessary, nor do you need to write down or print out any weird codes.

Hell, even people who supposedly are "tech savvy" are using brain wallets. You see them advocated for all the time on these forums. McAfee's latest hardware wallet scam turned out to be a glorified brain wallet. It's no excuse though really - if you can figure out how to buy and transfer bitcoin, you know how to install an app on your phone and use a mobile wallet as a bare minimum. Sure it's not the best, but it's 1000x better than a brain wallet.

Brain wallets are for the brainless.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on October 07, 2018, 11:24:19 AM
Hmm, that gives me an idea. It should be possible to do some basic (automated) analysis on brainwallet transactions, to find common theft destination addresses (such as https://www.blockchain.com/btc/address/1brain7kAZxPagLt2HRLxqyc3VgGSa1GR ) and then work back a level or two to find other potential compromised wallets. This may help flag wallets which were not instantly cleaned out - which is a red flag for sure - but where funds ultimately ended up at the same address as the more blatant thefts.
I have/had the same idea. Let me know if you're going to work on this. Otherwise I will pick it up. I already have all btc transactions in a database so I guess I already have the right tool in place. Now all I need is (more) time :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 07, 2018, 01:22:46 PM
I'd say most of the people still using a brain wallet are simply not tech savvy, and see it as a low friction solution for storing their funds. No software is necessary, nor do you need to write down or print out any weird codes.

Hell, even people who supposedly are "tech savvy" are using brain wallets. You see them advocated for all the time on these forums. McAfee's latest hardware wallet scam turned out to be a glorified brain wallet. It's no excuse though really - if you can figure out how to buy and transfer bitcoin, you know how to install an app on your phone and use a mobile wallet as a bare minimum. Sure it's not the best, but it's 1000x better than a brain wallet.

Yeah, but the term "brain wallet" is fairly broad. We're really only discussing simple privkey = sha256("user chosen passphrase") type wallets in this thread; I've probably failed to make that important distinction when writing my own replies. Brain wallets which use a passphrase generated by a computer, representing a cryptographically strong random private key expressed in text form, are on a completely different level. Even a key-stretched user-entered passphrase with salt is significantly more secure. It's a pity that the same term continues to be used for these more secure methods, because it probably gives some credence to the original wildly insecure version.

Hmm, that gives me an idea. It should be possible to do some basic (automated) analysis on brainwallet transactions, to find common theft destination addresses (such as https://www.blockchain.com/btc/address/1brain7kAZxPagLt2HRLxqyc3VgGSa1GR ) and then work back a level or two to find other potential compromised wallets. This may help flag wallets which were not instantly cleaned out - which is a red flag for sure - but where funds ultimately ended up at the same address as the more blatant thefts.
I have/had the same idea. Let me know if you're going to work on this. Otherwise I will pick it up. I already have all btc transactions in a database so I guess I already have the right tool in place. Now all I need is (more) time :)

Yeah, I know what you mean about time. I've been spending a disproportionate amount of time on this, and also some cash (had to buy some extra HDs, and rent some server space). I'm probably at the point where I've grabbed most of the low hanging fruit by now, so to be honest, the buzz from finding a new (and good) passphrase and being able to trace the wallet's history is wearing off. Although it is interesting to come up with new data sources, and think about how to manipulate them into forms that may represent passphrases. Some of the user-entered data I've collected from websites I run, which have nothing to do with cryptocurrency or infosec, have resulted in SHA256 brainwallet hits.

I'm still trying to understand why someone would do this for money. Maybe in 2013 it may have worked, but these days the investment in effort (custom coding) and equipment (storage, virtual CPUs for cracking) seems to outweigh any potential benefit. Perhaps it's a criminal ego thing.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on October 07, 2018, 04:37:14 PM
Oh for sure, but as I've mentioned before, the human brain is completely fragile. With no way to back up or recover data, and all it takes is a minor blow to make you forget you even have passphrase, let alone what it is.

Even if your brain wallet is more secure than a simple song lyric or something equally stupid, it's still a bad choice for storing your coins.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 08, 2018, 07:24:55 AM
Oh for sure, but as I've mentioned before, the human brain is completely fragile. With no way to back up or recover data, and all it takes is a minor blow to make you forget you even have passphrase, let alone what it is.

Even if your brain wallet is more secure than a simple song lyric or something equally stupid, it's still a bad choice for storing your coins.

But, but... this website says I can withdraw to a password.  :D

(Some of the still-existing SHA256 brainwallet generator sites do not make it clear just how risky choosing to use/continue using that type of wallet is. I'd say they're partially to blame for the more recent thefts.)

---

This is an interesting slide I came across, showing a visual depiction of the 4 digit PIN space, when chosen by humans:

https://i.imgur.com/EPC64ET.png

I can see a few obvious patterns:

1. 1234 is a popular PIN. 4321 is also up there.
2. 69 is a popular part of a PIN.
3. Repeated double digit sequences are common, eg 1717 or 6969 (the latter appears to be the most popular repeated sequence)
4. 19xx and 20xx are popular; perhaps the year of birth of the card owner, or their offspring.

I'm not sure if it would be possible to represent SHA256 brainwallets in a similar visual way, but it would be interesting if there were some way to map phrases to a two or three dimensional space.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on October 08, 2018, 10:09:15 AM
-snip-

The darker "L" shaped region in the bottom left has an obvious cut off at 12, and also between 28-31, representing a significant portion of people use either DD/MM or MM/DD as a pin. I would wager the majority of these are probably their own date of birth.

Lots of number patterns are very obvious too - 2468, 2345, 5678, 9876, 2580/0852 (straight down/up the middle of the keypad).

In short - people are bad at security.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 08, 2018, 10:47:52 AM
My system just found this wallet:

https://www.blockchain.com/btc/address/17EzdiY1PT1okKj9wnUx8a4eCXaddhgfgR

Another recent transaction, although not an immediate sweep, so hopefully not a theft. (The password is not listed in Google or haveibeenpwned.)

The funding transaction has lots of small outputs, and one large output, so I suspect this is the hot wallet of an exchange or similar payment service. Really scary that people are still making new SHA256 brain wallets. I wonder if this exchange offers that option?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 15, 2018, 03:20:15 PM
This one seems to be just for fun:

"i killed the bank"

https://www.blockchain.com/btc/address/14GZ9Azv3bQqHv2pPDvyezAgHDJ7m1y9aJ

Funded with 1 Satoshi in 2012. (The transaction fee was 50000 Satoshis. 8) )

This tiny balance was cleared out in 2015, along with the funds from at least one other brainwallet.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 15, 2018, 03:49:53 PM
Doing some quick back of the envelope calculations. Consider this a thought experiment rather than anything too accurate.

My server with a 2010 era quad core CPU can check about 300,000 keys per second. It could probably be pushed further with some tweaking.

Let's say (conservatively) that a more modern quad core CPU can do 500,000 and use that as the reference. That means it can check 43.2 billion keys per day.

Brute forcing the "correct horse battery staple" space

One dictionary that includes a rank of how commonly a word appears on the web ranks the least common word "staple" at 16904.

So let's use that hint (some mild cheating) and set our limits to the 20000 most common words.

Total keys to check (20000 x 20000 x 20000 x 20000) =
160 000 000 000 000 000
And a server can check this many keys in a day:
         43 200 000 000

So in this instance, we would need approximately 10,000 servers running for a year to brute force every combination of those 20000 words. Not practical, but certainly not impossible.

But what if we use only the most common 1000?

Total keys to check (1000 x 1000 x 1000 x 1000) =
     1 000 000 000 000
And a server can check this many keys in a day:
        43 200 000 000

In this case, we only need about 23 server days (one server running for 23 days, or 23 servers running for one day) to cover the space.

And if we try the top 500:

Total keys to check (500 x 500 x 500 x 500) =
        62 500 000 000
And a server can check this many keys in a day:
        43 200 000 000

Now a single server can cover the whole space in about one and a half days. That's actually (much) less time than to brute force a simple 6 character password.

I'm not suggesting that everyone's four-word-wallet can be cracked wide open in a day, but it does mean that low hanging fruit - think simple, common words - will be quickly found.

Blockchain+SHA256 brainwallets: the world's biggest encrypted password file...


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 27, 2018, 07:05:58 AM
I'm doing a writeup on why SHA256 brainwallets are bad, and I'm working on a list of particularly bad passphrase choices:

- Using a single dictionary word. [Funds will be stolen instantly.]
- Using two to four dictionary words in sequence, such as the famous example "correct horse battery staple". [This does not imply that five or more words is necessarily secure.]
- Basing your passphrase on a pop culture reference, such as a quote from a movie, or a meme, or song lyrics.
- Repeating a dictionary word (or common string such as "123456789") multiple times to form a longer passphrase.
- Preprending or appending a few extra letters, numbers, or other characters, to the passphrase.
- Converting certain letters to form l33t speak (eg "hello" -> "h3ll0").
- Typing a sentence, or short sequence of random dictionary words, without spaces.
- Repeating a simple sequence of characters to form a longer passphrase.
- Any patterns related to keyboard layout, such as "qwerty" or "qazwsx".
- Part or all of a well known number, such as Pi, or the speed of light.


Any other suggestions?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ebliever on October 27, 2018, 03:51:49 PM
I wonder, is there any way to estimate the % of brainwallets (either by number of accounts created or amount of funds deposited) that have been compromised? This would take more than just blockchain research but I'm curious as to whether researchers have taken a stab at understanding just how bad use of brainwallets really has been. 1%, 10%, 90% lost?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 28, 2018, 02:58:30 AM
I wonder, is there any way to estimate the % of brainwallets (either by number of accounts created or amount of funds deposited) that have been compromised? This would take more than just blockchain research but I'm curious as to whether researchers have taken a stab at understanding just how bad use of brainwallets really has been. 1%, 10%, 90% lost?

There's really no way to know how many SHA256 (or similar type) brainwallets exist, because the public information (the address, and possibly public key) looks just as random as something generated by a more traditional wallet client. It's not until you crack the passphrase that you know it's a SHA256 brainwallet.

As I've surmised previously in the thread, I suspect that a lot of thefts do not go reported, publicly anyway, because the typical person who uses a SHA256 brainwallet is probably not very technically minded, and may not think to find a forum such as BCT where they can ask for help. Pride may also play a part. I imagine there's a fair few exchange support tickets asking about a withdraw that "didn't work".

I think that showing how funds can be stolen within literally seconds is a pretty powerful indicator of the potential risk of using a SHA256 brainwallet ... but those same non technically minded people may never find that information.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on November 08, 2018, 12:07:06 PM
I saw someone mentioned in an earlier thread that their SHA256 brainwallets were also swiped on testnet, so I just tried a test transaction, sending to 50 random dictionary words that also appear as SHA256 wallets in the main blockchain:

https://testnet.blockchain.info/tx/8956ca8164d08087627e42eb6895984ac4960e61af3a04983de5bd0edbd100e8

This block explorer shows spent outputs:

https://live.blockcypher.com/btc-testnet/tx/8956ca8164d08087627e42eb6895984ac4960e61af3a04983de5bd0edbd100e8/

As I write this, only a few minutes after sending, the only output which hasn't been spent appears to be the change (which is a random wallet generated key). All of the SHA256 derived keys were swept within seconds, just like the bots do on mainnet.

I was planning to write a very simple bot to demonstrate (on testnet) how quickly funds can be stolen, but it looks like I don't need to bother. Mine would have been a clunky hack that took five or ten minutes to sweep the funds back to the testnet faucet... but it seems there's already something more sophisticated listening in!

These are the words I sent to:

disparities
aggrandize
perfectionists
genuinely
creations
earthworms
intimidated
lengthened
conquered
decrementing
gianni
astronomer
inapproachable
sterilizations
interruption
insulation
nationalize
demographic
cocoana
retransmitted
ammunition
antagonize
vacationing
complexion
trickiness
housebroken
embarrassing
distraught
brownness
juxtaposing
trigonometry
pernicious
arrowhead
scratchers
tempestuously
pornographer
luxuriant
geometrical
inorganic
reinserting
refinement
approachable
screening
broadcasted
normalize
superposed
formulating
screenplay
cannibalizing
glorifies


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: aplistir on November 08, 2018, 12:28:16 PM
I saw someone mentioned in an earlier thread that their SHA256 brainwallets were also swiped on testnet, so I just tried a test transaction, sending to 50 random dictionary words that also appear as SHA256 wallets in the main blockchain:

As I write this, only a few minutes after sending, the only output which hasn't been spent appears to be the change (which is a random wallet generated key). All of the SHA256 derived keys were swept within seconds, just like the bots on mainnet.

I was planning to write a very simple bot to demonstrate (on testnet) how quickly funds can be stolen, but it looks like I don't need to bother. Mine would have been a clunky hack that took five or ten minutes to sweep the funds back to the testnet faucet... but it seems there's already something more sophisticated listening in!

LOL that is funny. Some criminal mastermind is trying to get rich by stealing testnet coins ::)
I have to try it out with my testnet coins.

Has anyone searched brainwallet addresses with those same words, but doing the sha256 more than once? Would be interesting to know how many addresses have been made with 2*sha256, or 4*sha256










Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on November 08, 2018, 12:39:35 PM
LOL that is funny. Some criminal mastermind is trying to get rich by stealing testnet coins ::)
I have to try it out with my testnet coins.

I guess that's the best way to confirm your bot works. Wouldn't be surprised if some of the funds sent to those addresses (and maybe even their mainnet counterparts) originated from the wallets of the bot authors.

I had a quick look at a few of the destination addresses and did note that one transaction sends everything to an address which has been reused multiple times, whereas the others use newly created addresses. So just like mainnet, it's possible there's two or more bots competing in order to sweep the funds first.

Has anyone searched brainwallet addresses with those same words, but doing the sha256 more than once? Would be interesting to know how many addresses have been made with 2*sha256, or 4*sha256

I did some basic dictionary checks and only found a few results (on mainnet) :

hello (4 rounds)
sender (2 rounds)
receiver (2 rounds)
my property (2 rounds)
dupa (1000 rounds)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on November 18, 2018, 02:56:21 PM
Doing some research on other networks, it turns out there are four SHA256 brainwallet passphrases (those that I know of) which are common to all 3 of the Bitcoin, Litecoin, and Dogecoin blockchains. The first two are no surprise:

1. <empty string>
2. correct horse battery staple

But the remaining two are odd:

3. 16fawJbgd3hgn1vbCb66o8Hx4rn8fWzFfG
4. 16fawJbgd3hgn1vbCb66o8Hx4rn8fWzFfG11

16fawJbgd3hgn1vbCb66o8Hx4rn8fWzFfG is a valid Bitcoin address that has been used, it appears in the "sending to sha256 of blockchain data" pastebin, and is tagged "xsimple" on blockchain: https://www.blockchain.com/btc/address/16fawJbgd3hgn1vbCb66o8Hx4rn8fWzFfG

As a SHA256 brainwallet passphrase on the Bitcoin blockchain it's not that odd - it's one of many - but why is that passphrase also being used for Dogecoin and Litecoin? And what does xsimple mean?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on November 18, 2018, 09:22:44 PM
If anything, this thread shows definitively that no brain wallet based on any kind of memorized passphrase is safe.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on November 18, 2018, 09:31:09 PM
I'm doing a writeup on why SHA256 brainwallets are bad, and I'm working on a list of particularly bad passphrase choices:
...
Any other suggestions?

The standard brain wallet is generated by hashing a passphrase with SHA-256, but I wonder if there are private keys generated by using other hashes. Running a your search-space through RIPEMD-160 followed by one or more SHA-256 passes might generate some hits. I have no doubts that running your search-space through scrypt will generate some hits on Litecoin and its derivatives.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on November 19, 2018, 08:29:34 PM
The standard brain wallet is generated by hashing a passphrase with SHA-256, but I wonder if there are private keys generated by using other hashes. Running a your search-space through RIPEMD-160 followed by one or more SHA-256 passes might generate some hits. I have no doubts that running your search-space through scrypt will generate some hits on Litecoin and its derivatives.

I did do some basic testing using the default hash suite available in a standard PHP install. From memory, I found a few hits for key = sha256(md5(string)) hashes.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on December 30, 2018, 05:17:43 PM
My system is still finding the occasional SHA256 brainwallet. This wallet stands out because it held 1.7 BTC for nearly 4 years, until being emptied in February 2018:

https://www.blockchain.com/btc/address/00790d4c5ec89c0e30e1343a2eafc901ee136e9b

The equivalent balance on the Bitcoin Cash chain was also transferred out.

A substantial amount to have sitting in a SHA256 brainwallet through the bubble of 2017/2018. Hopefully the transfer was done by the rightful owner. Maybe cashing out as the downward spiral started?

The passphrase is "Thats what she said 1974"



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on December 31, 2018, 12:06:14 AM
The passphrase is "Thats what she said 1974"

I'm curious about how you came up with that phrase. Are you going through permutations of dictionary words (and years) or do you have a database of phrases and quotes, or something else?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on January 01, 2019, 05:25:36 AM
The passphrase is "Thats what she said 1974"

I'm curious about how you came up with that phrase. Are you going through permutations of dictionary words (and years) or do you have a database of phrases and quotes, or something else?

I've come up with various methods to generate candidate passphrases. In this instance, it was prepending and/or appending common password substrings such as "qwerty", "1234", years etc to a set of common phrases. Basically building all possible phrases from the contents of two distinct dictionaries.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on January 01, 2019, 10:51:33 AM
My system is still finding the occasional SHA256 brainwallet. This wallet stands out because it held 1.7 BTC for nearly 4 years, until being emptied in February 2018:

https://www.blockchain.com/btc/address/00790d4c5ec89c0e30e1343a2eafc901ee136e9b

The equivalent balance on the Bitcoin Cash chain was also transferred out.

A substantial amount to have sitting in a SHA256 brainwallet through the bubble of 2017/2018. Hopefully the transfer was done by the rightful owner. Maybe cashing out as the downward spiral started?

The passphrase is "Thats what she said 1974"

It's pretty much a miracle that a passphrase like this went untouched for nearly 4 years.

Looking at how both the BTC and the BCH transaction where made in parallel within minutes, forwarding the coins to identical addresses on both chains, I get a feeling that automation may have been in play though -- the kind of automation that scans for brainwallets and steals them, unfortunately.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on January 28, 2019, 03:28:31 PM
Another odd one which was swept last month:

https://www.blockchain.com/btc/address/45990fb9a0434d35607320d7b501938ea70f01c4

The password is the ultra-simple dictionary word "turn", so it's not surprising that it was stolen within minutes, however, 0.02854667 BTC is not exactly an amount you'd send just for fun. Perhaps it was someone new to BTC, who bought $100 worth, then withdrew to a "password protected" wallet without understanding what that meant.

Local wallet protected with password "turn" -> Despite password being incredibly weak, funds are still fairly secure.

SHA256 brainwallet protected with password "turn" -> Gone in 60 seconds.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: o_e_l_e_o on January 28, 2019, 03:43:12 PM
The password is the ultra-simple dictionary word "turn", so it's not surprising that it was stolen within minutes
Interesting that "turn" is one of the 2048 BIP39 words. Wonder if someone got hopelessly confused between passwords and mnemonic seeds? Or if it's just really bad security and purely a coincidence?

Have you checked all the other BIP39 words at any point? Is there a pattern at all?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on January 29, 2019, 12:13:02 AM
The password is the ultra-simple dictionary word "turn", so it's not surprising that it was stolen within minutes
Interesting that "turn" is one of the 2048 BIP39 words. Wonder if someone got hopelessly confused between passwords and mnemonic seeds? Or if it's just really bad security and purely a coincidence?

Have you checked all the other BIP39 words at any point? Is there a pattern at all?

I have specifically checked BIP39, but since they're so simple the words are also covered by other databases, such as dictionary (web words, wikipedia words) and also 5 letter combos.

I personally think that someone misunderstood the difference between (local) wallet passwords, and SHA256 passwords, but we'll probably never know. It's a pity we can only speculate.

This is the only dictionary word I can recall that's had an appreciable amount sent to it. Everything else is just dust.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on January 29, 2019, 12:18:51 AM
I personally think that someone misunderstood the difference between (local) wallet passwords, and SHA256 passwords [...]

This is the only dictionary word I can recall that's had an appreciable amount sent to it. Everything else is just dust.

Hmm, maybe not. I've just found another $100(ish) transaction, and given that it was sent to the "toy" key 23 hex, it seems to be deliberate.

https://www.blockchain.com/btc/address/82e2f248afe732a2e5973600ca97a61fe3d240fd

Private key: 0000000000000000000000000000000000000000000000000000000000000023

Swept immediately, of course.

Another toy key (0000000000000000000000000000000000000000000000000000000000000d56) with not insignificant amounts recently sent to it: https://www.blockchain.com/btc/address/da681e4e2cd40b6ba6b1f6b4844b10219c7204b5


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on February 06, 2019, 12:11:02 PM
I have been running some scans like this I grabbed about 2TB of word lists for brain wallet hunting.

At the moment it is currently syncing up with bitcoin-abe into mysql database (taking forever)

I wrote a small python script to create seeds that can be piped into a seed checker as such.

Code:
import random

filename = "YourWordList.txt"

def main(filename):
    words_file = open(filename, 'r')
    words = words_file.read().split("\n")
    temp_words = []
    for word in words:
        temp_words.append(word.strip("\r"))
    words = temp_words

    while True:
        length = int(raw_input("12:"))
        for i in range(0,length):
            print(words[random.randrange(0,len(words)+1)]),
        print("\n")


if __name__ == "__main__":
    main(filename)

Still buggy welcome any adaptation  ;)

Code:

Output
12:12
twist flush ranch screen yard film option walk stuff sick maximum stumble

12:12
ill banner replace snack athlete wage patient right sell bicycle meadow weekend

12:12
knock include learn fruit video drama sort crunch cost people undo inherit

12:12
close symbol either voyage cool life obtain enemy valve process consider project

12:12
fish tube lunar among adjust inch transfer slight evil tell apology negative

12:12
host century basket drift scatter raven job carbon excite gym biology hospital

12:12
soup verify mouse whisper weather resource upon  lens slim consider celery

12:12
farm gold useless area renew settle until soap rent attract unique ceiling

12:12
code stage dad two brick clock gospel voice easily impose grunt cry

12:12
roast garment board wise fabric bus bundle idea street asthma horse language


I have also been piping in random text like such

Code:
1xjPr0ta5PsTrKTlETa3
ay9RDUrEhjdkNX6ynm8V
GsAupTvPwo3t0875dsBF
LCHaTQYseeu833Wrs3eu
53fCknZ7XGn2CSpDhLVV
jX8Tex8rafMjEsQTmY9S
yuOEOXF0JzYc0TmB4R36
MolQV7IKX15RSSo4s7OM
ZoKMjxUvV5QwTL8ZdCRo
9YLZNaUklLxx6rCwyQKg
lekYEIMpEhkPlnFw32bk
W7meYuwMyrJtnsL3biLH
8z1FKk39xpPtzzLmtdeQ

No results yet from random data.

From text word lists I have found around 500+ empty brain wallets so far most of which have already been published in the list.

I have been collecting hash160 addresses from the blockchain and have them in a bloom filter searching against the word list but still no results with a small sample space of hash160 at the moment.

I have also been testing with random hex being pushed to the brain wallet.

Code:
//using namespace std;
int main(int argc, char *argv[]) {
 srand(time(NULL));
 bool risky_mode = false;
 bool even_only = false;
 bool odd_only = false;
 bool output_random = false;
 bool use_lower = false;
 bool use_upper = false;
 bool use_len_8 = false;
 bool use_len_9 = false;
 bool no_0 = false;
 bool no_1 = false;
 int desired_uniques = 0;
 int min_uniques = 6; // 94.6% chance of having 6 to 9 uniques
 int max_uniques = 9;
 int min_numbers = 4; // 94.02% chance of having 4 to 8 numbers
 int max_numbers = 8;
 int min_letters = 2; // 94.02% chance of having 2 to 6 letters
 int max_letters = 6;
 bool negate_sequential = true; // 89.8% chance of not having any 3 consecutive sequential chars (123) or reverse sequential chars (321)
 int differential = 0;
 int slot1_start_at = 0;
 int slot1_stop_at = 0;
 bool starts_with_letter = false;
 bool make_next_start_at = false;
 bool make_next_stop_at = false;
 int make_next_start_at_cnt = 0;
 int make_next_stop_at_cnt = 0;
 unsigned long long int start_at_long = 0;
 unsigned long long int stop_at_long = 0;
 if (argc > 1) {
  for (int i=1;i<argc;++i) {
   if (stricmp(argv[i], "-risky") == 0) { risky_mode = true; }
   if (stricmp(argv[i], "-evenonly") == 0) { even_only = true; }
   if (stricmp(argv[i], "-oddonly") == 0) { odd_only = true; }
   if (stricmp(argv[i], "-random") == 0) { output_random = true; }
   if (stricmp(argv[i], "-lower") == 0) { use_lower = true; }
   if (stricmp(argv[i], "-upper") == 0) { use_upper = true; }
   if (stricmp(argv[i], "-len8") == 0) { use_len_8 = true; }
   if (stricmp(argv[i], "-len9") == 0) { use_len_9 = true; }
   if (stricmp(argv[i], "-no0") == 0) { no_0 = true; }
   if (stricmp(argv[i], "-no1") == 0) { no_1 = true; }
   if (stricmp(argv[i], "-no01") == 0) { no_0 = true; no_1 = true; }
   if (stricmp(argv[i], "-no10") == 0) { no_0 = true; no_1 = true; }
   if (stricmp(argv[i], "-1unique") == 0) { desired_uniques = min_uniques = max_uniques = 1; }
   if (stricmp(argv[i], "-2uniques") == 0) { desired_uniques = min_uniques = max_uniques = 2; }
   if (stricmp(argv[i], "-3uniques") == 0) { desired_uniques = min_uniques = max_uniques = 3; }
   if (stricmp(argv[i], "-4uniques") == 0) { desired_uniques = min_uniques = max_uniques = 4; }
   if (stricmp(argv[i], "-5uniques") == 0) { desired_uniques = min_uniques = max_uniques = 5; }
   if (stricmp(argv[i], "-6uniques") == 0) { desired_uniques = min_uniques = max_uniques = 6; }
   if (stricmp(argv[i], "-7uniques") == 0) { desired_uniques = min_uniques = max_uniques = 7; }
   if (stricmp(argv[i], "-8uniques") == 0) { desired_uniques = min_uniques = max_uniques = 8; }
   if (stricmp(argv[i], "-9uniques") == 0) { desired_uniques = min_uniques = max_uniques = 9; }
   if (stricmp(argv[i], "-10uniques") == 0) { desired_uniques = min_uniques = max_uniques = 10; }
   if (stricmp(argv[i], "-1minunique") == 0) { min_uniques = 1; }  if (stricmp(argv[i], "-minunique1") == 0) { min_uniques = 1; }  if (stricmp(argv[i], "-min1unique") == 0) { min_uniques = 1; }
   if (stricmp(argv[i], "-2minuniques") == 0) { min_uniques = 2; } if (stricmp(argv[i], "-minuniques2") == 0) { min_uniques = 2; } if (stricmp(argv[i], "-min2uniques") == 0) { min_uniques = 2; }
   if (stricmp(argv[i], "-3minuniques") == 0) { min_uniques = 3; } if (stricmp(argv[i], "-minuniques3") == 0) { min_uniques = 3; } if (stricmp(argv[i], "-min3uniques") == 0) { min_uniques = 3; }
   if (stricmp(argv[i], "-4minuniques") == 0) { min_uniques = 4; } if (stricmp(argv[i], "-minuniques4") == 0) { min_uniques = 4; } if (stricmp(argv[i], "-min4uniques") == 0) { min_uniques = 4; }
   if (stricmp(argv[i], "-5minuniques") == 0) { min_uniques = 5; } if (stricmp(argv[i], "-minuniques5") == 0) { min_uniques = 5; } if (stricmp(argv[i], "-min5uniques") == 0) { min_uniques = 5; }
   if (stricmp(argv[i], "-6minuniques") == 0) { min_uniques = 6; } if (stricmp(argv[i], "-minuniques6") == 0) { min_uniques = 6; } if (stricmp(argv[i], "-min6uniques") == 0) { min_uniques = 6; }
   if (stricmp(argv[i], "-7minuniques") == 0) { min_uniques = 7; } if (stricmp(argv[i], "-minuniques7") == 0) { min_uniques = 7; } if (stricmp(argv[i], "-min7uniques") == 0) { min_uniques = 7; }
   if (stricmp(argv[i], "-8minuniques") == 0) { min_uniques = 8; } if (stricmp(argv[i], "-minuniques8") == 0) { min_uniques = 8; } if (stricmp(argv[i], "-min8uniques") == 0) { min_uniques = 8; }
   if (stricmp(argv[i], "-9minuniques") == 0) { min_uniques = 9; } if (stricmp(argv[i], "-minuniques9") == 0) { min_uniques = 9; } if (stricmp(argv[i], "-min9uniques") == 0) { min_uniques = 9; }
   if (stricmp(argv[i], "-10minuniques") == 0) { min_uniques = 10; } if (stricmp(argv[i], "-minuniques10") == 0) { min_uniques = 10; } if (stricmp(argv[i], "-min10uniques") == 0) { min_uniques = 10; }
   if (stricmp(argv[i], "-1maxunique") == 0) { max_uniques = 1; }  if (stricmp(argv[i], "-maxunique1") == 0) { max_uniques = 1; }  if (stricmp(argv[i], "-max1unique") == 0) { max_uniques = 1; }
   if (stricmp(argv[i], "-2maxuniques") == 0) { max_uniques = 2; } if (stricmp(argv[i], "-maxuniques2") == 0) { max_uniques = 2; } if (stricmp(argv[i], "-max2uniques") == 0) { max_uniques = 2; }
   if (stricmp(argv[i], "-3maxuniques") == 0) { max_uniques = 3; } if (stricmp(argv[i], "-maxuniques3") == 0) { max_uniques = 3; } if (stricmp(argv[i], "-max3uniques") == 0) { max_uniques = 3; }
   if (stricmp(argv[i], "-4maxuniques") == 0) { max_uniques = 4; } if (stricmp(argv[i], "-maxuniques4") == 0) { max_uniques = 4; } if (stricmp(argv[i], "-max4uniques") == 0) { max_uniques = 4; }
   if (stricmp(argv[i], "-5maxuniques") == 0) { max_uniques = 5; } if (stricmp(argv[i], "-maxuniques5") == 0) { max_uniques = 5; } if (stricmp(argv[i], "-max5uniques") == 0) { max_uniques = 5; }
   if (stricmp(argv[i], "-6maxuniques") == 0) { max_uniques = 6; } if (stricmp(argv[i], "-maxuniques6") == 0) { max_uniques = 6; } if (stricmp(argv[i], "-max6uniques") == 0) { max_uniques = 6; }
   if (stricmp(argv[i], "-7maxuniques") == 0) { max_uniques = 7; } if (stricmp(argv[i], "-maxuniques7") == 0) { max_uniques = 7; } if (stricmp(argv[i], "-max7uniques") == 0) { max_uniques = 7; }
   if (stricmp(argv[i], "-8maxuniques") == 0) { max_uniques = 8; } if (stricmp(argv[i], "-maxuniques8") == 0) { max_uniques = 8; } if (stricmp(argv[i], "-max8uniques") == 0) { max_uniques = 8; }
   if (stricmp(argv[i], "-9maxuniques") == 0) { max_uniques = 9; } if (stricmp(argv[i], "-maxuniques9") == 0) { max_uniques = 9; } if (stricmp(argv[i], "-max9uniques") == 0) { max_uniques = 9; }
   if (stricmp(argv[i], "-10maxuniques") == 0) { max_uniques = 10; } if (stricmp(argv[i], "-maxuniques10") == 0) { max_uniques = 10; } if (stricmp(argv[i], "-max10uniques") == 0) { max_uniques = 10; }
   if (stricmp(argv[i], "-startswith0") == 0) { slot1_start_at = 0; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith1") == 0) { slot1_start_at = 1; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith2") == 0) { slot1_start_at = 2; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith3") == 0) { slot1_start_at = 3; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith4") == 0) { slot1_start_at = 4; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith5") == 0) { slot1_start_at = 5; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith6") == 0) { slot1_start_at = 6; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith7") == 0) { slot1_start_at = 7; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith8") == 0) { slot1_start_at = 8; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswith9") == 0) { slot1_start_at = 9; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswithA") == 0) { slot1_start_at = 10; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswithB") == 0) { slot1_start_at = 11; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswithC") == 0) { slot1_start_at = 12; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswithD") == 0) { slot1_start_at = 13; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswithE") == 0) { slot1_start_at = 14; starts_with_letter = true; }
   if (stricmp(argv[i], "-startswithF") == 0) { slot1_start_at = 15; starts_with_letter = true; }
   if (stricmp(argv[i], "-start") == 0) { make_next_start_at = true; make_next_start_at_cnt = i; }
   if (stricmp(argv[i], "-stop") == 0) { make_next_stop_at = true; make_next_stop_at_cnt = i; }
   if ((make_next_start_at) && (i == (make_next_start_at_cnt+1))) { std::istringstream str_to_num(argv[i]); str_to_num >> start_at_long; if (!str_to_num) {std::cout << "ERROR: start is not a number" << "\n"; return 1;} make_next_start_at = false; }
   if ((make_next_stop_at) && (i == (make_next_stop_at_cnt+1))) { std::istringstream str_to_num(argv[i]); str_to_num >> stop_at_long; if (!str_to_num) {std::cout << "ERROR: stop is not a number" << "\n"; return 1;} make_next_stop_at = false; }
  }
 }

// ---------------------------------------------------
 // Number of combinations (10-length)
 // ---------------------------------------------------
 //  # of combos (10-length) = 1,099,511,627,776 (16^10) (13,194.14 GB)
 //  # of combos (10-length) with rules (6-9 uniques): 564,561,702,612 (51.3%) (6,774.74 GB)
 //  # of combos (10-length) with rules (10 uniques): 18,649,285,466 (1.7%) (223.79 GB)
 //  # of combos (10-length) with rules (09 uniques): 116,641,092,458 (10.6%) (1,399.69 GB)
 //  # of combos (10-length) with rules (08 uniques): 226,271,576,762 (20.6%) (2,715.26 GB)
 //  # of combos (10-length) with rules (07 uniques): 170,561,659,663 (15.5%) (2,046.74 GB)
 //  # of combos (10-length) with rules (06 uniques): 51,087,373,729 (4.6%) (613 GB)
 //  # of combos (10-length) with rules (05 uniques): 5,392,440,877 (0.5%) (64.7 GB)
 //  # of combos (10-length) with rules (04 uniques): 132,844,293 (0.012%) (1.59 GB)

 // ---------------------------------------------------
 // Number of combinations (10-length) (RISKY)
 // ---------------------------------------------------
 //  # of combos (10-length) = 1,099,511,627,776 (16^10) (13,194.14 GB)
 //  # of combos (10-length) with rules (6-9 uniques): 367,647,332,933 (33.4%) (4,411.8 GB)
 //  # of combos (10-length) with rules (10 uniques): 12,010,291,278 (1.1%) (144.1 GB)
 //  # of combos (10-length) with rules (09 uniques): 75,876,130,604 (6.9%) (910.5 GB)
 //  # of combos (10-length) with rules (08 uniques): 147,638,929,917 (13.4%) (1,771.7 GB)
 //  # of combos (10-length) with rules (07 uniques): 111,045,927,794 (10.1%) (1,332.6 GB)
 //  # of combos (10-length) with rules (06 uniques): 33,086,344,618 (3.0%) (397 GB)
 //  # of combos (10-length) with rules (05 uniques): 3,472,496,526 (0.31%) (41.7 GB)
 //  # of combos (10-length) with rules (04 uniques): 85,114,150 (0.008%) (1.02 GB)

instead of creating the lists I am piping the output of the scan direct to the scanner which save on the disk space some what.

I would like to hash some lists of words I have then pipe the input to the scanner what would be the best method of hashing large passwords lists to a specific hash output?

Thanks





 


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on February 06, 2019, 02:43:24 PM
where is admin, mod? Why topics like this can exist?

Security liabilities need to be discussed publicly, otherwise you have no basis for public discourse, awareness and improvement.

Note that this thread is about monitoring and documenting cases of brainwallet thefts, rather than stealing them.

While these thefts are happening regardless of whether threads like this exist, it may prevent some people from generating weak brainwallets and becoming victims themselves.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on February 06, 2019, 05:48:51 PM
so why have to write and post script here? Teach everybody do with him?

I don't think there's really been any great detail discussed in this thread. This is not a plug and play Docker image that any script kiddie can have running in 30 seconds. Although the basic premise is simple, building a system that can efficiently check trillions of potential passphrases against hundreds of millions of active addresses is not a trivial task, and it's become more difficult as the blockchain grows. I've spent many hours developing custom tools, a lot longer than I probably should have, but this is a hobby, not a criminal business.

If I was driven by something besides geeky curiosity I probably never would have bothered. This is unlikely to be profitable for a criminal. It's not 2015 any more.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on February 06, 2019, 06:13:43 PM

I wrote a small python script to create seeds that can be piped into a seed checker as such.

Output
12:12
twist flush ranch screen yard film option walk stuff sick maximum stumble
 

Hmm... what's the point of throwing randomly selected word sets at your address checker? The chances of matching a 12 word passphrase are essentially zero.

I think your size calcs may be off a bit, too. I pre-calculated the RMD160 values for all ASCII 1 to 5 character words, and the output is about 0.9TB in size. To increase to 6 characters would result in a file size about 95 times that (about 80TB) and to go up to 7 characters would result in an output of over 7000TB. And consider the amount of time needed to check 135 trillion entries.

That's one of the interesting things about SHA256 brainwallets (so long as you're doing this for fun) : it can be easy to find them, but it's also very, very hard. :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on February 06, 2019, 10:30:58 PM
I think your size calcs may be off a bit, too. I pre-calculated the RMD160 values for all ASCII 1 to 5 character words, and the output is about 0.9TB in size. To increase to 6 characters would result in a file size about 95 times that (about 80TB) and to go up to 7 characters would result in an output of over 7000TB. And consider the amount of time needed to check 135 trillion entries.

How long did it take you to generate a rainbow table of this size? I'm just curious about the timescale (so hardware specs for reference would also be nice).

Sorry in case you already mentioned it upthread and I overlooked it.


That's one of the interesting things about SHA256 brainwallets (so long as you're doing this for fun) : it can be easy to find them, but it's also very, very hard. :)

Stealing brainwallets is probably still profitable though, as I assume that the running costs are close to nil once you've set up the infrastructure.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on February 07, 2019, 03:06:14 AM
I think your size calcs may be off a bit, too. I pre-calculated the RMD160 values for all ASCII 1 to 5 character words, and the output is about 0.9TB in size. To increase to 6 characters would result in a file size about 95 times that (about 80TB) and to go up to 7 characters would result in an output of over 7000TB. And consider the amount of time needed to check 135 trillion entries.

How long did it take you to generate a rainbow table of this size? I'm just curious about the timescale (so hardware specs for reference would also be nice).

It took something like 3 weeks, on a leased 4 core Xeon server. Sorting and removing duplicates from 1TB+ of raw data presented some challenges.

Note that this table is not indexed in any way, it's just a text file with hashes. I use a custom filter program to check which of those precomputed hashes appear in a given blockchain. To go further and build a database that can watch for known addresses in real time would be quite a bit more complex, and would need a lot more than 0.9TB of disk space.

That's one of the interesting things about SHA256 brainwallets (so long as you're doing this for fun) : it can be easy to find them, but it's also very, very hard. :)

Stealing brainwallets is probably still profitable though, as I assume that the running costs are close to nil once you've set up the infrastructure.

I disagree, which is why I qualified my above statement with "so long as you're doing this for fun". Imagine how many things have to go right when someone sends funds to a weak SHA256 brainwallet:

- The thief needs a fast connection with multiple peers so that his bot (hopefully) sees the funding transaction first.
- The thief needs a fast database server that is able to check the outputs of each new transaction, and if any addresses are known, return a private key (or keys), within a very short period of time.
- The thief needs to decide how much of a fee to pay for the sweep transaction, bearing in mind that someone else's bot may choose a higher fee to override the transaction. (This could end up being a race to the bottom.)
- The thief then needs his sweep transaction to be the one that propagates out to the majority of nodes (and more specifically, mining nodes) first.

I've probably missed other factors. This is not the sort of thing you can run on a $5/mo VPS. I don't think it would be worth it, but as I've stated in this thread earlier, maybe it's an ego thing.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Effingham Hoofnagle on February 07, 2019, 03:59:56 AM
Seems like a waste of time to use random BIP words, as the seed word generation process involves checks, and many randomly generated combinations will be invalid.

Plus, even with a list of valid word combinations, it's a fools game in terms of odds.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on February 07, 2019, 05:50:41 AM
Plus, even with a list of valid word combinations, it's a fools game in terms of odds.

May as well just generate random private keys then. :)

Code:
// output random hex digits as a 256 bit priv key

#include <stdio.h>
#include <stdint.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/time.h>

uint64_t timeuseconds() {
        struct  timeval thistime;

        gettimeofday(&thistime, NULL);
        return((thistime.tv_sec * 1000000) + (thistime.tv_usec % 1000000));
}

int main() {

        int i;

        srandom(timeuseconds() );

        while (1)
        {
                for (i = 0; i < 16; i++)
                {
                        printf("%04lx", random() & 0xffff);
                }
                printf("\n");
        }
}

Although this program seems silly, it was done for a purpose: to check the false positive rate of brainflayer.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on February 07, 2019, 12:20:07 PM
Seems like a waste of time to use random BIP words, as the seed word generation process involves checks, and many randomly generated combinations will be invalid.

Plus, even with a list of valid word combinations, it's a fools game in terms of odds.


That may be the case but what about weak seeds I also think the use of the script below might be helpful?


Hmm... what's the point of throwing randomly selected word sets at your address checker? The chances of matching a 12 word passphrase are essentially zero.

I think your size calcs may be off a bit, too. I pre-calculated the RMD160 values for all ASCII 1 to 5 character words, and the output is about 0.9TB in size. To increase to 6 characters would result in a file size about 95 times that (about 80TB) and to go up to 7 characters would result in an output of over 7000TB. And consider the amount of time needed to check 135 trillion entries.

That's one of the interesting things about SHA256 brainwallets (so long as you're doing this for fun) : it can be easy to find them, but it's also very, very hard. :)

As for the tables sizes I think they are about right to be honest they are not hash160's they are raw hex combinations see below I have tested on the smaller value ones at the come out pretty close to the figures quoted.  So the DB for this type of data is vast.  

I am currently at around block 259090 of importing all the transactions into mysql database ( Currently 3 days reading from blk files)

Code:
Combination data from 10Hex  ./10hex | brainflayer -v -b example.blf 

https://github.com/wpatoolkit/10-Hex-Generator

010316ead1
010316ead2
010316ead3
010316ead4
010316ead5
010316ead6
010316ead7
010316ead8
010316ead9
010316eada
010316eadb
010316eadc
010316eadd
010316eade
010316eadf
010316eae0
010316eae1
010316eae2
010316eae3
010316eae4
010316eae5
010316eae6
010316eae7
010316eae8
010316eae9
010316eaea
010316eaeb
010316eaec
010316eaed
010316eaee
010316eaef
010316eaf0
010316eaf1
010316eaf2
010316eaf3
010316eaf4
010316eaf5
010316eaf6
010316eaf7
010316eaf8
010316eaf9
010316eafa
010316eafb
010316eafc
010316eafd
010316eafe
010316eaff
010316eb01
010316eb02
010316eb03
010316eb04
010316eb05
010316eb06
010316eb07
010316eb08
010316eb09
010316eb0a
010316eb0b
010316eb0c
010316eb0d
010316eb0e
010316eb0f
010316eb10


after setting up ABE it is far quicker at checking against the database for balance than my previous method of API calls to Blockchain.com

Code:
def mn_encode( message ):
    out = []
    for i in range(len(message)/8):
        word = message[8*i:8*i+8]
        x = int(word, 16)
        w1 = (x%n)
        w2 = ((x/n) + w1)%n
        w3 = ((x/n/n) + w2)%n
        out += [ words[w1], words[w2], words[w3] ]
    return out

def mn_decode( wlist ):
    out = ''
    for i in range(len(wlist)/3):
        word1, word2, word3 = wlist[3*i:3*i+3]
        w1 =  words.index(word1)
        w2 = (words.index(word2))%n
        w3 = (words.index(word3))%n
        x = w1 +n*((w2-w1)%n) +n*n*((w3-w2)%n)
        out += '%08x'%x
    return out

def stretch_key(seed):
    oldseed = seed
    for i in range(100000):
        seed = hashlib.sha256(seed + oldseed).digest()
        return string_to_number( seed )

def mpk_from_seed(seed):
    curve = SECP256k1
    secexp = stretch_key(seed)
    master_private_key = ecdsa.SigningKey.from_secret_exponent( secexp, curve = SECP256k1 )
    master_public_key = master_private_key.get_verifying_key().to_string().encode('hex')
    return master_public_key


class Account(object):
    def __init__(self, v):
        self.addresses = v.get('0', [])
        self.change = v.get('1', [])

    def dump(self):
        return {'0':self.addresses, '1':self.change}

    def get_addresses(self, for_change):
        return self.change[:] if for_change else self.addresses[:]

    def create_new_address(self, for_change):
        addresses = self.change if for_change else self.addresses
        n = len(addresses)
        address = self.get_address( for_change, n)
        addresses.append(address)
        return address

    def get_address(self, for_change, n):
        pass
        
    def get_pubkeys(self, sequence):
        return [ self.get_pubkey( *sequence )]
class OldAccount(Account):
    """  Privatekey(type,n) = Master_private_key + H(n|S|type)  """

    def __init__(self, v):
        self.addresses = v.get(0, [])
        self.change = v.get(1, [])
        self.mpk = v['mpk'].decode('hex')

    def dump(self):
        return {0:self.addresses, 1:self.change}

    @classmethod
    def mpk_from_seed(klass, seed):
        curve = SECP256k1
        secexp = klass.stretch_key(seed)
        master_private_key = ecdsa.SigningKey.from_secret_exponent( secexp, curve = SECP256k1 )
        master_public_key = master_private_key.get_verifying_key().to_string().encode('hex')
        return master_public_key

    @classmethod
    def stretch_key(self,seed):
        oldseed = seed
        for i in range(100000):
            seed = hashlib.sha256(seed + oldseed).digest()
        return string_to_number( seed )

    def get_sequence(self, for_change, n):
        return string_to_number( Hash( "%d:%d:"%(n,for_change) + self.mpk ) )

    def get_address(self, for_change, n):
        pubkey = self.get_pubkey(for_change, n)
        address = public_key_to_bc_address( pubkey.decode('hex') )
        return address

    def get_pubkey(self, for_change, n):
        curve = SECP256k1
        mpk = self.mpk
        z = self.get_sequence(for_change, n)
        master_public_key = ecdsa.VerifyingKey.from_string( mpk, curve = SECP256k1 )
        pubkey_point = master_public_key.pubkey.point + z*curve.generator
        public_key2 = ecdsa.VerifyingKey.from_public_point( pubkey_point, curve = SECP256k1 )
        return '04' + public_key2.to_string().encode('hex')

    def get_private_key_from_stretched_exponent(self, for_change, n, secexp):
        order = generator_secp256k1.order()
        secexp = ( secexp + self.get_sequence(for_change, n) ) % order
        pk = number_to_string( secexp, generator_secp256k1.order() )
        compressed = False
        return SecretToASecret( pk, compressed )
        
    def get_private_key(self, seed, sequence):
        for_change, n = sequence
        secexp = self.stretch_key(seed)
        return self.get_private_key_from_stretched_exponent(for_change, n, secexp)

    def check_seed(self, seed):
        curve = SECP256k1
        secexp = self.stretch_key(seed)
        master_private_key = ecdsa.SigningKey.from_secret_exponent( secexp, curve = SECP256k1 )
        master_public_key = master_private_key.get_verifying_key().to_string().encode('hex')
        if master_public_key != self.mpk:
            print_error('invalid password (mpk)')
            raise BaseException('Invalid password')
        return True

    def redeem_script(self, sequence):
        return None

def b58encode(v):
    """ encode v, which is a string of bytes, to base58."""

    long_value = 0L
    for (i, c) in enumerate(v[::-1]):
        long_value += (256**i) * ord(c)

    result = ''
    while long_value >= __b58base:
        div, mod = divmod(long_value, __b58base)
        result = __b58chars[mod] + result
        long_value = div
    result = __b58chars[long_value] + result

    # Bitcoin does a little leading-zero-compression:
    # leading 0-bytes in the input become leading-1s
    nPad = 0
    for c in v:
        if c == '\0': nPad += 1
        else: break

    return (__b58chars[0]*nPad) + result

def b58decode(v, length):
    """ decode v into a string of len bytes."""
    long_value = 0L
    for (i, c) in enumerate(v[::-1]):
        long_value += __b58chars.find(c) * (__b58base**i)

    result = ''
    while long_value >= 256:
        div, mod = divmod(long_value, 256)
        result = chr(mod) + result
        long_value = div
    result = chr(long_value) + result

    nPad = 0
    for c in v:
        if c == __b58chars[0]: nPad += 1
        else: break

    result = chr(0)*nPad + result
    if length is not None and len(result) != length:
        return None

    return result

__b58chars = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
__b58base = len(__b58chars)

def EncodeBase58Check(vchIn):
    hash = Hash(vchIn)
    return b58encode(vchIn + hash[0:4])

def DecodeBase58Check(psz):
    vchRet = b58decode(psz, None)
    key = vchRet[0:-4]
    csum = vchRet[-4:]
    hash = Hash(key)
    cs32 = hash[0:4]
    if cs32 != csum:
        return None
    else:
        return key
def public_key_to_bc_address(public_key):
    h160 = hash_160(public_key)
    return hash_160_to_bc_address(h160)
def hash_160(public_key):
    try:
        md = hashlib.new('ripemd160')
        md.update(hashlib.sha256(public_key).digest())
        return md.digest()
    except:
        import ripemd
        md = ripemd.new(hashlib.sha256(public_key).digest())
        return md.digest()
def hash_160_to_bc_address(h160, addrtype = 0):
    vh160 = chr(addrtype) + h160
    h = Hash(vh160)
    addr = vh160 + h[0:4]
    return b58encode(addr)
mnemonic_hash = lambda x: hmac_sha_512("Bitcoin mnemonic", x).encode('hex')
hmac_sha_512 = lambda x,y: hmac.new(x, y, hashlib.sha512).digest()
Hash = lambda x: hashlib.sha256(hashlib.sha256(x).digest()).digest()

def hack(t, d):
while True:
guess = random.sample(words,12)
#guess = "shirt always flat become bird company everytime poet least soar crack story".split()
#print guess
seed = mn_decode(guess)
mpk = OldAccount.mpk_from_seed(seed)
acc = OldAccount({'mpk':mpk, 0:[], 1:[]})
#pk = number_to_string( secexp, generator_secp256k1.order() )
#compressed = False
# SecretToASecret( pk, compressed )

addy = acc.create_new_address(False)
myurl = "http://localhost:2750/chain/Bitcoin/q/getreceivedbyaddress/" + addy

f = urllib.urlopen(myurl)
balance = f.read()
print balance + ": " + addy
if balance != "0":
with open("addresses.txt", "a+") as myfile:
myfile.write(balance + ": " + addy + "\t" + seed + "\n")


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on February 07, 2019, 12:35:25 PM
where is admin, mod? Why topics like this can exist?

Security liabilities need to be discussed publicly, otherwise you have no basis for public discourse, awareness and improvement.

Note that this thread is about monitoring and documenting cases of brainwallet thefts, rather than stealing them.

While these thefts are happening regardless of whether threads like this exist, it may prevent some people from generating weak brainwallets and becoming victims themselves.

so why have to write and post script here? Teach everybody do with him?

1. Most of this code is available online or on github as already said we do this to improve the security of bitcoin to help users understand about brain wallets and the dangers of them.
2. I feel it much better to see a community attempting to eradicate and document this by-design un-secure wallet.
3. Who would you rather be talking about this issue,  the open community who are pushing new users away from this dangerous way to store funds or the criminals behind closed forums scanning new users funds away.

I have a feeling this guy has a brain wallet :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on February 07, 2019, 01:34:27 PM
The tools are already out there.

You could argue publishing the result to be a issue but nothing I have posted is not already in the public domain.

https://www.youtube.com/watch?v=foil0hzl4Pg

A simple google search or github will show how many tools are out there for this type of thing.



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on February 07, 2019, 02:43:32 PM
i just ask why you have to write and post script here. Now anyone can use your script and scan brainwallets with you

Because simply closing your eyes to a problem won't make it go away.

Anyone willing and able to steal brainwallets won't need a thread like this to run their operation. Anyone lacking the skills and tools to steal brainwallets won't gain either from simply following a thread like this.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on February 19, 2019, 06:36:51 AM
I cache the blockchain API data. Just had a thought to delete the cached data for wallets which were previously showing (small) balances, and noticed that despite the almost nil value of each wallet, some have been cleaned out within the past few months. (A symbolic act? A researcher importing private keys into his client then forgetting about them?)

https://www.blockchain.com/btc/address/462259f237e3cd1b088e466da8f6da3428971a07 psykachu39 (0.00000001)
https://www.blockchain.com/btc/address/551222dc9f6f3ce2ec65b338549e35a8f8f14afa psykachu56 (0.00000001)
https://www.blockchain.com/btc/address/58ce18bdc94c7f2601e48f1aa27fabde545634ee psykachu137 (0.00000001)
https://www.blockchain.com/btc/address/7d44d5edef9b6f21ae780d1918dc2e28ea4e1ed2 psykachu138 (0.00000001)

https://www.blockchain.com/btc/address/97202615f86a3cdeb991d3623a692e2ab7380886 hello world hello world hello world hello world hello world hello worldhello world hello world hello world hello world hello world hello world (0.00001661)

https://www.blockchain.com/btc/address/59c872935f6c0acc81aa953cf3009f96597b250f orenattar@gmail.com (0.00000600)

https://www.blockchain.com/btc/address/e0d996260606eb7994517a2b173f917c79d55745 fuck bitcoin (0.00001000)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on February 23, 2019, 10:21:18 PM
A symbolic act?
My guess is someone uses a (dumb) script that doesn't check if the balance is worth the fee.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on March 28, 2019, 02:44:43 PM
Latest passphrase to be found is one of those that seems so obvious once it's been discovered.

https://www.blockchain.com/btc/address/377a08e417b77640cdf8ce300d45897384479e38

The passphrase is (in its entirety) Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

https://en.wikipedia.org/wiki/Lorem_ipsum


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on March 30, 2019, 06:50:04 AM
An unusual passphrase:

WARNING: This key is not certified with a trusted signature!

(That's the passphrase.)

https://www.blockchain.com/btc/address/8d940736aae07fb4df7865b1e163d7bcd4112ce0


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: djhomeschool on April 06, 2019, 02:58:35 PM
Is there any python script to start testing passprhases or wordlists? I would like to test some private lists.

EDIT: found one and got it working


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on April 06, 2019, 07:15:17 PM
An unusual passphrase:

WARNING: This key is not certified with a trusted signature!

(That's the passphrase.)

https://www.blockchain.com/btc/address/8d940736aae07fb4df7865b1e163d7bcd4112ce0

The fact that you were able to find this convinces me that any passphrase that can be memorized is not safe.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on April 07, 2019, 05:10:20 AM
An unusual passphrase:

WARNING: This key is not certified with a trusted signature!

(That's the passphrase.)

https://www.blockchain.com/btc/address/8d940736aae07fb4df7865b1e163d7bcd4112ce0

The fact that you were able to find this convinces me that any passphrase that can be memorized is not safe.

This appears to be generated by GPG, so at first I thought it may have been someone feeding the output to SHA256 to generate their private key - without realising the output was an error message - but from a quick look the program is more verbose when reporting such an error. Perhaps it's a geeky easter egg?

The way I found it was odd: I extracted strings from my boot drive, and fed them to brainflayer...


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: djhomeschool on April 07, 2019, 11:40:24 AM
Did a small test:

Code:
dictionary word, received bitcoins, wallet address, private address, current balance
Found used wallet: automobile,0.00006460,1F38xmnZPVsDtt5n4zjrowJequwSHL1ALT,f4c7ec93811087e5c3da505c080be9badac8b956d62aa6f13e02a56bbbbaee8a,0.00000000
Found used wallet: champions,0.00005460,15wyRo8uzzFAe98MvgnsHM8BzQrghdxDZB,7f18c9fcb3aac93ee3adc39486a3fcb1ff69bd4b036437c0fc20f32f2c1112d3,0.00000000
Found used wallet: Cinderella,0.00005460,13MFaz8tBX8vr5aYd2kEbfuLiov4uCbL5j,c728d8328425762a5801ab3dcfbb92d7989dcfcde5b52b094042d6d7a8456c4e,0.00000000
Found used wallet: millionaire,0.00005460,1QFkX2h8BKijQwQ5hSzeW5uhtVgSGxs2VM,725544de96fa7e38e7c1e3911d79770f6de178c52d4b87702ad820f5fe7e135c,0.00000000
Found used wallet: sultan,0.00020108,13kynW3MZXwR2QABv9u4oz6BfCrL3izegh,02cf1cce1b9414df96996756be90dc9f025acfd806a060a07ae5bcf5b133fe12,0.00000000
Found used wallet: 1234567,0.00032923,1B96DTqj2GNFm5VGDfLGyCoZtDFvqWHjG7,8bb0cf6eb9b17d0f7d22b456f121257dc1254e1f01665370476383ea776df414,0.00000000
Found used wallet: buttonhole,0.00005460,1Ark1g3VUgWc6oUfTsj8ssTvkJEgTivXG5,a53ee1e8509e93360ebce965bec238fc6169896696ea318b795f6503debbeb6d,0.00000000
Found used wallet: decathlon,0.00005460,1KuwgrMWGMy7fP6nbBzB6S71QRjYqPhfRU,71508df592b4e7185299e7fcdf1de9165e9ff4d182085df3ab3fbbbc46adecbc,0.00000000
Found used wallet: announced,0.00005460,1AvkDHNFFrcFmN59jGAegdRwUmoQhykySN,3cf46ab4906eb199effdf0e8354e6a065a0213c5febbf8edb534b762bed6194a,0.00000000
Found used wallet: extravaganza,0.00005460,1EPMMSJXYsV8RqiGNuiU2Vfa8UTS82jPL3,b210d806ca7463d8d5a904d141a84ccdfb81d2afd9e51582dfb2462875e90bb2,0.00000000
Found used wallet: 6,0.00058258,1JmrvhqYP4EpSRAhuKkn2NtmPvPNCxA9Kd,e7f6c011776e8db7cd330b54174fd76f7d0216b612387a5ffcfb81e6f0919683,0.00000000
Found used wallet: tranquility,0.00005460,1CwgKGLDeWkmbapmTS97xre9G8z1vwxmVN,06b384b3b9798926c2a48eb5a4e8d9c651b29f33328b72a1a66c93210a39ac70,0.00000000
Found used wallet: passwerd,0.00050000,1DDeCGwbBabA1VuMLegXCNe8jonH5oKNEQ,f22da79757db234aa4a5b17acefd73f62c1be0eea0f195ee2eaabca9e5527b46,0.00000000
Found used wallet: roma,0.00100000,1DNPdWrno9DvR5xaU2mB5MQkFxUKHjCo9d,b0c27fca74fa91934900c9ffcb3dcca5b807a3c059a3b516cdd0788807b5ff49,0.00000000
Found used wallet: godfather,0.00005460,126itomxM9vVQbR1oGMirQv465adsfVeov,a55b0153fdbfc0fb5605e4ba6cb14642e9f17f008feb86853fbc27ad2b9fdf09,0.00000000
Found used wallet: breakthrough,0.00005460,1DCFdRouHvfzVErRMuS4wCM4y6PSa1U8KW,2142487324cdb6d8c5049bc331d48db21152f53ab33d0e4faaaa91ea79ba5f2d,0.00000000
Found used wallet: confession,0.00005460,1QDJe16GgwHuoFvADZnYuB6tt7Zs5rrzcz,ae714c76abba41e031af1ce848865082ff1e52de11e1c57590c5329e3c5efe41,0.00000000
Found used wallet: 123456,0.00177480,1565qkBbLcuFP78f7MFKkK8jtHGDwdSgvX,8d969eef6ecad3c29a3a629280e686cf0c3f5d5a86aff3ca12020c923adc6c92,0.00000000
Found used wallet: pistachio,0.00005460,1LmEq6TGnKMyvLZ7vh61vLZBzCq73t4S6r,34c4ba8f5ba5f40e56e4056a7cfbf8b15f9db557bcafb8103f243aa7509ea802,0.00000000
Found used wallet: 1,0.21096594,12AKRNHpFhDSBDD9rSn74VAzZSL3774PxQ,6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b,0.00000000
Found used wallet: selective,0.00005460,176TwDNQdJ373vCysfMPmfEcGv8317KDhP,c0f7c0be2df73e42f3efadec327e70537bdd84d2c1b0016ff3c850ddd5a44e83,0.00000000
Found used wallet: marco,0.00050000,1NffPAxVTc7mixNS48NDRDmMKBJHmA6zBT,7c8ccc86c11654af029457d90fdd9d013ce6fb011ee8fdb1374832268cc8d967,0.00000000
Found used wallet: Anastasia,0.00005460,19KuT3SnUMPKeuUL47hFDSCoF8ay8KaHiN,e3facb7c91f0f86764b31e8d842100bf302d15bc14313453895c29e78f8a25be,0.00000000
Found used wallet: testament,0.00005460,183x5Uvmd74gL6hABb6JvLGLEBZDZ5JM8Q,039b1751609c775495c4bf7d4218285157cb920f11ea769b373bb1aa3ffe661d,0.00000000
Found used wallet: sacrifice,0.00005460,17mEdLbarARHbNqSa71zC9xwqGi6nHSSgG,d17bd922ea9dd14143a1c40cffad198af1314d34b49c819d47454114cb4bc224,0.00000000
Found used wallet: kindergarten,0.00005460,1KZJtoNrUL6JsQytoG3a5J2vP7CjvZW88f,7e48b820f4c8f67210bf2f416e533b3a2a24ccc7ab6c1d297d56b3d209ba3e6e,0.00000000
Found used wallet: jellyfish,0.00005460,1E54Rdd9cTmSRi6HvCcF5ioUjHhuJqWeqv,a0ea5328f032f1557fbc5d6516c59cc85e7c0fa270c43085f9c994ef2915449b,0.00000000
Found used wallet: irrational,0.00005460,1K25qPbzTTkqgSRmAwRzuScycVa6PJWhZW,2faee31f585e23f714b4298d880f85c71ad3a1a41d5812138ac29e38fdf14800,0.00000000
Found used wallet: occasions,0.00005460,1BikoR8icUa9YDYCksSU8jLemAcMi9wX8m,fdd0b4595d9e2287b65a2afbf7e7dab77041b63903aea24777c450d29f31be80,0.00000000
Found used wallet: cafemom,0.00013127,1127tVgpehWDG9CFqTw4xWvDbzTLydTJij,e31a852c5ef0e407c156b1cd1f62f847c80f7d93ad02d01a747fa54d5c86922c,0.00000000
Found used wallet: timeshare,0.00005460,1Mfu3PXVTR8QbSnfDkyVSQahXpsEeHkUCU,2327acf01775e30a0ceba54d5dd57e015243866acbda36d81149ef18a4ce3fce,0.00000000
Found used wallet: 42,0.13861027,14ZtDMZF1k2tFfVE1gzmTHMxyq8Maa6Hj9,73475cb40a568e8da8a045ced110137e159f890ac4da883b6b17dc651b3a8049,0.00000000
Found used wallet: cute,0.00009933,17MAEM2TEEvMXg5Vtq1SCmiJxCjFFsyqTy,17550e2bb9ff2c26dcce8ed178e326202cc9c67f16b79470767f01839a062249,0.00000000
Found used wallet: superman,0.03461000,18rSmNDoYC28pCLGP3XRqRJHkMw4X5rcwn,73cd1b16c4fb83061ad18a0b29b9643a68d4640075a466dc9e51682f84a847f5,0.00000000
Found used wallet: scientific,0.00005460,17iZyCFTvWrLQ3Zcvj5nCL6uY5EaHXwNEA,8592edc04aed3012ef2f4f447051e44409627bf4d8b7d8684822225e73f02a52,0.00000000
Found used wallet: phenomena,0.00005460,1CBdtKnXz5zqRggoxvbNtAqoomdLBZdV3P,8eb84dd4dcf6d17d96e26e57e09319a155ca0e92c8f944772910c1b80f84f5fc,0.00000000
Found used wallet: curriculum,0.00005460,1445daxre7ye9xKaYBbK4RJmGwx1pF6ZMz,d54eb7dce184bf90f597ca9dd1e548d13788be311d5e5ab8ecd5b64abf722fde,0.00000000
Found used wallet: prejudice,0.00005460,1ByttdYTgPFp5FK7rAM3cY68Q7926dp2E4,14a62b33decfa1b796452370c0a1c91136f8f71ebe1a469a2691d7f6e55a288b,0.00000000
Found used wallet: footprints,0.00005460,1JMmw5CVGXLEGQwHQc2DvrFHhThBwjVSxE,297fd6226a7eab1523b3cd5cc1f2b6d61986ae0a273183c798397fcb8ff2001e,0.00000000
Found used wallet: pass123,0.00015519,1P9KLNMLetT2nbJzySxJ4NtdU6bdoSp9Ne,9b8769a4a742959a2d0298c36fb70623f2dfacda8436237df08d8dfd5b37374c,0.00000000
Found used wallet: yahoo,0.37090000,1Ee6Y6dHRBUMm7VDnS8Q3F2gNNi8n9HpMX,a7a4ded2d5035adb26a222c67032f04cfcd2279ab508cf2a7ff612aead97551e,0.00000000
Found used wallet: mechanical,0.00005460,17wj9uMuGtn6Sewg7MQ3jQVzJW3MosUh1L,96ae0f875bd9062d5e263473590877f82d65b160571e0d4385c65d9a3e3c081f,0.00000000
Found used wallet: sensation,0.00005460,1JMnA8vXBr8TJZnChgB5c1XYzeTCcYphJW,595f053100ff2951992165de4576db0099b48b26251737b22acec4bc31d89440,0.00000000
Found used wallet: propaganda,0.00005460,1GrXYT11f43YGeNXCJUEDj8jp9zoQ43LR6,c82d3d4865e41e2a263ff0427c4df2b8e3e43a85c835404d033d764468b3ba55,0.00000000
Found used wallet: foundation,0.00005460,1HvFQHSCVjstBGezidwqQQkMF3xXqwU8nL,2bd8b7b0d83e0ec92abdf6f714ca199a7874d08636965471035c4dcd1b38b6fb,0.00000000
Found used wallet: marketing,0.00005460,127Te2BL6YVyc7VwuTwTzGzTccFLa4h9c9,e2a530e251d3675034d23f5c5f87f54ec3182a088ba7d13350824794f8e6b76e,0.00000000
Found used wallet: traverses,0.00005460,18Nosr7qSuHHcjaDjPukz2ab1RkaV52RPV,4c3242e2a5195cd8b3acfcb68cceea61a8a57eed4bc0a6ba818c1ef0eba963c9,0.00000000
Found used wallet: chemistry,0.00005460,14gAvxeiAck9JkzY7y953roZWJYLAaj3y9,de0152f952776f09f537d309f1f3f0ec7369c8df1297071e946952f798c86063,0.00000000
Found used wallet: the,5.28098999,1CgCMLupoVAnxFJwHTYTKrrRD3uoi3r1ag,b9776d7ddf459c9ad5b0e1d6ac61e27befb5e99fd62446677600d7cacef544d0,0.00000000
Found used wallet: Albuquerque,0.00005460,1HQG98kysyBNfYecfBLAoGANPzT1tvvJ8N,b3fb95a5f48cd83a60f9edcc6b5bc75078f526eea51ec65575d80505c9baffe0,0.00000000
Found used wallet: newsletter,0.00005460,1BYsS2USaFj931LqyG3Fctwp6pTfoyEhDN,dd6f465f6810e92c01cf36d8272b2181ac54f825365184ef4255b27ef917677b,0.00000000
Found used wallet: outrageous,0.00005460,1J92VCVVhy2h9vTE6RGvAYfYfuZbe1DYpX,d560e0630ab7cc86d34bd770986c86c077bf70b110b65bed6c517a56790cbd50,0.00000000
Found used wallet: mistletoe,0.00005460,15GHniyPzmhaJ4YWyLQ3JyajBfQRLwZFAW,9dd4592981dca3318ebd8ef8c62163532761dfff8d70882dca1e51228edfba50,0.00000000
Found used wallet: anniversary,0.00005460,14wMQhfw4bFFxzcyUVzgmVamjCjzXeozuJ,40c12bd9c3e15b47999aeda1dd3bf3ecad770496cec7a0ab16246f85eca366cb,0.00000000
Found used wallet: Bruxelles,0.00005460,1GCmP1H19mGRmXd9R4QMeKAQuUutd2C2dB,1f34d736766d93f0ace55e14e5eee7e041b36162aa918db0b467bafa5f5098f7,0.00000000
Found used wallet: kill,0.00035693,14GVHgqKmXZoxGzPuBAgkyDhWSpk6ZhmGb,2bda9b4dfbabfdb17cd74d827768da5198ae2b8155002a494524bbeaf6f5cdba,0.00000000
Found used wallet: dictionary,0.00005460,17ABHtqc9swa1sjifBATY4jMyccoKkccj8,177ca70f42def1238e36da329473263ed3feadd14094c079a2230be0193436f5,0.00000000
Found used wallet: retrospect,0.00005460,15Hus5kYDKtVPzEHMXd5t6D8HCHWVXJpxr,4836600918f39fa20fd2afbc4aa8e27bd4e5e770ad15e222241f865f6290af67,0.00000000
Found used wallet: aftermath,0.00005460,1un9QyprNTdFeDpF2wn8xVVAvzupSBL1T,bf648e312779342bb0c687654e34338830c9a6df999f1d64bf3e2237e93e222a,0.00000000
Found used wallet: Ridgefield,0.00005460,16rwmZZX9TkH57xoVxBha48zLmc28RThcH,425c4905c4f30e52b29a65a2ec51c76e657d17879134c1e812abf9dce6b77870,0.00000000
Found used wallet: leslie,0.83726198,1LaXN9PTDqs9w3eokECrcXapiALqDBGoRs,104f24e15f4dba76498bb256593dc6d95876d881ee2201ff369225b6d51e8b45,0.00000000
Found used wallet: residents,0.00005460,16BadGA5TgxFb9LsT5XztJVq8HFc8W9Fje,50286229439eccf54660bd7d555a4f7c6223d14d23b1565b7a2f71f359686144,0.00000000
Found used wallet: penis,0.00013277,12TDRfu5EqepHd1fNBiv4ThJxbeLNQRYe5,f6952d6eef555ddd87aca66e56b91530222d6e318414816f3ba7cf5bf694bf0f,0.00000000
Found used wallet: Password123,0.00010000,1CZMi7F5F3gq7e67SjJTFsoTZuj1ms5fqm,008c70392e3abfbd0fa47bbc2ed96aa99bd49e159727fcba0f2e6abeb3a9d601,0.00000000
Found used wallet: gymnasium,0.00005460,1BPWT2MYe5MJQntqUKMHe1oLPQuHbQiKuQ,db7d1e32769c6a3bbe48af465d898b74e5a69f243eadd50ce5cfca5e42614a8d,0.00000000
Found used wallet: horseshoe,0.00005460,15qEK5KARYpcxH9iarXq6MsFZAcBj3FuN7,1f9fbd028c61b5062a91d6db0df4849a474ef8137963a154f8d51080a1871389,0.00000000
Found used wallet: chocolate,0.06151460,1DTqPEUuuTeCJAYDadDnoPDKGvqDVFLRJN,7499aced43869b27f505701e4edc737f0cc346add1240d4ba86fbfa251e0fc35,0.00000000
Found used wallet: supernatural,0.00010920,1KARJxv23j232tB9XHVDCu9yYpALLZH97c,c1b59ba0c56e6b217dfdd0de59e40718568517c076a012c4ea34ba867f08c5e2,0.00000000
Found used wallet: barbie,0.00000666,1KqHsf6rwscLD6TkznauZZ6QPCwRkK4mNy,15065d771f7c8746bd30c125f9bb68a5ec7a84fccd7f0a82b38e760f39521c05,0.00000000
Found used wallet: 22222222,0.00100000,1Kq2aXcq1R1mFtRkdYS2n6bmvnGtzcawgK,33a7d3da476a32ac237b3f603a1be62fad00299e0d4b5a8db8d913104edec629,0.00000000
Found used wallet: boris,0.00066602,1CxNDxKBE4kJADZmteBfzbpW6FsrTZfkMW,0df89317e02535902d116be0f27294a75145339bf4af53fb35131aea8071a0e1,0.00000000
Found used wallet: hitler,0.00101000,1EYz2AhbVe2GJ1th1j5czNkAeSBViQfrUW,fd70ad909b94deb27b460692084d9f2b1dbc9df3c6bcfd3caee571e707031e3f,0.00000000
Found used wallet: brilliance,0.00005460,1Pra4fu9seTEGmEKDmtuhJDJ2ThjC9hT3d,b9573e6bb24c4c2411affe6ff4b97e16e0e3c7e6f0d28a6033b21fd74aec07f3,0.00000000
Found used wallet: magazines,0.00005460,13DaJn8eqvBDiuUoafUmD5n3LAXFhQyDY6,16f75b51f05c7d5c4419881f4d43b5635417e9cdfb51230f2dfed41e73ef0ba8,0.00000000
Found used wallet: mysterious,0.00005460,1AFg71PXb8KQHj4pQqiCx47Q5siMj7FqA1,da7cc64ae8ad7e0b926b366259b43fdc92dae8c483214a5665b3711a59d38255,0.00000000
Found used wallet: samuele,0.00010000,16TaVKKa9fVimReN2RpsnEXELA8ddL9eUa,6c1bdfb0f1ec46ffd6ddb972d02049c9d2168515bd9fd23c7eda144607891b5f,0.00000000
Found used wallet: Descartes,0.00005460,1PBCsNt8Hsqh1BhEPHbYAa28YgruL5mz7A,c7a7f7571af5fa3e0c75800058edd8b66704e042e6a16a79c41cf7ea3df3aad1,0.00000000
Found used wallet: astronomy,0.00005460,1PxfCWr5w1iZmGsqmM8d7iWru5kec69ER6,603354159847d671cd7c8e67b726829ebc19101932e2dbafd8da87ebd41cd1b6,0.00000000
Found used wallet: hurricane,0.00005460,12CZfr7SoYMRB3JNbX3oG18La1ZVSkkDwd,3fb312f8c4f8ecac0a0586a9b443ed140697af9256f3208625a370c77d47c92d,0.00000000
Found used wallet: Alexander,0.00005460,1HuaMiuSi2Y1RYAokNFifNG1nVweC4sXQ7,dbadfc88144b0c153a2d1bdf154681c857a237eb79d58df24e918bca6e17db05,0.00000000
Found used wallet: ballerina,0.00005460,17q6Ua27SkRoQyyWNy2T72NeiWcJZBnSYC,5237f55320b3a8b73460ed0c24dac63b5b9a5fe22811e76793705b342238147f,0.00000000
Found used wallet: embroidery,0.00005460,173hDVCYm9X9tT4jyknmoT337f45uF7Jq2,1f276c3d7706932b737ee3063b3310549272996e77fac5aa2d0a7c457923c29c,0.00000000
Found used wallet: transportation,0.00005460,1NFHt3TCXCkqf64VnFEfNt8ERQ8EqA36w9,0b349c79e44d2b99d730dd75fa754c9e5c9c055bdd78ad07504e4464479d8f5c,0.00000000
Found used wallet: franchise,0.00005460,13FNmgmXb3YR1CMSd3rcYpoDso96qAS1gj,9fe8ef24525db81848e6c53328e1d5aa55bfb178f8e4555ca3d4b614f0ff520d,0.00000000
Found used wallet: fireflies,0.00005460,16UMA292BZoMGv18qt9e5zfHhmJL9NnCX8,161c26cc674bc61b2f4f0e96f51d75753a0ac436f7053806897efdc952997342,0.00000000
Found used wallet: calcio,0.00020000,151n92Legc2a9g9UprisDc6LUJGqE4MUKT,7bb858128c1e10a5e12e71c71a7b681f20942fd645c9628d4da84a93bf6bd8d7,0.00000000
Found used wallet: separator,0.00005460,1Ki1eZsXHJ5cQq8HPDZB6WkHQX9kCaBpLi,080856f98d1eb14b814733d0c19b1af3161009c39e8e44ac79fe80a05b94f425,0.00000000
Found used wallet: cooperative,0.00005460,1PrjPiS3NFAxpK9dwRSEQiFjSyzUSMSAbi,975a0c6243cb25756fb243ed67c7db4c492b97f124baf7ace9c04b243d0fcbd5,0.00000000
Found used wallet: connection,0.00005460,1KX4zUq86KfWz8gDpn3FVME2HTPQjYhzCJ,b38d9d168c3aedf156f4f249b81adaef4b738790510573f57b502cca0c35f16f,0.00000000
Found used wallet: consulting,0.00005460,1ARo4nKDrdAX6SDNZXyaBHtayG4TpUm64V,7242dfd44b1ebef4fa2ad4d3abf2fea23ff5a4c798e2a8db6e6c033ea39e29c6,0.00000000
Found used wallet: mirko,0.00010000,1PasPhdM1MfAZKLY5HkL5ddsRMX3oEFR6E,6eb44ff6ac59c9b9d39e7ac203910f0384e4c2d3a59c8bfd7fecb7a5f6de1e10,0.00000000
Found used wallet: essential,0.00005460,1MmYN5UbP5MCEHrtCtAzzQXifRnVB66Neq,a55751cecd11bad874efb36d7746fd2651a5736260d611ccb8fb43091b90e744,0.00000000
Found used wallet: lucia,0.00020000,14Uqwu9yudb1dBS9GRgjyELi5Hi2xziXLz,6326e0e8cfdaab9af83026a0620bafd05179e3a0cd1b812222682d86285b30cc,0.00000000
Found used wallet: rendezvous,0.00005460,121Cr2RTisBQfkXchgX9dJqeDmFyQAxnnH,b8a201afe114d8d6e7b9fb56dd3a3ad6fc33a96fda253ba13b0281aa29c1002f,0.00000000
Found used wallet: grapefruit,0.00005460,14WiKYHcM2DUvXdYdBXCjWwpG6N5uhVUnx,e30970665ed2e34594c2645ba9d3c307b36fc95efb92136b18ebdeee48b9072b,0.00000000
Found used wallet: hydraulic,0.00005460,19rYb8CWW2sBRR8dvBfNrxVormsPJM3Q5w,2b0d221ea282a3ba40c2c95983b6e332ada542a12527d2f7892ad1680e3ca94a,0.00000000
Found used wallet: performance,0.00005460,14LySzy6yoJ99txi91ZfUXFwofcv4ZTu6V,4a1898716ef67796fcc80c7426c4f876d398de27da5c73a3accf425e42a7f412,0.00000000
Found used wallet: trieste,0.00010000,12SzWpN6A7V7eQUx9yzjiJ5Pu5yDNzWf75,f32484b9ba652695099b62eb326c4279ad3ccee64f875ab9568dc6de7afde8ad,0.00000000
Found used wallet: bittersweet,0.00006460,1LBYuF4X374SoNckFouQqKUh9uRL95aFN1,556ded69059a18b07235d44763c00d840a81aeff461aacf494ea42dc92830ae4,0.00000000
Found used wallet: lokesh,0.00060000,1H8uZX7qiC1WHxbTjNqF17AMSLJtYYAqoh,a5f3ad0d95c2afe089bc751a56f8a0f34e19bb28c528263d9135ac0ea45ba708,0.00000000
Found used wallet: department,0.00005460,1Kx88AS1hK6rBCPBkt5K5mZnYM24iXGgE,2ad29f65743a0524d916bfb3e24f5034c970b8daa7749699a88bd7096129fa09,0.00000000
Found used wallet: cows,0.24308000,1QEmV8FoxNQqjREEhyXeLn1UMSejBQXoWt,c6520d7c46b53b2f4567cb3b29b93b19c775b601d5a0e9e06315ca9e79751e7c,0.00000000
Found used wallet: interiors,0.00005460,194pKiQWzfNYF1TRKWrURMGc63z4L5amKB,91538b64771cbd776fe85f028c8a264583ed29a37445822a60dd07106577ec42,0.00000000
Found used wallet: conductor,0.00005460,1MgrG41eyd69DE79fzQwYLqDr7rWzNtCza,0380db97ec507816cb2435f11d56f1bfe151dea2ae25a75859e9b2f0417dda5b,0.00000000
Found used wallet: purchasing,0.00005460,1APUFeQcWfE1Q6bfvWVRmRgG8zX46HUozr,93fa6393336f975afcfb6e9bd36654239164e645f64ce2e9d4ab75149ee6bd8e,0.00000000
Found used wallet: invention,0.00005460,12cBWFm6pFm384RfA6yhB4KTWSg7AiBMBJ,5bebe4b948683362feab006f3c34d9045902a470ca7dcbbf35f0275295c9c3f4,0.00000000
Found used wallet: Katherine,0.00005460,1EKTFKEnGodxApZ2akoVwKpTbshgW8As6j,5632e195ae87f23c49c2803e1c40d0401d5f8da65ad49c6e01bf8e803266ecc9,0.00000000
Found used wallet: crocodile,0.00005460,1JtsNnvgMGg71G9iH63WG6JGwjuYVKb5zC,02766f3002eaa501317fc1ac658a30ec6fba6be867f2624ce7d2b8bc31a83ca8,0.00000000
Found used wallet: highlander,0.00005460,1CaTEzjjRgDa9LXqQpdqga3SPPnEBcu7PB,300cb2d7a5270ddfccd779f46c7bc9839db6f6cf6f08200be93407622d159954,0.00000000
Found used wallet: breakfast,0.00005460,1PEysPp7nNkfD1cPad6gcYd29f8oW1iZ9n,7c58ea253628feed6583e78db4fd9fab131e0016ade168b4c200eb41d6aa93b1,0.00000000
Found used wallet: placements,0.00005460,1NTe195aMUu7zB2uY4y3KsvQ5YNkTzkZov,2be9c792a9d92b04b3057a7eb76fca2eb3ae77eda06156d97491fdb2ed690911,0.00000000
Found used wallet: freemoney,0.28061728,12VXcoAabff2pjwchqDZm25drNnLEM4vKy,8416c455bad6679155f5f431ec228491500d692982a5a1ffebee83d4f9819f27,0.00000000
Found used wallet: incognito,0.00020000,14MdHVZtDWhrm21o1W4Ld5saAMXxj1FtgU,3c7f75ed7842eae7dc838f6202355fcbf8c6eff336e11088b31fff48f4df67ae,0.00000000
Found used wallet: rodina,0.05777600,19W4zoNbRvJAibJ5nbQqSvxYVLvui4DXiB,92971e212c4073e786c0f116915d2481f985736696b2eb0c591dd563ae612f66,0.00000000
Found used wallet: archipelago,0.00005460,1GjAKvscLxxBRKq9afETLrKtQEv5ydYnNF,201efa284e839229c41b8eda3c74f8d3a58fd9941f5b6d8424622b1789a78379,0.00000000
Found used wallet: Barcelona,0.00005460,1NjGkpUQrj7S8PQwdtaxJNRAJVeM4Jf7GW,062dda15f8838576019a50b01bdf29cc5046008bbfcfaa292350ccd382b51ec9,0.00000000
Found used wallet: different,0.00005460,13zJp8PV7cY2cgLubFQzDFihHArgBgtM3C,9d6f965ac832e40a5df6c06afe983e3b449c07b843ff51ce76204de05c690d11,0.00000000
Found used wallet: instrumental,0.00005460,1F7Xni8kEREsTDMfVoh137TNhzLUwrzBWC,32528ed2244f2862f45198934d8ad057ab94ee63d928f99c1188aeae20eee65b,0.00000000

Nothing very special but interesting to see some wallets had 0.1 or more in them in the past.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: mr.mister on April 09, 2019, 12:02:17 PM
As been discussed many times before using a Brainwallet is a bad idea.

I disagree, I have never lost anything from a brain wallet but I have lost quite a few coins from failing hardware wallets and dying hard drives.


I have to agree. It would appear to me that your Brainwallet will be as secure as the passphrase you used to create it. So if you choose a very difficult passphrase your brainwallet will be secure. I would assume it's the same as choosing a passphrase for your encryption vault.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on April 09, 2019, 12:45:34 PM
I would assume it's the same as choosing a passphrase for your encryption vault.
It's not. To brute force your own local encryption, an attacker needs access to your encrypted file, and dedicate all his computing power to just your case.
With Brainwallets, one attacker can brute force all existing users on the planet at the same time, and thus has a much larger chance of finding a match.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on April 09, 2019, 12:54:04 PM
I have to agree. It would appear to me that your Brainwallet will be as secure as the passphrase you used to create it. So if you choose a very difficult passphrase your brainwallet will be secure. I would assume it's the same as choosing a passphrase for your encryption vault.

I can think of two very important differences with brainwallets, versus a wallet.dat encrypted by a Bitcoin client:

1. The blockchain is like a public password file that can be passively cracked. If someone cracks your passphrase, they can steal the funds, without ever needing physical or remote access to your machine in order to copy wallet.dat.

2. Brainwallet cracking doesn't need to be targeted. It's only a little less efficient to check each candidate passphrase against the entire set of unspent outputs - every funded address on the blockchain - versus just one specific address.

A basic SHA256(passphrase) brainwallet is very dangerous, because the keys can be checked at a great rate. My ageing Core2Quad server can check around 14 billion candidate passphrases per day.

edit:

It's not. To brute force your own local encryption, an attacker needs access to your encrypted file, and dedicate all his computing power to just your case.
With Brainwallets, one attacker can brute force all existing users on the planet at the same time, and thus has a much larger chance of finding a match.

Okay, well you said the same thing I did, just faster... :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BurtW on April 09, 2019, 06:23:48 PM
Code:
cows,0.24308000

cows?  really... cows?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on April 10, 2019, 01:18:00 AM
Code:
cows,0.24308000

cows?  really... cows?

There's several thousand dictionary word brainwallets which were funded with 0.0000546 BTC back in 2013, however, looking more closely, this is not the typical dictionary word brainwallet. There are 30234 transactions associated with this address!!!

https://www.blockchain.com/btc/address/fee56f465d92e6c52a8dd455e4e10cf835554097


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on April 21, 2019, 12:10:56 AM
This is for Litecoin, but I thought I'd mention it because of the substantial (~$30,000 USD at the time, more now) amount involved.

http://explorer.litecoin.net/address/LP27QTd7DpQTEyoREubXSY2JhyBPBbiqFa
https://ltc.explorer.berrywallet.io/address/LP27QTd7DpQTEyoREubXSY2JhyBPBbiqFa

Around a year ago, this address was funded with 500 LTC, then a few hours later, 0.99 LTC was added, and a few minutes after that, the entire 500.99 LTC balance was transferred out.

I'm going to withhold the passphrase because of the value and relatively recent transactions, but it's simply someone's name, and from some basic research it seems that he's involved with investing in Litecoin. Some kind of vanity thing, either by the person with that name (side thought: I wonder how many people use their real name as passphrases for their encrypted local wallets?), or someone else trying to make a point? Not a small amount, either way.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: digitalcitizen on April 25, 2019, 11:49:40 PM
Code:
cows,0.24308000

cows?  really... cows?

There's several thousand dictionary word brainwallets which were funded with 0.0000546 BTC back in 2013, however, looking more closely, this is not the typical dictionary word brainwallet. There are 30234 transactions associated with this address!!!

https://www.blockchain.com/btc/address/fee56f465d92e6c52a8dd455e4e10cf835554097

Found a lot of those old ones running a brain wallet search tool with standard spelling dictionaries on most *nix systems, where the dictionary itself was run through a password transform tool.  For instance /usr/share/dict/american-english or equivalent.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Syche on May 05, 2019, 03:13:35 PM
Is there any python script to start testing passprhases or wordlists? I would like to test some private lists.

EDIT: found one and got it working


could you let me know how i can get started, been looking for this, i dont have any coding skills but i would like to feed my own ideas into the system and see what results come out, thanks.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on May 06, 2019, 07:10:20 AM
Another unusual SHA256 brainwallet, derived from a rather long passphrase... one billion and two characters, to be exact. One billion and one of them are numerical digits.

Can you guess what it may be? :)

https://www.blockchain.com/btc/address/cd66242a2f19b7b6eeb4f4eaf7aa69d071ade6c6

I notice that 1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB (gmaxwell) appears in 3 transactions which spend both the 1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB and brainwallet outputs, so it appears those transactions were created by him (or someone possessing his privkey).

Possibly related to this coin mixing thread I found: https://bitcointalk.org/index.php?topic=139581.0


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on May 06, 2019, 07:34:21 AM
Can you guess what it may be? :)
Something like:
1000000000000000000000000000000000...............000000000000000000000000000000 000a


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on May 06, 2019, 08:55:59 AM
Can you guess what it may be? :)
Something like:
1000000000000000000000000000000000...............000000000000000000000000000000 000a

Strong hint: Think... recurring never-ending decimal number


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceMobile on May 06, 2019, 09:19:34 AM
Lol 3.1415927….......

How did you even try that? And have you tried more decimals?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on May 06, 2019, 10:10:07 AM
Lol 3.1415927….......

How did you even try that? And have you tried more decimals?

Two things had to happen to discover that particular private key:

1. I decided to try feeding the SHA256 hash of every file on my NAS to brainflayer.
2. One of those files contained the value of Pi to a billion decimal places.

Another match was the hash of the goatse photo. (If you don't know what that is, goatse is an old school shock site that is very, very NSFW. I didn't even realise I had that photo sitting on my storage.)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on May 06, 2019, 11:07:32 AM
Another match was the hash of the goatse photo. (If you don't know what that is, goatse is an old school shock site that is very, very NSFW. I didn't even realise I had that photo sitting on my storage.)

...because of course it was.

There should be a word for being surprised while not being surprised at all while feeling both disgusted and nostalgic at the same time.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on May 07, 2019, 02:53:45 PM
I thought the mini private key format, used for Casascius physical bitcoins should rate a mention here, because it's basically a SHA256 brainwallet... but with a randomly generated passphrase.

https://en.bitcoin.it/wiki/Mini_private_key_format

Given that the random passphrase length is 22 characters (early version) or 30 characters, the chances of brute forcing it are still virtually nil, but technically, it is less secure than a standard key, in particular because 99%+ of the tries can be discarded after the first SHA256 hash.

By the way, funds have been sent to (and promptly swept from) the address associated with the sample mini private key on that page:

https://www.blockchain.com/btc/address/7f6ab65fa911f558ca2dde3e9d073acb02c0d5c6 (uncompressed: 1CciesT23BNionJeXrbxmjc7ywfiyM4oLW )
https://www.blockchain.com/btc/address/f78c1591f3f34fd1fe339dc371069b7b492bf370 (compressed: 1PZuicD1ACRfBuKEgp2XaJhVvnwpeETDyn )


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on May 11, 2019, 11:49:10 AM
I created a simple word smasher as a way to pipe content to BF.
So I use the power of 2 scale with randint between specific values.

Depending on the size of the list you will need to set the values according.

I did find a few wallets this way with specific word lists being used and changes to the values.

I have another version that will take content and hash it with hashlib and pipe the output to BF and again this also threw back some results.

Code:
## Word Smash Power Of 2
## Set wordlist and pipe output
## Python
from time import sleep
import random
import sys

my_file = open("words.txt", "r")
words = my_file.readlines()


## Power of 2 select from wordlist : ToDo - Evaluate methods
i = 1
while i > 0:
    number_1 = random.randint(0, 128)
    number_2 = random.randint(0, 256)
    number_3 = random.randint(0, 512)
    number_4 = random.randint(0, 1024)
    number_5 = random.randint(0, 2048)
    number_6 = random.randint(0, 4096)
    number_7 = random.randint(0, 8192)
    number_8 = random.randint(0, 16384)
    number_9 = random.randint(0, 32768)
    number_10 = random.randint(0, 65536)
    number_11 = random.randint(0, 131072)
    number_12 = random.randint(0, 262144)
    word_1 = words[number_1]
    word_2 = words[number_2]
    word_3 = words[number_3]
    word_4 = words[number_4]
    word_5 = words[number_5]
    word_6 = words[number_6]
    word_7 = words[number_7]
    word_8 = words[number_8]
    word_9 = words[number_9]
    word_10 = words[number_10]
    word_11 = words[number_11]
    word_12 = words[number_12]

    print(word_1.rstrip() + " " + word_2.rstrip() + " " + word_3.rstrip() + " " + word_4.rstrip() + " " + word_5.rstrip() + " " + word_6.rstrip() + " " + word_7.rstrip() + " " + word_8.rstrip() + " " + word_9.rstrip() + " " + word_10.rstrip() + " " + word_11.rstrip() + " " + word_12.rstrip())
    i += 1
    sleep(0.005)
    pass


Some of the values

Code:

number_1 = random.randint(0, 128)
number_2 = random.randint(0, 256)
number_3 = random.randint(0, 512)
number_4 = random.randint(0, 1024)
number_5 = random.randint(0, 2048)
number_6 = random.randint(0, 4096)
number_7 = random.randint(0, 8192)
number_8 = random.randint(0, 16384)
number_9 = random.randint(0, 32768)
number_10 = random.randint(0, 65536)
number_11 = random.randint(0, 131072)
number_12 = random.randint(0, 262144)


number_1 = random.randint(0, 1024)
number_2 = random.randint(0, 2048)
number_3 = random.randint(0, 4096)
number_4 = random.randint(0, 8192)
number_5 = random.randint(0, 16384)
number_6 = random.randint(0, 32768)
number_7 = random.randint(0, 65536)
number_8 = random.randint(0, 131072)
number_9 = random.randint(0, 262144)
number_10 = random.randint(0, 524288)
number_11 = random.randint(0, 1048576)
number_12 = random.randint(0, 2097153)


number_1 = random.randint(0, 2048)
number_2 = random.randint(0, 4096)
number_3 = random.randint(0, 8192)
number_4 = random.randint(0, 16384)
number_5 = random.randint(0, 32768)
number_6 = random.randint(0, 65536)
number_7 = random.randint(0, 131072)
number_8 = random.randint(0, 262144)
number_9 = random.randint(0, 524288)
number_10 = random.randint(0, 1048576)
number_11 = random.randint(0, 2097153)


=== OFFSETS ==

    number_1 = random.randint(0, 256)
    number_2 = random.randint(64, 512)
    number_3 = random.randint(128, 1024)
    number_4 = random.randint(256, 2048)
    number_5 = random.randint(512, 4096)
    number_6 = random.randint(1024, 8192)
    number_7 = random.randint(2048, 16348)
    number_8 = random.randint(4096, 32768)
    number_9 = random.randint(8192, 65538)
    number_10 = random.randint(16384, 131072)
    number_11 = random.randint(32768, 262144)
    number_12 = random.randint(65538, 524288)



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on May 18, 2019, 01:18:54 PM
Around USD100 worth of BTC sent to a weak private key, stolen pretty much immediately:

https://www.blockchain.com/btc/address/a27d952a793dd83d82cfaa8431c6d36450683f6d

The key is 00000000000000000000000000000000000000000000000000000000000005a1, a value which anyone playing with key cracking would almost certainly attempt. (With my modest setup, a single core running bitflayer in private key mode would find this key around 0.01 seconds after starting.)

Again not really sure of the intent. Was this someone throwing a hundred bucks away for fun, or the result of buggy private key generation?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on May 19, 2019, 04:49:25 AM
Speaking of weak private keys, this one had 0.1647412 BTC (approximately $USD 1133) sent over two successive transactions back in August 2018:

https://www.blockchain.com/btc/address/1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc

Promptly swept away.

The private key is 000000000000000000000000000000000000000000000000000000000000001f, which is essentially the 30th possible key if you count upwards. Something that could be discovered manually. Exceptionally weak.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BurtW on May 20, 2019, 02:36:01 PM
LBC (https://lbc.cryptoguru.org/stats) has sequentially searched and swept all private keys under 55 bits and is pressing on at about 20.82 trillion keys per day.  So all short private keys are a bad idea.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on May 20, 2019, 05:22:25 PM
LBC (https://lbc.cryptoguru.org/stats) has sequentially searched and swept all private keys under 55 bits and is pressing on at about 20.82 trillion keys per day.  So all short private keys are a bad idea.

Sound advice, but bear in mind that the really low ones (say, 32 bits or so) are likely watched by bots for future activity, rather than simply being checked once by LBC.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: daboehla on June 05, 2019, 04:50:12 PM
Last big transaction to weak private key on my radar was 0,06473026 to 0xBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
(1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet)

Why does somebody do this? Donation to the bots? or really accidentally?



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on June 05, 2019, 07:16:37 PM
Last big transaction to weak private key on my radar was 0,06473026 to 0xBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
(1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet)

Why does somebody do this? Donation to the bots? or really accidentally?
I'm amazed it lasted that long: it took 7 minutes (https://www.blockchain.com/btc/address/1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet) to be sweeped! The private key to address 1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet was even posted on Bitcointalk in 2011:
Code:
Addr B: 1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet (PrivKey:bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: malevolent on June 05, 2019, 08:07:38 PM
I'm amazed it lasted that long: it took 7 minutes (https://www.blockchain.com/btc/address/1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet) to be sweeped!

I'm not. I would imagine almost everything that could be feasibly stolen has been stolen between 2011-2015. Around 2013 it has become increasingly clear that most people choose too easy passwords for brainwallets and their use has been discouraged, and if you really have to use one, at least use one with key-stretching, such as warpwallet. Now thieves can either put increasingly more resources into searching for (most likely older) brainwallets, whose owner might have emptied them anyway, or fight for scraps that occasionally gets sent to some of the easier brainwallets. There probably aren't that many people nowadays who're bothering with monitoring brainwallets, otherwise the address you linked would have been emptied in under 7 seconds instead of 7 minutes.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: daboehla on June 06, 2019, 06:22:58 AM
I'm amazed it lasted that long: it took 7 minutes (https://www.blockchain.com/btc/address/1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet) to be sweeped!

I'm not. I would imagine almost everything that could be feasibly stolen has been stolen between 2011-2015. Around 2013 it has become increasingly clear that most people choose too easy passwords for brainwallets and their use has been discouraged, and if you really have to use one, at least use one with key-stretching, such as warpwallet. Now thieves can either put increasingly more resources into searching for (most likely older) brainwallets, whose owner might have emptied them anyway, or fight for scraps that occasionally gets sent to some of the easier brainwallets. There probably aren't that many people nowadays who're bothering with monitoring brainwallets, otherwise the address you linked would have been emptied in under 7 seconds instead of 7 minutes.
I am sure the timestamp of the emptying transaction is wrong.
Because I also run a program, which tries to empty these weak private keys.

At 29.05.2019 00:41:26.300 I recorded the transaction. (+2 timezone)
On 29.05.2019 00:41:26.324  I already got txn-mempool-conflict

So I think there are Many very fast out there.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: daboehla on June 06, 2019, 11:16:14 AM
Today was also a high value transaction to weak private key:
06.06.2019 10:39:25.107 0,25000000 1FJJTKza3HovjzguAnMY9VYPu5Kd6CRKa -> 07D6D38FF15148A755F8E64F2C3F7860DEBEBB1C / 00000000000000000000000000000000000000000000000000000000000007B7 / LowerAddr


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: buwaytress on June 06, 2019, 11:46:14 AM
I'm amazed it lasted that long: it took 7 minutes (https://www.blockchain.com/btc/address/1NiEGXeURREqqMjCvjCeZn6SwEBZ9AdVet) to be sweeped!

I'm not. I would imagine almost everything that could be feasibly stolen has been stolen between 2011-2015. Around 2013 it has become increasingly clear that most people choose too easy passwords for brainwallets and their use has been discouraged, and if you really have to use one, at least use one with key-stretching, such as warpwallet. Now thieves can either put increasingly more resources into searching for (most likely older) brainwallets, whose owner might have emptied them anyway, or fight for scraps that occasionally gets sent to some of the easier brainwallets. There probably aren't that many people nowadays who're bothering with monitoring brainwallets, otherwise the address you linked would have been emptied in under 7 seconds instead of 7 minutes.
I am sure the timestamp of the emptying transaction is wrong.
Because I also run a program, which tries to empty these weak private keys.

At 29.05.2019 00:41:26.300 I recorded the transaction. (+2 timezone)
On 29.05.2019 00:41:26.324  I already got txn-mempool-conflict

So I think there are Many very fast out there.

Indeed! 7 minutes was merely the time between blocks, as it turns out. So we can actually confirm that after all these years there are still people who actively run programs that automatically empties these addresses, even those as old as 8 years like this one now.

Curious to know, does your program know of and then attempts the sweep transaction as soon as confirmation is received or do you already try to sweep it when the incoming tx is recognised?

In other words, is your sweep tx created as soon as incoming tx is broadcast or only once confirmed? $500 is not bad at all.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on June 06, 2019, 11:55:17 AM
Today was also a high value transaction to weak private key:
06.06.2019 10:39:25.107 0,25000000 1FJJTKza3HovjzguAnMY9VYPu5Kd6CRKa -> 07D6D38FF15148A755F8E64F2C3F7860DEBEBB1C / 00000000000000000000000000000000000000000000000000000000000007B7 / LowerAddr
Someone paid 21% ($400) fee to steal these funds! Bots are competing heavily to get picked by a miner.

Curious to know, does your program know of and then attempts the sweep transaction as soon as confirmation is received or do you already try to sweep it when the incoming tx is recognised?
The theft gets confirmed in the same block as the original transaction, so it doesn't wait for a confirmation.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 06, 2019, 12:59:50 PM
Today was also a high value transaction to weak private key:
06.06.2019 10:39:25.107 0,25000000 1FJJTKza3HovjzguAnMY9VYPu5Kd6CRKa -> 07D6D38FF15148A755F8E64F2C3F7860DEBEBB1C / 00000000000000000000000000000000000000000000000000000000000007B7 / LowerAddr

Pure speculation here - I'm not very good at following transaction trails - but the source wallet has a high number of transactions and large cumulative balance, so I'm guessing it could be an exchange wallet, and that 0.25 BTC was a withdrawal by a customer. Question is, how did the funds end up being sent to that address? Was this some internal software deliberately stealing funds, or did this key get imported into someone's wallet somehow?

IDEA: exchanges and any other services which allow customers to withdraw should maintain a blacklist of addresses with weak keys / broken brainwallets, so that any attempts to send to such an address are blocked.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: malevolent on June 06, 2019, 07:41:54 PM
I wanted to say someone's watching this thread, but I think $400 is a bit too much to waste on proving a point. I wonder how many more tried to steal those coins.



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 06, 2019, 10:52:43 PM
I wanted to say someone's watching this thread, but I think $400 is a bit too much to waste on proving a point. I wonder how many more tried to steal those coins.

Sweep bots existed long before this thread was started...


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: malevolent on June 06, 2019, 11:53:10 PM
Sweep bots existed long before this thread was started...

Doesn't mean many people still bother running them.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 07, 2019, 07:04:51 AM
Sweep bots existed long before this thread was started...

Doesn't mean many people still bother running them.

I posted in this thread a few months ago that even on testnet funds get swiped instantly. :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on June 09, 2019, 11:27:26 AM
The real issues is the weak PK values here and education on how to create secure keys.
I tested lot's of the tools that are available out there even going as far as to parse the entire blockchain into MySQL table while running ABE and BF and a few other scanners I have there are still 100's of un-secure wallets out there waiting to be picked up by the sweepers (just for the record I don't sweep funds and never will.)

But it's quite a concern that many people seem to have funds laying out there which any competent person with python and a word list could find.
I also ran some checking on the old style electrum seeds with a "modified" word list and have had some wallets return with funds highest was around 0.15 BTC.

I am unable to post the results as the wallets seems to be active.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 20, 2019, 12:00:36 PM
https://www.blockchain.com/btc/address/b09a09458fe9bb86b0d897b4c244b05432bad28d

This one is interesting for a number of reasons...

- It seems to be a relatively early use of a SHA256 brainwallet (January 2012).

- The transaction originally funding this brainwallet split 1 BTC into neat sets of 0.001 and 0.005 BTC. Could other outputs from this transaction - there are 101 in total - also be brainwallets, or some other kind of special address? Some are still unspent, 7.5 years later.

- A second set of funds (6.08 BTC) was sent a couple of weeks later, then all funds were swept the following year. Over time, the value of 6.08 BTC appreciated from around $USD 35 in February 2012, to almost $USD 600 in July 2013. (The sweep output is still unspent; 6.08 BTC is now worth nearly $60,000. Hope the owner still has the privkey!)

The passphrase is just let the lovin take ahold


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on June 23, 2019, 03:19:53 PM
https://www.blockchain.com/btc/address/b09a09458fe9bb86b0d897b4c244b05432bad28d

This one is interesting for a number of reasons...

- It seems to be a relatively early use of a SHA256 brainwallet (January 2012).

- The transaction originally funding this brainwallet split 1 BTC into neat sets of 0.001 and 0.005 BTC. Could other outputs from this transaction - there are 101 in total - also be brainwallets, or some other kind of special address? Some are still unspent, 7.5 years later.

- A second set of funds (6.08 BTC) was sent a couple of weeks later, then all funds were swept the following year. Over time, the value of 6.08 BTC appreciated from around $USD 35 in February 2012, to almost $USD 600 in July 2013. (The sweep output is still unspent; 6.08 BTC is now worth nearly $60,000. Hope the owner still has the privkey!)

The passphrase is just let the lovin take ahold


I think there are still many many more to be found out there my guess.
Interesting find on the 6 words are those song lyrics by any chance?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: avw on June 26, 2019, 10:15:51 AM
- The transaction originally funding this brainwallet split 1 BTC into neat sets of 0.001 and 0.005 BTC. Could other outputs from this transaction - there are 101 in total - also be brainwallets, or some other kind of special address? Some are still unspent, 7.5 years later.
You can see that addresses are arranged alphabetically, sorted by first two letters (first is always lowercase).
Looks like addresses were generated by vanitygen.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 27, 2019, 08:14:59 AM
- The transaction originally funding this brainwallet split 1 BTC into neat sets of 0.001 and 0.005 BTC. Could other outputs from this transaction - there are 101 in total - also be brainwallets, or some other kind of special address? Some are still unspent, 7.5 years later.
You can see that addresses are arranged alphabetically, sorted by first two letters (first is always lowercase).
Looks like addresses were generated by vanitygen.

I thought at first you were onto something, but when you look more closely, it is not cleanly sorted.  For example, the address 1Ct2qiAXf6iYHQ3iUB3sfinR5SfzhYQf4u (output 86) is alphabetically lower than the address 1FuicRGD8kQoPmnsXTirEoeoVtVwrjQs7T (output 0)

Here is the raw transaction:

https://www.almightycoins.org/cc5e0d2d0f46b56ab57027e236ed3ebff4ed7157238947db2ae59cddca60e08b.txt

And the output scripts only, which show the RIPEMD160 hex representation of the addresses:

https://www.almightycoins.org/cc5e0d2d0f46b56ab57027e236ed3ebff4ed7157238947db2ae59cddca60e08b-outputscript.txt

You can see here the outputs are loosely but not perfectly sorted.

There is still something unusual about this selection of addresses, because for 92 of the 101 outputs, the first byte of the RIPEMD160 hash is between a3 and cf. This includes the address which is generated from the passphrase "just let the lovin take ahold" (first byte is b0). If the addresses were truly random, you would expect a much wider distribution over 101 values, but only 9 values fall outside of that cluster. So there's some kind of filtering going on, for whatever reason.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on June 27, 2019, 08:36:15 AM
So there's some kind of filtering going on, for whatever reason.
My guess: someone created a list of addresses, sorted it, and copied a part of it to be funded. I don't think there's much more behind it.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 27, 2019, 09:24:09 AM
So there's some kind of filtering going on, for whatever reason.
My guess: someone created a list of addresses, sorted it, and copied a part of it to be funded. I don't think there's much more behind it.

Occam's razor? I guess so, although it would seem more likely if only a single address (say, for change) was the odd one out.

Just for fun, I quickly hacked together something to generate four random words and filter the output so that the first bytes of the address are b0, 9a, 09 (which match the last passphrase I mentioned in this thread). The same could be done with real-world phrases if you had a sufficient number of them. A crude form of SHA256 brainwallet vanity address generation.

1H6nTM5TVQc31YqhVzVPrRUmNsL9pGJAwV b09a091fccb7e1f2f0a8120f3e17117a79759920 "captaining financial conservatism mayonnaise"

1H6nTPYd9sKto7bn7ptVqGWzD3mUdByNMy b09a0947f10d65c58ad6f7bc551b85d6d399b3b5 "gladiator playmates reduction disseminates"

1H6nTZUuqwmwKy6C64UK5jAdZATAMfpasK b09a09e9865339e6a5beabd64682380bd7862fd3 "physicists rottenness displaces processed"


=== ADDED LATER ===

Here's some real-world phrases which happen to match the simple vanity address requirements from above. I forgot about it and left things running for longer than I should have.

1H6nTagcotDzbyM3W3ymWRBRcwuJV1Cpvd b09a09fd11c309d6ae2321406c3cd8540cee9174 "scott and andrea"

1H6nTRxrjZ3PiiPvwLwegQFrtBURsKvjUo b09a096f42e5efd99614509be6625e7c1119b539 "colonel edward mandell house"

1H6nTUtXkLPgU36ufJeVEpTmPvbVGXLypV b09a099ed5ce28e7f241ce53893045ad88d48da3 "never gonna be as big as jesus"

(Note: These are examples from my vanity generation experiment, not actual cracked passphrases.)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: larks500 on June 27, 2019, 11:49:36 AM
What if you add your own personal coding to the obvious phrase?

Lets say, replace all the letters A with B.

For example "cbptbining finbncial conservbtism mbyonnbise" instead of "captaining financial conservatism mayonnaise"

Will it more difficult to get the key?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BurtW on June 27, 2019, 01:24:21 PM
What if you add your own personal coding to the obvious phrase?

Lets say, replace all the letters A with B.

For example "cbptbining finbncial conservbtism mbyonnbise" instead of "captaining financial conservatism mayonnaise"

Will it more difficult to get the key?
I think the point of this entire thread can be summed up as follows:

Give up and use a secure random number generator based on a qualified true random number source of entropy unless you want to lose your Bitcoins.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ABCbits on June 27, 2019, 06:07:26 PM
Will it more difficult to get the key?

Most likely yes, but :
1. It's useless if attacker know you use brainwallet & know this method
2. Unless you write down passphrase for brain wallet, you will forget your passphrase or/and your clever method
3. It's still far less secure than simply use CSPRNG to generate your private key/seed



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: HeRetiK on June 27, 2019, 08:55:05 PM
What if you add your own personal coding to the obvious phrase?

Lets say, replace all the letters A with B.

For example "cbptbining finbncial conservbtism mbyonnbise" instead of "captaining financial conservatism mayonnaise"

Will it more difficult to get the key?


Maybe a bit, but not really.

An attacker with the skills and resources to create and scan a precomputed list of brainwallets based on the most common words and phrases will likely also start scanning the most common permutations eventually.

So it's safer in the sense that the coins will probably only be snatched after a couple of days instead of after a couple of seconds.

Granted, given a long enough passphrase or a complex enough "cipher" your coins should be reasonably secure. However it's hard to guess at which point this is the case, which is why one should resort to more reliable methods. It's probably not at 4-word phrases with single-letter-replacements though.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: larks500 on June 28, 2019, 06:15:23 AM
What if you add your own personal coding to the obvious phrase?

Lets say, replace all the letters A with B.

For example "cbptbining finbncial conservbtism mbyonnbise" instead of "captaining financial conservatism mayonnaise"

Will it more difficult to get the key?
I think the point of this entire thread can be summed up as follows:

Give up and use a secure random number generator based on a qualified true random number source of entropy unless you want to lose your Bitcoins.

Yes. Random key it is the best decision, but problem that it is easy forget this random key. You should keep this random key or feed in other place than your mind, so it is additional risk.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 29, 2019, 01:49:12 AM
Yes. Random key it is the best decision, but problem that it is easy forget this random key.

Forget? Normally human can't even remember number with length above 10, let alone private with 256-bit length (or 64 if  you try to remember HEX format)

I realised the other day that I still remember a few (randomly generated) 10 character passwords that I haven't used for years, and if I put them together, they could form a fairly strong 40 character brainwallet phrase. The difference with those passwords is that they were protecting access to a server, and if I forgot them, I could recover access in some other way (boot with rescue disk, phone call to data centre etc). Different matter if I forgot my brainwallet password.  :o

---------

I've seen someone (I think ryanc) mention before using a combination of a passphrase plus a random (weakish) seed. The seed needs to be printed out and stored somewhere safely. The beauty of this arrangement is that the seed is weak enough to be expendable, but strong enough to add some extra protection against casual hunting. If the seed is lost, you can use a program to brute force it until it finds a match for your brainwallet address. The strength of the seed is chosen so that some time (say one to two days) of brute forcing would be required.

It won't stop an attacker who is focussed specifically on you, but it will add extra protection against people who are just hunting for any passphrase matches.

You could also store some funds using the passphrase alone, using that brainwallet as a canary to alert you that someone has discovered your passphrase. For example:

10 BTC in the brainwallet-with-seed "MYPASSPHRASE_sVjH$4R"

0.1 BTC in the canary brainwallet "MYPASSPHRASE"

Disclaimer: I mention this only out of interest and don't represent that it would necessarily be secure. I don't think SHA256 brainwallets are secure anyway, so...


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: larks500 on June 29, 2019, 08:56:18 AM
Yes. Random key it is the best decision, but problem that it is easy forget this random key.

Forget? Normally human can't even remember number with length above 10, let alone private with 256-bit length (or 64 if  you try to remember HEX format)

You should keep this random key or feed in other place than your mind, so it is additional risk.

To be fair, any option have it's own pros and cons.

But it's most common practice (except we randomly generate xprv/seed) & you probably use this method as well.

Sure. It is absolutely right.

But we are started talking about brain wallets and brain wallet feed could be generated randomly. I can keep in mind 16 random generated words, but  problem that words are already existed and could be generated again.  Good way to change 1 word from this 16 to your own created word.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on June 30, 2019, 09:28:17 AM
I've seen someone (I think ryanc) mention before using a combination of a passphrase plus a random (weakish) seed. The seed needs to be printed out and stored somewhere safely. The beauty of this arrangement is that the seed is weak enough to be expendable, but strong enough to add some extra protection against casual hunting. If the seed is lost, you can use a program to brute force it until it finds a match for your brainwallet address. The strength of the seed is chosen so that some time (say one to two days) of brute forcing would be required.

Interesting idea, while it's far less secure than CSPRNG/PRNG, it's acceptable assuming no one know you use this method.

No, that would be security through obscurity. It's fun to have some cool secret way to generate your key, but if it's too complex, you (or your benefactors, say if you suddenly die) could risk losing the funds.

The point is that if you must use a brainwallet, the random seed will at least make it more secure against untargeted privkey hunters. Remember that each ATTEMPT at brute forcing the passphrase+seed takes 2 days, so in theory, even a reasonably common dictionary word as your passphrase could take years to crack. (In practice, a cracker is going to be using multiple cores and possibly optimised cracking methods, so it will take less time.)

Multiple seeds can be used, for example:

1. Seed #0, which is an internal seed that is not disclosed or stored. This must be brute forced when re-generating the private key, so it is quite weak. It is intended as some extra protection against an attack.
2. Seed #1 (stored in one location) which takes ~1 day to brute force if lost.
3. Seed #2 (stored in another location) which takes ~1 day to brute force if lost.

If the user has the passphrase, seed #1, and seed #2, all it takes is (say) 60 seconds to brute force the internal seed, and generate the correct privkey.

If the user loses either of the seeds, it takes 60 seconds + 1 day.

If the user loses both seeds, it takes 60 seconds + 1 day + 1 day.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 07, 2019, 10:44:34 PM
Nearly $2k USD blown by sending to a very weak key (7b7)

Swiped quickly, with about $USD400 paid to the miner which incorporated the transaction.

I really hope this was deliberate.  ???

https://www.blockchain.com/btc/address/02b443fb5654d5fb6323dff432b90f6e204b9676


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 14, 2019, 12:25:40 AM
This one is unusual because:

1. It was sent around 3 months ago to a seemingly random passphrase (looks like a 21 letter keyboard bash), but that passphrase appears in a password list from 2012.
2. This time it was a whopping 1 BTC ($USD 4k at the time), swiped immediately.

Why was 1 BTC sent, in 2019, to a brain wallet using a passphrase that's been known for 7+ years?

Because of the large amount and recent transaction, I won't reveal the passphrase publicly, but I'm sure there's a few people reading this that who know it. And there's at least one bot that does...

https://www.blockchain.com/btc/address/af867f1c5287676c97dfc402e3e642ac97652670


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: avw on July 15, 2019, 04:23:28 PM
also ran some checking on the old style electrum seeds with a "modified" word list...
What is "old style" different from the new?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 22, 2019, 06:52:47 AM
Multiple seeds can be used, for example:

1. Seed #0, which is an internal seed that is not disclosed or stored. This must be brute forced when re-generating the private key, so it is quite weak. It is intended as some extra protection against an attack.
2. Seed #1 (stored in one location) which takes ~1 day to brute force if lost.
3. Seed #2 (stored in another location) which takes ~1 day to brute force if lost.

If the user has the passphrase, seed #1, and seed #2, all it takes is (say) 60 seconds to brute force the internal seed, and generate the correct privkey.

If the user loses either of the seeds, it takes 60 seconds + 1 day.

If the user loses both seeds, it takes 60 seconds + 1 day + 1 day.

Was thinking about this again today, and I've found a flaw in the above. I believe the total effort required to cover the search space is actually the product of the effort per seed, rather than the sum. This is because there's no way to know if you've correctly found a match for a single seed. The complete passphrase+seed+seed+seed combination is either matched, or not matched; there's no way to match a part of it.

In other words, if you lose both seeds, it will take 60 x 86400 x 86400 seconds (5,184,000 days) to brute force all possibilities, not 60 + 86400 + 86400 (2 days and 60 seconds).

To be able to independently crack a lost seed would require additional external validation, such as a hash of each seed stored in the blockchain.

Just wanted to update the above idea to point out that multiple seeds won't work as expected. A single seed would still work, since there's only one unknown part to force if it is lost.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: igordata on July 23, 2019, 10:04:07 AM
If the user has the passphrase, seed #1, and seed #2, all it takes is (say) 60 seconds to brute force the internal seed, and generate the correct privkey.

why do we need #0 if it's so easy to brute force it then?

If the user loses either of the seeds, it takes 60 seconds + 1 day.
no, if you loses both seeds you die :D

Edit: yep, if I lose one of #1 or #2 seeds it gonna take a month to brute force it of a couple of weeks with 50% probability if I'm lucky guy.
If I lose both seeds I'm in the deep trouble even if I'm extremely lucky.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 23, 2019, 11:36:25 AM
If the user has the passphrase, seed #1, and seed #2, all it takes is (say) 60 seconds to brute force the internal seed, and generate the correct privkey.

why do we need #0 if it's so easy to brute force it then?

Shrug. I guess as some extra protection if the two main seeds (which would need to be printed out or stored somewhere) are recovered by an attacker.

Without seed #0 the attacker would only need to bruteforce the passphrase, but by requiring the additional (unknown) seed the work is increased by a factor of at least a few million.

Disclaimer: I'm not a cryptographer, so I freely admit these ideas are probably a little crazy.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: igordata on July 24, 2019, 04:46:49 PM
OK, you're right. We have a passphrase and without #0 it is just a millisecond to try. With #0 each passphrase will take a minute to try.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on July 24, 2019, 09:59:37 PM

Multiple seeds can be used, for example:

1. Seed #0, which is an internal seed that is not disclosed or stored. This must be brute forced when re-generating the private key, so it is quite weak. It is intended as some extra protection against an attack.
2. Seed #1 (stored in one location) which takes ~1 day to brute force if lost.
3. Seed #2 (stored in another location) which takes ~1 day to brute force if lost.

If the user has the passphrase, seed #1, and seed #2, all it takes is (say) 60 seconds to brute force the internal seed, and generate the correct privkey.

If the user loses either of the seeds, it takes 60 seconds + 1 day.

If the user loses both seeds, it takes 60 seconds + 1 day + 1 day.

I wold like to point out that your times are correct only if the user has a way to know that an individual seed has has been cracked. Otherwise, you must multiply the number of attempts rather than add them.

Edit: Oh, I see that you have already arrived at that conclusion.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 25, 2019, 01:56:30 AM
[...] If the user loses both seeds, it takes 60 seconds + 1 day + 1 day.

I wold like to point out that your times are correct only if the user has a way to know that an individual seed has has been cracked. Otherwise, you must multiply the number of attempts rather than add them.

Edit: Oh, I see that you have already arrived at that conclusion.

You're the second person to point this out after I corrected myself. ;)

You could store hash(passphrase+seedX) in the blockchain so that the brainwallet client can figure out when it has cracked the seed, but that means an attacker also has that clue. Not such a good idea: now an attacker can hunt for hash(passphrase+seedX) matches to discover seeds with weak passphrases, and once they find two different seeds with the same passphrase, they're less than 60 seconds away from finding a private key.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: igordata on July 25, 2019, 09:31:20 AM
> hash(passphrase+seedX)

that operation reduces security due to attacker can brute force quicker with a single hash iteration


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TechPriest on July 25, 2019, 06:58:37 PM
I've seen someone (I think ryanc) mention before using a combination of a passphrase plus a random (weakish) seed. The seed needs to be printed out and stored somewhere safely. The beauty of this arrangement is that the seed is weak enough to be expendable, but strong enough to add some extra protection against casual hunting. If the seed is lost, you can use a program to brute force it until it finds a match for your brainwallet address. The strength of the seed is chosen so that some time (say one to two days) of brute forcing would be required.

Interesting idea, while it's far less secure than CSPRNG/PRNG, it's acceptable assuming no one know you use this method.

No, that would be security through obscurity. It's fun to have some cool secret way to generate your key, but if it's too complex, you (or your benefactors, say if you suddenly die) could risk losing the funds.

The point is that if you must use a brainwallet, the random seed will at least make it more secure against untargeted privkey hunters. Remember that each ATTEMPT at brute forcing the passphrase+seed takes 2 days, so in theory, even a reasonably common dictionary word as your passphrase could take years to crack. (In practice, a cracker is going to be using multiple cores and possibly optimised cracking methods, so it will take less time.)

Multiple seeds can be used, for example:

1. Seed #0, which is an internal seed that is not disclosed or stored. This must be brute forced when re-generating the private key, so it is quite weak. It is intended as some extra protection against an attack.
2. Seed #1 (stored in one location) which takes ~1 day to brute force if lost.
3. Seed #2 (stored in another location) which takes ~1 day to brute force if lost.

If the user has the passphrase, seed #1, and seed #2, all it takes is (say) 60 seconds to brute force the internal seed, and generate the correct privkey.

If the user loses either of the seeds, it takes 60 seconds + 1 day.

If the user loses both seeds, it takes 60 seconds + 1 day + 1 day.

That is very compicated, really. Also, if noone doesn't know your passphrase you shouldn't afraid seed compomising. Because the fact of knowing your seed can't help to hacker.

If you afraid that your passphrase will be brute forced or social hacked (as we know, people's brain provides very low enthropy) , then i have some interesting algorithm for you:

1. Create easy master passphrase you always will remember.
2. Create your own algorithm of lower passphrase derivation. It can be like:
Code:
SHA2/RIPEMD-160(my-master-passphrase-that-I-always-remember + "1")
SHA2/RIPEMD-160(my-master-passphrase-that-I-always-remember + "2")
.......
3. Use result as passphrase (following BIP39) for specific wallet. (for wallet 1 - passphrase1 + 12/24 seed)
That's it. You can use different wallets for different purposes without fear your wallets being linked (like addresses in one wallet).
Also, while only you know derivation algorithm no one can get access to your wallets even seed or/and master-passphrase compomised.
You can store your seed without any protection, you can put it into the bank or write on paper.

To hack all your wallets, hacker needs to know your seed + master-passphrase + derivation algorithm. It's not so easy to hack such protection.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 31, 2019, 04:53:29 PM
https://www.blockchain.com/btc/address/1d923c954d8901d559f1262fec66ed08fdac73cb

Value of around $USD 55 swept immediately.

At least one of the inputs in the funding transaction appears to be an exchange hot wallet (1NDyJtNTjmwk5xPNhjgAMu4HDHigtobu1s, which has nearly half a million transactions [edit: this is a Binance wallet -> https://twitter.com/binance/status/961666467325358081]). Are people still deliberately withdrawing funds to brainwallets?

The passphrase is "weadmittedwewerepowerlessoveralcoholthatourliveshadbecomeunmanageable" which appears to be the text (sans spaces) of the first step in the 12 step Alcoholics Anonymous program.

It amazes me how obscure passphrases are still swept away almost immediately. The cracking that I do for fun represents literally months of CPU time and trillions of candidate passphrases. At full tilt my i7 can push out about 43 billion passphrases per day, which would require over 1TB of storage per day if saved permanently.

People running stealer bots must have massive databases of pre-computed candidate passphrases.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: itod on August 01, 2019, 08:17:40 AM
Are people still deliberately withdrawing funds to brainwallets?

Brainwallets were the worst idea from the beginning, but for some mysterious reason they are attractive to newbies. There s something in the human psychology, I guess the simplicity of the solution and the masochistic aspect torturing themselves to remember long passphrases and the risk they may forget it which has an allure off challenge. There is also an aspect they do not get the math and reasoning behind reliable alternatives, like Bitcoin Core wallet, that turns them away from better alternatives.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on August 01, 2019, 10:58:45 AM
Brainwallets were the worst idea from the beginning
There are 2 problems:
1. Anyone can search all existing brainwallets at the same time
2. It doesn't require much CPU-power to test a password

Without promoting brainwallets, I could think of several solutions:
1. If you add something unique to you to a brainwallet, it's  much less likely to be found. Say I would add LoyceValenzuela to this:
"weadmittedwewerepowerlessoveralcoholthatourliveshadbecomeunmanageable"
That would make:
weadmittedwewerepowerlessoveralcoholthatourliveshadbecomeunmanageableLoyceValen zuela and instantly adds many more possibilities to the search space than "just" searching all available digital text on the planet. Or add your phone number.
It's not perfect, but it makes it several orders of magnitude less likely to be brute-forced.

2. The protocol should use CPU-intensive encryption like BIP38 uses. That reduces the number of tries per second from billions to dozens.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Welsh on August 01, 2019, 12:21:10 PM
Brainwallets were the worst idea from the beginning
They're flawed due to the fact that they're easy to bruteforce, and test different password combinations on without any sort of limit. However, a brainwallet is as secure as the user makes it. As LoyceV points out putting unique information within a sentence instantly makes it more difficult to crack. Common passwords for brainwallets used to be sentences from books, and I think there was a pretty famous one which used a random page in the Lord Of The Rings books. I've never used a brainwallet, and would recommend against them just for the sole reason that they can be attacked easier than most other ways of storing Bitcoin.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: itod on August 01, 2019, 05:23:38 PM
Brainwallets were the worst idea from the beginning
...
1. If you add something unique to you to a brainwallet, it's  much less likely to be found. Say I would add LoyceValenzuela to this:
"weadmittedwewerepowerlessoveralcoholthatourliveshadbecomeunmanageable"
That would make:
weadmittedwewerepowerlessoveralcoholthatourliveshadbecomeunmanageableLoyceValen zuela and instantly adds many more possibilities to the search space than "just" searching all available digital text on the planet. Or add your phone number.
It's not perfect, but it makes it several orders of magnitude less likely to be brute-forced.
...

Don't do this, there is no need for it. Just use regular high quality wallet like Bitcoin Core wallet and you will get incomparably more secure private keys without the need for any mental gymnastics. The quality wallets get their entropy from the hardware layer beneath, not from something humans can think of.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: malevolent on August 01, 2019, 08:14:19 PM
2. The protocol should use CPU-intensive encryption like BIP38 uses. That reduces the number of tries per second from billions to dozens.

Most commonly used brainwallets, i.e. single round unsalted SHA-256 are a terrible idea leading to loss of funds for many users, but something like a warpwallet isn't too bad if someone's really set on using a brainwallet:

https://keybase.io/warp

Using a salt should still be recommended though.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on August 13, 2019, 08:43:04 AM
Now for something a little different:

https://www.blockchain.com/btc/address/674239f32cd4041965f3a9e1fdeb09356f07887a

Passphrase: ประวิตร วงษ์สุวรรณ

According to Google this is Thai, and translates to "Wittawong Suwan" but I think the correct (Westernised) translation is Prawit Wongsuwan, who is a General that became the Deputy Prime Minister after a 2014 coup. He seems to be fond of expensive watches.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: rosengold on August 30, 2019, 10:07:05 PM
Don't let this list dies  ;D

https://www.blockchain.com/btc/address/1KTtPr67kxRu1MTk5FyqQj1Q8xT95KCFMP (https://www.blockchain.com/btc/address/1KTtPr67kxRu1MTk5FyqQj1Q8xT95KCFMP)

Quote
Bitcoin: A Peer-to-Peer Electronic Cash System

Thanks for that coffee  :P


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on August 31, 2019, 10:23:56 AM
Don't let this list dies  ;D

https://www.blockchain.com/btc/address/1KTtPr67kxRu1MTk5FyqQj1Q8xT95KCFMP (https://www.blockchain.com/btc/address/1KTtPr67kxRu1MTk5FyqQj1Q8xT95KCFMP)

Quote
Bitcoin: A Peer-to-Peer Electronic Cash System

Thanks for that coffee  :P

Some other variations:

Peer to Peer Electronic Cash System
Peer-to-Peer Electronic Cash (on testnet)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 09, 2019, 09:25:23 AM
0.4995 BTC rested in this brainwallet for about a week:

https://www.blockchain.com/btc/address/1NibpGrUoUd9ywXm5Q2Zx5w12pZN3V3z8G

Since the transactions are so recent, I am not going to disclose the passphrase, but let's just say that it's the title of something. Not super weak, but not exactly secure, especially when you're sending half a Bitcoin to it. Don't know if the rightful owner took the funds, or they were stolen, but if I can find it, so can someone else.

The chain of transactions leading up to the one funding this address look interesting, can anyone better at exploring blockchains than I am offer an explanation?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 15, 2019, 05:02:03 PM
This brain wallet hasn't been used for several years, but even back in 2013 it held a substantial amount of funds (USD $6k+), protected by a weak passphrase:

https://www.blockchain.com/btc/address/16jLdtAxgXVwcG93MyPcNALXMCv3D6dyDB

The passphrase is "arretonprimaryschool"


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 17, 2019, 06:13:02 AM
An idea I came up with today: using a standard wallet file (must be encrypted) to create a hidden "brainwallet" private key.

These help protect the hidden key:

1. You need access to the wallet file; an attack would need to be targeted.
2. You need the password to unlock the wallet; that's the brain part.
3. There is no external indication that the hidden key exists.

To create the hidden key:

1. Combine all unencrypted private keys in the wallet in some way (eg SHA256 hash of concatenated keys)
2. For additional bruteforce protection, stretch the new key.

But here's the cool part: the wallet can be completely cleared of all funds, either before or after you create the new key. This means that if anyone does gain access to the wallet file, all they see is a wallet with no balance (this can be seen without needing the wallet password). Even if they suspect you may be using a hidden key, they cannot regenerate it unless they know the password to decrypt the wallet.

tl;dr you can create a hidden key from a wallet with zero balance that anyone poking around your file system will probably ignore.

Thoughts?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on September 17, 2019, 08:13:53 AM
These help protect the hidden key:

1. You need access to the wallet file; an attack would need to be targeted.
2. You need the password to unlock the wallet; that's the brain part.
3. There is no external indication that the hidden key exists.

To create the hidden key:

1. Combine all unencrypted private keys in the wallet in some way (eg SHA256 hash of concatenated keys)
2. For additional bruteforce protection, stretch the new key.

But here's the cool part: the wallet can be completely cleared of all funds, either before or after you create the new key. This means that if anyone does gain access to the wallet file, all they see is a wallet with no balance (this can be seen without needing the wallet password). Even if they suspect you may be using a hidden key, they cannot regenerate it unless they know the password to decrypt the wallet.

tl;dr you can create a hidden key from a wallet with zero balance that anyone poking around your file system will probably ignore.

I feel like that is about equivalent to a password-protected wallet with a sprinkle of additional cleverness thrown in.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 19, 2019, 02:27:12 AM
This address is kind of related to brainwallets:

https://www.blockchain.com/btc/address/1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E

Current balance is 72.13442756 BTC.

The classic brainwallet is created with ripemd160(sha256(pubkey(sha256("passphrase")))), but this address is the result of ripemd160(sha256(""))

I don't know if it's a broken brainwallet generator, or just a broken wallet. Possibly the latter, with the wallet mistakenly hashing a zero length buffer, instead of hashing the pubkey.

Any funds sent here are permanently lost, because there's no private key involved in the address generation process. Despite this, nearly $15k USD worth of Bitcoin has been sent there in the past 12 months!

https://github.com/bitcoin/bitcoin/issues/445

I think it would be a good idea if wallet software included a blacklist of such addresses, as well as known weak brainwallets, showing an additional dialog with a strong warning that funds may be permanently lost (or stolen) if the transaction proceeds. Checking any generated (inbound) addresses against the list would also help catch any glaring address generation bugs. (An assert that the result must not equal <hash of empty string> after each call to sha256 or ripemd160 would have caught this error.)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on October 14, 2019, 06:46:46 PM
https://www.blockchain.com/btc/address/b09a09458fe9bb86b0d897b4c244b05432bad28d

This one is interesting for a number of reasons...

- It seems to be a relatively early use of a SHA256 brainwallet (January 2012).

- The transaction originally funding this brainwallet split 1 BTC into neat sets of 0.001 and 0.005 BTC. Could other outputs from this transaction - there are 101 in total - also be brainwallets, or some other kind of special address? Some are still unspent, 7.5 years later.

- A second set of funds (6.08 BTC) was sent a couple of weeks later, then all funds were swept the following year. Over time, the value of 6.08 BTC appreciated from around $USD 35 in February 2012, to almost $USD 600 in July 2013. (The sweep output is still unspent; 6.08 BTC is now worth nearly $60,000. Hope the owner still has the privkey!)

The passphrase is just let the lovin take ahold


I think there are still many many more to be found out there my guess.
Interesting find on the 6 words are those song lyrics by any chance?

Yes, that was a song ) Have a look since 1:01
https://youtu.be/JBCJKbLhHwU?t=60

By the way, interesting way to promote the singer  ;D Put some words of the song as the passphrase to the private key and make transactions with that wallet!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on October 14, 2019, 07:56:14 PM
This address is kind of related to brainwallets:

https://www.blockchain.com/btc/address/1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E

Current balance is 72.13442756 BTC.

The classic brainwallet is created with ripemd160(sha256(pubkey(sha256("passphrase")))), but this address is the result of ripemd160(sha256(""))

Can you clarify please?
sha256("") is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
ripemd160(sha256("")) is ba084d3f143f2896809d3f1d7dffed472b39d8de

And this is the hash160 of another address with the balance 0.000928 BTC: https://www.blockchain.com/btc/address/1HxedVkdFALLtLzqKFfDBzPyZRLq7QKbm5 (https://www.blockchain.com/btc/address/1HxedVkdFALLtLzqKFfDBzPyZRLq7QKbm5)

I don't know if it's a broken brainwallet generator, or just a broken wallet. Possibly the latter, with the wallet mistakenly hashing a zero length buffer, instead of hashing the pubkey.

Any funds sent here are permanently lost, because there's no private key involved in the address generation process. Despite this, nearly $15k USD worth of Bitcoin has been sent there in the past 12 months!

I guess that these funds lost like some other funds on the address with the lost private keys. As there are in average 2^96 possible private keys for every bitcoin hash160 address, so some "other" private key could fit the address you mentioned.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 14, 2019, 10:16:48 PM
This address is kind of related to brainwallets:

https://www.blockchain.com/btc/address/1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E

Current balance is 72.13442756 BTC.

The classic brainwallet is created with ripemd160(sha256(pubkey(sha256("passphrase")))), but this address is the result of ripemd160(sha256(""))

Can you clarify please?
sha256("") is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
ripemd160(sha256("")) is ba084d3f143f2896809d3f1d7dffed472b39d8de

And this is the hash160 of another address with the balance 0.000928 BTC: https://www.blockchain.com/btc/address/1HxedVkdFALLtLzqKFfDBzPyZRLq7QKbm5 (https://www.blockchain.com/btc/address/1HxedVkdFALLtLzqKFfDBzPyZRLq7QKbm5)

ba084d3f143f2896809d3f1d7dffed472b39d8de is the result when you provide e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 to the input of RIPEMD160 as a hex representation (in ASCII characters), but it should be raw bytes.

In other words, you've calculated ripemd160(hex_display_string(sha256(""))

Unsure how to do it with Linux (there's no RIPEMD160 application on my Ubuntu install) but under BSD this will convert the hex output of the SHA256 commandline application to raw bytes, so that the correct RMD160 value is calculated:

$ cat /dev/null | sha256 | xxd -r -p | rmd160
b472a266d0bd89c13706a4132ccfb16f7c3b9fcb



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on October 15, 2019, 12:03:25 AM
Can you clarify please?
sha256("") is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
ripemd160(sha256("")) is ba084d3f143f2896809d3f1d7dffed472b39d8de

And this is the hash160 of another address with the balance 0.000928 BTC: https://www.blockchain.com/btc/address/1HxedVkdFALLtLzqKFfDBzPyZRLq7QKbm5 (https://www.blockchain.com/btc/address/1HxedVkdFALLtLzqKFfDBzPyZRLq7QKbm5)

ba084d3f143f2896809d3f1d7dffed472b39d8de is the result when you provide e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 to the input of RIPEMD160 as a hex representation (in ASCII characters), but it should be raw bytes.

In other words, you've calculated ripemd160(hex_display_string(sha256(""))

Unsure how to do it with Linux (there's no RIPEMD160 application on my Ubuntu install) but under BSD this will convert the hex output of the SHA256 commandline application to raw bytes, so that the correct RMD160 value is calculated:

$ cat /dev/null | sha256 | xxd -r -p | rmd160
b472a266d0bd89c13706a4132ccfb16f7c3b9fcb


Yes, right, thank you. I made a quick check with the online tool, and of course it pushed ascii characters, not bytes.
Made the test on python and receieved the same value ass yours:

Code:
>>> import hashlib
>>> sha = hashlib.sha256()
>>> sha.update(bytearray.fromhex(""))
>>> rip = hashlib.new('ripemd160')
>>> rip.update (sha.digest())
>>> print (rip.hexdigest())
b472a266d0bd89c13706a4132ccfb16f7c3b9fcb
>>>

However, making this "small mistake" I found another not empty brain wallet with the small balance  ;)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 15, 2019, 04:01:23 AM
However, making this "small mistake" I found another not empty brain wallet with the small balance  ;)

Yes, at least one other person (or program) made the same mistake. :) Hopefully a bug which was quickly noticed, since those funds are also unspendable.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: bartekjagoda on October 15, 2019, 03:32:32 PM
Hi,

As been discussed many times before using a Brainwallet is a bad idea. I ran some test myself and found 18.509 BTC-addresses based on a brainwallet which also has been used in the blockchain before.

I tried to compare my results with the results of other researchers but could not find any lists online at all. I found some examples but not a comprehensive list. So I published my own results over here: https://eli5.eu/brainwallet

Please note: all published addresses have a balance of 0 so this is not a list for robbers :). There are also a lot of extra datasets I haven't used this far so I expect the numbers to go up once I use them as well (I'm in the middle of perfecting my own tooling and blockchain parser so this will take some more time first).

I love to get some feedback and if you have results to share which I missed in this round I'm more than happy to hear from you and include them.

TA

Do you have a repo for the code??


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 28, 2019, 04:40:22 PM
I wrote a program to create a simple mapping for the brainwallet passphrases I've cracked. Here are the most common mappings.

A=capital letter
a=lowercase letter
d=digit
p=punctuation
?=other

First field is the number of times this mapping appears in the passphrase list.

5327 > aaaaaaaaa
4145 > aaaaaaaaaa
2847 > aaaaaaaaaaa
1781 > aaaaaaaaaaaa
1081 > aaaaaaaaaaaaa
 784 > Aaaaaaaaa
 518 > aaaaaaaaaaaaaa
 475 > Aaaaaaaaaa
 280 > aaaaaaaaaaaaaaa
 244 > Aaaaaaaaaaa
 122 > Aaaaaaaaaaaa
 113 > aaaaaaaaaaaaaaaa
  89 > aaaaaa
  87 > aaaaa
  85 > aaaaaaaadd
  75 > aaaaaaa
  72 > aaaa
  66 > Aaaaaaaaaaaaa
  64 > aaaaaaaaaaaaaaaaa
  56 > aaaaaaaa
  43 > aaaaaaaaaaaaaaaaaa
  41 > Aaaaaaaaaaadd
  38 > aaaaaaaaddd
  38 > Aaaaaaaaaaaaaa
  34 > aaa
  27 > Aaaaaaaaaaaaaaa
  20 > dddddddddd
  18 > aaaaaaaad
  17 > aaaaaaaaaaaaaaaaaaaa
  17 > aaaaaaaaaaaaaaaaaaa
  16 > Aaaaaaaaaaaaaaaa
  15 > Aaaa
  13 > Aaaaaaa
  13 > AaAaaaaaa
  12 > dddddd
  12 > Aaaaaaaa
  12 > Aaaaa
  11 > dddddddd
  11 > dddd
  11 > Aa Aaaaadd
  10 > aaaaaaaaad
  10 > aaaaaaaaaaaaaad
   9 > aaaaa aaaaa
   9 > Aaaaaaaaaaad
   9 > Aa Aaaaad
   9 > AAAAA Ad
   8 > ddd
   8 > aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
   8 > aaaaaaaaaaaaaaaaaaaaa
   7 > aaaaadddd
   7 > aaaaaaaaaaaaaaaaaaaaaaaa
   7 > aaaaa aaaaaa
   7 > Aaaaaa
...


The large majority (shown in the first several lines) would be the dust sent to several dictionary words, which isn't very interesting.

There's some more interesting ones further down, like aaaaaaaadd, Aaaaaaaaaaadd, AAAAA Ad, etc. At the bottom you see the long tail where passphrases are unique sentences:

   1 > aaaa aa aaa aaaaaaaa aaaa aaa aaaaaaa aa aaaaaaaa aaa aaaa
   1 > aaaa aa aaa aaaaaaaa aaaa aaa aaaaaaa aa aaaaaaaa aaa
   1 > aaaa aa aaa aaaaaaaa aaaa aaa aaaaaaa aa aaaaaaaa
   1 > aaaa aa aaa aaaaaaaa aaaa aaa aaaaaaa aa
   1 > aaaa aa aaa aaaaaaaa aaaa aaa aaaaaaa
   1 > aaaa aa aaa aaaaaaaa aaaa aaa
   1 > aaaa aa aaa aaaaaaaa aaaa
   1 > aaaa aa aaa aaaaaaaa
   1 > aaaa aa aaa aaaaaa
   1 > aaaa aa aaa aaaa aaa aa aaa aaaaaaaaa
   1 > aaaa aa aaa aaaa aaa aa aaa aaaaaaaa
   1 > aaaa aa aaa aaaa aaa aa aaa aaaaaa
   1 > aaaa aa aaa aaaa aaa aa aaa aaaa


Probably not much practical use - even if filtered using this mapping the brute force search space would still be impossibly large - but it's interesting...


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on October 28, 2019, 04:45:38 PM
I wrote a program to create a simple mapping for the brainwallet passphrases I've cracked. Here are the most common mappings.

A=capital letter
a=lowercase letter
d=digit
p=punctuation
?=other
I assume this mapping is mainly based on the brute-force method used: I assume it didn't search for just random strings, so for example ??d?pa???A? doesn't show up becasue it was never found!
Am I right?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 29, 2019, 01:30:20 AM
I wrote a program to create a simple mapping for the brainwallet passphrases I've cracked. Here are the most common mappings.

A=capital letter
a=lowercase letter
d=digit
p=punctuation
?=other
I assume this mapping is mainly based on the brute-force method used: I assume it didn't search for just random strings, so for example ??d?pa???A? doesn't show up becasue it was never found!
Am I right?

It's a mapping of passphrases that were already found (by other methods). Really just a visualization of what was previously discovered.

The other mapping characters do appear lower in the list:


...
   4 > AAAAAAAAAd
   4 > ??????????
   4 > ?????????
...
   2 > a aaaa ?? aaaaa aaaa
...
   1 > pppAaaa aaaaa pppAaaaappp pa??a??a??a??a??p
   1 > Aa aaa aaaappp ???p??d??p??? pp???


The latter mapping represents the passphrase "To the moon!!! ┗(°0°)┛ ..○" -> https://www.blockchain.com/btc/address/18vqVNQi9fobKZcJWCjZNoDzBxronENfZr


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on October 29, 2019, 08:34:36 PM
I assume this mapping is mainly based on the brute-force method used: I assume it didn't search for just random strings, so for example ??d?pa???A? doesn't show up becasue it was never found!
Am I right?

It's a mapping of passphrases that were already found (by other methods). Really just a visualization of what was previously discovered.

I think he is asserting that your results are filtered by the search algorithms because results that aren't found by the search algorithms won't be in the list, and changing the the algorithms will change the list. It would similar to the difference between lists based on cracked passwords and lists based on leaked passwords.

The latter mapping represents the passphrase "To the moon!!! ┗(°0°)┛ ..○" -> https://www.blockchain.com/btc/address/18vqVNQi9fobKZcJWCjZNoDzBxronENfZr

That is another great example showing how a brain wallet is not secure.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on October 30, 2019, 02:18:00 AM
-snip-
The latter mapping represents the passphrase "To the moon!!! ┗(°0°)┛ ..○" -> https://www.blockchain.com/btc/address/18vqVNQi9fobKZcJWCjZNoDzBxronENfZr
That is another great example showing how a brain wallet is not secure.

The most examples with brain wallets are related to small amounts. There were some large amounts, but only in the very past. All the recent disclosed and found wallets are just very small.
For example this one with "To the moon!!! ┗(°0°)┛ ..○" passphrase had only 0.000006 BTC in transactions.

So there is one explanation for this: the address was used just for test/education/presentation purposes. Nothing serious. The same is with all the majority of brain wallets. Morover, the funds on "to the moon" address (18vqVNQi9fobKZcJWCjZNoDzBxronENfZr) stored only for 9 hours, and after that were transferred togeter with other 60 addresses to new address. The majority were small amounts like 256 satoshi. So, somebody made experiments with the transactions, or these were the activities of a bot.

I do not beleive that somebody keeps real funds on brain wallet.

Interesting thing: the  destination address of 600 satoshis released from "To the moon!!! ┗(°0°)┛ ..○" still has the balance 22.32BTC (https://www.blockchain.com/btc/address/1AzRkXiGpHbXyWok4uXvCzmezDuW8FGa3m). Who knows, may be this was not just experiment but another puzzle? ) Like you need to find all the passphrases for small released wallets in order to understand the main key.

PS. Look at this: https://www.youtube.com/watch?v=KBX89TY6uXI


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on October 30, 2019, 10:07:26 PM
-snip-
The latter mapping represents the passphrase "To the moon!!! ┗(°0°)┛ ..○" -> https://www.blockchain.com/btc/address/18vqVNQi9fobKZcJWCjZNoDzBxronENfZr
That is another great example showing how a brain wallet is not secure.

The most examples with brain wallets are related to small amounts. There were some large amounts, but only in the very past. All the recent disclosed and found wallets are just very small.
For example this one with "To the moon!!! ┗(°0°)┛ ..○" passphrase had only 0.000006 BTC in transactions.

I agree that a lot of recent brainwallet activity seems to be just for curiosity and fun, but I'm still finding the occasional large transaction.

- March 2019: 1 BTC sent to a 21 character passphrase that appears in cracked/leaked password lists. https://bitcointalk.org/index.php?topic=4768828.msg51813899#msg51813899

- June 2019: 0.25 BTC sent to weak key 0x7b7. https://bitcointalk.org/index.php?topic=4768828.msg51745655#msg51745655

- August 2019: 0.4495 BTC stayed for just over a week in a brainwallet which has a title for the passphrase. Subsequently another 0.01 was sent and it seems to have been swept immediately. https://bitcointalk.org/index.php?topic=4768828.msg52403221#msg52403221



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on October 30, 2019, 11:39:22 PM
-snip-
The latter mapping represents the passphrase "To the moon!!! ┗(°0°)┛ ..○" -> https://www.blockchain.com/btc/address/18vqVNQi9fobKZcJWCjZNoDzBxronENfZr
That is another great example showing how a brain wallet is not secure.

The most examples with brain wallets are related to small amounts. There were some large amounts, but only in the very past. All the recent disclosed and found wallets are just very small.
For example this one with "To the moon!!! ┗(°0°)┛ ..○" passphrase had only 0.000006 BTC in transactions.

I agree that a lot of recent brainwallet activity seems to be just for curiosity and fun, but I'm still finding the occasional large transaction.

- March 2019: 1 BTC sent to a 21 character passphrase that appears in cracked/leaked password lists. https://bitcointalk.org/index.php?topic=4768828.msg51813899#msg51813899

- June 2019: 0.25 BTC sent to weak key 0x7b7. https://bitcointalk.org/index.php?topic=4768828.msg51745655#msg51745655

- August 2019: 0.4495 BTC stayed for just over a week in a brainwallet which has a title for the passphrase. Subsequently another 0.01 was sent and it seems to have been swept immediately. https://bitcointalk.org/index.php?topic=4768828.msg52403221#msg52403221

Yes, this is noted and clear for me. I agree that 0.5-1BTC is a valuable amount. However people could play with different amounts. For example, ones will play with 100-1,000 satoshi, and others will play with 0.1-1BTC. Play money are different for different people.

And yes, 0.5-1BTC is real "digital riches" for ones and only play funds for others. I still do not beleive that somebody keeps real funds on brain wallet. Even that somebody put 0.5BTC to brain wallet, these fund are not real funds for him, but only play money.

Anyway, thank you for sharing your findings!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: iparktur on November 03, 2019, 08:49:29 PM
-snip-
The latter mapping represents the passphrase "To the moon!!! ┗(°0°)┛ ..○" -> https://www.blockchain.com/btc/address/18vqVNQi9fobKZcJWCjZNoDzBxronENfZr
That is another great example showing how a brain wallet is not secure.

The most examples with brain wallets are related to small amounts. There were some large amounts, but only in the very past. All the recent disclosed and found wallets are just very small.
For example this one with "To the moon!!! ┗(°0°)┛ ..○" passphrase had only 0.000006 BTC in transactions.

I agree that a lot of recent brainwallet activity seems to be just for curiosity and fun, but I'm still finding the occasional large transaction.

- March 2019: 1 BTC sent to a 21 character passphrase that appears in cracked/leaked password lists. https://bitcointalk.org/index.php?topic=4768828.msg51813899#msg51813899

- June 2019: 0.25 BTC sent to weak key 0x7b7. https://bitcointalk.org/index.php?topic=4768828.msg51745655#msg51745655

- August 2019: 0.4495 BTC stayed for just over a week in a brainwallet which has a title for the passphrase. Subsequently another 0.01 was sent and it seems to have been swept immediately. https://bitcointalk.org/index.php?topic=4768828.msg52403221#msg52403221



Hi almightyruler  !

Can you send me PM ?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on December 03, 2019, 01:23:11 AM
A small amount sent by someone making a statement:

https://www.blockchain.com/btc/address/15h4F5yxeJHDgDJR5dnJwsNbETpktMnQzm

"Nick Szabo is Satoshi Nakamoto"


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Danydee on December 04, 2019, 09:20:44 PM
 Using the bitaddress.org donations address ( 1NiNja1bUmhSoTXozBRBEtR8LeF9TGbZBN ) on the passphrase field of the brainWallet generate the address ( 1Ns55SngRhshA8kEnyuQ9ELZZPN7ubYfQJ ) wich contain some small transactions !  :o


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: naska21 on December 07, 2019, 07:41:44 AM
A small amount sent by someone making a statement:

https://www.blockchain.com/btc/address/15h4F5yxeJHDgDJR5dnJwsNbETpktMnQzm

"Nick Szabo is Satoshi Nakamoto"

There are people who believe this stuff is real,and it is therefore not surprising that someone of them has incorporated that statement into his BTC transaction.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on December 13, 2019, 06:37:20 AM
Using the bitaddress.org donations address ( 1NiNja1bUmhSoTXozBRBEtR8LeF9TGbZBN ) on the passphrase field of the brainWallet generate the address ( 1Ns55SngRhshA8kEnyuQ9ELZZPN7ubYfQJ ) wich contain some small transactions !  :o

There's also two similar passphrases I've found (original address in bold) :

h1NiNja1bUmhSoTXozBRBEtR8LeF9TGbZBNz
g1NiNja1bUmhSoTXozBRBEtR8LeF9TGbZBNy


"Nick Szabo is Satoshi Nakamoto"

There are people who believe this stuff is real,and it is therefore not surprising that someone of them has incorporated that statement into his BTC transaction.

No such entry for Craight Wright, though.  :D


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on December 13, 2019, 10:57:17 AM
I still beleive that the most brain wallets are not serious wallets, and used for test/education/fun transactions. For these transactions (as well as for some quick transit transactions) no need to create the crypto secured wallet, and the brain wallet is used.

Of course there are some real wallets generated in "brain wallet way", but such wallets can be counted on one hand.

By the way, what do you think about time locked wallets based on easy brain wallets? Let's say we take the easy passphrase "bitcoin", hence the corresponding brain compressed address to it is 18VkRiDhFu2Z17AvtpU3vL2LbTXDzCvDVo (this address has already been used of course).

However, we take the public key of this address (02218ad6cdc632e7ae7d04472374311cebbbbf0ab540d2d08c3400bb844c654231) and create the time locked wallet (for example with the help of this tool: https://coinb.in/#newTimeLocked), let's say with time lock 31 December 2019:

https://coinb.in/?verify=0450650a5eb1752102218ad6cdc632e7ae7d04472374311cebbbbf0ab540d2d08c3400bb844c654231ac#verify

We receive the P2SH address 3NTavRnFZHkMmSFYVMz5PPb48WsNyVszDW, which could be accessed only by both redeem script and private key/signature from that easy address (18VkRiDhFu2Z17AvtpU3vL2LbTXDzCvDVo). The redeem script will not by available in blockchain till the funds are released from the address.



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: daboehla on December 20, 2019, 02:55:10 PM
WOW big transaction to a brainwallet:
0,50000000 16qVRutZ7rZuPx7NMtapvZorWYjyaME2Ue -> 400453AC5E19A058EC45A33550FDC496E0B26AD0 / 5E884898DA28047151D0E56F8DC6292773603D0D6AABBDD62A11EF721D1542D8 / Brainwallets
 ??? ??? ???


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: stalker00075 on December 20, 2019, 05:44:13 PM
WOW big transaction to a brainwallet:
0,50000000 16qVRutZ7rZuPx7NMtapvZorWYjyaME2Ue -> 400453AC5E19A058EC45A33550FDC496E0B26AD0 / 5E884898DA28047151D0E56F8DC6292773603D0D6AABBDD62A11EF721D1542D8 / Brainwallets
 ??? ??? ???

brainwallet "password"


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: daboehla on December 20, 2019, 06:28:46 PM
WOW big transaction to a brainwallet:
0,50000000 16qVRutZ7rZuPx7NMtapvZorWYjyaME2Ue -> 400453AC5E19A058EC45A33550FDC496E0B26AD0 / 5E884898DA28047151D0E56F8DC6292773603D0D6AABBDD62A11EF721D1542D8 / Brainwallets
 ??? ??? ???

brainwallet "password"
shit, true stroy! I don't save this in my database...
why should somebody do this :O


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on December 21, 2019, 10:12:43 AM
WOW big transaction to a brainwallet:
0,50000000 16qVRutZ7rZuPx7NMtapvZorWYjyaME2Ue -> 400453AC5E19A058EC45A33550FDC496E0B26AD0 / 5E884898DA28047151D0E56F8DC6292773603D0D6AABBDD62A11EF721D1542D8 / Brainwallets
 ??? ??? ???

brainwallet "password"

It seems that sombody "was listening" to this brainwallet address because the outgoing 0.5BTC transaction was included in the same block as incoming transaction (block 608894)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on December 22, 2019, 06:20:54 AM
WOW big transaction to a brainwallet:
0,50000000 16qVRutZ7rZuPx7NMtapvZorWYjyaME2Ue -> 400453AC5E19A058EC45A33550FDC496E0B26AD0 / 5E884898DA28047151D0E56F8DC6292773603D0D6AABBDD62A11EF721D1542D8 / Brainwallets
 ??? ??? ???

brainwallet "password"

It seems that sombody "was listening" to this brainwallet address because the outgoing 0.5BTC transaction was included in the same block as incoming transaction (block 608894)

Very likely. Some block explorers show double spend attempts. Some of the earlier messages in this thread include links to show that double spends happened multiple times shortly after a known brainwallet was funded. Presumably the double spend attempts are by several different "brainwallet stealer" bots.

I've even seen funds sent to dictionary word brainwallets on testnet vanish instantly.

Wonder if the person who lost 0.5 BTC used a brainwallet generator that helpfully prefilled the password field with the word "password", intending the user to replace it with their own text?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Financisto on December 27, 2019, 01:33:44 AM
Hello there,

I started (some years ago) a list that's a compilation of (open-source) Brainwallet projects (for study and improvement purposes only) here: https://bitcointalk.org/index.php?topic=1164163.0 (https://bitcointalk.org/index.php?topic=1164163.0)

Enjoy!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on January 20, 2020, 04:19:34 AM
A couple of months ago someone sent 3.4 BTC to a brainwallet

Funds were appropriated immediately; sweep transaction was included in the same block as the funding transaction.

https://www.blockchain.com/btc/address/13QZd78daoq3HaMKN9KAdFsVY9iYLKLfbm

Since it's so recent I won't post the passphrase, but it seems to be just a simple saying, perhaps also referring to a book title.

3.4 BTC!!!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BTCW on May 19, 2020, 02:24:03 PM
I have discovered what I called "perturbed SHA256 hashes". Like this:

SHA256("398") leads to

Code:
188c1fdca79d927f6e812133173fc41d3a4e57074de521020274caa9bb29af7d (found in "all" hash databases)
5J16cPLSHRR7CLQuKRWzCWDeXfrzDWYRUksjaTSH86x349BxuUk
17XNdhPkz8eSWibrMRjYY292Y9B6uRFvir

which is probably in every bot's database. However, check this out

Code:
188c1fdca79d927f6e812133173fc41d3a4e57074de521020274caa9bb29ae57 (found in "no" hash databases)
5J16cPLSHRR7CLQuKRWzCWDeXfrzDWYRUksjaTSH86x2Uzb2iY9
19rDLwxcP9Y3hEjXAkpkuMamKjLs1dgtiA

Both are found on the blockchain. Notice the pattern? The two differ only by a few bytes at the end of the hexadecimal string. The latter one is with an extraordinarily high certainty not the SHA256 hash of a known input.

Looks like someone took a known hash and changed it just a little. Clever!

My recommendation is perturbing well-known hashes.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BTCW on May 27, 2020, 06:41:56 PM
I thought this was a little cute

Code:
printf '\xF0\x9F\x92\xA9' | sha256sum
34722ef0267ceda14f0e2b756b83e85d6e79e458967895e72b07f87da7c0e275
5JDPFAB3Nt52bb2kQ4Sw2vi5JCi5LvPYdxtZu9LysDT52R2HBzh
1CNmL3ECHtAPxb9QZWrW29bq4t9T4SDUR4

https://www.blockchain.com/btc/address/1CNmL3ECHtAPxb9QZWrW29bq4t9T4SDUR4

Since it is (pseudocode): SHA256(poop emoji)

(Reference: https://www.fileformat.info/info/unicode/char/1f4a9/index.htm)

Conclusion: Add emojis to your wordlists  :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ashraful1980 on July 11, 2020, 07:53:16 AM
I thought this was a little cute

Code:
printf '\xF0\x9F\x92\xA9' | sha256sum
34722ef0267ceda14f0e2b756b83e85d6e79e458967895e72b07f87da7c0e275
5JDPFAB3Nt52bb2kQ4Sw2vi5JCi5LvPYdxtZu9LysDT52R2HBzh
1CNmL3ECHtAPxb9QZWrW29bq4t9T4SDUR4

https://www.blockchain.com/btc/address/1CNmL3ECHtAPxb9QZWrW29bq4t9T4SDUR4

Since it is (pseudocode): SHA256(poop emoji)

(Reference: https://www.fileformat.info/info/unicode/char/1f4a9/index.htm)

Conclusion: Add emojis to your wordlists  :)


Dear Sir,
You are really great. But i have a question that the value of '\xF0\x9F\x92\xA9' how to find and where from found......


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: vapourminer on July 11, 2020, 12:32:16 PM
I think it would be a good idea if wallet software included a blacklist of such addresses, as well as known weak brainwallets, showing an additional dialog with a strong warning that funds may be permanently lost (or stolen) if the transaction proceeds. Checking any generated (inbound) addresses against the list would also help catch any glaring address generation bugs. (An assert that the result must not equal <hash of empty string> after each call to sha256 or ripemd160 would have caught this error.)

centralized database of bad addys?

may sound good on 1st glance but nope for me.

maybe check against some private, local blacklist maintained by the user but thats up the user.

EDIT: saw that post was 7 months old oops



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BASE16 on July 11, 2020, 05:09:06 PM
I thought this was a little cute

Code:
printf '\xF0\x9F\x92\xA9' | sha256sum
34722ef0267ceda14f0e2b756b83e85d6e79e458967895e72b07f87da7c0e275
5JDPFAB3Nt52bb2kQ4Sw2vi5JCi5LvPYdxtZu9LysDT52R2HBzh
1CNmL3ECHtAPxb9QZWrW29bq4t9T4SDUR4

https://www.blockchain.com/btc/address/1CNmL3ECHtAPxb9QZWrW29bq4t9T4SDUR4

Since it is (pseudocode): SHA256(poop emoji)

(Reference: https://www.fileformat.info/info/unicode/char/1f4a9/index.htm)

Conclusion: Add emojis to your wordlists  :)


Dear Sir,
You are really great. But i have a question that the value of '\xF0\x9F\x92\xA9' how to find and where from found......

Hi please see emoji bytecode here https://apps.timwhitlock.info/emoji/tables/unicode (https://apps.timwhitlock.info/emoji/tables/unicode)  :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 20, 2020, 04:18:36 AM
I think it would be a good idea if wallet software included a blacklist of such addresses, as well as known weak brainwallets, showing an additional dialog with a strong warning that funds may be permanently lost (or stolen) if the transaction proceeds. Checking any generated (inbound) addresses against the list would also help catch any glaring address generation bugs. (An assert that the result must not equal <hash of empty string> after each call to sha256 or ripemd160 would have caught this error.)

centralized database of bad addys?

may sound good on 1st glance but nope for me.

maybe check against some private, local blacklist maintained by the user but thats up the user.

EDIT: saw that post was 7 months old oops



The blacklist check doesn't need to block the transaction, just strongly advise that it's a known compromised/problem address and to double check that everything is correct before clicking on OK.

It's not a general blacklist, just specifically for addresses where the keys are widely known (SHA256 dictionary words, low range private keys) or they are 99.99999999% likely to be unspendable (address of 0, RIPEMD160 hash of dictionary words, RIPEMD160 hash of empty string).

Perhaps you think I was suggesting that there should be some global "this person ripped me off so I want to add their address" kind of thing... no.

BTW, wallet software is pretty centralized anyway, right? :) I would actually appreciate if a wallet popped up a warning that my funds were likely to be lost.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on July 20, 2020, 06:01:25 AM
BTW, wallet software is pretty centralized anyway, right? :) I would actually appreciate if a wallet popped up a warning that my funds were likely to be lost.
I see no point in this. If I'm paying someone who sent me a compromized address, he could just as well scam me by using a brand new address so this doesn't help. If my own wallet generates a new address, proper random generation should ensure it's not part of such a list. You could easily create and publish billions of private keys, I don't want such a database bloating my wallet.
If you're manually creating such an address using dumb methods, you're on your own :P


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 20, 2020, 08:03:10 AM
BTW, wallet software is pretty centralized anyway, right? :) I would actually appreciate if a wallet popped up a warning that my funds were likely to be lost.
I see no point in this. If I'm paying someone who sent me a compromized address, he could just as well scam me by using a brand new address so this doesn't help.

I don't understand your point. Why would a scammer invite you to send money to an address where the private key is known by multiple people?

This is nothing to do with scamming - it's about preventing mistakes. Like people sending to the brainwallet "password", or software having a brain fart and sending to the hash of a blank string.

Original post for more context: https://bitcointalk.org/index.php?topic=4768828.msg52494961#msg52494961


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on July 20, 2020, 08:51:23 AM
Why would a scammer invite you to send money to an address where the private key is known by multiple people?
I had a different interpretation of what you meant.

Quote
This is nothing to do with scamming - it's about preventing mistakes. Like people sending to the brainwallet "password", or software having a brain fart and sending to the hash of a blank string.
Still, that's going to be a very long list. Brainwallets must be brute-forced by many different attackers who check billions of addresses.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on July 21, 2020, 12:45:35 AM
This is nothing to do with scamming - it's about preventing mistakes. Like people sending to the brainwallet "password", or software having a brain fart and sending to the hash of a blank string.
Still, that's going to be a very long list. Brainwallets must be brute-forced by many different attackers who check billions of addresses.

Yeah, there's no way it could be a comprehensive list (and with user passphrases, no list could be near 100% complete anyway), so I could imagine it getting out of hand, however even a list with say 50k entries could still prevent some silly mistakes.

(I wonder if anyone has ever trolled a victim by convincing them to send funds to a provably unspendable address? The troll gains no financial benefit, but the victim still suffers a loss.)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: naufragus on July 21, 2020, 12:59:48 AM
that is almost silly
we need to be sure the parametre space is large enough


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: DaCryptoRaccoon on July 21, 2020, 09:05:45 PM
This is nothing to do with scamming - it's about preventing mistakes. Like people sending to the brainwallet "password", or software having a brain fart and sending to the hash of a blank string.
Still, that's going to be a very long list. Brainwallets must be brute-forced by many different attackers who check billions of addresses.

Yeah, there's no way it could be a comprehensive list (and with user passphrases, no list could be near 100% complete anyway), so I could imagine it getting out of hand, however even a list with say 50k entries could still prevent some silly mistakes.

(I wonder if anyone has ever trolled a victim by convincing them to send funds to a provably unspendable address? The troll gains no financial benefit, but the victim still suffers a loss.)

This sounds horrible I sometimes wonder about funds that end up sent to these known addresses it would be nice if there was somewhere you could check this like you do with haveibeenpwnd password checker it would be nice to be able to throw a public key into something similar to see if it's known already on the network I know a simple check on explorer would do but if there were a way to collect all the known brainwallets or "weak" addressing i'm sure people would use it.

Anyone found anymore interesting ones recent?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: cr4zyd3v on July 21, 2020, 09:57:32 PM
This video https://www.youtube.com/watch?v=Xml4Gx3huag (https://www.youtube.com/watch?v=Xml4Gx3huag) has a very cool approach about how to find private keys in the open source repos from github.. I wonder if a smart enough sql query could be able to find brain wallets..


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on January 12, 2021, 03:19:29 PM
I thought the mini private key format, used for Casascius physical bitcoins should rate a mention here, because it's basically a SHA256 brainwallet... but with a randomly generated passphrase.

https://en.bitcoin.it/wiki/Mini_private_key_format

Given that the random passphrase length is 22 characters (early version) or 30 characters, the chances of brute forcing it are still virtually nil, but technically, it is less secure than a standard key, in particular because 99%+ of the tries can be discarded after the first SHA256 hash.

By the way, funds have been sent to (and promptly swept from) the address associated with the sample mini private key on that page:

https://www.blockchain.com/btc/address/7f6ab65fa911f558ca2dde3e9d073acb02c0d5c6 (uncompressed: 1CciesT23BNionJeXrbxmjc7ywfiyM4oLW )
https://www.blockchain.com/btc/address/f78c1591f3f34fd1fe339dc371069b7b492bf370 (compressed: 1PZuicD1ACRfBuKEgp2XaJhVvnwpeETDyn )

Hi,
How do you manage to hash 300k passphrases per second? What do you use for that? My Pythons script with 'bictoin' library on 8 cores is doing only 800/s :(


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: NotATether on January 12, 2021, 05:00:48 PM
Hi,
How do you manage to hash 300k passphrases per second? What do you use for that? My Pythons script with 'bictoin' library on 8 cores is doing only 800/s :(

He definitely did not use Python because that's the reason your script is so slow!

Python executes all statements through an interpreter, it does not compile it down into assembly code so the extra overhead that the Python runtime is adding is killing the speed of your script. You should look into using brainflayer (https://github.com/ryancdotorg/brainflayer) which is written in C, and is optimized with its own hashing functions instead of relying on a third-party library.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: szosti94 on January 23, 2021, 01:21:44 PM
Hi, I have a question about braiflayer, I launched it, found a hash and password, the problem is that I don't know how to get information about the wallet and key, how to get the address and private key with the hash sha265 and password?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on April 09, 2021, 03:38:30 PM
2. One of those files contained the value of Pi to a billion decimal places.
I thought about this post when I found the private key to 111exFkjLXP5mXmEfVqGd2r7bXQhVhux3 (https://blockchair.com/bitcoin/address/111exFkjLXP5mXmEfVqGd2r7bXQhVhux3): it's the second set (https://gist.github.com/retrohacker/e5fff72b7b75ee058924) of pi's 64 hex characters: 9216D5D98979FB1BD1310BA698DFB5AC2FFD72DBD01ADFB7B8E1AFED6A267E96
Back then, it took half a day to be sweep 0.37149557 BTC (41.29 USD).


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: NotATether on April 10, 2021, 06:52:56 AM
Just for future reference:

Hi, I have a question about braiflayer, I launched it, found a hash and password, the problem is that I don't know how to get information about the wallet and key, how to get the address and private key with the hash sha265 and password?

You start with getting the private key. The double SHA256 hash of the password will give you that, and you can derive the public key from it as normal - Elliptic curve multiply, and then RIPEMD160 the public key, hash that through double SHA256 again and take the first four bytes of that and stick it at the end. Then stick a 0x00 byte at the beginning and encode the combined byte array through BASE58Check to get the address.

2. One of those files contained the value of Pi to a billion decimal places.
I thought about this post when I found the private key to 111exFkjLXP5mXmEfVqGd2r7bXQhVhux3 (https://blockchair.com/bitcoin/address/111exFkjLXP5mXmEfVqGd2r7bXQhVhux3): it's the second set (https://gist.github.com/retrohacker/e5fff72b7b75ee058924) of pi's 64 hex characters: 9216D5D98979FB1BD1310BA698DFB5AC2FFD72DBD01ADFB7B8E1AFED6A267E96
Back then, it took half a day to be sweep 0.37149557 BTC (41.29 USD).


I think it's just a coincidence that some brainwallets hash to Pi digits since Pi doesn't really have anything to do with number theory.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: fxsniper on April 10, 2021, 11:18:36 AM


Brainwallets is keyword or message + sha256 = private key , right?

What if using  random 256 number (character) and + sha256 = private key it still safety?
or   random text 256 character and + sha256 = private key  still safety?

Brainwallets count only word and language human read only right?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: NotATether on April 10, 2021, 11:24:00 AM
Brainwallets is keyword or message + sha256 = private key , right?

Yes.

What if using  random 256 number (character) and + sha256 = private key it still safety?
or   random text 256 character and + sha256 = private key  still safety?

Think of it this way - your brainwallet is just as secure as a password, so if you hash a 256-character text then the security will be equal to using a 256-character password (that is hashed with double SHA256 into a database by some server somewhere).

I would not view any kind of brainwallet safe. Even if you're using extremely long lengths, there is no probably secure brainwallet generator that doesn't leak the password in memory.

Brainwallets count only word and language human read only right?

Not quite. Anything that you'd use as a password can be considered a brainwallet, it's not limited to English words, or any language's words in particular.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: NotATether on April 11, 2021, 09:11:17 AM
Think of it this way - your brainwallet is just as secure as a password, so if you hash a 256-character text then the security will be equal to using a 256-character password (that is hashed with double SHA256 into a database by some server somewhere).

Except the attacker can brute-force unlimited times, while on website/server you have very limited try. Additionally, single SHA-256 uses very few resource and good GPU can make few hundred MH/s.

I was actually referring to the case where a site's database with the password hashes is stolen. Then you'd be able to run as many tries as you want.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ABCbits on April 11, 2021, 09:15:43 AM
I was actually referring to the case where a site's database with the password hashes is stolen. Then you'd be able to run as many tries as you want.

I see, but AFAIK most website isn't that stupid. They usually would use salting, hash the password many times or just use algorithm focused on security (such as PBKDF2).
Meanwhile, most brainwallet only use single SHA-256 hash.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on April 11, 2021, 09:25:20 AM
I was actually referring to the case where a site's database with the password hashes is stolen. Then you'd be able to run as many tries as you want.
Brainwallets are much worse: an attacker can try to brute-force all of them at the same time, while with a hacked password database you have to try them one by one (assuming the password hash uses something like hash("secretKey777" + username + password); (https://security.stackexchange.com/questions/69421/is-it-a-good-idea-to-use-the-users-username-as-a-salt-when-hashing-a-password-l)).
So, if 100,000 brainwallets are in use, it's 100,000 times more likely to find one of them than cracking a password.
You can improve this by adding for instance your real name or email address as a salt to your brainwallet (but it's still not recommended to do).


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: fxsniper on April 11, 2021, 09:44:39 AM
I agree Brainwallets are much worse

Brainwallets use keywords + sha256

I see mini private key is using by 30 character and hash with sha256 still safety
 but mini privatekey have format

However random text and number or text only or number only 256 character (or 512 character ) hash with sha256  (64 character), I think it is safety not easy to butte force with random 256 key easy (just 64 bit key
but some duplicate some private key will duplicate with number 265 bit (77 character) convert to HEX  (64 character)

private key require HEX  in 64 character right
so, What method to can generate it to safety?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: NotATether on April 11, 2021, 04:46:16 PM
...while with a hacked password database you have to try them one by one (assuming the password hash uses something like hash("secretKey777" + username + password); (https://security.stackexchange.com/questions/69421/is-it-a-good-idea-to-use-the-users-username-as-a-salt-when-hashing-a-password-l)).

Just to point out, if you reverse the order in which you hash this stuff and make it hash(password + salt), and you leave the value of hash(password) somewhere, somebody can do a length extension attack (https://en.wikipedia.org/wiki/Length_extension_attack), especially on SHA256, by using that value to compute the hash of the password plus anything appended to it without knowing the password itself.

And in a way, if your salt is constant and an attacker managers to find it elsewhere, the length extension attack negates the security of the salt.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on May 18, 2021, 10:13:42 AM
I wonder what was the oldest brainwallet ever found. Vasek reported this one in her paper: "This string contains 0.25 BTC hiding in plain sight." -> 1AJ3vE2NNYW2Jzv3fLwyjKF1LYbZ65Ez64
It has been used for the first time on 2011-07-14.
The story behind it here: https://bitcointalk.org/index.php?topic=28877.0

1. Was there anything older found by anyone?
2. What has been used before? Purely random generated numbers?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on May 18, 2021, 10:33:00 AM
And look how wrong your first impression can be...
I was good until Step 4.

Agreed. We urgently need a user-friendly import/export function in the client!

This is the most secure "wallet" there could possibly be. No no copies of wallet.dat, no encryption, no USB stick/paper/printing which can be lost, no malware which secretly steals my coins, no storage or bank vault, no life CD, no nothing! Just a simple passphrase I can remember. Since nothing is stored or written down anywhere this wallet concept is basically impossible to compromise.
The only flaw is that I might forget my passphrase, but I can still write hints/clues which can make my help remember while still being 100% secure. We need this.

.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on November 07, 2021, 09:03:59 PM
Brain wallets are used for fun purposes I believe:

Code:
~$ echo -n "odolvlobo ozono" | sha256sum
f98ae1f0a6e25e76429800c26efec5c9938e267867e5b97ed7705b039829dad4  -

So, brain wallet for odolvlobo ozono leads to the address 13u28uKzciwUpqCtVrCzk5d8KSbypjokck with the transactions dated 2 years ago  ;)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on November 08, 2021, 02:11:46 AM
Let's say (conservatively) that a more modern quad core CPU can do 500,000 and use that as the reference. That means it can check 43.2 billion keys per day.

Brute forcing the "correct horse battery staple" space
Most "brain wallets" are not brute-forced. Hackers will use various literature as a starting point for passphraises, and will use permutations of said phrases to check for a brain wallet with coin unspent.

The reason for the above is that, although the English language is vast, and it would be difficult to brute force a random 4-word brain wallet, most people are not going to select words for a brain wallet at random.

Most people will select words that are easy to remember because they coincide with a meaningful event, or are otherwise meaningful to the person. This is not random, and as such can be easily be "guessed" by hackers.

If you were to create a brain wallet of 4 words randomly selected from 171k English words, it would be one possibility out of ~855 million trillion possible combinations. However, if the brain wallet is created from some set of words in a book or bible verse, the possible combinations is reduced by multiple magnitudes. 


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on November 08, 2021, 08:37:25 AM
Brain wallets are used for fun purposes I believe:

Code:
~$ echo -n "odolvlobo ozono" | sha256sum
f98ae1f0a6e25e76429800c26efec5c9938e267867e5b97ed7705b039829dad4  -
The associated uncompressed Bitcoin address is 1GRUEoTSW9MRcNooxFRt8h8eL9gsPgGxzu, which looks like a vanity address for grue (https://bitcointalk.org/index.php?action=profile;u=5797), but it's unused so I guess that is a coincidence.

Quote
So, brain wallet for odolvlobo ozono leads to the address 13u28uKzciwUpqCtVrCzk5d8KSbypjokck with the transactions dated 2 years ago  ;)
User odolvlobo (http://User [url=https://bitcointalk.org/index.php?action=profile;u=62955) Someone just got 555 sats burned donated to miners (https://blockchair.com/bitcoin/transaction/a2d51f74ddaeadce1eb893e5791a58053508891a25ecfcb84d0e7092214724c0) (it wasn't me).


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on November 08, 2021, 08:50:57 AM
User odolvlobo (http://User [url=https://bitcointalk.org/index.php?action=profile;u=62955) just got 555 sats burned donated to miners (https://blockchair.com/bitcoin/transaction/a2d51f74ddaeadce1eb893e5791a58053508891a25ecfcb84d0e7092214724c0) (it wasn't me).

FYI, I don't think that is my address (I don't remember creating it). I don't know why someone would use "odolvlobo ozono" for a brain wallet, except that they noticed the words in a post and thought they were obscure enough to use. Apparently not.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: MrFreeDragon on November 08, 2021, 09:59:54 PM
Brain wallets are used for fun purposes I believe:

Code:
~$ echo -n "odolvlobo ozono" | sha256sum
f98ae1f0a6e25e76429800c26efec5c9938e267867e5b97ed7705b039829dad4  -
The associated uncompressed Bitcoin address is 1GRUEoTSW9MRcNooxFRt8h8eL9gsPgGxzu, which looks like a vanity address for grue (https://bitcointalk.org/index.php?action=profile;u=5797), but it's unused so I guess that is a coincidence.

-snip-


Wow, what is the connection between odolvlobo and grue except for the fact they are both Legendary members?
Interesting thing that the brainwallet from one's name signature leads to the the vanity address of another one.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Danydee on November 08, 2021, 10:21:15 PM


     ;D    ;D    ;D    ;D    ;D








It makes think to a puzzle !
( ozono )  z <=> n (N)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: mynonce on November 11, 2021, 07:19:35 PM
Hi,
...
I love to get some feedback ...

Is it possible, that Satoshi used for his ''early mined coins'' precalculated SHA256 addresses like we do it here?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ABCbits on November 12, 2021, 10:54:11 AM
Hi,
...
I love to get some feedback ...

Is it possible, that Satoshi used for his ''early mined coins'' precalculated SHA256 addresses like we do it here?

Possible? Yes, but IMO it's very unlikely since,
1. Satoshi also use SHA256 for Proof of Work, which means he know how fast SHA-256 speed on CPU/GPU.
2. Creating private key with such weak method allow people to steal Satoshi's Bitcoin and impersonate Satoshi easier, which could disrupt Bitcoin in many ways (e.g. crashing Bitcoin price, influence people to reduce strength of Bitcoin protocol, etc.).


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on November 12, 2021, 09:01:18 PM
Code:
~$ echo -n "odolvlobo ozono" | sha256sum
f98ae1f0a6e25e76429800c26efec5c9938e267867e5b97ed7705b039829dad4  -
The associated uncompressed Bitcoin address is 1GRUEoTSW9MRcNooxFRt8h8eL9gsPgGxzu, which looks like a vanity address for grue (https://bitcointalk.org/index.php?action=profile;u=5797), but it's unused so I guess that is a coincidence.
Wow, what is the connection between odolvlobo and grue except for the fact they are both Legendary members?
Interesting thing that the brainwallet from one's name signature leads to the the vanity address of another one.

If it isn't a coincidence, then there is a serious problem. Also, there are 3.4 million Bitcointalk users, so the chances of a random address matching a user's name seems pretty high to me.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on November 12, 2021, 11:03:22 PM
Code:
~$ echo -n "odolvlobo ozono" | sha256sum
f98ae1f0a6e25e76429800c26efec5c9938e267867e5b97ed7705b039829dad4  -
The associated uncompressed Bitcoin address is 1GRUEoTSW9MRcNooxFRt8h8eL9gsPgGxzu, which looks like a vanity address for grue (https://bitcointalk.org/index.php?action=profile;u=5797), but it's unused so I guess that is a coincidence.
Wow, what is the connection between odolvlobo and grue except for the fact they are both Legendary members?
Interesting thing that the brainwallet from one's name signature leads to the the vanity address of another one.

If it isn't a coincidence, then there is a serious problem. Also, there are 3.4 million Bitcointalk users, so the chances of a random address matching a user's name seems pretty high to me.
The brain wallet for your name does not match that address. The brain wallet for your name with the string " ozono" appended at the end is associated with that address.

The chances of that particular brain wallet being associated with an address with that particular "vanity" would be the same as any other vanity of that length.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: larry_vw_1955 on November 14, 2021, 04:54:30 AM
Let me pipe in here about brainwallets since I know a thing or two about them. I think the standard sha256 brainwallet was invented for one reason only: to steal peoples money. Anyone with half a brain would be very wary of using the standard sha256 brainwallet. Not that it can't be done it just probably shouldn't. The fact that people have huge databases of precomputed hashes lying around proves that. Now if the brainwallet algorithm was a secret then that would make you guys that store these large databases of hashes look like some one fumbling around in the dark wearing a pair of sunglasses. You wouldn't have the slightest clue how to begin your search even if you knew the brainwallet passphrase. without the algorithm, you might as well just start picking private keys at random and seeing if they match the address.

just think about it. some of you guys are like cavemen in the stone age when it comes to even testing simple alternatives to the sha256 brainwallet. to say nothing of someone that had a more sophisctocated method of producing their brainwallet addresses.

now bring on the hate.



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: itod on November 14, 2021, 09:31:27 AM
Let me pipe in here about brainwallets since I know a thing or two about them. I think the standard sha256 brainwallet was invented for one reason only: to steal peoples money. Anyone with half a brain would be very wary of using the standard sha256 brainwallet. Not that it can't be done it just probably shouldn't. The fact that people have huge databases of precomputed hashes lying around proves that. Now if the brainwallet algorithm was a secret then that would make you guys that store these large databases of hashes look like some one fumbling around in the dark wearing a pair of sunglasses. You wouldn't have the slightest clue how to begin your search even if you knew the brainwallet passphrase. without the algorithm, you might as well just start picking private keys at random and seeing if they match the address.

just think about it. some of you guys are like cavemen in the stone age when it comes to even testing simple alternatives to the sha256 brainwallet. to say nothing of someone that had a more sophisctocated method of producing their brainwallet addresses.

now bring on the hate.

Amen!

I've being talking about this forewer. To be completly honest: it may not be invetned to steel peoples money, maybe the general idea was to remove any needed computer skills as an obstacle from going into BTC, but once it was there, the motivation for promoting this flawed concept may be exactly that.

Talking to people who claim brainwallets are secure enough is like talkin to cult members, no rational argument gets through.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on November 14, 2021, 09:49:25 AM
Talking to people who claim brainwallets are secure enough is like talkin to cult members, no rational argument gets through.
Of course it is possible, just not for most people (including me) ;)

I've never used it, but if you use for instance brainwallet.io's implementation (offline of course) where a passphrase is salted with your personal details and much slower encryption, it's no longer possible to do a brute-force attack on all existing brainwallets at once.

Update:
I already mentioned it many times, but also check https://keybase.io/warp (https://keybase.io/warp).
This is the one I was looking for, thanks.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on November 14, 2021, 10:02:23 AM
now bring on the hate.
Why would we bring on the hate because you give your opinion/view on the matter?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: larry_vw_1955 on November 14, 2021, 10:27:16 AM

But if the algorithm itself is secret/closed-source, only the author and people who trust the author who would use it.

In another thread https://bitcointalk.org/index.php?topic=5369436.msg58401834#msg58401834 (https://bitcointalk.org/index.php?topic=5369436.msg58401834#msg58401834) I posted the btc address and brainwallet phrase for a secret brainwallet algorithm i came up with I don't think its been cracked yet! That's right! I gave away the brainwallet phrase for free something one would traditionally want to keep secret and something an attacker would not have the pleasure of necessarily knowing  under most circumstances. Of course, it's not going to do them any good...

I should really fund that address sometime to encourage people to "give it their best shot". ;D But first I need to commit that dang algorithm to memory. ::)

Quote
Why would we bring on the hate because you give your opinion/view on the matter?

Assumed that people want other people using the simple sha256 brainwallet and dont want someone saying it's a bad idea?



To be completly honest: it may not be invetned to steel peoples money, maybe the general idea was to remove any needed computer skills as an obstacle from going into BTC, but once it was there, the motivation for promoting this flawed concept may be exactly that.

Talking to people who claim brainwallets are secure enough is like talkin to cult members, no rational argument gets through.

Well I think it's like you said. the idea started out innocent enough. the idea kind of caught on and people were using brain wallets like crazy. that's kind of died down with hd wallets and things but in the early days, i guess brainwallets were all the rage. once the weaknesses were realized it was too late cat was out of the bag, default sha256 brainwallet was the de facto standard even though as i think you and the other person posted links to warpwallet and brainwallet.io which are way more secure. but they missed the boat. the train took off without them long ago so the story goes... ;D

[moderator's note: consecutive posts merged]


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on November 17, 2021, 10:37:09 AM
I wonder what was the oldest brainwallet ever found. Vasek reported this one in her paper: "This string contains 0.25 BTC hiding in plain sight." -> 1AJ3vE2NNYW2Jzv3fLwyjKF1LYbZ65Ez64
It has been used for the first time on 2011-07-14.
The story behind it here: https://bitcointalk.org/index.php?topic=28877.0

1. Was there anything older found by anyone?
2. What has been used before? Purely random generated numbers?

Interesting question, I was curious myself so did some analysis into this. This is the top-5 of known brainwallets and when they first were used on the bitcoin blockchain:
Code:
Date first used  Address                                Passphrase used
2011-07-14       1AJ3vE2NNYW2Jzv3fLwyjKF1LYbZ65Ez64     This string contains 0.25 BTC hiding in plain sight.
2011-09-05       1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm     0000000000000000000000000000000000000000000000000000000000000001
2011-09-14       1ERczz9PRkdcbLmFRgGKKTU5BADthAcHdi     one two three four five six seven
2011-10-14       1Km3PemDrwiwA1gEEgKLgizLgdsqwp4XZz     testing 123
2011-12-03       1JryTePceSiWVpoNBU8SbwiT7J4ghzijzW     Satoshi Nakamoto
So it does seem the "This string contains 0.25 BTC hiding in plain sight." was indeed the very first one.

Disclaimer: based on the brainwallets I have available. Could be older ones I simply am not aware of. If that's the case please let me know!


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: larry_vw_1955 on November 18, 2021, 02:37:27 AM
I wonder what was the oldest brainwallet ever found. Vasek reported this one in her paper: "This string contains 0.25 BTC hiding in plain sight." -> 1AJ3vE2NNYW2Jzv3fLwyjKF1LYbZ65Ez64
It has been used for the first time on 2011-07-14.
The story behind it here: https://bitcointalk.org/index.php?topic=28877.0


So it does seem the "This string contains 0.25 BTC hiding in plain sight." was indeed the very first one.


it would have had to have been because most of the people in that thread seeemed totally clueless about how. except the person that lifted the funds in the first 5 minutes. oh actually that person was clueless too! ;D


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on August 06, 2022, 08:24:38 PM
I thought the mini private key format, used for Casascius physical bitcoins should rate a mention here, because it's basically a SHA256 brainwallet... but with a randomly generated passphrase.

https://en.bitcoin.it/wiki/Mini_private_key_format

Given that the random passphrase length is 22 characters (early version) or 30 characters, the chances of brute forcing it are still virtually nil, but technically, it is less secure than a standard key, in particular because 99%+ of the tries can be discarded after the first SHA256 hash.

I came across my simple mini key generator tonight, and I'm having another play with it.

The naive version uses random() and outputs about 8000 valid keys per second on a single core of an i7-3960X.

I updated it to use the xoshiro256** PRNG, and the speed increases to around 13000 valid keys per second.

Because the generation process requires that the first byte of the candidate hash be '00', on average only 1/256 candidates will be valid, so it's really testing about 3.3 million keys per second.

It's still a massive search space (58^30?), even for a SHA256 brainwallet, and prematurely discarding 255 out of 256 candidates does not reduce the search space... it just makes searching faster. Plus, how many Casascius coins were ever created, and how many would still be funded? So this is really just a curiosity.

Here's a small sample of randomly generated valid keys:

Code:
S8Q2r4p3HKtDGYXYgcoE6N
SAN7cS1MnFNps25QHt4pRk
SCG9csSvqn2kytKW1WdNd6
SCzCTefJ7J7iGsz4XbMhU6
SFHwkzYdQgDVdhHSdGmCxCZN8YQiNT
SFikz2eev6PMNhU9JNo1DAJ2bcdvSL
SKNzLVj4LHzG8C95ZpjFL5X8HDZNyx
SKgC6zF8opjFQqHhL2Nud1Qx5FpsBc
SN5FSGaCVahVDmM7ARQgijwTExfsWK
SP41nfQVpTpFqfaPUREfBu
SPHPyjWYQKzwrw4bW4ckwwhGNvkSo1
SPpof8XT1ZfrjFBqMaqqN9tuaJ6SyL
SQHv63Wu43viTu2CnbWasR
SQpKTKp1t1phNgg4Qt8piwGxsCxxp1
SQqX32iniiKPqhVbFsuK5RQWqnHUnu
SUZNCr2iXiA4B9qiLVAWJEmMC9LfUj
SWyMZq87mrvSqjiU3KRJ7CbXKtEW6A
SZLdpNMFDfnxMSLKXmaUckAgXMuLXL
Sai3S1jgnN5E2QoydQAVr7u4U3KYFU
Sc9wTknTRqXUTSkB8pFWbX
SdUecesqKtj77JhrQT4obAt5XnCScf
SdXNZMq45NZGdYGzb7UnCe
Sdc3fyobJE2AAKxSLvnYia

The private key is simply the SHA256 hash of the string, like a brainwallet.

Some useless information, but hopefully it might kickstart the thread again. :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: fubly on August 06, 2022, 08:54:57 PM
Hi,
...
I love to get some feedback ...

Is it possible, that Satoshi used for his ''early mined coins'' precalculated SHA256 addresses like we do it here?

I don't know, but here: https://github.com/sCrypt-Inc/boilerplate (https://github.com/sCrypt-Inc/boilerplate) you will find a script wich can check if he uses the same private key to create a new address


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: phrutis on August 06, 2022, 09:21:25 PM
~
Some useless information, but hopefully it might kickstart the thread again. :)

Not that useless  :)


We have something that could kickstart the thread too:

https://github.com/phrutis/BrainWords (https://github.com/phrutis/BrainWords)

Search passphrases on the fastest program in the world
GPU RTX 3090: 180 Mkey/s
GPU RTX 3080: 150 Mkey/s


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on August 06, 2022, 09:31:43 PM
We have something that could kickstart the thread too:

https://github.com/phrutis/BrainWords (https://github.com/phrutis/BrainWords)

A link posted by a newbie to a github rep that only has executables, and no source? That's a pass from me...


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: odolvlobo on August 07, 2022, 12:39:16 AM
I thought the mini private key format, used for Casascius physical bitcoins should rate a mention here, because it's basically a SHA256 brainwallet... but with a randomly generated passphrase.
...
...
The private key is simply the SHA256 hash of the string, like a brainwallet.

The fact that the private key is derived using SHA-256 does not make it a brain wallet. A HD wallet seed comes from the SHA-512 hash of the BIP-39 seed phrase. Does that make an HD wallet a brain wallet? A brain wallet is derived from something that can be memorized. That is why it is called a "brain" wallet. The mini-key is a random sequence and is not intended to be memorized so it is not basically a SHA-256 brain wallet.

Because the generation process requires that the first byte of the candidate hash be '00', on average only 1/256 candidates will be valid, so it's really testing about 3.3 million keys per second.

Another minor correction: The hash of the string concatenated with a '?' must have a first byte of 0, and not the hash of the string itself. It does reduce the number of keys that must be checked as you noted, but the derived private key itself does not always begin with a 0-byte.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on August 07, 2022, 07:39:19 AM
I thought the mini private key format, used for Casascius physical bitcoins should rate a mention here, because it's basically a SHA256 brainwallet... but with a randomly generated passphrase.

https://en.bitcoin.it/wiki/Mini_private_key_format

Given that the random passphrase length is 22 characters (early version) or 30 characters, the chances of brute forcing it are still virtually nil, but technically, it is less secure than a standard key, in particular because 99%+ of the tries can be discarded after the first SHA256 hash.

I came across my simple mini key generator tonight, and I'm having another play with it.

The naive version uses random() and outputs about 8000 valid keys per second on a single core of an i7-3960X.

I updated it to use the xoshiro256** PRNG, and the speed increases to around 13000 valid keys per second.

Because the generation process requires that the first byte of the candidate hash be '00', on average only 1/256 candidates will be valid, so it's really testing about 3.3 million keys per second.

It's still a massive search space (58^30?), even for a SHA256 brainwallet, and prematurely discarding 255 out of 256 candidates does not reduce the search space... it just makes searching faster. Plus, how many Casascius coins were ever created, and how many would still be funded? So this is really just a curiosity.

The reason why brain wallets are insecure is that they are typically generated in ways that are not truly random. Generating a brain wallet using a random function will not have this problem.

For example, if a brain wallet is a phrase that is found in literature, there are a very limited number of phrases in literature, and the number of candidate brain wallets are many orders of magnitude less than the number of potential private keys.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PawGo on August 07, 2022, 07:44:09 AM
The fact that the private key is derived using SHA-256 does not make it a brain wallet. A HD wallet seed comes from the SHA-512 hash of the BIP-39 seed phrase. Does that make an HD wallet a brain wallet? A brain wallet is derived from something that can be memorized. That is why it is called a "brain" wallet. The mini-key is a random sequence and is not intended to be memorized so it is not basically a SHA-256 brain wallet.

What about "my private key is generated from 111th block's hash in bitcoin blockchain"? You do not remember exact value which is used to produce private key, but you remember the way how to find it - exactly like "my phrase is second verse of song X".
One thing is sure in my opinion - brain wallets belongs to past.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on August 07, 2022, 09:30:56 AM
The fact that the private key is derived using SHA-256 does not make it a brain wallet. A HD wallet seed comes from the SHA-512 hash of the BIP-39 seed phrase. Does that make an HD wallet a brain wallet? A brain wallet is derived from something that can be memorized. That is why it is called a "brain" wallet. The mini-key is a random sequence and is not intended to be memorized so it is not basically a SHA-256 brain wallet.

What about "my private key is generated from 111th block's hash in bitcoin blockchain"? You do not remember exact value which is used to produce private key, but you remember the way how to find it - exactly like "my phrase is second verse of song X".
One thing is sure in my opinion - brain wallets belongs to past.
Using a private key that is derived from in a similar manner is very risky, and is very likely to result in tears. There are many people who are monitoring a large scope of potential addresses for transactions being sent to them, and some of these people look to bitcoin-related forums to increase the scope of these addresses. You can call it a brain wallet if you want, but my advice is to not do it.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Cricktor on August 07, 2022, 09:56:08 AM
So true. It's rare to see such large amounts get likely lost to those "snatchers". On 2022-07-27 some (not so smart) entity sent 0.9BTC to the "empty string" brainwallet in block 746835 (tx 37e166a1e52e96bcfe535738082e328ef8db56aafd6945d9cad6f2afdb34b4a4) which was very likely claimed by some of those bots who constantly monitor mempool transactions for such brainwallet transactions.

Seriously, how stupid is someone to use SHA256("") or SHA256 of any publicly available data, block hashes included, as private key and believe this is in any way "smart"?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on August 07, 2022, 01:43:06 PM
Seriously, how stupid is someone to use SHA256("")

More likely to be a programming error. I recall suggesting a few years ago in this thread that something like (pseudoish code) assert(key != 0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855) would have avoided this particular issue.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on August 07, 2022, 03:33:39 PM
I came across my simple mini key generator tonight, and I'm having another play with it.

The naive version uses random() and outputs about 8000 valid keys per second on a single core of an i7-3960X.
I did that for a while a couple of years back (with a python generator), trying to create vanity addresses with mini private key, but I had to search through large output files and the output was far too slow to find anything meaningful.

One thing is sure in my opinion - brain wallets belongs to past.
I'm pretty sure people still use them. Even better if they use something they use much heavier encryption (such as WarpWallet).
The idea of simply remembering your money is appealing to me (but I don't dare risk it for a large amount).


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BlackHatCoiner on August 07, 2022, 04:06:54 PM
I'm pretty sure people still use them. Even better if they use something they use much heavier encryption (such as WarpWallet).
The idea of simply remembering your money is appealing to me (but I don't dare risk it for a large amount).
What I don't understand is why don't they use the hash function millions of times to make their brain wallet even more secure? We all know that just hashing a subjectively difficult passphrase isn't as much secure as it is to generate an entropy randomly. There wouldn't be such thread if brain wallet users hashed more than once, because, apparently, some passphrases aren't as strong as they thought.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: pooya87 on August 07, 2022, 04:37:01 PM
What I don't understand is why don't they use the hash function millions of times to make their brain wallet even more secure?
It has to do with the time consumption. When the user enters a password they want to get their address as soon as possible, if you increase the number of hashes it would consume more time hence ruins user experience. And considering that brainwallets that I've seen are browser based they are even more limited to the amount of computing power they can use so the process could be even slower than it could be.

Besides, brainwallets aren't serious projects and weren't designed for security at first. Some tried to replace SHA256 with stronger algorithms such as scrypt but such projects don't gain any popularity since the idea of brainwallet itself is flawed.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PawGo on August 07, 2022, 04:40:00 PM
What I don't understand is why don't they use the hash function millions of times to make their brain wallet even more secure? We all know that just hashing a subjectively difficult passphrase isn't as much secure as it is to generate an entropy randomly. There wouldn't be such thread if brain wallet users hashed more than once, because, apparently, some passphrases aren't as strong as they thought.

Because it is not kind of "standard". If at this moment you have an idea to create a new wallet using a given phrase, you have software to do it quickly. I am not aware of any program which would accept other parameters, like number of iterations.
We may imagine that you want to launch hash function 20220807 times - and even if you forget that number but you remember period of time when the wallet was created, there is still way to restore it.

Seriously, how stupid is someone to use SHA256("") or SHA256 of any publicly available data, block hashes included, as private key and believe this is in any way "smart"?

Honestly speaking, I have asked Loyce to prepare list of tx ids and launched search on that. The result is surprising! (I mean it is surprising how many wallets were using that method). Each of that values generates address which was used in the past.
Code:
305ba804e692949587a24ea94a48e1d800732589e9203a8bfc271b9bc0c50f7a
4c63c5d9d30db0fd211ebaebeb6d7bcc335c5a0244a7c59fc9df7801b4433509
62373043bc609add196b91426a54bf99bb96f306e7853b41845e0943902206fc
3119bc423c50b6da00047e76f4860a9eb7d9aabc0d5e06256cd0347825e0cb18
fa09f349487b69294f6b9a0f3f953d07ae99b0ececae7cca617f6aa46e505613
983a65341472c787f3a125f9d1f58ddbe06533f9042c3938095e8ea093d15ffa
4330d40c8fc1185cd614c7f7e8bccbe3fd1a1542ac076da7d03a6a0cfc14fcb5
2b5bc89856010733006aad8747f4954af26c3b2d2427c4ce526e5ef435fba1d0
a62a09ba9cae34859ff31efd15427633f1b1ee043dbf2dbd03cc73f94320e611
2ecd32b4a7eb2bee20c071ab6c7578c5e821f722595037ac1a60ee5caff60d9e
882fd03f3af3df994ede0131eb818fd57e91cf01b12b1c0fcfac7271067550fe
72def37c867d4841066f8f0e4fe63986d8b2e6c6b3ed2dd187dbb434c919def9
7cbdf77eb3f12a784c90a7783f0b3f84e3e828d66dd06d92594a05052b63e6ab
099057f824134129de11dfef261371d0108d1283f5b0d561097c95c0221ba0ec
0f46e1323cf1c32d29ae3d292fd8e1ab4e21a53e621cf95245337bdd0a52bae5
4196d328b10bad238f9a25246aaaa4e6c306ae7f31ab0e508502f39dc8b2d001
30b02b8f71d3ee0bfa26ea7283458758a0fff362135f1be5f22c9f32d0767b59
0d064df9159fc070de9b4f56f8670ebcd788ba56d8da06b3f0bf0204ec07411a
f1a0a7ccefc9e267f7bcedf884e489cd6a63ed0424c59cfcef189f40720a2edd
d89d3edf5ca1fc1af2c2cb21765dfec6ee842b33ee803db6c792fa8cdf830fad
b818a01dda4dfa70ef60670ab9f68a919856e45eeb2cf087a63c9a5d32067c75
bab55a1138e548e9dd6a8a01fcd3815a490c6fa582e446f59cfd32e82330bed9
9f2e7d7d6c1e7c7e574bcc6e0aa9ad7892a70b4bb03a05776e7f11b04d5ff343
6469ae78933e4da4f7700f93a2b414cfdc71cfcbc379964eb83adb2f570a94a2
7823ea0c60a4e5da7996b425527da9ced7ee6478b9b677fe3b004cfc21eacb66
59a37302f7012c2504b633e39cd5d286bd2f5c35327364cf4e95eb5f37657961
15d47c31f45ceac4ace19eed79a5d12566381161517a234c0967107ed0a8fa41
3f18e8e85fde3ec91a28b30ef17cbb713833447b24cc952828e0aa3501465b8e
00f8cd36954bcf69b5a6771c2b4ac15f1081c93feb676e78d628c5ee10d86dd5
ddae4ebc790a08cc63dcca4cb2c4e73674968c3f8a14df8d9a9966e88aff757f
e7409a15445142ade0076388519aefdb7a47faf6be104fabf8f8d22707f28564
54baa588f27d87629331eaa3c20f7aa6dfeadf80ce448287e51c89b887beb08a
2067a48eef1668c2c0228afdf621a93ebd034010b1f2663e4815b2b38388c5f0
14b203d048823bf68d9bcf8db47c6cd08daf2f9e032bd6a8c8b7f43c160d1309
bb9cd9d5d0e98014d83fc1f66398149602912a31fec45df5ebfe863e05ffa354
02a625e3e97dde0908db07685f2e1731696dc041fe354db9d32d04bc30e06b2f
54a89c0b2496e12f3c2d89ee131860b4ca3a1585e08b157e91e1f0b76a6a561d
154ef68fbe8809071b6a9dcb3122a303a29d5c9fcd9b3b9e3cfcfe6c77dad065
842abafc65a857bb07322bc28c5e1f2dba5f26b516ebd335520571fc538a1c49
ae685b8a27cf92ab55bac2b92fa89a0daa72a13c8e98bcdbfd38eef02f80b78b
f6de9b3dac2ab3daf7e9b33501e2913c29f21b73e75ffcd069ca88d3db2fb361
af838994c95310a566e9f521ac6259d59b1d54fe460e5ff4ca4498fa1011131f
1367606da02c03de512fce626c2aec8195b8df26e50ac8327f458f116856ba6f
6cb722477452bd3b7e1fbdfaf7187bfb94276ee510f351f8fcfc1a37fddd770e
af58611dc4d71864da71c624f7cbf0aaa44b6923cd4a9a1611d725075477ba43
5bc0e29ac470ad305ba2685ec0c54d60dc6451b23d041c6d6cb2d8302aa79403
6db86ee51fb0b6fbd08c91bc49d71b114fb8ac53be029bcaf6561211dfa14bee
29d2200f20c54ffedbe035ab6bec64cf78051656b4d846a966647b0a6060e9c6
0ee8ce8769beabc9d96bf0785f6b3af4048f160a3fa32b571a6070bac7baaa7f
8abfdb0478f112f9d5ea21783f4ebcfbfccb5921554f3ea396aee04a17b7e3ba
72eef7b462ca3da832f82c9f573e4e14b5f348570cda73d346f8c701901a54b9
341146b95b75e1e113af666322b484f57ae2524cf74202a7cd6e04c77c27f6d7
6c951c460a4cfe5483863adacafad59e5de7e55876a21857733ca94049d7d10c
0c9961c84791dcfd1b99605f2de80d5893809a57daf2f97e5a20769ddbfa8b03
409f40e6972e2234f05365bd6c8dbbabdd6c31e639164f57ab13b722a03d0de7
d080d433eff0a6b9b0ea46b601479c845161296490cd201a625133f4b4fbe30a
3b9869e91d108a5d1b00796a3322ca05eb1fc85f0c6b0a62ec1d3768668f3057
40ef87da22bb5d75979c47afa5e1d81adaf63cbd0f9295720e35b412fe96155e
09ad1efa724471cd4cc19d3ab609477c9e66e489dabb5bbf07c6f7397ab99c25
c4abe25b029293ff9738e7a12f9b45863fcdab1ff0603dc923bbba397bf24e56
2f4d0e362895fb5c6bb3e9164e92f15fe8c65b5a9238ded20c6f826191e7d094
6e73d6a15fa21e298bbd46a7188d37ab20b8ef2dbebc7afadb9a48684ed36c20
d2fe0faa63f9394b5bbb9019cd64df071085710750c08e6e16806925fd202afe
961c297fa5e11ee671da53efc53b650aa6bd1804dcc3cbb18510c6245038b03d
8f439723d8c49be86cf7f3044536ce41c07367cd0a246e4a4909978daa074a82
527d59f0100c78832b0d42a32ee863f0e7e72c9d2eeeca09293f0bb19282591c
7fdce3d4c949374b3288061159a1b15ae30379e5f97d5fc4d9e67fb462edcae5
79c36f6248c09c795d6ed5c79d55c556fa9a198fef470ef92a132c5c1def60a4
97d4924e06704d4a96d2776e43bb8c8c489d8e17db2236db2c1cf4209b62a254
dfef2e0e5822b161597a2403dc97f749244ac73515cb4524c553debfff9e162a
3c72816104dcd242474d20444455299b8027c490f72e5e3098cd5231e1376854
6c0b2d9cc290f722c1c4378ab075fc7f7a7b911df0bd78c247bca493534f1889
0a85fd7a6486bfef24413ac82445dee24a7e2cc3bb5085988f125d079c3da01d
bfb0cca224467480f64a12fb12c282eded4bd21ffb623214c256f81599486e03
1ad76949f2d7f351fae05c6941fcc7072f4c46a3a9558c40edd8809d04955cde
c32bd956c8d1dd48ed5eeb1541724790996ce67090f44a58a365bce4fcb25ce7
b18f92605fe1de73b3710d9e546d6588bde3606f1f9f9b6e7b818cbedaa52974
bded176176b775344aa8a1586e12044831d5376c3587c8d4b3ec531d84d34d88
6d020a049e623eb33a965f5826b14b6dcbb6d6f0038ee7e6725c434ed461a318
48bed89bc989927e1d61d0f3817d3a33072b2f6524820925661d60d448bc9eef
a7f4def1c7ff07d17b5dd58fc92f18ee2dbee6dc7654fd30a8653bd9d848f0a0
e3c32c4322ce2bcef5c9f9b6ec952bdf39417b10d26783c41cb5c3800829e167
e354f50debc1875c8d91cfe18b29f339b95e48585e9a9574704a8c0e98e9a31b
d9bec1f15abcc3bf7e650ccecf7d9c4d4d626d75f1e37e32010d828186f0cc58
f9e3cb3620a282ae799e24014204decccdc68a3aa437d7483fb9493bb7cecd11
d8915be09d47ab13b6ddb51675df4c41bbef9a71cfacc102005245d32db31ab2
c75178fe56938310a09541354ec4e4206b8c82d6bb021e9283053aee22d579f1
78d8e5605763f7972ad7543fe0a9dbc0f5358530c5b7e372362fa791a9d71021
2689f871e649ff598196192acd0f0278a4fb687a44186402db3602d18c1064a7
36f9448ddb2d7e5566ded020b3a5db143447218ef4fb262b7aefd311d7d00a08
f26be4514268363e9ee4fbdb47403ea9f4e1bb48369fa38f2e4f9c48912a93fb
0de586d0c74780605c36c0f51dcd850d1772f41a92c549e3aa36f9e78e905284
080cfc2f2af45393383fefa52a71a221398b1436a6eb634af16a6bc132d4bd5b
f2499fa015e9ab1cfdb11c613b66d9be72901ab8d105864b8ab228f4083f964b
5fa7bd35d3568bec4fe069f285c8122193ecb54096db8e691de97fffbd3ead05
84067f4cf110288b4c773a01f43514fea90e25482589df1c90549b66af872472
4371ac84df7063f7e82980318a7322c32a8be2fc69704f8948bb4fe805d478b1
da5fc56dfd1c80dc3d495f30490f2c677b5401ece7fcc61591f71dba3306e988
79e0cbe60504c42151ccefbac0034d60814b3c68c0ff6d6afefcf016a2cac108
c891a7cac93d0898dd640bb7dc8874b69ef28c2dc0ec37291eb3ec5c18d4831f
13847834e3295bb1edcfc6453e81a6c351de860cafff04114b5a4e205ba58bb9
e14038d130cbcf48db7f431031b4e18e4b003d196dd249c61adaa08e03360d1d
66f55b0ff8332a6ef017b1486371a397ae03e73ded935fe1ce4e5423e50825f3
b082e3529b700824e075d0d51aecaa2138fa05d10003d7b617e1d1d36d0fe31a
fbd72501c8faabc92f74e709266255d78c4c91aa3ef38c621acf3ef9c62936f7
06d79cd52fdb691a54fa96e23215fa13e61f5883828ca469b749b2e3b3fa27d5
b3c651dc5c91337d3b5471571d8470cd4c314da4a972f4a9288fa1f0c6348cb3
5ac42d247222ba86956d42dd253c4d8d22c1c22937a412fb21a129f14cb99921
7db2046d3dc779a630f5704a82f4375af77281f07046760afdda93c8e697de72
9360d830d54ffb7a3ac9eb1123a31ca53538c1c2f109cb366bd78c236ccf737b
83848a69eae624492bf1a4c8fa60a3169e65cb606e5db65b0a61177afbbd60d9
ee2d41cec1138c87fba9f13eb02afbd2c5f5e31279ad1b7ad31857350db136b0
ea70e1021581ad52fc7b28278b3dd046875e03d5c46b290acfc514bd0252298a
53d348ca871dc1205e778f4d8e66cfdadbd105782dba6688e9a0b4bdee4763e4
a9a90162c463954667f60abc94eb20c76e2bf8ddd085e2d10395e375383f533b
7bef9c4b04556c91a5dee0620d6e975d5707f02f0ad73d1c2b18d270eab7e779
3cb959eea969289fa67d3d71aba6acc765cb8fb1bc3bf95355451abb8c02859b
24b0c46484a28736a7250b7d8a1449bf1e578df7a963948a42f7eeede4c66b11
92dacddaa8097cd2401394a4ad1e032b112ebd5d9f8801b2ea102920214c91ce
e87638b9682d71f8331898734064ed13e2754ad53d9046af8548421178f6717b
64bb0b8eee86acb34b57fbc43a0c65cc1b13383940e7c50c6f74665d39f78fb4
b498e102569546ab2eaaacc7576ffa6526f74c72ba680d778a3068773343daff
a71628c9cc10200c9566ffcfbe48965cd21a192ae908a1f251dde3c94ba9e2df
39b4b52a4a8078b5bd20f8afc9f3eee55e285442a882b702931f4edde38e5b47
72977f5d634ec231dd6285e0c0eeb1053496164ff5d1088c8db2a1370d6b647d
93725430dcb60157a0cfd9984e92bb52359bf40506f9a61f1bf1fc990fb325ae
939e54315a013d24d6b0f54b56e87b23f89a7e19103cbbfcf4c78423d31d3f70
c451c6d3f16ba7f232511c855856f80adfc83ac53890a03f0d50f4f426e6e33b
2b0c03c8a399975a07c78a6959b12cd8bab62a478bc1f912db34bfcabb35fcfb
864a102aeedf53dd9b2baab4eeb898c5083fde6141113e0606b664c41fe15e1f
1e08b2704f291d11d628f51505f5884800655658452f093c4bce4186a2441c6a
c688254b98eb5f736097df4f156237b3d48d21d651d227b1a0adc32c543e93f4
de053a67b29319a4e8988c9b666ed9f43cac43fd62c56c844615a4bbbf417b54
85fd8d91629bb18b27441038f3dde60a3a8aca35adeb11b39fa4f7202298f22b
7b41a279684efaa27afe90cd1abe1b29d79684c235e77138cb6439cdc4689725
cb06d7b0d36eff3f5c9b7baf8392c3ad39a2be882cbf688bed055c62f27052cd
bdd35ef9a81822df969fbfe6a0bbc7a0d0635a7a082a8105a001a20a8f557ae5
3fdcacdf51a2f08339d2660a004d06b3bb7f16564d4b9329b8d94c2f3a56dff6
d49d01f0f06a4d33fac8c0a34a507d876d62ac98b60ba836df063b2811a4af64
46b90fcc9b0d8d3e99bb77a1cacd65ac927bcf012dde69b8cee438875741b632
540792da9cfcd43dd4ed831f0af021329db3a8ca28d93d65444c6f98ceec287a
a45febacfe256008d9d3d993869166e5438e3036164cfc7e3ac2e494fa5f27be
3a7ffab4f7548f89a383724c1d344eb68d9aa6d2b51ba840c0a78c20849c115d
f4a0bee94e611229b9d258d77c7066b3f9ea325dd4125fcac6022caa37c61f4b
1cf23909cca7b223cde4627d1d95f392b7ac0e6daf4c41dbd1f38910875f88ae
e0fa1c4ad3af4af45a12ac8ea3850ae414d44685b445efa3d14c36110688be08
1495105d6a80057d5952bf824cf45bf6a5b6b0685d08585d105b5df01ba421a8
7c5e9f900cd2ef6af8b5a2e973e3d019157b99e96a6faa5ea58dd0c4cb4f01cd
14901163fbbd5b4663d8d303fae86e920c0d46b318534a344df12a47ab6bf51c
c8109cfc1c4610554b877c0c8cc9e72d8539a3c92fea2e4b660d8b83bdbf97e9
f5e1c106d1252a1f23d87c87a7ecd4c04be4204e4a7eb9812e9f182e9853ceb3
410f532b707e3e0709345bf77ec11797924c6b9cca80f2c5d03c8fe231098613
089bb8fb9f12cb9969272c1698c8005ebd08a978d0c27b7c29e83d5e6184ec4a
1d613bce91a4087d78d671442710367350d24e01949d880a81c4a97edfa92a99
416df2f768c9a9f5bfcb0a481a069a4b531d7facc2abab390521a591fce03c71
81be0417ab688cdc89adf70d626e98790bf61916a8648f15ad8d641d8e786db4
175589c1683688a692a964885eacfb03eabfa7d0706ca9997ae43a29e5f72ea1
c23b05c7c1b1ec8d0764f458dcead560cc95d8b349d8a81138964e2abbcaa879
3c10d93b58bc8b717f9855ac233ee1769713a6821967295903eec2f9e94eb154
c314d7c79165de87411761a66181b337d4871ff1581b55a13461ec69e70bfa21
3c2629215af4e369e66273621b863af3b475ecc437cdcc52513689bc728424f3
a55d27a2bf320b7a9d8869eee09afcf173ff550257b83eb19e6eb435bd83ebd7
cce0bb89ce4d8707bcbb0dccafb60417e01d794e0c92d3619309fb9a7c8e9601
ffe8225e824c6921049085ea50fc2cabacc508aafe996542561cf2a3dd458e37
7493245ec313ca18d7ca85d3cdb7c60afb0d66c3ecab18d01d9b837cc3951b09
a4b90c9e1fb90a73852d65b317aede1b2b8a11e16cfebb30380f27198b96d1a5
fa70267e7df9afa4119abd32a79e0f0ddb03a257229aa17a5f2cc27b6b0e57a9
1f13943fba6a68dff004495feb6b1b389962c83adbfcafd3c80d44a8cef0c6c1
cd12d78004cb941659a1c7b2f10cdde746a754de8f02fe49a9ddcecffd51252e
993803ab04765677115011943ec35997846aab147e5ef18c227ad6c5e98f124a
f321d3427ecddce14dd3167895b3ba9ccebb90978f20919ee518ee8a91de0255
11a1f5c1484cab33ed3beb5e86fca251f7fd94c9715857b660a2b47c35492dbe
778fa98adb08eb7c785e83c02160df897a624edfd9984e82eda09e3253e638ed
b60fe032ad6543d858007f32a0ac022fead12391ae9e7022a144e67651f75cd7
889b68c8ea65fbe5f1cd6c790a7282492f2963cb8a6025d726fc9b7edc1aa98a
b8e1542e1a73fb0c587e8fa249ca3f444e88757855368fe9099cd5f44a89e662
4dad77630dc307f9158c74d250f2df579d0d98c136c5cf07b56b6353f5f71d4d
c63194382398876de2e3c993c99b16d6b9d539c6dcb5ad817dff0a5bf80478a2
b5d8d11b7d8bd19ecccf2cd5012d2d56dd1adc0111a6752d1d1669fcd9fe6fef
1524170d75d95ac77a05a847a67a264b8ab0c13d3ac7fe92b72831c201cc3764
9d19abce0558d99b5f76c605c86a5d0d05b645ad533eb95a5f0c7fdd6257b166
f926f8045cabe4ec8f7d4c501299a12c1e70eaead4fc8da10138d966f00ba885
6c5c8f543b7c306547550876a39cf720383405ba49d04b9fec78dfe58528d489
4e8a21554dd9c561252cfce7365c38ed0a99f435abe52a78f93cb0b920c95d5a
067481bbff0492b02ff025405aad744318a2b1eaeeac5a8387bff3d5591fc958
aa12955bc31d3ca9a35060104cfa905088ebfa08e1bccfdfa2789f22cf0b3569
7e1f1728c5f9c0fe19428f07922fd914b5d717502c702b748ed80f59e0ba1537
d96ff0175bd81a56cdd0314afe5fdc347c3913faf82252b11dd43535485021bb
8f716720ef9caf72149e262748e543df1fc2996cb5ae95d6cec2678dd06601ce
d950a5680508203fbb8a8f3fd31d3ca86429a931a4c65430862221ea13cdf959
533da7e41bd99550f63f152ef1e613f1a78e3bed12788664d536c6ec42b5e0aa
2cf35ac96bb23982d8ccd084a8ee029dbb268cdafad42d8da3c3d8cfe61924de
d6083933b9b5719a03522b372361e1228b365fe12abcee7fe383b4f481dedb18
ecaa3cb0bea1fcfcfe2e0aab715068987ab9f911fe68c250a81c89845841f0a2
9f370991169c0bc6ab2bf7d4e7acecea6f21bbbce47bb0a6759e5fb00956dfae
794628944c0d887c40bb399c4c5843235843e5e0e6cc0d9625b599516c7fb7db
331449e74c5e18879ca4fd0e09397ec1f351c3a3231265b9c6c65ed22fda58a7
d5f2a3b15df54eb6759a61add5f98588548e52332b9576dc15f15649d4785848
ccfc4cdfdaa25f9e5565f239ed0b16054f1db47c05ad62aa859c06632bfa2841
a0b3f66a172de753bc0c50243f1e9379e75bbc697756312e64a262a719a0dc12
d5afa16ec85de3ea0d0d443c15f8f9a473a2f3c1e7d97e31c9de49ee26b46f1e
5ce23e94594b8358cc81dcd3ddfa42806ea285c11c6c1ee6468e291af199481e
a0a5595a51b99c087e57a9af34aea3df9975b20e3f3ca214338642b018adfc66
2dd3787610d40ef3c18fbe5472ac12bc60f28a7fbb67d488538573b12d536e8b
ad87e5a5b3c44d829f99eb8250ba3d7df296a8f252aa92c670f1b55e4c95851c
f1e1bd2df35ad65862908a77b6be130084ef584ccaef8248edc0230c37195d12
1e3eb73258c1342715e1f54a6715bc81808f081a85cf9167013828e6c269f2c3
56bab805b358c0a6803509b48d35d565344f09b6001f5d923ea0c0f38353f9a6
29fde3de7973ffdd6e13578da0e7056f5e36c07b0c83d7e350e56927639a4454
7c1a381b46af4abe71170523c74387c433a82c46401d66bf855ab96611998862
6f80a01c348b19255e5a1f2403aca5034d167d7daba7563fc30b7941465d3ea9
a35374953cd98bb905640ec11d905f954e74333fdf28f516835b2382bd0b74d4
f37eb3f37c03761494b43c4704c9feb28dd19770ae8ef5b0eb5cbe6462bda62b
73bbce40d06171a4f7c2540f904c19d55ea888f86781e8e19b958e583bc64aa8
890061d496e45f2ca2f740f67cc2dcb5aa3395336be2425147ed27d464d2f3f7
53d348ca871dc1205e778f4d8e66cfdadbd105782dba6688e9a0b4bdee4763e4
ba6db07f5c7db82438e7a2afb5bbb52b08b1b4771a8e602b650fa7e7f7ce5b75
6726ed70fed76560026ebed8a93550496817379eee894c870be016b22f709846
a0ca1f7fa9fee26261bd13d726bca6260639a8f9717a697ffe8c0905f873841c
5461b24e5869dfa3a8c0f886e57be5b6471158615551e785d3e68a3c7fe193d1
2380b0d9088acdb5b0820620eba208e4bc6dea8897269baedb755ae437a81edf
f92101ceaceca3cb1f25030c72e3442cb9d9dda6fbe943d95d98ce213aadfb6d
9daa9e205fbe1059cc0c3f19fc334113e7102c6b76dc80c6ef2874f607b7dde1
5604967767c82a70d262d96575747fcb337fda1abaa26e8b27d3ef98cef8355b
c25b763f656235540a7121d8fcb57a63e600d635c6772fd554f1837ab873e522
7790533ea7b9af05128306c4b422cbbdc01382dacdc8d1b82eee025b29b3936d
4b74a861f5fa13fe806582b4bab4a19c96e58e0f0b4bd7e6755a18372bcb65d9
580021fd8718c614104dc092f44ac20350b0fc83a0144f1a3a1cef03894451e6
eab6c3a9a3d333fc310902cc71b34ba3437bbaad0e978b19542c8a4e9f4cde72
0de0a7ebf50fcf6c4b82bc7c6c7f6c20034b5d3fe782b81de3d7e896eb9ab6be
6ebd4c027dcc11132b02df9011be80947ca913f0462c4fbe0e78a7d92b1185a5
0da5741c5126f9df3eb47ac151666c603878491a01917c6e997e6e48a9147f4f
627c859b5af6d537930fd16148eb0597542bea543f65fc2b0e5f188b5a458529
c1177cd0fb7fdf70863faf7a839d4a25d4d292eb70fb3fbe155cf50f61b2941a
9f33109fed31478a5832a240fd19b1657cb5c2218b766f0c316958b0aa367a2f
1721de3fe9a6541355d787d3201c1808133cab712d09d486f02a5559ad0ea53d
d4f5c88aafc6dde3603baf2d90b5d9ae107f7d85c6badc9d989e195409435510
b47b991186ee6666d7a47005f949b5c2b183757fad52c7256ef4b6b15eb6cfa2
4f258b03ba2741fe8410819ae5658be896570327ab357a3e4159ac8db03c4ddf
7764e4c8dfa72e26fd6d4f02a41f2621aa6eef234a55c52a1db9285052cd3f36
591a7d20969f081cc3ce052c0264a71ec657c8fc9db1b35bf6648a156a9aa651
b669e07c7bd22e571f9abc1d110ec9e133db14e65c618a4476d5f6453c96ff46
3765519f3bf5d212e279536c9f042971fe2c012f78720a4e115d69f438e92ebf
5c6e5907d508eec7c9d0ea3f42669bd0b12811672d020711765fc3d60b39483c
d5ebc563f657b729df2aaa85c73ce8dd2678696722a01435e5e269b92c1fddc5
9d5bf2f9466bcd8b5fbe20f14083066c260a932fc01ebd8c7286db4268a9ca1c
77a0b2b0becd26c5a7f0c0c8e7afdb98cd48a5b9ef990816861e9fed060a1f45
e08c6a611538bb926c919b70a9a9ec64259a59632b492ca9de35d87cecd617fc
a6afafdc3369382d0239457a7eca353d509a5b12280467a4893ac804a7d26e10
278462b5a4a2f9a9d672f903e37b53b4654148c56ef76ae1107618c8ffdc31f7
7eae4af7f8316b663bc7d46491d055a32ce2a74bd30495df200474ff542c7b78
ce6faa407798d091eaf0b88175fe47395a8b15c918ef24a7dc940e2de29c33ad
94a000efc8133b2efa5d2366ca39844b3275b80560f2871ef0ee7198be6590b0
47819c48208e7314358f0a3ac48915d40be4e5255eefdbe6ff83ec3a62452cd3
b3df557c8453058252defc9710ed3409be6f058f5b6266964e304985b11bd975
ed6aa53cf73e7131badf8d0d2afb3d77f638cfc1fef4900207d1c589a89e75ea
27f1d66f8a1ee5280f4e92508dcb647e954d53004905d08a75574daee4988360
3ec2fcfff2c1ae95ec6fd092b205076e38da8ff37a5c335a235e058b34489fde
84b2bd2b6c7d59e459ee1eb49cfc8443f70142f6335b48b88574a3bf018a6263
565f5db1fa49c9b610e62e3076da1c599036c3cd015a46b757314dd510f499f3
a184cec893f8d2628194ef3c51a6037dae98031ba24f6fdafe7437f5a11be73d
8296f44ffc8f567b75a50e545c691287fbaa5cbc038079fdfea327981f3c669a
17daa50766e6c78885da33671385e9150fd91399955b57907fbdca3c41268aae
f5d8c8686424921ecae57b691ea11d38c8f0bc6fae4b670dd61f63ffb4a999b4
0a24ab7f300fa8d99ba389d52e228cf6556a9d27257efc4a81e8ee87b0247cd8
8c0182209d882ea3906289406e3ab3e25838120b82dda91b314d7abf5cd2939f
e9f17bb0b9c3f00de3cc32b22ced3d291aadb523ef89dc6c3cca9787310e6018
b38af404bc6f7c6a144bd3221d396b40cd01e81ebc8b0f3feb03f70f9b1e6ff3
4ce204a89f19570a9ff48b5399ecafe5fee94688650dd642aa9c09f132041bff
3aa00ec7efd27489e104d7d36dcb33cb55df2fb4a69f5736202e66d9f5c30f3c
3723825814b18804bce74619f2a4d0e8baf62370a40ff434a4babeb979ef092f
ff82a7105d9b292dabd82d524ca655e40e1b7e12a8efa04334499d5402de3901
8136a1e328a7fb95d790463b1f76632ef20e0984006d141d50742db1523cade3
36d9bfb943eb7c380f08e1ace2945a947bc0f020087fb75dbb3eb79933936d32
0ae8f6a3c78170af32976c1fedaa4a71e2b2a6607beaca60a2c5f2edc0330cf8
c7280d391460598dcfaa25a636739af4610fc93e1b8bb6661510889f9f86bc9f
d982982a36dc51d1345168047874405685ac15e82bc19d605af6cfc73ca0a359
6a662d67f4e19656c1d1ae51a63cc472191c22ed3551fc5438b148d95b691bcf
5a9553883d576cff433406cc9a949fa6fa7565f3cb60956d511711ff829b5b7f
e12e52ebeb8c0f0edc1ee4340b0f9d7a1bdcccd8a5cf9d38e4a5daea173e40a7
623e067f349d6d8de3b322fff2e96ffcfc4649f29278f6bf1dde1ec286fc9502
e31132d0fccfbe9667551d1dca4c4969c1b53c460fd1c26e4311bd1ab8367b05
07e613d68dfe479ecb362a2baa313ab79a8e2796ea6ba16ff41c47af33b84cb7
4465cd3efa5684665c72cee11bb734afa1dfca8531b459802ab952dbc3a5b4c6
13b1c2ccad8e209cdb46ff2787819fbb9e9c5554b931ef49f0a12eeb960fe937
38ee0ba81290236441e54a5cdd0071a684a4a63180aaee63619ebc883ba2547e
9c33048aa3bdbb4cdfbc045e42c9cf02c632687f105df5c03543dbd91aea6c1f
6466e536271398cde0baef87998dd5fd14118242310b99f2971da7fb236c3267
27c0e69e629658c264da83391b5ab2ccee10ecd357d4da2b4b0e52cd9d7faa9f
8b905d5986ce45a268a4b0b0255601821424b8313ccf399f67a32aca1b3456c0
60ccb6bb561d93e142b4d68d2afc1d0519e3f8450e38f0d137fbf66c871602b1
4f4f218f6636f2dc65607a485fadeb5e53b8d42f81ac989f5b7e230c3b4e87c3
f843926f2adeff2032e4bb4d8fa7a38ff86d76947de2a1a2e37313f8221aecf8
f0211d32c841abf05167f202c3d6c2314a44d575fb758e903463128917c1ebe1
bb4ff4269f6563b7f45eac4775845a91f6c04049f4a11570954efd7624b145ac
00c69656fed25c4c2dd1d9093c164d3ede9d5c341c756bd08b3d24338186178a
7b8dbad6649c4c7f5104218e59fcc3913f11065c1198033f44cd1787bd77e8fe
53b6f100899f5ba32861f86395a326223de33879a5545717f3863e4164b80fb4
23b8bcbf74eec492080ce6961007520caa2df23061441647f4053c533a58f833
e860979a03e85d285360d0b5fa2d085e945ffc7146a48c0a82eb5ed627878a75
827bfa078a353d1097cbd1b5672c2d2ee21326b932939541d42bdf43d33cb65a
cefed99cbb7b857fa9fa7353291449b912c90619139e737db338d71c72866b74
a4e6cb6e23d6dabbeb96777d05500033a98040e2b080a0d96ba3f58d9d7ea9a3
0aad1b00a5227d9b03d33329a5a11af75c75c878a064c69b276063cbea677514
d4461bb2bc7b436a21cec9040beeb64981d5abe5f6a79fc11a0f367f58c8d546
b21eecb69eb61bd371f4e6816869f427fb1f3a9beaea5305f5d284a5d2ac02b4
530ccd7b3b485a6441beedbc663ae6b5cc7f6f3ebb2d3f5d7a1f5d1a7ad78e38
9c24e363722356ed5de895dbcb8ab77cef68fd70fbb708612dfe83def9c48233
69ff7fa5b8a541952c772b98027a703fd4031e1c9c02ae7ef0f7d452905fc642
ae92e6f6735b158706cf1cb306cd35b90539557444af7f1eb393b3269fba1714
cb01a74e23e701744c0df6b83ba30c6cf818cb0b7cdbaaf7c050ebc130902976
4b3a6306c6173baef5a2b89dbc946a4fdacd4fd6b0f6a2326b69ee78d09c829d
2b6e320e1944c9af7d7fff60c9128db4a4dd594737d0550cfc0cfd91156f2d01
60d731bb731cdaf286a7ea8fe0c8e5f50bbdc4d9db7fd5c4061430fc6e292298
d39e1ad139e9c165ed53d5537876b9e5c8f6c470ca78db27c45dde3fe2ec2112
679ec912359feba3c7072295d84e26464a54d70b2b82cdc67a82381cd860ff0b
4e3e23965cea8085b28b39e2c896c60d8b8b58d46a6ade43647fee1d2908b2f3
a1923ed584a7bf961375f454c626c7134e24965fbe7ae8e77c350ca67d1ae321
8b1a9f74ed2cae27638deb7ceaae634bfb8e776b015ec54e7033608edaba37db
80430b64202051d0fd09bad73bcc14acb9bddf7bf065254940ab7ec51a4bff8c
80702600ca372c0af610b65708d152883d4fc3b153b3d5aabf32b641b0aa7cef
ebb4635ae9ae7a3c6574126cc0ecf619fbdb0e3b1436694d788bbcc56472cca5
ef08a74b03dca1d3fa1b327ca5cbcc05f5bbdf947a6ab3c787ab332f4d7d84a5
eba1859b09c2d461f7b79df6cfb97c915328d182ecec901b45b1ff793f970198
cbb042eda7050326455dda506133680d5ecdcd81ca26d56b2cd9ea359146ed6e
30db9aa99ad68f4d75f2575865bc20407f73457609d9bf77e1cf9032e0936b7d
551a6ca27feab07d53bba655094291891ec3310f40cd455157ae14633be8b0f5
9997064773767eb1f231693a01329c082e4a2fbbbbe07b35134337dad90e0d76
fbbf3897c6679c021d898eef1a0e32b048a8b8635388268e614cb673fe1be234
c6a1fc06bb1588f2748a0197431ab7ca4e00e06c5a477a8cc3ac2f7b1d832a9f
39841f10b64b2117af6f2c501f30724ea7962ecd1cdf7c4109310a3ae4bdf9ab
2e17040f459cd0088ce8681b54fba52647b78d09e585565d65f6ab7777e72b1d
9338ceef7ee3656d8dbaea3b56240bb51020d01b1b1ec2e1f907cf71717c1ae4
16ffc21d24db9c88a87edec39bcee63e610d99c81c9696c7d989ce1abe927d47
bc13f7dfeb8a4c26a649b313f6b9e603e0328440613f69cdb2926632c5c2db12
40f087dd977495465c75f433772d4f7d07084d3933c4a444198403935f40ceea
554828fffc5a1c93710b91243a221845fce8f1b87122ac952550d6158b019090
a5b59579bd854f5f04681f507f562df8c40ccd3ed64ab3dc39f036c202f0a5d1
f9fe7236491dfd794e2953a08ffb2536beb4159cef48a34847b8185ee8db2ab8
246759b27732c7b4ea56b1e315087bceec9837d09661ba967221ef4ed8c70609
e5f7303ed1e6c24e3dba39592e0cf7b79407f9bfeb7de2cfb9add2ee29ca66e7
e2223d5be4f1bc5e9708eea506989957eb2a1509a382b2c8cd96c339d1dd100e
60c1f1a3160042152114e2bba45600a5045711c3a8a458016248acec59653471
d7df631a86f5d0080a81166b4c8e0e6988ceb123e807cc68ab815789a1197cee
b863cd00ba119c8eb8bfd86cb2c86128f942a9588a25684105d842e97cab54a3
f2215af0c8885ec788a4ca9ca9293ebbb41f3139d9847756fb66292c35afd87b
810477a2082e6062816d1f0a7305bb6c5fe419c340363699ca915fbd9dce23ae
8f2c93e9e30320153cfa47a94998f88d91e425d1336d05a8debe6a84c8f2c79a
23f97b243c12a3bef7001e36cd63e9b41cbd536c3f45264c93e5d1177a396a2f
783dee744ae85750068b55e1c12505f23361901866b0cbc9ea12ba68f38c253d
c193edeeb4e7fb5c3e01c3aebd2ec5ac13f349a5a78ca4112ab6a4cbf8e35404
2671b142f60e1dac579c9186cd1253698a854ed26d30d6696137694099f61e69
32f123e08f6ec788caa7ff19d122f449a0f5d9dc9263ab23c57141901f923288
444caa37b4c6db313d3515f714cd9841d866ffc5b845b2a2a596824cb893765d
961bb76313cfc53905d3bf9297bc1d61beed386f9e5dfb521ff1b825abd5a24c
68c76a1f4a2f48267542bf680903738188cbccb1a9cb49eb6c59bc0b569ecc4b
26e5bc89af547e29b147d31eabe0b6f9ba6571543301989c6c98abef69fd0cde
0ce6747062e06a8dcb21ad4ffbf7b80473f1b3b078e4897f5d69438c89b2aa6f
5473d313b9e5c139292203f3401dfac659e485245463389a64fcb7bbb60b92f0
2bedfd92a6136566bb858b2f0d223744a41a987c468356d069acc86f45bf68ac
a20e2703763a7efaf871b180af7e805990301307e8c2f250279ba782030264e8
16fe19c281523e2126d1f03c47ae95e769b7b2c395513beb5263637236b529ec
1db71941526a216209d1861fff6e82c9d5afc101b19d375248fe2c194e5a5421
3ee198fa17dd846d603e8af406c4b9363ddfd498011863fcec6299c9f91063da
bc0a282b61f079448035d6db6f8ff14cbb27794dc82617d03e6377145fdb9a6f
a48f9e9728b88b612c8fab8c790869c1ee8240c3cf4f9c099e979bb8575ce652
ad6043001ba9b2b3935cea77a1362907966a73ad2d8f0a4b4deedb29cbd4d84b
1966418f69f22c467fa1d698464baf96ec0298efa739743c5b060b93fcb0dbfa
463a51f6789517093a76d7eb08837502682798b00079d78722da62ad09e5acef
8d678f9dc967ec84913e4e0b8779dc404ad19309e09fc57df0aa37f3f63ec239
216fb568589629b115b0ed8fc41fdf3219d9ab804c6ce5e53fbc581a88427c3f
3695b8595fba49a64553809aadd00c2898eb454cf1655b0a940dd1584c443ecb
3a2dc5080830820f1e3ace98fa050eb6a19b209ddb799c4412a176588687783d
63e59d33220e0583576136de2dca308eb40c8443ee8a79713d6aeb929d481caa
8791e67141383854e27fa42bf42f42a26613f79a2397ba767d1ae9763e13d0bb
790e0d0e41dd15ebf666cfba72a892e30df332f8d68cd7abd562b8de129d329c
5b95a50b3c922298af9b4721ea475d07a10a69fe9b1279d9bdd4613f5aac2a45
c3c36f7f0bb89b97ae3b2df74153d09d8a4e82943308be947708f51d2ee3b56e
44afaa2b348594ad3486b74c4ff9236048db92c2911b5c4468fe99bdbfad212d
cc2c156442a979bcbc3eb9aa7db65a0c03ed65d10cd25b3108a006e4d778631f
39174c53daddb6e25b12210907656978430dbec58df84aef844b5e08e99339c2
315aafdff343cd5afe62096285197c413646e119f253f2cf87ad46866754e1bc
23433f041b55f15efea0bf2398a196cecee15af4bb2ff3c3587ca779e1a53391
1d68892f88afdaccfeb1109dabef8ab0f14146adaac06980fabd79b0dff99290
c70adf71eb16b52302de5c128c4ddfbc2e747ad8003123c42c6b0b1181a5eb8e
014fd2b123dd9c2a44eb28f329b95b06450ff00b840dbbef62bea69cea470102
00db894135643a78329b040712b3c54b759513b06cb00fa700c34c4afe8508b8
4acf3e4cd9e30735ddf7553e0d8b14e01bfefae6cc1bf0630c570d719ac38311
9399db17384092592431f2fe850d9e3baa3372dcbfb2c00dd4180900db2eaab4
897bb25a4d664992db60e5b17ac1f28f57f69c0c1d7225672c3bb8e28aa1ec4e
32d77a483c0e1a9db6299f3fad29f0cf358080385c57ac99721d678f1c2c7477
585a904f2da26e613a78e54317e94cda383c70fd73ed9cca8825084842998841
c50ec867359c4133c76e0e788636f36abbcd77ea9e64699e9f3e704b6120de4c
91e491caf0a3ddee36fbff1e4a99e854636f4faf178ae93e4e3f06de00a001e7
c7e5923fe07123b2a6a65e63de9f40ed5ae5bd5b2c3af06b5cd8d27a0ab78812
f9153776b8b8bde9fb16fc838464329d1b6b98f94d9481c3c01ff1b41ba66854
ed7e81d58f20c24e196886b5c37af8dff23d477548e53de63fb1eeb3996db53e
1ad7ffa59a6261c8b9b47f34a47766adeafef3cd72471da894304fa56ebb132f
e617da41cfa5547bcf7b5deb39ba985879ee33e6fce3914634477761ec40305f
70093065130ae0ca376982651919215f112ed6abaa66eb1a084c8ab183ddad61
f28c849bb477a7c47ec4f5bec9a6e72bc17a17439190707e6c5afbe539e71743
a2cd59624ff2f12cb434b2807b492e50299ac181da4358d25bb93aa747fdf676
df890b4c812b1542c81b91bea028aa4dc74fd1536591306bffd0742746176f00
e52e0c04e99645db14a476b639cca4099186bc379e2f2b94e386f5527875f8a3
3f4962cd5e2270ed1867999ff40bd0fe9539cd90380d395ed1b74510733b4a2f
b196d2e8bfe263e11f86981cdaaf0f053910cc275e5b0bac91134b959a92cb8b
a9aa4950906ec94c0278c7383f5de1ffab9bdbbc08fba4330ba5f26ebccdf785
7bdfdc10f37326264bdde13d38d850296f20fb9949e0574ff5e1028a8580f794
c17d16db53fdfc9b96d4e840f8543c6f9cbc1aaffad5e781f8c7aa474534fa11
f87b08218888f97388218d3e2489962403f7eece98dd8b4733671edeb9ad1a7c
0591550390996d992eecb96a5935a2f9b588e1c9984b74047b6a94a4b1940034
c40fd94f63f7139ffbeef9f2ecc92e9e902fab67ac7cb386fd84d65ead5c65ec
8e66d94ca595392f58fecad2652ce3615217d252f2bb681a67cb5c81b02e142d
ce55c63fc8659ab1fa24666b4291ac09ba5771f90a952063a061cf2d671fda98
208ad045a169d4a6d49fc2e31abd455e18611321d2fa1c8a5b0a8b9420add066
f3119d387c61c6eac021e5b28614b47ae27bb15f6ae2af1499127225602d1df7
f20d6657a733f160adaad298d79f887d6cb64be1114104f1441442d9f216bda5
49f0c3bfc89ba0cecd25e5db1a8645906717f2e2de2b76e0b437ca5b1bbf84e0
16cfdfffd18287652fc5e207b98024645bc05c87f02bcd8cbacfef98b7d00e19
2c2c7db13913420f51579acbb4eabff5f7487e4a2d10b2f004f718530fb90f00
3170f59bf2c4bf106712df7f11f7aedae8bd835b21b950be269bb3dd7141a71d
7f3af92c4d68d43530a2459f6db43fcb5873d9b53bbb27f79c9783cce5e27957
85035189f50b184e56d15ae1059af2d62b4a555a58dc5ded5a43b9c6668ff185
216aaff29e97f97e0be2bedf68dfebc39854531d9d8fa59d5ba2de36a17bdfad
e98e2a7c524ecf1dafc4e3eef9923233cb0b87d7c7b09dbfb598e564d2174014
fa107a3f9eb74b7c096ed1b67049171e17a1236fee62639941bbcdfb590f7ea9
498482fa9815bfc30830dcde2eaa3380eb31ca8c07a21d3e79db7d0d18b3cf07
52404b9c5d7fc487ed3f0e49d2c37d06e06b9cfeb10f9660d4b8099e5c1a9cac
f1599a1ced833d95a54aa38a1a64113d5f0a4db3cb613ef761180cab57155699
5391977978bb9c5fee3934bed2e8c891d7c732ad7d70dc2e0c922b6c0f62344a
dd8148a28955a7753548e34b0e729c56ea96d73592aafaf4e46a61307c36a6b9

It was my try to solve Lauda Memorial Puzzle, as "All of the information required to reconstruct the private key is published on the blockchain". But it was not as easy ;-)




Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BitcoinADAB on August 07, 2022, 06:13:43 PM
~ as "All of the information required to reconstruct the private key is published on the blockchain". But it was not as easy ;-)

Maybe also valid for Satoshi's mined blocks?

~
We can visualize with the blockchain data, how satoshi Mine his coins:



Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Cricktor on August 07, 2022, 09:07:38 PM
Seriously, how stupid is someone to use SHA256("")

More likely to be a programming error. I recall suggesting a few years ago in this thread that something like (pseudoish code) assert(key != 0xe3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855) would have avoided this particular issue.

Maybe a few of them might have been some programming errors, but I doubt that for the majority of funding transactions for this private key. Many are probing or dusting, but why should there be such a lot of wacky programming?
About the half of the total transactions are funding, the other half is stealing the coins as of now, today. Ridiculous game...

Public addressNumber of Tx Private key type
1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN
717
uncompressed
1F3sAm6ZtwLAUnj7d38pGFxtP3RVEvtsbV
129
compressed
3DnW8JGpPViEZdpqat8qky1zc26EKbXnmM
14
compressed
bc1qngw83fg8dz0k749cg7k3emc7v98wy0c74dlrkd
6
compressed


Maybe also valid for Satoshi's mined blocks?
Who knows, Satoshi was smarter than many. I doubt he used some deterministic way to compute his used private keys. But I can only guess wildly...


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BlackHatCoiner on August 07, 2022, 09:22:34 PM
It has to do with the time consumption.
Sure, you don't want to wait for 10-15 minutes? Wait a few seconds to do a few thousands hashes. You can't seriously trade security for a few seconds.

And considering that brainwallets that I've seen are browser based they are even more limited to the amount of computing power they can use so the process could be even slower than it could be.
Browser-based wallets are generally 🚩🚩🚩

Some tried to replace SHA256 with stronger algorithms such as scrypt but such projects don't gain any popularity since the idea of brainwallet itself is flawed.
It's outdated currently that we have standards such as BIP39, but it might wasn't a bad idea to create a secure brainwallet if the other choice was to keep a wallet.dat secure.

We may imagine that you want to launch hash function 20220807 times - and even if you forget that number but you remember period of time when the wallet was created, there is still way to restore it.
If you remember the passphrase, there's no problem. Just hash the hash, until you find the proper hash.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on August 07, 2022, 09:24:55 PM
I'm pretty sure people still use them. Even better if they use something they use much heavier encryption (such as WarpWallet).
The idea of simply remembering your money is appealing to me (but I don't dare risk it for a large amount).
What I don't understand is why don't they use the hash function millions of times to make their brain wallet even more secure? We all know that just hashing a subjectively difficult passphrase isn't as much secure as it is to generate an entropy randomly. There wouldn't be such thread if brain wallet users hashed more than once, because, apparently, some passphrases aren't as strong as they thought.
Dont do this. Hashing a pass phrase will not result in additional entropy. If an adversary were to know that you hashed a brain wallet pass phrase, they could do the same to brain wallet candidate pass phrases they believe you are likely to use.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BlackHatCoiner on August 07, 2022, 09:38:02 PM
Dont do this. Hashing a pass phrase will not result in additional entropy. If an adversary were to know that you hashed a brain wallet pass phrase, they could do the same to brain wallet candidate pass phrases they believe you are likely to use.
It does the same harm it does for an attacker to know that my password is 18 characters long. It lowers my security, but it's infeasible to break it if chosen properly. Same happens with more hashes; if an adversary knew that I'm hashing a million times, he'd need a million times his computational power to do the same work.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on August 07, 2022, 09:54:29 PM
Dont do this. Hashing a pass phrase will not result in additional entropy. If an adversary were to know that you hashed a brain wallet pass phrase, they could do the same to brain wallet candidate pass phrases they believe you are likely to use.
It does the same harm it does for an attacker to know that my password is 18 characters long. It lowers my security, but it's infeasible to break it if chosen properly. Same happens with more hashes; if an adversary knew that I'm hashing a million times, he'd need a million times his computational power to do the same work.
The scope of realistic brain wallets is very small when compared to all potential private keys. Requiring an adversary to do a million times more work might sound like a lot, but compared to all potential private keys, it really is not.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Maidak on August 08, 2022, 02:45:08 AM
Hi,

As been discussed many times before using a Brainwallet is a bad idea. I ran some test myself and found 18.509 BTC-addresses based on a brainwallet which also has been used in the blockchain before.

I tried to compare my results with the results of other researchers but could not find any lists online at all. I found some examples but not a comprehensive list. So I published my own results over here: https://eli5.eu/brainwallet

Please note: all published addresses have a balance of 0 so this is not a list for robbers :). There are also a lot of extra datasets I haven't used this far so I expect the numbers to go up once I use them as well (I'm in the middle of perfecting my own tooling and blockchain parser so this will take some more time first).

I love to get some feedback and if you have results to share which I missed in this round I'm more than happy to hear from you and include them.

TA

ahahaha wow so whats the public address ?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: pooya87 on August 08, 2022, 02:54:21 AM
It's outdated currently that we have standards such as BIP39, but it might wasn't a bad idea to create a secure brainwallet if the other choice was to keep a wallet.dat secure.
These two are not comparable though and BIP39 wasn't a replacement. That's because the brainwallet is a "human memorizable string" while BIP39 is a "human readable string", or in other words you are not supposed to memorize your mnemonic but you are supposed to memorize your brainwallet.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on August 08, 2022, 05:56:46 AM
I'm pretty sure people still use them. Even better if they use something they use much heavier encryption (such as WarpWallet).
The idea of simply remembering your money is appealing to me (but I don't dare risk it for a large amount).
What I don't understand is why don't they use the hash function millions of times to make their brain wallet even more secure?
I'm pretty sure some people do that. And I'm pretty sure some others are searching for it too.

But isn't that what WarpWallet (https://keybase.io/warp) was created for? 524,288 times scrypt, followed by 65,536 times pbkdf2. A simple manual "brute-force" tells me that "satoshi" was used to deposit 0.0003 BTC (https://blockchair.com/bitcoin/address/1DChnBTeDCRGxTV55oxJRYRTRqdN1j4Fxu) in 2015. It wasn't moved out instantly (only after 7 blocks).
If you use a decent password, and your email as salt, it's much more secure than regular brainwallets. My own (very inaccurate) estimate: a million times more secure because of the heavy encryption, and another factor one million because of the email address that makes it impossible to brute-force everyone's wallet at once.

Honestly speaking, I have asked Loyce to prepare list of tx ids and launched search on that. The result is surprising! (I mean it is surprising how many wallets were using that method). Each of that values generates address which was used in the past.
The first one I checked lost 7.72 BTC (https://blockchair.com/bitcoin/address/113pJ2WaiZRBwA9HTFuiSF2KX1h7gSPJfU) in 2014 (back then valued at almost $3k).

The scope of realistic brain wallets is very small when compared to all potential private keys. Requiring an adversary to do a million times more work might sound like a lot, but compared to all potential private keys, it really is not.
If you're the only one who uses 1,276,816 rounds of hashing, the number of potential wallets that can be found is limited to only your wallets, versus many different wallets that all use only one round.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on August 08, 2022, 07:42:53 AM
I'm pretty sure people still use them. Even better if they use something they use much heavier encryption (such as WarpWallet).
The idea of simply remembering your money is appealing to me (but I don't dare risk it for a large amount).
What I don't understand is why don't they use the hash function millions of times to make their brain wallet even more secure?
I'm pretty sure some people do that. And I'm pretty sure some others are searching for it too.

But isn't that what WarpWallet (https://keybase.io/warp) was created for? 524,288 times scrypt, followed by 65,536 times pbkdf2. A simple manual "brute-force" tells me that "satoshi" was used to deposit 0.0003 BTC (https://blockchair.com/bitcoin/address/1DChnBTeDCRGxTV55oxJRYRTRqdN1j4Fxu) in 2015. It wasn't moved out instantly (only after 7 blocks).
<>

The scope of realistic brain wallets is very small when compared to all potential private keys. Requiring an adversary to do a million times more work might sound like a lot, but compared to all potential private keys, it really is not.
If you're the only one who uses 1,276,816 rounds of hashing, the number of potential wallets that can be found is limited to only your wallets, versus many different wallets that all use only one round.
How is someone supposed to remember the exact number of hashing rounds? I think in both the WarpWallet and your proposed ~1.2 million rounds of hashing implementations, you will need to either document the rounds of hashing,  or rely on a third party to help calculate the private key, and I don't think this meets the definition of a brain wallet.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on August 08, 2022, 07:55:20 AM
How is someone supposed to remember the exact number of hashing rounds? I think in both the WarpWallet and your proposed ~1.2 million rounds of hashing implementations, you will need to either document the rounds of hashing,  or rely on a third party to help calculate the private key, and I don't think this meets the definition of a brain wallet.
With WarpWallet you can (and should!) keep your own offline copy.
If you're going for a "weird" number of hashing rounds, I can think of many ways to remember the number. It could be your phone number or full date of birth. Or just something you remember. Worst-case, if you forget the exact number, you can still brute-force it yourself given that you know the pass phrase.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PawGo on August 08, 2022, 07:56:15 AM
How is someone supposed to remember the exact number of hashing rounds? I think in both the WarpWallet and your proposed ~1.2 million rounds of hashing implementations, you will need to either document the rounds of hashing,  or rely on a third party to help calculate the private key, and I don't think this meets the definition of a brain wallet.

Talking about definition - there is no strict definition. The idea is that you "remember" how to produce private key. Somehow (I do not know why and how) single iteration of sha256 became "a standard". You may use other hash algorithm (eth & keccak), you may use other number of iterations, you may use any other way you want - as long as you remember what to do, it could be still a "brain wallet" (the question is if you remember your 12/24 words seed, is it brain wallet or not, theoretically yes).
The more additional steps you use or need to perform, it complicates thing and make it easier to forget. About number of iterations - you may use date, like I proposed few posts ago. Then you may know that number of possible iterations was for example between 20210101 and 20221231. But then we go to another point - are you able to restore your private key quickly? With single iteration of sha256 - probably yes. With more complicated scenarios - you will probably need your own dedicated program.
Of course we may think about many many possible ways to "remember" private key. Even the ways which allows you to restore that using just a piece of paper and pencil - for example, you take your name, dog's name, email address, phone number etc, take letters as a numbers (a=1, b=2, whatever) and then use modulo 16 to produce hex string. Is it possible? yes. The question is if it is safe - I would say it is probably safer than typical sha256 brainwallet from common phrase, because it is very custom method and there is no automated attack for that (yet).


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: BlackHatCoiner on August 08, 2022, 08:49:32 AM
These two are not comparable though and BIP39 wasn't a replacement.
It wasn't a replacement, but an even better proposal. Yes, you don't memorize seed phrases, but write them down. But: If you told me to choose between brain wallets and securing a wallet.dat file, which is how things worked before BIP39, I'd go with the former.

I'm pretty sure some people do that. And I'm pretty sure some others are searching for it too.
Hadn't found the choice from popular brain wallets such as: https://brainwalletx.github.io/.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Cricktor on August 08, 2022, 10:12:23 AM
An arbitrary number of SHA-256 rounds for your brainwallet secret is still security by obscurity for me. If your to be memorized secret is "bad" or publicly available anywhere you trust that no attacker tries to check multiple SHA-256 rounds. I wouldn't bet that no one is going to try this.

Brain wallets have in many cases proven to be a terrible idea, because those who failed and were cracked had initially bad or worse secrets. Your initial secret must already be complex and good enough to withstand even heavy possible cracking in the first place. If it isn't, don't use a brainwallet. Yes, a high number of hashing rounds do delay an attacker, I don't dismiss this. It still leaves the risk open to crack a brainwallet, especially with a poorly chosen initial secret.

And don't forget (haha, what a coincidence) that the human memory is a fragile thing. It's easy to forget something if you don't repeat it regularly. It's easy to become ill or injured and forget more than you can imagine. To verify you memorized something complex enough, you should have it properly written down. Then it doesn't make much sense to me to memorize it anymore and I could skip the whole brainwallet thing alltogether.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ABCbits on August 08, 2022, 11:46:11 AM
These two are not comparable though and BIP39 wasn't a replacement.
It wasn't a replacement, but an even better proposal. Yes, you don't memorize seed phrases, but write them down. But: If you told me to choose between brain wallets and securing a wallet.dat file, which is how things worked before BIP39, I'd go with the former.

Since you mention wallet.dat which usually associated with Bitcoin Core, i'd like to mention Bitcoin Core doesn't use BIP39. You still have to backup your wallet.dat or alternatively master private key from dumpwallet command/output descriptor.

... Then it doesn't make much sense to me to memorize it anymore and I could skip the whole brainwallet thing alltogether.

For most cases, i would agree. But i'd like to quote a page from Bitcoin Wiki.

Brainwallets are not recommended to be used in general because of fallible human memory. But in special situations they could be very useful, for example when fleeing a country as a refugee with only the clothes on your back.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: d3bt3 on August 08, 2022, 01:06:01 PM
For most cases, i would agree. But i'd like to quote a page from Bitcoin Wiki.

Brainwallets are not recommended to be used in general because of fallible human memory. But in special situations they could be very useful, for example when fleeing a country as a refugee with only the clothes on your back.
So for such case use https://brainwalletx.github.io/ ?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: itod on August 08, 2022, 01:25:44 PM
These two are not comparable though and BIP39 wasn't a replacement.
It wasn't a replacement, but an even better proposal. Yes, you don't memorize seed phrases, but write them down. But: If you told me to choose between brain wallets and securing a wallet.dat file, which is how things worked before BIP39, I'd go with the former.

Since you mention wallet.dat which usually associated with Bitcoin Core, i'd like to mention Bitcoin Core doesn't use BIP39. You still have to backup your wallet.dat or alternatively master private key from dumpwallet command/output descriptor.


Backing up wallet.dat that is encrypted with decent passphrase is not a big issue, attacker first has to hack you to access your backup, and then has to attack the file's encryption passhprase. This is so complicated attack vector that all attackers rather choose to attack idiotic brainwallets.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ABCbits on August 09, 2022, 09:14:32 AM
For most cases, i would agree. But i'd like to quote a page from Bitcoin Wiki.

Brainwallets are not recommended to be used in general because of fallible human memory. But in special situations they could be very useful, for example when fleeing a country as a refugee with only the clothes on your back.
So for such case use https://brainwalletx.github.io/ ?

Tool you mentioned only use single SHA-256. Use WarpWallet[1] or rehashaddress (part of ecctools[2]) instead, which harder to brute force.

[1] https://keybase.io/warp (https://keybase.io/warp)
[2] https://github.com/albertobsd/ecctools#rehashaddress (https://github.com/albertobsd/ecctools#rehashaddress)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: fxsniper on August 15, 2022, 09:47:18 AM

[2] https://github.com/albertobsd/ecctools#rehashaddress (https://github.com/albertobsd/ecctools#rehashaddress)

rehashaddress it work by using privatekey to hash with sha-256 and use it again for next privatekey and loop right?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: fxsniper on August 15, 2022, 11:40:12 AM

No, rehashaddress use user-chosen password/passphrase. It'll hash at least one time and perform additional rehash based on m parameter value. Here's snippet from the source code comment.


Thank you. I got it.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrimeNumber7 on August 21, 2022, 09:48:56 PM
How is someone supposed to remember the exact number of hashing rounds? I think in both the WarpWallet and your proposed ~1.2 million rounds of hashing implementations, you will need to either document the rounds of hashing,  or rely on a third party to help calculate the private key, and I don't think this meets the definition of a brain wallet.
With WarpWallet you can (and should!) keep your own offline copy.
If you're going for a "weird" number of hashing rounds, I can think of many ways to remember the number. It could be your phone number or full date of birth. Or just something you remember. Worst-case, if you forget the exact number, you can still brute-force it yourself given that you know the pass phrase.
You can keep your own copy of the software used to generate the private key, but if you are relying on a specific, non-standardized software implementation, you must have access to a copy of that software implementation to access your coin. This creates another layer of risk because now, without the software, you will not have access to your money.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: phrutis on August 21, 2022, 10:55:17 PM
https://en.bitcoin.it/wiki/Mini_private_key_format

I came across my simple mini key generator tonight, and I'm having another play with it.

Here you have another toy to play with :

https://github.com/phrutis/MiniKeys2 (https://github.com/phrutis/MiniKeys2)

This is the fastest public program to find old Serie1 minikeys (22 characters) in the world.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: almightyruler on September 18, 2022, 11:19:16 PM
Here you have another toy to play with :

https://github.com/phrutis/MiniKeys2 (https://github.com/phrutis/MiniKeys2)

This is the fastest public program to find old Serie1 minikeys (22 characters) in the world.


Link 404?

Other repositories under that account seem to be cracking based, with executables only... so yeah, nah.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: n0nce on September 18, 2022, 11:24:43 PM
Here you have another toy to play with :

https://github.com/phrutis/MiniKeys2 (https://github.com/phrutis/MiniKeys2)

This is the fastest public program to find old Serie1 minikeys (22 characters) in the world.


Link 404?

Other repositories under that account seem to be cracking based, with executables only... so yeah, nah.
No vouch or idea whether legit or not, but there is one result on GitHub:

https://github.com/Yanmailde/Phrutis_MiniKeys2

No source code either, just binaries; so proceed with extreme caution. Maybe it's possible to contact the repo's owner to clarify.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ABCbits on September 19, 2022, 12:30:20 PM
--snip--
No vouch or idea whether legit or not, but there is one result on GitHub:

https://github.com/Yanmailde/Phrutis_MiniKeys2

No source code either, just binaries; so proceed with extreme caution. Maybe it's possible to contact the repo's owner to clarify.

After reading one of the FAQ and knowing the owner delete original repository, you could wasting your time.

If I find the private key can I take all the coins for myself?

No, you will find the encrypted key.
Only the organizers can decrypt this key and pay you a 50%.

I'd recommend people to use different tool such as https://github.com/Coding-Enthusiast/FinderOuter (https://github.com/Coding-Enthusiast/FinderOuter) to brute force mini private key.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on September 23, 2022, 04:11:19 PM
Interesting update...
Address 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN is derived from hashed empty string "". Two moths ago (!) someone sent almost 1BTC to this address. I guess by mistake. It took as mush as 10 minutes to drain this address.

https://www.blockchain.com/btc/tx/37e166a1e52e96bcfe535738082e328ef8db56aafd6945d9cad6f2afdb34b4a4


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: casinotester0001 on September 23, 2022, 06:01:23 PM
Interesting update...
Address 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN is derived from hashed empty string "". Two moths ago (!) someone sent almost 1BTC to this address. I guess by mistake. It took as mush as 10 minutes to drain this address.

https://www.blockchain.com/btc/tx/37e166a1e52e96bcfe535738082e328ef8db56aafd6945d9cad6f2afdb34b4a4

Maybe the miner inserted both transactions into the block and we never saw them in the mempool before being in the block.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: COBRAS on September 25, 2022, 06:27:55 PM
Interesting update...
Address 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN is derived from hashed empty string "". Two moths ago (!) someone sent almost 1BTC to this address. I guess by mistake. It took as mush as 10 minutes to drain this address.

https://www.blockchain.com/btc/tx/37e166a1e52e96bcfe535738082e328ef8db56aafd6945d9cad6f2afdb34b4a4

adres privkey https://privatekeys.pw/address/bitcoin/1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: larry_vw_1955 on October 12, 2022, 11:18:27 PM

Interesting update...
Address 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN is derived from hashed empty string "". Two moths ago (!) someone sent almost 1BTC to this address. I guess by mistake. It took as mush as 10 minutes to drain this address.

https://www.blockchain.com/btc/tx/37e166a1e52e96bcfe535738082e328ef8db56aafd6945d9cad6f2afdb34b4a4

how would someone make a mistake like that? it doesn't seem probable.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: n0nce on October 13, 2022, 11:57:25 PM
Interesting update...
Address 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN is derived from hashed empty string "". Two moths ago (!) someone sent almost 1BTC to this address. I guess by mistake. It took as mush as 10 minutes to drain this address.

https://www.blockchain.com/btc/tx/37e166a1e52e96bcfe535738082e328ef8db56aafd6945d9cad6f2afdb34b4a4

how would someone make a mistake like that? it doesn't seem probable.
I guess it's always possible to use something like this for money laundering.
I.e.: (1) Send 1BTC to address whose private key is publicly known.
(2) Sweep the funds a few minutes later (depending on the amount of plausible deniability vs. risk you're willing to take).
(3) Claim you mistakenly sent the funds and that they're gone, since it's an address whose private key is known.

Then mix and be happy. Just an idea.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PrivatePerson on October 14, 2022, 03:12:15 AM
I guess it's always possible to use something like this for money laundering.
I.e.: (1) Send 1BTC to address whose private key is publicly known.
(2) See how your BTC was collected by someone else's bot.
(3) Cry because you are a loser  ;D


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on October 14, 2022, 09:28:05 AM
I guess it's always possible to use something like this for money laundering.
~
(3) Claim you mistakenly sent the funds and that they're gone, since it's an address whose private key is known.
That's not money laundering. It sounds more like a "boating accident".

Quote
Then mix and be happy. Just an idea.
Now you have money you don't officially have, and can't officially spend. Great for buying drugs, terrible for buying a car.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: n0nce on October 14, 2022, 10:43:03 PM
I guess it's always possible to use something like this for money laundering.
I.e.: (1) Send 1BTC to address whose private key is publicly known.
(2) See how your BTC was collected by someone else's bot.
(3) Cry because you are a loser  ;D
I actually addressed your criticism: 'a few minutes later (depending on the amount of plausible deniability vs. risk you're willing to take)'.
Never claimed that this was a risk-free method. ;) As we saw above, it took a whole 10 minutes for (maybe) a bot to sweep the funds.

I guess it's always possible to use something like this for money laundering.
I.e.: (1) Send 1BTC to address whose private key is publicly known.
(2) Sweep the funds a few minutes later (depending on the amount of plausible deniability vs. risk you're willing to take).
(3) Claim you mistakenly sent the funds and that they're gone, since it's an address whose private key is known.

Alternatively, generate private key with relative weak (but not publicly known) string before executing your idea. After some time you could make an account on social media/forum and claim you found another weak Brainwallets which already emptied.

P.S. This is informative post, i'm not taking any responsibility if you weaken your privacy or lose your money :P.
That's much better actually! :D All hypothetical of course. ;)

I guess it's always possible to use something like this for money laundering.
~
(3) Claim you mistakenly sent the funds and that they're gone, since it's an address whose private key is known.
That's not money laundering. It sounds more like a "boating accident".

Quote
Then mix and be happy. Just an idea.
Now you have money you don't officially have, and can't officially spend. Great for buying drugs, terrible for buying a car.
Very true. Similar to mixing and buying on decentralized exchange, I guess. Except you can keep / export Bisq trade records and mixing receipts. Would you recommend this?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on October 15, 2022, 09:12:41 AM
I actually addressed your criticism: 'a few minutes later (depending on the amount of plausible deniability vs. risk you're willing to take)'.
Never claimed that this was a risk-free method. ;) As we saw above, it took a whole 10 minutes for (maybe) a bot to sweep the funds.
It's rare, but I think you missed the point completely. It doesn't take 10 minutes to sweep the funds (and you shouldn't trust Blockchain.com on this). This is what Blockchair.com shows:
https://loyce.club/other/anditsgone.png
I give it half a second between the moment you broadcast the transaction, and the moment you see it disappear from the compromised address. Many bots are competing to steel those funds, and the fastest wins. You won't have minutes, you won't have seconds. Your money is instantly gone.

Quote
Now you have money you don't officially have, and can't officially spend. Great for buying drugs, terrible for buying a car.
Very true. Similar to mixing and buying on decentralized exchange, I guess. Except you can keep / export Bisq trade records and mixing receipts. Would you recommend this?
It depends: your drug dealer won't care about receipts, your tax man will.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PawGo on October 21, 2022, 06:39:11 AM
Quote
Then mix and be happy. Just an idea.
Now you have money you don't officially have, and can't officially spend. Great for buying drugs, terrible for buying a car.

recently I have found https://bitcars.eu/ Nice initiative, but I did not investigate deeply how they wok - if they sell cars directly or if it is just a catalogue with offers where owner accepts crypto. But what I like is that they offer almost everything - from aston martin sport car to volkswagen camper ;)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on October 21, 2022, 07:18:45 AM
recently I have found https://bitcars.eu/ Nice initiative, but I did not investigate deeply how they wok - if they sell cars directly or if it is just a catalogue with offers where owner accepts crypto. But what I like is that they offer almost everything - from aston martin sport car to volkswagen camper ;)
That doesn't change the problem if you have "drug money": if you register the car in your name, you have some explaining to do when you get checked.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: casinotester0001 on October 21, 2022, 09:03:48 AM
recently I have found https://bitcars.eu/ Nice initiative, but I did not investigate deeply how they wok - if they sell cars directly or if it is just a catalogue with offers where owner accepts crypto. But what I like is that they offer almost everything - from aston martin sport car to volkswagen camper ;)

© BitCars | The Crypto Car Marketplace. Since 2016  (btw they are in Switzerland)
https://bitcars.eu/pages/bitcars-bitcoin-automobile-boutique-imprint-legal-disclosure

 :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on August 08, 2023, 09:46:10 PM
So far I've seen only those online lists of brainwallets. I wonder if there are others available?
  • http://eli5.eu/brainwallet/
  • https://privatekeys.pw/brainwallet/bitcoin/1
  • https://privatekeyfinder.io/brainwallet/bitcoin/

Most of you probably know this science paper "The Bitcoin Brain Drain: Examining the Use and Abuse of Bitcoin Brain Wallets" (Marie Vasek, Joseph Bonneau, R. Castellucci, C. Keith, T. Moore). It is available from this link: https://tylermoore.utulsa.edu/fc16.pdf

Authors do not reveal brainwallets in clear text. However, I've found this resource that contains files that are attachments to this paper: https://dataverse.harvard.edu/dataset.xhtml;jsessionid=3b3325c3157850e2d961cf61dfb1?persistentId=doi%3A10.7910%2FDVN%2FRZHL3X&version=&q=&fileTypeGroupFacet=&fileAccess=Public&fileSortField=type

The most interesting files are probably: brainmaster.tab and attacksrc.tab files. They contain a list of more than 19k addresses identified to be protected with a brainwallet (again, no brainwallets in clear text, just information about the length of string). There are still many addresses in Vasek's list that you will not find on the websites mentioned in the beginning.
Some people that participated in this topic have their own lists of brainwallets. I wonder if there is anyone who cracked all addresses from Vasek's list? Probably not. Then, how many of them remain a mystery to you, still?

Are there other lists like this from Vasek? I mean, just addresses without brainwallets revealed?


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on August 09, 2023, 05:02:21 AM
The most interesting files are probably: brainmaster.tab and attacksrc.tab files. They contain a list of more than 19k addresses identified to be protected with a brainwallet

I wonder if there is anyone who cracked all addresses from Vasek's list? Probably not. Then, how many of them remain a mystery to you, still?
That's easy to check: get all Bitcoin addresses with a balance (https://bitcointalk.org/index.php?topic=5254914.0) and find the duplicates. There's only one:
15Mjbr23k7LfadNVAMmFZwdzcL5VFHe9gC (https://blockchair.com/bitcoin/address/15Mjbr23k7LfadNVAMmFZwdzcL5VFHe9gC).
There's 0.001 BTC in there since 2014.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on August 09, 2023, 06:39:34 AM
That's easy to check: get all Bitcoin addresses with a balance (https://bitcointalk.org/index.php?topic=5254914.0) and find the duplicates. There's only one:
15Mjbr23k7LfadNVAMmFZwdzcL5VFHe9gC (https://blockchair.com/bitcoin/address/15Mjbr23k7LfadNVAMmFZwdzcL5VFHe9gC).
There's 0.001 BTC in there since 2014.
Thanks, I know that, but I was not thinking about balances - just about brainwallets (phrases used to generate BTC addresses). Maybe let's use numbers to illustrate this.

Vasek list - 19430 addresses (contains addresses created between 2011 and January 2017)
Eli5 list - 18982 addresses (last time I've scrapped the website)

If you compare them there are:
- 18741 addresses common to both lists
- 689 addresses that are unknown to Eli5

Privatekeys.pw made progress in revealing the brainwallets, but still there are 611 addresses with brainwallet unknown.

So, I was wondering if there is anyone that cracked all or most of the remaining 611 addresses (list below).
Code:
address,compressed,pwdlength,endbalance,numdrains,firstTTD,totalamt,firstseen
1ze4KR7bTDnTQmsuGP7HSNxj5gfUBo11u, u, 6, 0, 1, 35741, 20108, 2014-08-17T14:31:18Z
1zSeCcg9cteDyNDknAZ6dnQ4diwxGiuPX, u, 22, 0, 1, 61334, 5000000, 2013-04-09T23:54:22Z
1z9SGFcpQLTnFjhfXY5yUhWgyBKQgLUNa, u, 5, 0, 2, 74228, 30108, 2014-08-17T14:31:18Z
1vVBEPttpHeprmYDTiJFooQ9AxF2w6AKn, u, 10, 0, 1, 54174, 190000, 2015-07-22T01:13:34Z
1gpKFHeP8RBL52MPABfmwvBYh9kEJURq9, u, 22, 0, 1, 80360, 2010000, 2014-08-29T21:20:01Z
1gCzekZetCwPSibmUKbfbmLoYJKs1ZqY6, u, 10, 0, 1, 67643, 4790000, 2015-07-21T22:00:33Z
1e5ZK5VjGRcabJUmcGoySVt5v8S53XZaM, u, 19, 0, 1, 45185, 50000, 2014-01-07T04:30:08Z
1e2TbZ5c8P7Q9YrUDAahRvgoxd8SQoua5, u, 10, 0, 1, 25877, 9390000, 2015-07-21T23:25:04Z
1dH46VDMCHT1HmBZVBofFgPW9nJWwwnrF, u, 11, 0, 1, 35674, 2186000, 2015-07-22T20:41:47Z
1WAkoExs25n4gnE8YoZKf7baA6HhG3NwB, u, 95, 0, 1, 26934, 60000, 2014-07-11T15:13:58Z
1QfYv9jjJsQJNMk7B3mv8ynADJoz1WCmd, u, 22, 0, 4, 57254, 185850, 2014-08-28T18:13:22Z
1QEYk6DLRouwgKPGn915RTPevUuk9VvGji, c, 9, 0, 1, 81409, 20000, 2016-01-19T05:03:07Z
1QCqZDr7odxL1pQ2wjAMydGVZUcSv8Kjmr, c, 28, 0, 1, 42797, 10000, 2013-12-24T10:13:15Z
1QAKKmjH7S9ko7txkVFwUSV52ydTDrK8FX, u, 13, 0, 1, 84779, 390000, 2016-05-12T06:19:57Z
1Q8Vuuqu8Vt4ozij9fjeckKdz8Nb35dCHu, u, 28, 0, 1, 24591, 1000000, 2015-04-01T03:35:27Z
1Q7eEfUSeFL1KEYaj6o1j7R5xe39p2Wqg7, u, 12, 0, 1, 65072, 20108, 2014-08-17T14:31:18Z
1Q5j3vo1ddVSHYsvo5feFHLbG7cqGYi6Z3, u, 10, 0, 1, 637, 200000, 2015-07-20T21:34:11Z
1Q57STy6daELZqToY4Rs2BKWxau2kzwjdy, c, 22, 0, 1, 68130, 5500, 2015-12-05T02:13:28Z
1Q3gVCdcgmU2jMjfHCcFXrTPB33YFCQm4, u, 10, 0, 1, 79706, 20108, 2014-08-17T14:31:07Z
1Puo8uHFTswmhFcsvS9ZVRgD8EyEMtvLog, c, 17, 73200, NA, NA, 73200, 2015-05-02T19:25:50Z
1Pt7EUZWuq8ThHvZr23Vvk4paRvwjL7MXV, u, 8, 0, 1, 1351, 1989000, 2015-07-23T23:20:57Z
1PsenWrxazHNrEC9pR7JESb37aogZZFWUW, u, 75, 0, 1, 71415, 1506475000, 2014-03-07T10:07:07Z
1PpPgTEWeDyCE715E3qhaUxQqCPFpa5PvF, u, 7, 0, 2, 2, 615000000, 2013-11-21T12:08:26Z
1PknmE3gJf57fYLUuaqGxGeBH3rPrwepXy, c, 12, 0, 1, 9252, 4590, 2013-12-03T10:08:44Z
1PigrEyV6P9wJU5jN5t3HmDAfYRQ9b6V5h, u, 13, 0, 1, 85363, 400000, 2016-05-12T06:10:13Z
1Phc4KcgPqTKzMpKWvTpkb1mK6cBJ8hFGS, u, 17, 0, 1, 54428, 10000, 2016-05-15T08:47:53Z
1PgjntmJKKAeSLoZdvebQxk5tg5wp9EPsu, u, 10, 0, 1, 932, 1969010, 2015-07-20T18:44:40Z
1PgiBmZyVVFLkXN1p1qJgTPbRnJ58JjsxW, u, 10, 0, 1, 4034, 185406, 2015-07-20T21:51:40Z
1PehbK7RHgyMjEPJxr6MjDubRBRfr6UtBp, u, 24, 500, NA, NA, 500, 2013-08-15T11:11:27Z
1Pea2cN9ETQzVKGY9zrm3JJtbbxrzjAn3L, u, 41, 0, 1, 79951, 100000, 2013-11-20T06:00:06Z
1Pe4PZrEjhjBMF7BdaNn5PvWZTTEh35Q9P, u, 47, 0, 2, 7356, 11950000, 2011-07-15T00:19:40Z
1PdaTMsrPVJ8M1WCoVWmXw7j5MzJFdbPcc, u, 41, 0, 3, 55601, 716531, 2014-09-15T12:10:26Z
1Pc4hiNs1zx1NJ7NSgKNpiqQdBQ8tpwSAM, u, 13, 0, 8, 18784, 136504133, 2015-10-11T21:49:20Z
1PbPADn4oszGo5ZAFNuimMyQ1gQ4gHA6qN, u, 10, 0, 1, 60480, 9690000, 2015-07-22T01:08:33Z
1PVATnQLLDTeNh7RZVfLkdgMEzWLspZavF, u, 31, 0, 1, 14003, 336768, 2014-06-27T21:19:50Z
1PSQXM2wipQG88pFzrRUXGmWzMDYBXnmaT, c, 5, 0, 1, 29, 100000, 2016-08-15T07:55:01Z
1PS9qj4bqRMS5i4MKUKfJHnPXzwuPBWcJD, u, 39, 0, 1, 37995, 1, 2012-08-18T17:39:22Z
1PRPqwUEA8ptwT12V491ZAwjmSirDbhoEL, u, 42, 0, 1, 23897, 5032000, 2012-09-14T00:26:17Z
1PLtos6AUED1yZrbqtmZB3BNZgTDJnYAEy, u, 10, 20108, NA, NA, 20108, 2014-08-17T14:31:07Z
1PJaLg5MG8BDWNA9VejT8juJURtyDMGeze, u, 10, 0, 1, 2367, 20108, 2014-08-17T14:31:07Z
1PGyZEiaorx5wRqaPBHDjy4moLVBAL8KD4, u, 22, 0, 2, 56945, 2020000, 2014-08-29T21:19:14Z
1PEHyyENNxTQDYuSC7kJuAtEAmzjr8zW8z, u, 21, 0, 1, 8113, 100000, 2013-02-09T15:58:30Z
1PEGGsACb6dCZ2icK9dTaLzkJR1RrPVGLA, u, 10, 0, 1, 2844, 10000000, 2015-07-22T00:50:40Z
1PE8j52i5hfBKyzh21URcDMAV5JG2R4vSg, u, 11, 0, 1, 78838, 9690000, 2015-07-22T01:53:18Z
1PBpnTGY2foFbGFAbb5LwDnCtrAYpKo2n4, u, 10, 0, 1, 765, 10000000, 2015-07-21T20:00:37Z
1PB77j229w4b5kLNUY91JTHQYWd2htqjrx, u, 37, 0, 1, 37950, 1, 2012-08-18T17:40:07Z
1PAMJAyqYQisRBzQgLieoCrm1mj7bvvgEw, u, 9, 0, 2, 81272, 20109, 2014-08-17T14:30:37Z
1P7qLxzmBGxF68iVBXP5GeskJqdonKsU1R, u, 10, 0, 1, 1776, 290000, 2015-07-21T21:38:49Z
1P77Cb3YsLyqSX6GGCiHcCEuCsXM2jZ3ou, u, 10, 0, 1, 632, 190000, 2015-07-20T21:51:39Z
1NzvNBqeqKbu6BzmEgBSPLPXUoByDNXru3, u, 10, 0, 1, 2060, 193166, 2015-07-20T22:40:41Z
1Nx6jvBVmPExLY61EGqYD9nQnwULzLvAmd, u, 53, 0, 1, 629, 20000, 2014-05-02T15:21:56Z
1NuDrHrDZtF2Aw1L46zJkG1rT5JpEGgFX6, u, 12, 0, 1, 68236, 100000, 2013-03-10T03:41:17Z
1Nkk3r5JwMdZZkhCqCN9fJfhUAJKZYoLu7, u, 5, 0, 1, 4, 1000000, 2015-07-09T14:21:46Z
1NiEUdfZmhHrMXcR5go3zotYwv6ub52RbW, u, 13, 0, 1, 85363, 400000, 2016-05-12T06:10:13Z
1NfnxAE8tWr1HWZAdg3bnEwRHTJamF3Fuz, u, 7, 0, 1, 14238, 10000, 2014-12-06T11:05:40Z
1NejMeJVZtG6giqDRbE9hdvyBuB7jfnWzA, u, 26, 0, 1, 65319, 891310, 2013-12-13T17:31:58Z
1NegGyAxccFHsdK7T4qvoZNg9w2MGNSBN6, u, 9, 0, 1, 17927, 100000, 2011-12-15T16:25:04Z
1NeGM3HJ8PUgfgGtQSmbX3aNzWkmqRP8mV, u, 10, 0, 1, 51614, 9590000, 2015-07-21T23:43:17Z
1NdoaUUcnmq5LuRBfwuu5roMoprLvMUUn8, u, 15, 0, 1, 42474, 2000000, 2015-01-13T15:54:26Z
1NcELnmnvGy5SwrqSH6ALLNSAFG9bK8i8U, u, 26, 0, 2, 81279, 800080000, 2012-01-28T13:56:54Z
1NW1WNXkdEUbbAwZoQbiAMS6Jt22CqMNWy, u, 8, 0, 1, 4770, 2990108, 2014-08-17T14:30:37Z
1NSm3D2491my8uY7qskKjVU1qt31csz66v, u, 9, 0, 1, 3181, 200000, 2015-07-20T15:48:22Z
1NMhaXi7MB4s87XRfEFoD37ZD2goN1zD4t, u, 10, 0, 1, 2844, 10000000, 2015-07-22T00:50:40Z
1NJFqBsAFBK7VyhmFNhbn7d6TeEEfGciBs, u, 64, 0, 1, 24753, 3850, 2015-07-30T18:00:32Z
1NHuhmVYw6Aj4oCtUHWw89nm7VhWDLznqj, u, 19, 0, 1, 52297, 6660, 2015-08-31T18:38:27Z
1N9kr6yRmjzX4DAEL1FRm7tvv9STBJADD9, u, 68, 0, 1, 6505, 100001000, 2013-12-21T19:05:19Z
1MzuMvwc1ruhxxFa8r7GAvX64JuDYpcdhn, u, 11, 0, 1, 62468, 20108, 2014-08-17T14:30:21Z
1MynYk8a51RY6TXfAfpuGq8dXHzgVGJfA5, u, 10, 0, 1, 79752, 20108, 2014-08-17T14:30:21Z
1MuByQpPWcVnS1L3v6UiuvrMNQLynBur8g, u, 10, 0, 2, 56971, 11956858, 2012-02-25T00:31:26Z
1MtKrXBHLCNziQgE4g9eN1v8zQbN2pNRiJ, u, 10, 0, 1, 39033, 1990000, 2015-07-21T18:20:18Z
1Mqo3Erkz47V8Hxu8TdnNDr4CcJAteL9U5, u, 8, 0, 1, 47416, 20108, 2014-08-17T14:30:21Z
1MmuyjN1Wk6yFHxQPaE3sPFaKDioVrdsmj, u, 13, 0, 1, 84439, 390000, 2016-05-12T06:25:37Z
1MmjBAQoK1o4ahYBK7XF9XuybKY8ZpYFML, u, 40, 0, 2, 67795, 2500000, 2013-06-09T03:26:45Z
1Mks4UJBm4zRAw5xAXbkrGZozSzBi6p7tm, c, 40, 0, 1, 72131, 85000, 2015-08-28T06:40:39Z
1MkT1vS4EVQJycmZFkFHL54eAP39ASsjZe, u, 11, 0, 1, 1559, 50000, 2015-07-23T18:18:36Z
1MkAHvLvQu8JnvXhgHDxBtmLb6yaCrhAWn, u, 64, 0, 1, 4, 200000, 2013-10-13T02:10:19Z
1MjGyKiRLzq4WeuJKyFZMmkjAv7rH1TABm, u, 36, 0, 39, 81556, 13159300000, 2012-11-08T02:43:01Z
1MiacouWd5CsXNnP8AmbD21gztXgvo92B8, u, 22, 0, 1, 409, 990000, 2015-01-10T08:39:29Z
1MfRyZP4Ynqdbdh6drdw44BxKpkL8uUvKv, u, 10, 0, 1, 4651, 10000000, 2015-07-21T22:22:32Z
1Mew8Nqc5ET8P37LDPSQ2bCXUzAF2r4Y6q, u, 13, 0, 1, 85033, 380000, 2016-05-12T06:15:43Z
1MbRseeqWjpUB62NYt1H8GTr1MXnQxLus5, u, 10, 0, 1, 54082, 10000000, 2015-07-22T00:50:40Z
1MamGvVVpHnJLh8gdWVD2LsecJmZgdDQ3t, u, 12, 0, 1, 1, 400000, 2016-05-12T06:02:53Z
1MaeR6hweVRH2HHqWgJVntxUxL63GkZ3mX, u, 12, 0, 2, 34357, 1999999, 2013-02-21T15:24:55Z
1MabtkZfQxzrCxygVmaVVbsZq2Y9ez4URj, u, 11, 0, 1, 9170, 180000, 2015-07-22T15:55:22Z
1Ma1Uj1tJ64JzVCA7TmV5jviiKJQjuz5LL, c, 17, 0, 1, 30603, 66600, 2016-08-09T08:29:21Z
1MZ5zLMQcznFwrH1mfMHaXPcWYMP8SSX6u, u, 11, 0, 1, 35482, 20108, 2014-08-17T14:30:21Z
1MX23G1zdentjx26MVQe7SWVedcMtdnSX2, c, 82, 0, 1, 79052, 4402000000, 2012-10-09T16:53:12Z
1MV1aAn9VnsV97kFYHTwCBr1hCr2awjqR9, u, 12, 0, 1, 5, 200000, 2014-03-09T16:56:13Z
1MUMMXjUktchWG4M6eaWkpJFjXw4WDViMM, u, 23, 0, 2, 42497, 1400000, 2012-07-08T05:19:17Z
1MMQEE2YSht3UyiGuEUQ7kCNv748zdfknS, c, 14, 0, 8, 130, 180000, 2014-08-02T17:42:42Z
1MJwAs6oVackg8xNTQkjaCszmJkMp6vw5d, u, 5, 0, 1, 8, 20108, 2014-08-17T14:29:58Z
1MJoKSio14iZd9rJSuwTsjnHxFfJLoN7fV, u, 9, 0, 1, 52396, 60000, 2014-07-11T16:27:34Z
1MJ91xzdxBTnXAYC37F5SGMkZwRYK3jhFE, c, 29, 0, 2, 0, 40000, 2014-09-23T19:29:38Z
1MHMUSePZbPZZ13BVcZf35ucG1nXUU2it2, u, 7, 0, 1, 52768, 60000, 2014-07-11T16:21:22Z
1ME6nAmCsXJywX5zFsYEKuLzaX2dHYq75v, u, 12, 0, 1, 39465, 211, 2013-03-31T22:28:25Z
1MB1q8bKtHZ6Eo9seN843Q3qoVBizHAAy8, u, 11, 0, 1, 40267, 10000, 2015-02-20T04:32:35Z
1M9yigr8Lc6rJcbNTAC9XyqzJNXcFLArw2, u, 11, 0, 1, 2407, 20000, 2015-07-23T15:52:11Z
1M9kzNAURtUijDX9yPGh5UAmcEHvWT79VJ, u, 32, 1000, 3, 485, 28668425, 2014-01-05T18:29:06Z
1M9ipUGaKW7ZXneAGKxhiHiL795EEsyi8u, u, 132, 0, 1, 71146, 200000, 2013-10-13T02:14:52Z
1M7JJ28bLUwZJQwBB8P1oH8T7E1U5JUQEd, u, 7, 0, 1, 80975, 811000, 2013-05-24T12:39:48Z
1M74xpnmoQHhzuBemQEUJcBYZxQ536FL85, u, 20, 0, 1, 6100, 1000, 2015-07-29T22:04:56Z
1M5A6A7QWA6HU5vsMwbdbuBGXhUrWh1Cwm, u, 10, 0, 1, 11644, 10000000, 2015-07-21T20:00:37Z
1M3WqCAKvAhB66fskxh7tANr23ycuKgphE, u, 6, 0, 1, 85367, 20108, 2014-08-17T14:29:58Z
1M2tL9RdYPkVbbfExRFE64ceZBFmMNVmaE, u, 94, 0, 1, 20220, 5000, 2015-07-29T13:17:00Z
1M2i6T9SqJSdwaTRy2jRthEapef6vwJ1uL, u, 6, 0, 1, 14542, 40000, 2016-07-21T00:03:40Z
1M1DguCtGZcgVKboB3VdN91gMwNjU5pojy, u, 19, 0, 1, 77739, 743494, 2012-12-06T17:54:09Z
1LzKfFiwyZ5R8DMtrJqzKfkshUZzyVKv7U, u, 6, 0, 1, 40650, 2990108, 2014-08-17T14:29:58Z
1LzEsbswMaLBFz1MMxZfyD5ASdHEvwXX6H, u, 13, 0, 1, 84918, 380000, 2016-05-12T06:17:38Z
1LyH7zvv9GVKcUbnxacTWAEYAoEyV6jieQ, u, 125, 0, 1, 2, 5000000, 2014-06-18T17:35:30Z
1LvZoVUYFCA8N48K26iGgQSVZnhKwaTwGN, u, 6, 0, 1, 3, 6047040, 2016-06-26T03:21:41Z
1Lu7xC2FWGGpsyNufjoVP35uAU8FXvmCji, u, 7, 0, 1, 55541, 30000, 2015-12-20T15:53:54Z
1Lu1dzceAcRAGLyKMfUWdJT5H8LBs8Ssus, u, 10, 0, 1, 31068, 290000, 2015-07-22T00:02:18Z
1LsBLvop4ja818V9oVEwEqWiyveU3XKC1d, u, 14, 0, 1, 1943, 168000, 2012-07-03T09:48:03Z
1LrRYjJHiMM7Sir1zs9rFGH3ayyjon88cy, u, 13, 0, 1, 0, 400000, 2016-05-12T06:08:24Z
1LrBnwfX1TCbvWexrVozCPDadxnepySxQF, u, 16, 0, 1, 3045, 500000, 2015-03-20T08:21:59Z
1Lq2taUxLKMqEHtKHowHpytmsrL9YphRi2, u, 126, 0, 1, 14704, 1000000, 2013-12-18T00:03:35Z
1Lo3DvinJiHjQqUs35d6sGx9VmTb7kg1wZ, u, 10, 0, 1, 32987, 100000, 2013-11-24T15:03:22Z
1LnepVXTdGUWFkb7ieLFr1h2Ss1zsVtodV, u, 10, 0, 1, 3548, 10000000, 2015-07-21T20:00:37Z
1LeT5PMHZVm8DgqBXNcmJMKhhMGCw5ahAT, c, 14, 0, 1, 31757, 34373, 2015-05-14T18:23:49Z
1LdRSJ8rHcXpnpYXozwkd65THaeCG92bu5, u, 13, 0, 1, 84439, 390000, 2016-05-12T06:25:37Z
1LdNN9GXmoKZs5vrQFL1d4NL9GgZ1PfCZk, u, 11, 0, 1, 84378, 1224120000, 2015-09-21T13:08:32Z
1LbkeSDXAiFR9oBAg7sET3nLseAb2fiBuk, u, 43, 0, 1, 16459, 100000, 2013-11-20T06:09:09Z
1LYixkq1pseTDT1Vw2QHfPJeLXnJARobre, c, 25, 0, 1, 37580, 82000, 2015-08-28T06:40:39Z
1LTVA6Ea98N1qUxsaLmqfjc7stqwqsCehJ, u, 11, 0, 1, 55200, 10000, 2015-07-23T17:50:04Z
1LT4zJGxYUbhPzH3xZjyFaa1gSGofGmfi3, u, 25, 0, 1, 28242, 10000, 2014-04-23T00:59:44Z
1LT2DamNS4r4qNZLUZttQ16mzqB2XeAxhy, u, 11, 0, 1, 4369, 250000, 2015-07-23T16:12:44Z
1LPJeehMdrGFdJEbQNzAfsQGrZgZnDb3rD, u, 35, 0, 1, 1, 100000, 2015-02-16T13:51:03Z
1LLgMjCXgSPpQFhcxNJfbkyG2TdMe9SN69, u, 35, 0, 1, 2050, 10000000, 2013-11-22T08:51:47Z
1LLLKcrjYDX4pCeF6mMTMbCcrvLh9JpuCu, u, 11, 0, 2, 51963, 55000, 2015-07-23T18:18:08Z
1LHXm9epphnPhpGaFWnoXekuMYUt3BJX2W, u, 11, 0, 1, 1075, 40000, 2015-07-23T18:44:01Z
1LDGsiVbwAqjGz4eZktmrmR7d46AknSVvf, u, 15, 0, 1, 16814, 20000, 2014-06-14T04:55:13Z
1LCz63gASHWHebhgShgHQLBPbQ8DpcPdya, u, 10, 0, 1, 8145, 10000000, 2015-07-21T20:00:37Z
1LC7Lsuh8gxGvBNXwTELNskZEotkzQN3KF, u, 11, 0, 4, 19507, 896185, 2014-08-07T16:34:03Z
1LBTr5x9PDzLhmTLFipGPmV3c63nCw5RSQ, u, 172, 0, 1, 81439, 100000, 2013-10-13T23:08:40Z
1LAojQFHZxjFdXpMwKdYBLspyDCQi1odGA, u, 10, 0, 1, 50483, 100000, 2013-07-29T23:30:02Z
1L6q1xsfVj8LEzmQ58USxhmxTuB6EzV1yo, u, 7, 0, 1, 1, 500000, 2014-12-16T10:33:41Z
1L5qymtPHCQcbSQzLzK7vCvaqBftEREyyx, u, 80, 0, 1, 2, 500000, 2015-12-31T15:33:50Z
1L4tibTzPvsYrWDVjcLeawAeneLHPSE6Q1, u, 11, 0, 1, 8085, 177644, 2015-07-22T18:46:17Z
1L4G4aBaQ9drttayUF53m4UB4B1cP12zs8, u, 37, 0, 1, 3602, 81988, 2016-08-01T21:07:57Z
1L23gyXDL15LbqJoxEL5T7CjjEat61ibB6, u, 10, 0, 1, 67740, 4300000, 2015-07-21T19:30:14Z
1L1jCqCMEk1bKP1gSLzuwZYzD6hZUFhzxa, u, 88, 0, 1, 552, 1000000, 2014-10-31T09:44:16Z
1KzgvpH3AEMZg8skGq7SzQerhkDD3irQyF, u, 21, 0, 1, 74423, 101000000, 2013-01-24T16:23:43Z
1KqxxxfLdPcr6apRft9JYZQvVrYFTrWMMB, u, 5, 0, 1, 37, 50000, 2016-07-23T17:19:08Z
1KmQDbeKReQHL7aozcgfoRPu3cy2WpQLYX, u, 24, 0, 2, 3, 3100000, 2013-11-27T17:37:59Z
1KiYvHP3i3FcnEakm5yhKConpM44D8enLi, u, 30, 0, 1, 70805, 1545500000, 2014-01-07T23:36:52Z
1KgykU1ybics2GHsJYwyXJumoyvcKnWUhi, u, 13, 0, 2, 61587, 439000, 2016-05-12T06:12:02Z
1KeHqYSMxkYhnhrjeSSFSLqKsxiXaTEHUn, u, 51, 0, 1, 3089, 100000, 2014-06-06T17:09:56Z
1KbZsjmJFF5zAqgyEzqkjKQe8JE6iUMLUG, u, 11, 0, 2, 81272, 20109, 2014-08-17T14:28:37Z
1KWzoZ8g2uapG5zMsC8SZnHzjwGiDtWFpr, u, 35, 0, 1, 55758, 90000, 2013-12-18T11:11:31Z
1KRnZ1zb2FuMHjtkgJMvw6ivgJiTfnbMWk, u, 10, 0, 1, 1892, 1000000, 2015-07-20T18:14:31Z
1KRPkXbBdsben2JBzqrjofE8NYD13KZnQN, c, 64, 0, 1, 79108, 242000, 2015-08-29T07:25:31Z
1KNbRHfqBNJfn3thXGWRRma4jBNJZd1uvn, u, 6, 0, 1, 37084, 20108, 2014-08-17T14:28:37Z
1KFYVCx59yvQaXt5wms4Fdyz4W3WqNAKUn, u, 28, 0, 1, 0, 136527, 2014-06-25T17:03:29Z
1K9ycm51i2wqdTmvUUwFFftfCGSzkWVVJk, u, 10, 0, 1, 2742, 1500000, 2015-07-21T10:57:04Z
1JyoixDY2A28ht38Hh8mTLsaLGUc114oBB, u, 9, 0, 1, 5, 26362617, 2014-01-27T16:45:45Z
1Jyi5DMhyNEawG4ytXF6ytsnZxDgyt8Jgn, u, 22, 0, 1, 74277, 101000000, 2013-01-24T16:39:38Z
1Jvd2E8x1K5a6ehNJTVPAQZcZ1d3X48K9C, u, 10, 0, 1, 8836, 5990000, 2015-07-21T21:35:47Z
1JqSa6ZH6tUMuJuMGFCjhNu7H8ckRJU1U8, u, 10, 0, 1, 31007, 190000, 2015-07-22T01:03:47Z
1JfrQPeTe3crPejx2FFKwAwT6DgFQHzuRU, u, 123, 0, 1, 70663, 200000, 2013-10-13T01:56:05Z
1JcwCTVuZmQAtERDA5k6zZbmBVj7jBNf8W, u, 21, 0, 1, 40390, 16800, 2013-03-10T17:20:46Z
1JYXN26Y7YLSxsK3DzzN5i8dCPsoMg2QQk, u, 19, 0, 1, 4, 10000000, 2013-12-02T09:49:24Z
1JW5VE358bbQzhKJhSBgmR4iKmgBEzTxTy, u, 41, 0, 1, 51095, 200000, 2013-11-08T14:01:02Z
1JTWqEuQXRrkfAka1LT9Lmgrt2ntLGY24T, u, 52, 0, 1, 8459, 200000, 2013-12-17T20:42:32Z
1JSVYaXiozc1mqqPmxRBrNRhmd72xjxEMj, u, 10, 0, 1, 2764, 2000000, 2015-07-21T08:46:20Z
1JRx6fkG2sQbE4wdwKdKbNmKbqzbcMXj2F, u, 25, 0, 1, 50554, 214000, 2015-04-22T04:28:20Z
1JQrdPJmte65XMuHDMutw4v3HKRfzEP6iY, u, 11, 0, 1, 58889, 14000, 2015-07-23T16:48:35Z
1JQoDKFCXHtNHXK67SJY3GAqgEKjtrUDAY, u, 10, 20108, NA, NA, 20108, 2014-08-17T14:28:24Z
1JNxnwXiQtcyFjioDgXbdg8inuPwVrwDgo, u, 10, 0, 1, 82177, 9790000, 2015-07-22T00:59:17Z
1JHrRqPPkd1UL1dptoFbzo8Q1BDYiRbJxv, u, 5, 0, 1, 3, 100000, 2017-01-02T13:15:52Z
1JFRG9nkHYn2wvAkaHPNoLjHed7MKTZK8G, u, 10, 0, 1, 1, 100000, 2014-03-28T22:31:08Z
1JEnL6xYG9iHPWFV4Zz1xYUq1kQTKmnJwM, u, 5, 0, 1, 27, 50000, 2016-07-23T19:17:23Z
1J6PzTXBzYzozKVKbjjiTxzpHWxfbJmHhK, u, 12, 0, 2, 0, 61000, 2013-09-20T04:56:38Z
1J5mcpQva48JsD4549AQsRnjz1QC2r2GS4, u, 6, 0, 1, 5329, 20108, 2014-08-17T14:28:24Z
1J5Voqt1uwHR3ZmPGzWDrnZJTgV7KWg1nU, u, 10, 0, 1, 4546, 159000, 2015-07-20T16:49:12Z
1J468Y65fQyYeuMyHhzAcWwxn6Je5d1oGx, u, 6, 0, 1, 65246, 20108, 2014-08-17T14:28:24Z
1J1JdehAxptUcRKvYohswV5zy3eSC9upFs, u, 11, 0, 1, 18304, 45000, 2015-07-23T18:43:18Z
1HzetU6QtPXm7e8dnhFbQpgzeUnU2AFg8h, u, 13, 0, 1, 61006, 60000, 2014-07-11T16:38:41Z
1Hxs8CkARaKvyB6uec9kR48XY2X8XH9gpB, u, 25, 0, 1, 3, 1000000, 2013-06-16T07:38:08Z
1Hv7vhJXGEVPbbPbzo28bx7Y5ydiQrWyzZ, u, 11, 0, 1, 50288, 190000, 2015-07-22T01:54:33Z
1Hgpnuvcw7nhZKDpi1UrzwA8RVbuAFi4Nq, u, 13, 0, 1, 2, 60000, 2014-06-29T02:03:40Z
1HerBRfHKvvWYuoB4nt7RDi15A7JY8sp1k, u, 12, 0, 1, 14332, 15000, 2015-01-03T01:03:18Z
1Hen1GrXdgoNFHhjgoNQsygBTpoTCq1qhX, u, 8, 0, 1, 55113, 50000, 2016-08-23T20:12:27Z
1He4DvZejE1Bnva1cDWorJr2r63CNEUFkF, u, 25, 0, 1, 63548, 12573, 2016-12-20T07:49:28Z
1HaCkkqBHkJUFvD1bUW4A7a8GTKLaYQuur, u, 10, 0, 1, 1082, 749369, 2015-07-20T18:11:40Z
1HZmtVN7kR4Qa1yz7BVbfwifi2QX3bKbN9, u, 15, 0, 1, 176, 5460, 2015-05-27T17:29:25Z
1HWvRLxw59cVqEq5rjqdzRdhEZ4BrH4oYT, u, 10, 0, 1, 55570, 190000, 2015-07-22T00:12:32Z
1HVm82CTZBsSCbmnUxkiXDfj5wNaAA3uhM, u, 40, 0, 1, 41324, 1, 2012-08-18T18:13:45Z
1HVYBvKt2S4hb1dMoa19Y3h2vy4Dt4AQx9, c, 11, 0, 2, 55774, 40000, 2014-08-03T04:09:31Z
1HNg5dx5qGmGWn5VTDmsK3u7QmoWapqF3r, u, 10, 0, 1, 5354, 10000000, 2015-07-21T20:00:37Z
1HMhcgyuknJ7cQzMAh8QhnXr4wGj8Pboqq, u, 10, 0, 1, 5801, 1000000, 2015-07-21T14:43:33Z
1HM9VyWYjS7XruY3p599hznPJnZma5A6GX, u, 13, 0, 1, 84552, 390000, 2016-05-12T06:23:44Z
1HLqeDxrvgASiKst1R7aJ6nqte7SBKtZgd, u, 20, 0, 1, 1783, 225752, 2013-06-01T13:56:13Z
1HGq8u6U8Bdp7mFttCXdEU56QQyKYLg8es, u, 9, 0, 1, 3245, 384020, 2015-07-20T16:45:40Z
1HGaKKGh9cMDrTHz9x7xBNzVGfUY7CJBFQ, u, 13, 0, 1, 31196, 100, 2014-12-14T19:45:11Z
1HCvKCpHUoKsYZvihAv4MQxgELh1EL9fAV, u, 10, 0, 1, 27931, 9890000, 2015-07-21T22:50:50Z
1HB1mb99X8b1eim82o81mEbFcaPmhtBFJC, u, 17, 0, 3, 20207, 6494812, 2013-10-15T13:07:54Z
1HA5gbFvEMGhvfGy1uKxXBj1mLZjtwqNNf, u, 23, 0, 1, 81660, 1876526, 2013-04-24T14:38:19Z
1H9rJxr4SRhBo6ra9C27jQFkHy78cmrisM, u, 48, 0, 3, 0, 265710908, 2014-10-28T10:22:09Z
1H9Soo4LqJjBv3CyLMpj6Jx26i2h7NoQE, u, 55, 0, 2, 85686, 285000000, 2013-04-16T15:23:52Z
1H83kKw3Zeo7HTxdKvztgAahd8Cznaz5Jf, u, 31, 0, 1, 0, 950000, 2016-06-07T09:54:22Z
1H6QTXMBZsteVXZPKCuW8G3NxQ3HBrszTn, u, 10, 0, 1, 34, 380098, 2014-10-08T08:07:34Z
1H4KufYkkRUaZLp69JgBihRje5zN5odh2H, u, 10, 0, 1, 74416, 20108, 2014-08-17T14:10:04Z
1H374YdEDGmM1FSy3LtJ7W9V8CMYkFgr7q, u, 34, 0, 2, 731, 2000000, 2013-06-20T22:23:09Z
1H17CEd7VMcecuKKr6G1brJxUBHsnkzTz5, u, 11, 0, 1, 624, 2000000, 2015-07-23T18:53:14Z
1GzHsdbrHWpNM2HrTt4DxbK56sVjPh8MVE, c, 16, 0, 1, 77339, 1000000, 2015-02-22T08:01:16Z
1Gz93s2D3HByxnxYmkmwoCPBubTchs2vhh, u, 19, 0, 2, 75879, 100263600, 2013-11-17T00:58:05Z
1GyYqfnLmwgwG6Jgs1rPkJgXEfKtAqpUiy, u, 21, 0, 3, 86384, 168533479, 2013-06-07T23:31:19Z
1Gy6sh3UmrvBa4Lr88BZ32Yjp6hp95rR5c, u, 12, 0, 1, 1, 100000, 2014-03-28T22:30:29Z
1GxqFVK3kf8rmPstB7s9XhRZfAixtUtAsi, u, 22, 0, 2, 62220, 2080860, 2014-08-29T21:20:14Z
1Gwv4wtDquGD6NNEGsaidap5phoPpfFk7f, u, 68, 0, 1, 46095, 700000, 2013-04-07T13:07:14Z
1GvZg1zvazo8HxMjrq6u2TVD95enZgRM8k, u, 8, 0, 1, 13618, 1000000, 2013-09-22T20:59:31Z
1GtmSDHzH7w15FqLzJkVxDRRqxVJxSWdqb, u, 15, 0, 1, 50952, 100000, 2013-07-29T23:30:02Z
1GrxmRs7ifjbhhphkKkSfVhpQzXwNCgRUZ, u, 12, 0, 1, 2, 100000, 2014-03-28T22:31:50Z
1Grma72MXyUxz2c1evjHinYCQD2Qgif7pX, u, 30, 0, 1, 6, 2000000, 2013-10-24T11:28:15Z
1GrLsCJKVCQade5wisMogv3xmBnE7BYNXB, u, 8, 0, 2, 33676, 2010000, 2015-07-23T22:52:31Z
1GmVxLrqqZqq6sfYNaVsxvJLv7CmZwXy8c, u, 11, 0, 1, 50483, 100000, 2013-07-29T23:30:02Z
1GiAEHndocLiH7wL1UKtN76ZNXKnvoh9PS, u, 84, 0, 1, 70877, 200000, 2013-10-13T02:01:32Z
1Gi7Bg2gGLeSPGdYjsEpYSB2AjL8k2XC1s, u, 8, 0, 1, 36607, 10000, 2015-04-14T17:17:42Z
1GgiAqyeRjAe5EEGx41LtVuc4VqjFQ77rq, u, 16, 20000, NA, NA, 20000, 2015-08-12T02:15:13Z
1GdwprmG3EGeo2ErjNWQfVbNLb4uYWB8eG, u, 11, 0, 1, 79961, 19570000, 2015-07-22T01:35:17Z
1GZsNh1a1yKgPNAQJc2wthBWmgaRC6zNVP, u, 24, 0, 1, 69516, 100000, 2014-04-07T13:49:36Z
1GZKgxGY8fk9TyN9S2quTBky93iSNarP7d, u, 9, 0, 5, 738, 160000, 2014-07-30T20:06:41Z
1GYswURYzCQs7ZUaPyz5BVVHgdPxGQ6ojn, c, 7, 0, 2, 11362, 186312, 2015-04-26T11:12:36Z
1GWUFUfB1XaJC9ESSwQFyPjs73AmT6PzE2, u, 8, 0, 1, 37494, 100000, 2013-07-29T23:30:02Z
1GLkKJAMoxRedrnBvLSyhkUb1wcgDRbSYE, u, 44, 0, 3, 0, 1116969, 2014-02-08T12:28:44Z
1GKPC5JmKnU6bUPRNmjXoZdkSTuqWqVREU, u, 28, 0, 1, 1, 100000, 2014-03-21T16:48:29Z
1GHaxh9sFY7UTaw5PL8XjNv3kHy1JuKMDF, u, 111, 0, 1, 24135, 1000, 2015-07-29T10:31:22Z
1GHShAru3CyySYHwNyf7eah53Yt4ncEgxK, u, 21, 0, 29, 121, 3868927383, 2015-09-14T04:22:52Z
1GFmed9rDYZ2LKK2mn4fquzi4kb2VhzWaz, u, 10, 0, 1, 15687, 2660542, 2014-06-07T14:17:43Z
1GDwKjdqJQUvwgBocwyPK1e81jhKDDszCt, c, 8, 0, 1, 74207, 30000, 2016-01-19T05:06:13Z
1GD5Shu7SsCuRvvrms3UgUQ3HmZaSTJBZG, u, 11, 0, 1, 13016, 180000, 2015-07-22T15:57:29Z
1GAwtJ9m7YizJ6ckDUycqXYE95eRXYJciV, u, 8, 0, 1, 6, 500000, 2013-12-11T09:58:46Z
1G9fRsZA4RYbgFahTsG8DtuSmxLSikNyg1, u, 10, 0, 1, 7496, 990000, 2015-07-21T18:19:03Z
1G9Cmynb3vk5B7gsbcjNW2heXa33VSPWWq, u, 16, 0, 1, 71765, 336900, 2015-07-27T21:34:47Z
1G3eNbZYY2UpkyY7t55Xfais1qXcgB9RmK, u, 19, 0, 12, 0, 7999305, 2013-10-19T14:58:34Z
1FzkWL7by7bKfRNXz2stvmn7o9yRjVKbF5, u, 11, 0, 2, 83491, 43240, 2016-02-14T16:45:13Z
1FwNakeXx2VJxLfViE6A9PVB3YyPhRBtmm, u, 10, 0, 1, 2844, 10000000, 2015-07-22T00:50:40Z
1FqFarxVJMcDtCU8KA3L7y7oMYevhTyb9F, u, 11, 0, 1, 2079, 200000, 2015-07-23T15:01:55Z
1FpiEm417BUMx9W6xYuwiXBpfeiwQ1wptb, u, 20, 0, 1, 4, 23350000, 2013-07-28T19:45:23Z
1FmGqfCLdzeRtFCUBm5XqirU3pzD3Q1oGC, u, 30, 0, 67, 3, 2126232926, 2014-10-10T14:35:57Z
1Fk23o2qVJNkppvqdjDVATeJBdRckbSj2Q, u, 8, 0, 1, 54052, 3360, 2013-05-04T13:02:51Z
1FjahFb9GvRNqHqn8kaoU5cSaiexUDRuK3, u, 22, 0, 1, 11990, 9661, 2013-11-15T20:35:11Z
1FhrECZgPmgiRLvkJQwhAjq3PRqe1sz71j, u, 13, 0, 1, 84664, 390000, 2016-05-12T06:21:52Z
1FhBpjtwdFt3bXFHTjjdWSttue4JS4pDZZ, u, 21, 0, 1, 43359, 430000, 2015-09-19T16:22:28Z
1FgtUixG15h9zX4j25X2cXQ5Q4KAkYUkkG, u, 10, 0, 1, 7007, 4990000, 2015-07-21T21:58:17Z
1Fe2p3ntSScKWY3VkNz5trWhXaupp7YZC7, u, 36, 0, 1, 12, 7800000, 2013-11-30T09:29:45Z
1FbGdoE6L3y2V8kWjmcNMYkx2fmHvXiz1K, u, 8, 0, 1, 3534, 1000, 2014-09-07T08:11:10Z
1FYnHspfmgDkdouDYvUhsRdMiJypQQ3rvW, u, 10, 0, 1, 3815, 1000000, 2013-04-08T13:55:51Z
1FWxRCwBciPoLH8Qu1nkxxV133kPY1yoHZ, u, 11, 0, 1, 58066, 38000, 2016-02-28T16:51:25Z
1FRjohKmsLji3rKd9Eis1RuWuj3KSJ8ken, u, 12, 0, 1, 34, 400000, 2016-05-12T06:04:41Z
1FPHpgE3mrB1enPHFpzqm1gY32WZh5mPbV, u, 16, 0, 1, 41217, 191144396, 2012-02-24T18:11:14Z
1FJX8dk1UMKm8Krkmq1RNwg4sBeXdQaDFj, u, 8, 0, 1, 48715, 20108, 2014-08-17T14:08:42Z
1FHULjCPb15WSE942HMkQhv4GdHaQ1AX9v, c, 29, 0, 3, 0, 50000, 2014-09-23T19:20:53Z
1FDJaAX2gRApoKo1cyfopee5Nh5mMR6yjm, u, 23, 0, 1, 29633, 15000, 2015-01-03T01:04:43Z
1F8ATJpwLfXZi4Ke5MFBH92R7UFNHiWfgB, u, 130, 0, 1, 18027, 1200000, 2012-12-15T23:06:07Z
1F5MHqYZm3vhYWJaKuoyDJ3v7JkJr7sC6a, c, 58, 0, 1, 37545, 482000, 2015-08-28T06:40:39Z
1F2K2bhfpRkLMtsNtpgKQToid23AZyvRZx, u, 11, 0, 1, 55166, 10000, 2015-07-23T17:50:38Z
1Ez18hZhq2P2ce9DCrHVqcbYMrTu3wi7ru, u, 11, 0, 1, 977, 15000, 2015-07-23T16:32:18Z
1EyJMd5BUBW3EqSUhUEBVywpEiecaGmGQs, u, 11, 0, 1, 61631, 20108, 2014-08-17T14:08:42Z
1EwrbpnHQZGrGwS3dMmcXhZcoF5juPKhdb, u, 10, 0, 1, 3712, 10000000, 2015-07-22T00:50:40Z
1EukaBty79YUNBdQbfCXX4Vq4Yem5H6k86, u, 26, 0, 1, 8036, 15000000, 2013-10-12T01:43:40Z
1EugGjko4dfEy9CX337wMBVkQ4mNZk45nF, u, 11, 0, 1, 33896, 76931227, 2013-04-11T12:38:58Z
1EtiEGBTp4kcTRA85oKzqakZJJ4sJMsrdz, u, 58, 0, 1, 9603, 100, 2015-07-31T22:50:22Z
1EqXwSZWqXMyDehLEvesqhiyBmJvDT21eH, u, 7, 20108, NA, NA, 20108, 2014-08-17T14:07:46Z
1EnAHWCeiX6guzXQcV8TCFKzQKx3nib8eA, u, 10, 0, 1, 24263, 7676, 2012-02-22T00:25:58Z
1EmUi8vm6xnKAEW2btFvx9w4XtbpaT2bLg, u, 11, 0, 1, 78508, 9690000, 2015-07-22T01:58:33Z
1EhgFEgRJuJrLJCNqgKmgjPuqwRAs73PXs, c, 16, 0, 1, 1989, 200000, 2014-05-16T00:49:03Z
1Eh45j1F7ZukynHYSnDX5kfjDkXohPN877, c, 6, 0, 1, 7619, 1000000, 2015-07-09T14:21:46Z
1EdqCmCxFLWP8kXhszdfvSSHUEzuA6ujcp, c, 7, 0, 1, 1770, 668012, 2015-03-23T09:38:53Z
1Ecrxej9XDm3T9VNDznm1Gwp64Vc9HbZgK, u, 10, 0, 1, 52653, 60000, 2014-07-11T16:30:03Z
1EZ1hHrhj89PwEkhaZ4ML1a5Mwmyrmeb9V, u, 11, 0, 1, 66484, 20108, 2014-08-17T14:07:46Z
1EXaMGL3B7Z2oGq4NDCd2ep1cEb6zgp3jg, u, 10, 0, 1, 7524, 10000000, 2015-07-21T22:22:32Z
1EWPHuSpyuvvfQ1ubgLXQnKZdFRDTaYDsg, u, 10, 0, 1, 770, 1000000, 2015-07-21T11:54:11Z
1ESdJgu3ov5Z1XUv1WdFFPogv9crQKGbec, u, 28, 0, 2, 5973, 9950000, 2012-10-09T10:15:56Z
1ERocRf5QJoGf1MxoEx8UG89k5ciJEe9mU, u, 9, 0, 1, 50483, 100000, 2013-07-29T23:30:02Z
1EQjYKmHYYJWHTv7LLhSr2zhFWt91RrkEZ, c, 10, 0, 1, 1, 100000, 2014-04-28T23:39:03Z
1EQdgCrBjhFPrd4VdeFp338A7YqY4qEVXw, u, 64, 0, 1, 3812, 81466, 2016-09-07T06:51:18Z
1ENBzDo58FdipPDqFk2EMi7VwMVmgG1ckD, u, 29, 0, 1, 19452, 1, 2012-08-18T18:17:14Z
1EFZR2WiC2X1gcjE6goBkjLCZh4Ahi5EyD, u, 5, 0, 1, 54793, 10000, 2015-01-27T00:01:31Z
1EEbuedhWRULsv8tkvXQBFdxjRUFbr3kVU, u, 10, 0, 1, 7664, 3384000, 2015-07-21T16:26:18Z
1EB3nq3YTqzQ8TFTqZS7ge3iWPmu3EzNkS, u, 10, 0, 1, 25797, 9790000, 2015-07-21T22:31:17Z
1EAi4ViQVVSn4jaa3PKMcJX2HxNspMpu9Y, u, 13, 0, 1, 84331, 390000, 2016-05-12T06:27:25Z
1EA6hPvU5wBi2VfUPVb7TYw1bPehTNr22Y, u, 11, 0, 1, 1528, 50000, 2015-07-23T18:17:50Z
1E9FnGzCrqKKtfzQyRyjTHTYMFXnwU5LKP, u, 8, 0, 1, 55616, 30000, 2015-12-20T15:53:54Z
1E5nZAR8HAkdtgXxKYGVxgPLL4XQpdYPvh, u, 8, 20108, NA, NA, 20108, 2014-08-17T14:07:46Z
1E3QtSv491Ku8EH3jN3hBErzQnm3YpSoPv, c, 9, 0, 1, 13905, 30000, 2014-07-25T22:44:18Z
1DzZ9NZfdvWqh1a1qcHCspq2nPTAC4sfuQ, c, 37, 0, 1, 54082, 188000, 2015-08-28T06:40:39Z
1DxYbxRXsZwVfkaoHW1LGVvwZFbftKumGr, u, 6, 0, 1, 16419, 10000, 2015-02-12T12:21:43Z
1DvCCsSegRdr3VBKuB5YEo1Ry4xRMxpT3h, u, 12, 0, 1, 0, 400000, 2016-05-12T06:06:29Z
1DrQmoSNYs973HpfmARFXWfvMUdqf1bqaq, u, 10, 0, 2, 18778, 2378410, 2015-07-21T20:37:17Z
1Dq6Q9SHh5sm5DQuDcEfDJdc5sQgcRQoJW, u, 17, 0, 1, 51, 15250, 2016-08-06T04:55:54Z
1DowDxPJYc8m7i6gpQjXyPgZr9zbN4fywN, u, 124, 0, 1, 44009, 1, 2012-08-18T17:29:00Z
1DkT3k1n9b3RKKMeYwcCiCCzHDGu6Upb4E, c, 10, 0, 3, 1759, 25177, 2015-04-26T13:53:50Z
1Dk8G3aDiBxXr3Hq89zScVqE7edK2nWfML, u, 13, 0, 1, 84779, 390000, 2016-05-12T06:19:57Z
1Dg3WRy9HizDWXj5ShKVxpRQiHi9g7kCcY, u, 33, 0, 1, 4935, 1952266388, 2013-12-01T22:00:55Z
1DeLtoi8Qvg8AgqkVC4645cqdekjeTqYhT, u, 6, 0, 2, 0, 45000, 2016-07-21T00:00:15Z
1DeL3QBq8SCrPbexxV99PnArxXNubsYyDi, u, 8, 0, 6, 48311, 28054000, 2015-06-30T16:02:46Z
1DdWb3WtHckqJkqwtRWgMdJ9CXNUA1gJkR, u, 12, 0, 1, 3316, 529661, 2013-11-15T19:39:55Z
1DZN7sRq7EdSt6XiYEyMgsC68TASQwi4Tq, u, 6, 0, 1, 77003, 20108, 2014-08-17T14:07:23Z
1DVmfiqkgHDvTUULfeWuJ7YzwTJDQJT6K2, u, 9, 0, 1, 49453, 5500, 2015-08-23T05:45:25Z
1DRs3YDAwoXSTi4FQN89aoy17aQ7i5Cqo3, u, 20, 0, 2, 63026, 2225850000, 2012-04-23T13:56:53Z
1DP8Qcw9r8LEYkcYwXgsvDpu5WLqJEdTfS, u, 70, 0, 1, 81996, 100010000, 2013-12-21T21:06:09Z
1DLAmCeBUVc9XPHhmpPp4JHGZQ4YF92TAK, u, 16, 0, 1, 74094, 100000, 2015-02-22T08:04:19Z
1DKQnoctNNucyEPK4m6gX7XJSPkAZB1LTi, u, 10, 0, 1, 6718, 10000000, 2015-07-21T22:22:32Z
1DGZMZQUhdsKiMgMLPb79EcgXarETBC3K4, u, 9, 0, 1, 4003, 180000, 2015-07-20T15:32:21Z
1DGXWdb6FREuCLUKf3FMcYKZX4XCZ4jU2J, u, 35, 0, 3, 8854, 88350000, 2011-10-12T19:14:29Z
1DEyq5vzyXNaQQVxAKLGrSUCDvHx9yTuVZ, u, 10, 0, 1, 1085, 1000000, 2015-07-20T18:14:31Z
1DEjgPZRZyHK6i5rn4hoi7tP5GiKsfbJ5X, u, 88, 0, 1, 70886, 200000, 2013-10-13T02:00:31Z
1DBGg9Nc3xgNxU8Tk5bsbSjKt55u1eq5Qv, u, 44, 0, 1, 2696, 1926526, 2013-03-30T13:53:23Z
1D8y12q87wfrVWK7WyVsqHTRJPt3NFVx35, u, 574, 0, 1, 54275, 100000, 2016-06-22T07:37:38Z
1D7W1MpRP3vEHiQuBmJnXZ31U5yVXewgmn, u, 57, 0, 1, 68062, 546, 2016-07-26T13:06:16Z
1CrBqjcfCqGneTW37hY8ieT2THwe6Ympew, c, 16, 0, 1, 9252, 4590, 2013-12-03T10:08:44Z
1CoyTMT4gxv2iJ2tLRsMZL3tf1FcAmtYZ3, u, 28, 0, 1, 16074, 6844, 2015-07-29T17:53:51Z
1CmwjJZvzGkgW8PofoFqn62QbxbWGgkHQL, u, 288, 0, 1, 11634, 5500, 2015-07-30T05:51:38Z
1CkY4S9bu4Ka8Kd6XH7tumPPFA8dbFwW3N, u, 10, 0, 1, 11928, 1000000, 2015-07-21T14:45:13Z
1Ciuor84QnzC52FSP5tGBLGCjSL96GVbw1, u, 14, 0, 1, 8162, 776, 2015-07-19T02:23:11Z
1Cibw3Wt3P3bV2dLZ1diA1tEBS9CGagLpc, c, 44, 0, 10, 0, 554840, 2014-05-05T15:54:47Z
1CiS1eV1cZdPgLeEV5nQLJrCDCU8LpMKwC, u, 22, 0, 4, 4765, 209560, 2014-09-13T15:12:49Z
1CcdoStu9NstpZUEPyJ3kTyhphrXvWEYSQ, u, 6, 0, 1, 2, 30000, 2014-09-17T04:55:58Z
1CaMS8Abhp2SkAx5NVC2biPwq1cd65quSk, u, 9, 0, 1, 4114, 200000, 2015-07-20T13:55:47Z
1CWPPeeTMBAbM1BEHTtcJ7AWkFhwSwvP9n, u, 7, 0, 4, 60924, 17242860, 2015-02-16T16:33:24Z
1CRcBbQPJ2YoPZZhNUUzFpw8gA5YbVtWuR, u, 13, 0, 1, 85363, 400000, 2016-05-12T06:10:13Z
1CNmL3ECHtAPxb9QZWrW29bq4t9T4SDUR4, u, 4, 0, 1, 86255, 60000, 2014-07-11T16:08:59Z
1CMMBYkiB3AVXbysaYuFEepSJTVRggFaNm, u, 29, 0, 2, 56976, 90010000, 2013-11-29T16:54:26Z
1CLrfZU9kPCT8JUX1KfdWbpBrJkx7rafi8, u, 18, 0, 1, 57567, 10000, 2014-05-01T07:55:34Z
1CFjVkKyUvRUS9FXGTc7WQ5M5XKZ6Lgkwz, u, 60, 0, 1, 1, 500000, 2015-11-27T13:57:09Z
1CFhGHGFVihPfhPqu9aLL7xz9pYD2pyLeN, u, 13, 0, 1, 84664, 390000, 2016-05-12T06:21:52Z
1CFewmRpUFGpTvjxdmniV4ffnxDVVWJv9P, u, 38, 0, 1, 1, 100000, 2015-02-02T13:06:20Z
1CArjb7kpTRxuNnFTL6kjs9DBsUcbwfA6U, c, 29, 0, 1, 38472, 387000, 2015-08-28T06:40:39Z
1C9Y7WM2zvGZjBFqHiqAw5Ks9GxP2sALws, u, 10, 0, 1, 11999, 490000, 2015-07-21T16:46:03Z
1C7yfdj7R8yFFVUqHoNXPogQjQqb1n8DyN, u, 26, 0, 1, 40961, 10000, 2016-02-25T12:46:26Z
1C7MQgKrygvvsFEpgkczHuMWtnB6km3aPA, c, 49, 0, 1, 37545, 375000, 2015-08-28T06:40:39Z
1C7A3EYjeaDCzFrwHc5SDDQ79L9Xfjawpz, u, 8, 0, 1, 42664, 20108, 2014-08-17T14:06:49Z
1ByuDqbsSxpUQqyTqQUMHTFkDHANFyHuU7, u, 44, 0, 4, 28822, 8551600000, 2011-12-10T02:02:04Z
1BuQYQecGhSmLDaLxT7fQXFqBFdMarXrGd, u, 5, 0, 1, 37, 30000, 2016-07-21T00:10:34Z
1BsNpknDfiz35aZXMzHbb8gWvqWx1ckWG9, u, 11, 0, 1, 37902, 20108, 2014-08-17T14:06:49Z
1BrS3zRnDHJEyeV3arQWrNrmtVA9uiv7T8, u, 22, 0, 3, 67003, 2086980, 2014-08-29T21:15:41Z
1BqKQtheChxvjv8eE976HxhAS7X5VFxD6g, u, 8, 0, 1, 66736, 35103, 2015-01-15T09:21:06Z
1BnmEfJbrwr29VczfduwfRDPYpuTLc7TvA, u, 10, 0, 1, 86264, 40000, 2015-07-21T22:45:18Z
1BnN5a635CZW8iGQ8v3CrF4egPX9x1GDzV, u, 56, 0, 1, 3, 1000000000, 2014-03-29T14:01:12Z
1BnDdPEKDj7ZJ5qFh2QXZaMHvR4YcASYkt, u, 17, 0, 1, 2, 500000, 2014-03-01T16:37:06Z
1BiPyR73R6VMMtGYHy1GfwixDz1piXwRnb, u, 17, 0, 1, 64749, 10000, 2016-09-25T15:10:55Z
1BhrsvzcbjP6cPUrQDBjYbTztnHHFDLE9W, u, 7, 0, 2, 74716, 1397948, 2013-05-21T00:07:17Z
1BesFUpZq1dWiorwSeVa2MREnzTmzXGkzn, u, 40, 0, 1, 23071, 1000000, 2013-10-07T20:33:51Z
1BbjBA3hh5VzCUaRZbCyrpM4WLGL7A9uS9, u, 22, 0, 2, 10783, 2020000, 2014-08-29T21:18:10Z
1BaMbbCuZFgs38FSaswzx3LDzFsFXHPgGj, u, 11, 0, 2, 566, 143312, 2015-02-20T09:30:16Z
1BYkmncRhkWXdX3aFhXrBr3pBNVHc724ZF, u, 10, 0, 1, 11732, 10000000, 2015-07-21T22:22:32Z
1BX4dH6MKVx97PmcvkhuhL9Tetry5Fpx4Y, u, 10, 0, 1, 36483, 2990000, 2015-07-21T20:28:18Z
1BW1RMWNL5aeRLgc3TK1vFbu6x265bAgLo, u, 8, 0, 2, 58331, 1941640, 2016-02-04T00:15:16Z
1BUyXsY6G7KYqQudrHQJTnQbPuvUrSQ4kP, u, 5, 0, 1, 59902, 20108, 2014-08-17T14:06:22Z
1BUXEGswgQPHxPudk16HWp7URf9PTkeYeZ, u, 22, 0, 2, 57538, 10020000, 2014-08-29T21:22:01Z
1BStui3issVdHZshnoNm6fScibnsq2fmyv, u, 6, 0, 1, 7492, 1000000, 2015-07-09T14:21:46Z
1BRbHFG6uz9kUhkehSMAt3tDhmGivD2Wqf, u, 34, 0, 1, 0, 403779, 2015-03-25T08:27:25Z
1BRUs7yjac9ySsVuYXc1mH5RZ4stcQ4wE2, u, 10, 0, 1, 32689, 2990000, 2015-07-21T21:31:32Z
1BQmbdHdtdJnGbhNLgnr5w5pKJ4aFghdLp, u, 139, 50001, 3, 7905, 6085500002, 2013-10-23T14:58:26Z
1BK4v5iSa8LnjwjF6qCM2mi3WnY2C89gWz, u, 13, 0, 1, 84552, 390000, 2016-05-12T06:23:44Z
1BJohDg8wTjfZWivMd3DzA8KMk4qjxo84w, u, 11, 0, 1, 29561, 20108, 2014-08-17T14:06:22Z
1BFQqCJFCbN8G4FXLEkmebNcgf39pi5oor, u, 13, 0, 1, 84664, 390000, 2016-05-12T06:21:52Z
1BEFyrNrGZqAkx4g1yv1a1CXcr5m32C2Ve, u, 11, 0, 1, 68868, 9990000, 2015-07-23T04:38:48Z
1BE2iG22WfLThgAA2GWCreqxRqA9bB9fCH, u, 18, 0, 1, 139, 1000000, 2012-11-10T13:20:58Z
1BDjyHZkq1FDdyjMcwxA6MLL6gBxrFX6Lv, u, 5, 0, 1, 33, 100000, 2016-07-23T15:48:15Z
1BADMvxJCx96Cb7m88wueMnVK8Ru2CD5dE, u, 10, 0, 1, 2845, 20108, 2014-08-17T14:06:22Z
1B9uy4MiysmPVJiZdWCa8LM8RyFZBi1DNC, u, 10, 0, 1, 84376, 50000, 2015-03-26T18:06:46Z
1B6xNAyuoHduRsa2rck9DUssP6s2yQrdqE, u, 13, 0, 1, 84439, 390000, 2016-05-12T06:25:37Z
1B6AErFq7usyGofG1RrRiVTHo4XxY4knzi, u, 13, 0, 1, 83065, 50000, 2015-04-26T04:01:04Z
1B5tcYNDVsZPZtBSiBwzW8BHBJoyfARHE2, u, 6, 0, 1, 14098, 20108, 2014-08-17T14:06:22Z
1B2VYgE1obx4A9M5Txm9MXAc7ZcFayvyhy, u, 11, 0, 1, 36827, 20108, 2014-08-17T14:06:05Z
1B1sMpijxxkvnYxj7SSiho3ELa7bcM7j6X, u, 24, 0, 1, 10, 17000000, 2015-05-14T16:10:00Z
1AzkH9mvyYY8MiNYoh7Pq76BcdDEXL1EBh, u, 13, 0, 1, 47192, 1000000, 2013-08-31T08:28:26Z
1AvGssrXx63hvc35CUhZccfEG5kFtcTRqk, u, 22, 0, 1, 22118, 10000, 2013-12-03T10:19:44Z
1Aq5Y2bMbJ6NjJ657gdMepZ6zUyXx88mq1, u, 8, 0, 1, 42708, 20108, 2014-08-17T14:06:05Z
1ApgaTN9BHxZbt742PErJQw9KWhghvVfB9, u, 10, 0, 1, 81083, 9690000, 2015-07-22T01:17:18Z
1AoCfAGNDRGWgawSe445zcfLxqsZWGvsH5, u, 18, 0, 1, 27966, 755287, 2012-12-23T19:50:32Z
1An9awMrB8Y4QTKyKcjMaE2Ttuz9gpuF2q, u, 6, 0, 1, 400, 20108, 2014-08-17T14:06:05Z
1AioskCBPdS4xu1PVTXsTMkVV9R4KvJrCi, c, 20, 0, 1, 54477, 119056, 2015-04-26T19:39:39Z
1AgbmcUPeUeXgyEyi59bTFgect2beXWXav, u, 56, 0, 2, 73, 133848693, 2015-06-04T22:10:26Z
1AeG6JsxeottBdSAKPbB89ndiW1R6NrwcR, u, 17, 0, 1, 0, 32480, 2016-05-09T22:20:53Z
1Ae5bLcHtvc6JRKUYyxqqGk3FeviUbCyTH, u, 67, 0, 1, 63508, 100000, 2015-03-22T01:11:35Z
1Ae3JwMsdHsLm6fRfp5W4JMswqiEHH6RV9, u, 5, 0, 1, 3, 20108, 2014-08-17T14:06:05Z
1AbGyrwwkxKVjqgCtHeJxUrQpJsmpX6sxj, u, 88, 5430, NA, NA, 5430, 2013-09-15T07:00:21Z
1AZqShz3rwGNUehpdDGYGXfzSDDKMPpCCW, u, 18, 0, 1, 21189, 1, 2012-08-18T18:18:18Z
1AZ4xXvv9TeQWTVed32Q1y5BqGtodLb8Ly, u, 13, 0, 1, 84552, 390000, 2016-05-12T06:23:44Z
1ARa9k6eB2UsdvVwMR7yFhJY4SXtiPBMPN, u, 24, 0, 1, 0, 84123, 2015-05-16T22:00:29Z
1AMY5NCme8mmqrAbawLeSXgfbZ9vteNPUm, u, 12, 0, 1, 28, 400000, 2016-05-12T06:01:00Z
1ALQ32ufG4cHPdFBnbgyRcMg25w12C5ric, u, 13, 0, 1, 4870, 3055, 2015-10-15T16:50:57Z
1ALL5MjUmrDihVRh9S2F9jth8XhMAShQKa, u, 13, 0, 1, 84331, 390000, 2016-05-12T06:27:25Z
1A9V4bDDnxqbBWREhTZkaDAdB8EajyHarP, u, 6, 0, 1, 66616, 20108, 2014-08-17T14:05:34Z
1A5UD9c4sBNZtaxekijBWyQEUxmAEazpPe, c, 26, 0, 1, 40443, 10000, 2016-02-25T12:46:26Z
1A1W9xiiism159GNR4vwLkfYyZKY2oWqxx, u, 11, 0, 1, 9798, 180000, 2015-07-22T15:52:41Z
19z4KF1642oUyprokUv8hnLuoCFiVvDmGe, u, 13, 0, 1, 50952, 100000, 2013-07-29T23:30:02Z
19yBEgoGAEEsw5sFGMGCQpKi4uL4RLVmPV, u, 11, 0, 1, 49859, 10000, 2014-07-25T22:45:34Z
19y3fXtDMx3oC1DFpNJCqemWfoNgEyvQDA, u, 11, 0, 1, 50054, 7265, 2013-08-14T20:20:46Z
19xmbz8gny2Q7GjCfUQkWQH93JmLBBRv5t, u, 13, 0, 1, 85143, 380000, 2016-05-12T06:13:53Z
19uZ5RgE2B4zx8FWez6TzPLfh7iCuyC1md, u, 58, 0, 1, 533, 298112, 2015-03-10T18:51:25Z
19uF1TTPRTRrGsCf9qt3CkMTvsUMUPkvd3, u, 10, 0, 1, 39488, 10000, 2015-10-25T04:45:31Z
19rPXUiPRuwJptkH9sDVh3MnDho1Zuhrdz, u, 7, 0, 1, 66999, 20108, 2014-08-17T14:05:34Z
19kCVKrrHGacFfsox3xqAc8eSZT82cWe1b, u, 5, 0, 2, 3, 60000, 2014-12-25T03:49:52Z
19isNwE5xs2YLgw2G1SLuarrxx2fBJbJMk, u, 36, 0, 5, 10030, 6069954769, 2013-07-12T03:17:25Z
19iANz9C8Xuw1LSHUedbZLpsjQizXEUdBH, u, 9, 0, 1, 4658, 200000, 2015-07-20T15:48:22Z
19gdYiQcbM3wNooEdibatb5orcLKYtRoKe, u, 34, 0, 2, 78, 19000000, 2012-12-19T21:27:29Z
19bhAYqtj7fQ7CWNbQ2StDLwnFQdnvLyJL, u, 12, 0, 1, 13533, 2049768, 2015-02-20T13:16:46Z
19Z4pjRSeLJZwSm4BQaGD5767apvNpsgvY, u, 15, 0, 1, 73049, 373971, 2015-08-14T19:18:28Z
19XdRczPbZ3oDKKCsyC7HP6f5nxf2tb41o, u, 12, 0, 1, 38, 400000, 2016-05-12T06:02:53Z
19X4Hm7e6pBuNBXcHtdUhjntUgaFixN2Nk, u, 17, 0, 1, 57478, 100000, 2012-05-19T21:03:16Z
19WtZfYzWzeX2g4AunbLXkSiHNFvaTPT5f, u, 11, 0, 1, 70993, 200000, 2014-04-01T12:23:56Z
19UvgoiuJdcKPR5vBr2C83Kv9kavBcBvDT, c, 24, 0, 1, 7877, 53799, 2015-05-16T21:57:34Z
19UnPBTpRsteNxmmYwd7uRb7ahwKtQjurg, c, 13, 0, 1, 4036, 20000, 2014-09-02T00:54:55Z
19RXqVmUeJCmxz2pwqLyMz1StNiFMoh7h2, u, 14, 0, 1, 50952, 100000, 2013-07-29T23:30:02Z
19PzpfAmaJyFz86maX3C7jS82t1H6SR1VF, u, 11, 0, 3, 73320, 20259058, 2012-02-24T23:11:40Z
19Lo8z1BGxSN5CyYSaQK73A5EQATBEa62M, u, 149, 0, 1, 1170, 500000, 2015-02-06T09:49:19Z
19LnVwFJ2pyqQo63YcfTzj8r7HFEWN4bTX, u, 89, 0, 1, 5346, 5460, 2015-11-24T14:06:50Z
19LbovXcsTrj5PAoszkq8d1EGS8ATQwtot, u, 12, 0, 1, 14193, 15000, 2015-01-03T01:05:37Z
19LBQ22pRujZZHAdvssRMjBDBqU8ndTc9T, u, 22, 0, 1, 58485, 71000000, 2013-01-29T17:01:17Z
19KmXRLBHjP2qxrWEqN6yFqcgYftmrAHak, c, 18, 0, 2, 780, 40000, 2015-01-26T11:37:27Z
19FrJCZPJcy9zVxxJVQSJxX8HziRY1cS1M, u, 5, 0, 1, 13816, 10000, 2015-02-12T12:23:19Z
19FkmhHEzgCXKfALXhahuCTDVcRnxT41MK, u, 8, 0, 1, 15419, 81878, 2017-01-26T15:56:41Z
19FD6u48uPUdkfjzLM21GQkfY81CVwWRaf, u, 22, 0, 4, 61192, 222140, 2014-08-28T18:13:00Z
19CSvGuyQGybDbUXbKMuKpQuRVn4CNsAp5, u, 8, 0, 1, 21511, 1000000, 2012-09-11T07:07:58Z
19BvpUJED8GTJ3cw3PBdQfrZyZE4udDKZH, u, 64, 0, 1, 53839, 500000, 2012-05-14T12:58:28Z
19BrbRNn5kFqLyoYzBs3ujLj3hHkDh1sC7, u, 10, 0, 2, 57077, 12009524, 2012-02-25T00:51:05Z
19BV9bM4RcW3HNFuaGBjfvripFQ1QpBmCx, u, 9, 0, 1, 84916, 20000, 2016-06-24T04:05:21Z
19AgyPo4p4Hdys41h41YWJMcCqapCnzmxH, u, 14, 0, 1, 3735, 300000, 2014-10-14T14:58:41Z
197zDV5sGxoWQ9opSnGbeY5DVq4SA7hwRd, c, 20, 0, 1, 21412, 48000, 2015-08-28T06:40:39Z
194oZWVg6XNuRbXnEuwRdjQN6vHf4Nz4Xn, u, 10, 0, 1, 53647, 20108, 2014-08-17T14:04:55Z
192DMLqKgJcM6ir9eFiVKtbtTSmXSVCoAz, u, 10, 0, 1, 8145, 10000000, 2015-07-21T20:00:37Z
18x2fd9CgitLdXHQjKpzdJNKsKvDcrnURV, u, 26, 0, 1, 45365, 10000, 2016-02-25T12:46:26Z
18q8nPHcnNp2kis5V35LZRxH7pXyYcq74z, u, 12, 0, 1, 0, 400000, 2016-05-12T06:04:41Z
18mbAiZxEbTGjMPbsTZubyN6J6xDr8SnMT, u, 64, 0, 1, 49832, 30000, 2015-12-18T00:15:56Z
18mGmhaPmpKUYRKhboav2kQDkoVWwrHHVE, u, 9, 0, 1, 2869, 200000, 2015-07-20T15:48:22Z
18hXnLqvCs4czG8xLzwgdR2cq9jmxbsjQ, c, 14, 0, 1, 36535, 46000, 2014-09-14T08:19:46Z
18gVYwzotgkQN84Q8MTXUYZAcrxeSFLPUK, u, 64, 0, 1, 26267, 13936, 2016-10-14T11:25:46Z
18fwBtCmd4SxKXgk8SHkEV2KK4oF27GiU2, u, 10, 0, 1, 52959, 190000, 2015-07-22T01:22:18Z
18cspJV49DKXx2NLf1o7e3xRoTy2wbyW7c, u, 43, 0, 1, 60489, 5463, 2015-09-29T17:13:13Z
18aLnvpi9MdnZmDsEEJK8Yg7Y3WSGiR6Np, u, 5, 0, 1, 73128, 10000, 2016-07-20T23:49:14Z
18VKZ7TP2jTzTw7EL9oryjYhmdArx8u7ZM, u, 25, 0, 1, 27972, 100000000, 2015-08-05T01:03:13Z
18UrXQoz8uL1z1SpzTTspm3dM7QmCDieMT, u, 6, 10000, NA, NA, 10000, 2016-09-24T16:33:30Z
18UAd9myYQBxm9THukV7KaU6MpMKHcM1qw, u, 10, 0, 1, 33866, 490000, 2015-07-21T23:20:18Z
18SLr7mLjA1KZjytQvAkEJ9mTqGdPPnmTJ, u, 27, 0, 1, 56321, 10000, 2016-02-25T12:46:26Z
18SDPoeP8XEVHH3NjJW8u5GdQc7YkGj5FB, u, 14, 0, 1, 3371, 9760000, 2012-04-10T04:10:53Z
18NoxJZtvZ6UVGwy7TUEAVGBuLsnq8WFbb, u, 16, 5460, NA, NA, 5460, 2016-04-27T12:26:53Z
18MTwXFipt3j4VASnfRUMkZhZEZaoB7io, u, 68, 0, 1, 1, 200000, 2016-10-06T20:53:51Z
18Lscr8hCpDGZqe2Hf5d84QVpR1dQ4JaTQ, u, 13, 0, 1, 85472, 400000, 2016-05-12T06:08:24Z
18LNLdrBbEJr2Q2YXZMJLJKvGiKZ8JVmrc, u, 10, 0, 1, 3350, 1000000, 2015-07-20T18:14:31Z
18J9hFHbyChNhHwzFV239fsJxTxbFckrT8, u, 11, 0, 1, 55148, 10000, 2015-07-23T17:50:56Z
18HaL88Nq63raSkEjoxxWyckgq5qjhv3GQ, u, 12, 0, 1, 14174, 15000, 2015-01-03T01:05:56Z
18FMHtu5nH9LjSEc4r13dqPPGPT8uGButC, u, 55, 0, 1, 42460, 50000000, 2013-12-03T12:48:49Z
18AZNBPqSdPFM27NfGVdkxUkfKMcvdqNge, u, 12, 0, 1, 0, 400000, 2016-05-12T06:01:00Z
188i6XYhgrS4LiJtQzVwKZJau3BcLnk1Xk, u, 11, 0, 1, 80485, 9690000, 2015-07-22T01:27:02Z
188Xk8baV9ei9FTf7NktytVdRBXXyoqmYG, u, 11, 0, 1, 6371, 190000, 2015-07-22T17:53:18Z
187qtwqcjepcQWA2ZFGTiykd9KbAv67VR, u, 8, 0, 1, 59516, 20108, 2014-08-17T14:04:37Z
183rrpv7UoaBHKq9okGVPcauNdMosHXDk8, u, 35, 0, 1, 6732, 100000, 2015-10-19T15:14:12Z
183EiK7o9ktAhzChqg3ncp88oEZYu4qqjz, u, 7, 0, 1, 50483, 100000, 2013-07-29T23:30:02Z
181F9BQbnu5xRqeKEjBVCPTcvGean8hanJ, u, 10, 0, 1, 4489, 2155691, 2015-07-20T19:23:39Z
181B17XzKRnmrEJoPbCHDBJM3ZKUAi9FLc, u, 13, 0, 1, 85143, 380000, 2016-05-12T06:13:53Z
17vbpumy3NemAcAX7232Brbty98RdbBFai, u, 16, 0, 1, 4483, 1000000, 2014-05-16T12:59:27Z
17n5bGM4r8oDEX3bg3HJmjFJmLF9XUY1GA, u, 30, 0, 1, 18707, 10000, 2014-11-02T23:13:20Z
17jPvjQuK46FozAViZnuaegCbB7ns1B5J9, u, 11, 0, 1, 40105, 190000, 2015-07-22T02:02:19Z
17f9V5bMPRogzUTqVToHAy1KT3oDLkxSzK, u, 5, 0, 1, 39, 40000, 2016-07-20T23:54:24Z
17SBD4YDAVHmCPzYeiiuBAY6zHMmf15aZQ, u, 7, 0, 1, 5307, 20108, 2014-08-17T14:04:08Z
17RWUcG1fLTiLkD7tto9xMZikyjC1qXt9K, u, 27, 0, 1, 17386, 1240, 2017-01-01T09:56:49Z
17K981v6fzXuCGS1wNfAzAApEtMiJAaUy5, u, 10, 0, 1, 33842, 90000, 2015-07-21T22:26:48Z
17FTTNjuHZa7cfPVgce2C4GjziKGN9ff9U, u, 18, 0, 1, 1, 1000000, 2015-06-04T07:03:43Z
17EaXeW9YWxgHuT4z1GXBPFE5ieLMANtav, u, 6, 0, 1, 77998, 10000, 2014-03-02T02:09:38Z
17DT6XAP1BewtB6ZRnepYQdYGwuafAWps2, u, 22, 15000, NA, NA, 15000, 2013-09-16T21:00:28Z
17BZGcdDA1K8wrsJZgnTqNUiTRqeYMukZ8, u, 6, 0, 1, 50483, 100000, 2013-07-29T23:30:02Z
174yAueGYfEF7QxDp6A22YyiHBVKQQB5tj, u, 21, 0, 1, 74639, 26833, 2016-02-02T18:20:40Z
172oMkYjCm5RYPpiGY5ncpRkT2tW6pTVjW, u, 13, 0, 1, 84552, 390000, 2016-05-12T06:23:44Z
16ztKVb5KDiNVYfpiUcYyTmDWANQWmtUdu, u, 107, 0, 1, 71094, 200000, 2013-10-13T02:24:52Z
16zULgpxG4fMiDF7qiK1Jcbj8r9poNGunk, u, 13, 0, 1, 84439, 390000, 2016-05-12T06:25:37Z
16y4nNeiiQk6yDqJJR41A56pkMvGSg1sjJ, c, 7, 0, 3, 26, 12250304, 2015-02-16T16:31:43Z
16xKpRC9Pe7FHaihuU5eniBV6m8mSCqF5G, c, 27, 0, 1, 13624, 10000, 2016-02-25T12:46:26Z
16uM2iwYbwCE3jhR3oRF1quECcXBceLVYA, u, 10, 0, 1, 25779, 9690000, 2015-07-21T23:35:18Z
16tR74nCgAKSYwapEoxc8k1cqaUcaDRNHW, u, 11, 0, 1, 51985, 190000, 2015-07-22T01:31:04Z
16iud2PDgfDYi3hBvoeJ68RjDKABrWZVmm, u, 80, 0, 1, 2579, 50000, 2014-12-27T14:36:05Z
16csYMjRrsPfcFxzT5Dau97YTp2AZuJh4p, u, 22, 0, 2, 57284, 2020000, 2014-08-29T21:17:09Z
16XqWrUUgqjC5PJX7cCvzs4NRZrU3dkdyQ, u, 10, 0, 1, 30965, 110000, 2015-07-22T00:53:04Z
16UeXLAp2kJoRLfGn6HeJ76MaseqKfLb1c, u, 6, 0, 1, 27604, 100000, 2015-01-15T09:15:18Z
16RmzY93uTnV5Q8NjEAWVWofUJJhne2qhF, u, 11, 0, 1, 610, 20000000, 2015-07-23T04:51:20Z
16RcEpg1J4mDLVpLiRxJDXtou8YBaHrJR6, u, 8, 0, 1, 4, 20000, 2014-12-07T02:11:40Z
16RPNy63RGMYHDjmvmLF5h8gfSj7qKzJKL, u, 11, 0, 1, 17186, 39500, 2015-07-23T19:01:56Z
16PWWF4mKH2grJVAFtAL4Z8KEestToeV4, u, 10, 0, 1, 85496, 9590000, 2015-07-22T00:08:18Z
16M46XRPbTRfoSX9dLFGPEd2PP9R3P5Wsr, u, 12, 0, 1, 50952, 100000, 2013-07-29T23:30:02Z
16JhNwXLDwr8AcAdE3fb9sd5JVBqF5GzbX, u, 11, 0, 1, 50899, 190000, 2015-07-22T01:47:03Z
16GsPwhmfrTLEqp9kVbtMXEuHztCsbYL19, u, 12, 0, 1, 35583, 66600, 2013-11-02T02:13:55Z
16FBGkzennuqJ78w9yL6ULDA3Rgt3Sz7qR, u, 24, 0, 1, 37226, 13813, 2015-01-23T13:34:35Z
16D5ozgHJxXxtLbwMAUfoGCBv4XDwQS1me, u, 9, 0, 2, 48813, 514880, 2013-11-26T15:41:00Z
16BmgPxPsGmNqJJaQkxHUu4Fz2QHp5NEsg, u, 39, 0, 1, 13598, 10100000, 2015-09-09T18:28:32Z
16AyBSicxLwtWZDarbJViuT76wqMHwuQd4, u, 10, 0, 1, 20610, 190000, 2015-07-21T23:30:04Z
16A9uDBNa9jz4fZrDDidAZ2B7ECcT5PTip, c, 5, 0, 1, 409, 1000000, 2015-07-09T14:21:46Z
16A5RFckRNW6fZzfjCGSneD3PApACLRwix, u, 45, 0, 18, 3884, 10568557389, 2013-02-13T20:32:08Z
168hYiiRm5vFZE3PYRTijn3bSRCTBpDnHQ, u, 13, 0, 1, 84331, 390000, 2016-05-12T06:27:25Z
166Mz3CYUBk93TesAn7F82AfeBmGSXmiFG, u, 11, 0, 1, 29193, 40000, 2015-12-02T22:20:28Z
1636h3bNkj9rtUmXRQNYu3zPorFZbP92W3, u, 10, 0, 1, 3122, 10000000, 2015-07-22T00:50:40Z
162cnv2dZWSyyCrP6gRSA54oVkuLZa1orW, u, 5, 0, 2, 3, 138813, 2015-02-16T21:41:16Z
15ytti5HgCvuBXmspJ89Qyfiuv9gNxLqaA, c, 26, 0, 1, 43328, 10000, 2016-02-25T12:46:26Z
15vVQwwkwoE7ENp6gmBVhjhv45d7TXWuqK, c, 11, 0, 1, 34199, 49500, 2015-06-26T19:02:29Z
15u76L9tuYdFcmC83rS9NspfUjcREn2FXt, u, 13, 0, 1, 84918, 380000, 2016-05-12T06:17:38Z
15tqBXfF5umoxWLp8tK3X33JRUVTiTktKd, u, 17, 0, 1, 6, 2000000, 2013-11-25T11:53:41Z
15rt9nwKC96sCbJhoXQ7oiahn3tAKMq9ZU, u, 13, 0, 1, 85363, 400000, 2016-05-12T06:10:13Z
15rYFDmusPjchktEirNiee354zD8MCorXv, u, 16, 0, 1, 56168, 100000, 2013-07-29T23:30:02Z
15r2TXtjKAxaWB8rRVPNFrMZTB5tuXipV8, u, 17, 0, 1, 48010, 66600000, 2012-09-07T15:24:07Z
15qkskBHR7LuRAiuVUdoU9fQeBZkbJ8zHF, u, 14, 0, 1, 3023, 20000, 2014-08-05T21:13:37Z
15ptPwbnLrUv1HnQEuYPrXg94KeJjFpKTz, u, 10, 0, 1, 84971, 9690000, 2015-07-22T00:16:47Z
15phnoqGifpVLbq2zoQzvkeBThrrV2Anax, u, 8, 0, 1, 72653, 374069, 2015-08-14T19:25:04Z
15pXngJPAwWYgKpXiajbvjdmAhki8Hz8Gj, u, 6, 0, 1, 54274, 111733, 2013-11-27T18:01:13Z
15gxRutb1rX17B4s5u9cejQXLEV4w6vLZm, u, 112, 0, 1, 2888, 5307000, 2013-02-26T18:23:26Z
15gkeGBxppZQ424DCyyRrydjkg1HjsNhrk, u, 19, 0, 1, 6, 1000000, 2013-10-30T09:03:20Z
15giDH2tdmXizyx981Y2QGQo4kKy2ZNPXb, u, 10, 0, 1, 28942, 20108, 2014-08-17T14:03:32Z
15gCfQVJ68vyUVdb6e3VDU4iTkTC3HtLQ2, u, 33, 0, 7, 46591, 26603099495, 2012-09-25T11:49:11Z
15feDg7SzfZhBhVdsDS8EKtbCx1w1jrpbD, u, 10, 0, 1, 1664, 200000, 2015-07-20T22:40:40Z
15eHdYLLYw5Yp8Yqp7ACpb6HNHVnQX6YXt, u, 35, 1000, 1, 771, 143919922, 2013-05-29T08:01:17Z
15e8DvWq5Muoi2hVtVZEa3jfxPQwm33wtV, u, 6, 0, 1, 8983, 100000, 2013-05-23T11:29:07Z
15ZyVdr5Yy8u2XRy6fyKZQAE9mV7RSPc4t, u, 17, 0, 1, 27279, 10000, 2013-11-05T20:37:58Z
15Y85aNAKdnzDjeoJwz74EgkUB2uotKevC, u, 6, 0, 1, 22116, 20108, 2014-08-17T14:03:32Z
15SoCUFq2YNv1ANNUuKMvF3FDqS9MCtVQb, c, 25, 76001, NA, NA, 76001, 2015-04-25T16:23:53Z
15Rkqg61KPAc4SNtbFj1KcoP8A7a1oYHrm, u, 18, 0, 1, 4, 1000000, 2013-06-18T07:06:20Z
15R1x4kuv8Lm5e4FqTtZg42WS11LXKpC8G, c, 53, 0, 1, 37545, 168000, 2015-08-28T06:40:39Z
15PCRJPG7QZbJzDriD5dC2EV3h6uB8Rd5x, u, 9, 0, 2, 18555, 209900, 2015-07-20T15:48:22Z
15Mjbr23k7LfadNVAMmFZwdzcL5VFHe9gC, u, 203, 100000, NA, NA, 100000, 2014-10-26T17:26:48Z
15MCCoqST2cFt3pt8kk7ikdFDPEvy1Dbwd, u, 11, 0, 2, 50848, 50000, 2015-07-23T18:44:35Z
15GXPwpngTY2dfZ3rq8YWAKaK7D4Q4RFJA, c, 17, 5716, NA, NA, 5716, 2015-05-09T18:41:46Z
15EyvxFfdSbuduV7TAvQWdZnTDJqf1BK1g, u, 16, 0, 1, 76902, 1000000, 2013-06-30T02:18:09Z
15ChK8e8GJ5DMpoeztAJ7DpQaa3qZAMjFj, u, 13, 0, 1, 84439, 390000, 2016-05-12T06:25:37Z
159NABN9T8WvJKuVMsnpz3SjjUx4Ju1DhB, u, 11, 0, 1, 15787, 2028498, 2015-07-23T19:22:30Z
157TgvQX8EoBdzccCC6AjpyhwT8zsw3KUa, u, 10, 0, 1, 9486, 10000000, 2015-07-21T20:00:37Z
156DqxZ1Sf2fbLd8zJgQT43mkaUacYfhME, u, 22, 0, 1, 85384, 100500000, 2013-10-28T15:19:29Z
151DirSo3K8UxoLGjJ2sxizkracPGq1hR8, u, 8, 0, 1, 80131, 20000, 2014-02-18T09:26:15Z
14w5PPktCgmD7c6Wc2AD2JrwTJPrnHymYC, c, 5, 0, 1, 10410, 9000, 2016-07-23T17:23:11Z
14tYNq3skctPPmcQYNEmmhMZcDD876ajgh, u, 9, 0, 1, 702, 1000000, 2012-09-23T00:14:42Z
14sC6HfKKwH9xdujLRKmLxEqVKMAFTkUVM, u, 10, 0, 1, 86230, 9590000, 2015-07-21T23:56:18Z
14rLUSER9ErRBWTSaeeN16EChEaoqoPB28, u, 8, 0, 1, 54055, 2762165, 2016-06-09T08:07:13Z
14jmx7rFXXKtGgizj1q8sWnQ3FHxMT41RQ, u, 36, 0, 1, 66114, 100000, 2013-11-20T06:01:46Z
14ePyt55vNZVNhzFP668VZ1AN7VMnAHZCY, c, 7, 0, 1, 84353, 12551, 2016-12-30T23:00:38Z
14auAibJ1MMsnH85PvBMywxeUMT3WhAgtm, u, 10, 0, 1, 2844, 10000000, 2015-07-22T00:50:40Z
14ap2o8YtUeQG2qJ7Ji1kef7UKvm7m4eXg, u, 7, 0, 3, 5, 9000000, 2015-01-06T09:14:57Z
14aSMXFapoRkNfspRJNbTttA4TXb5zMX7D, u, 13, 0, 1, 85254, 400000, 2016-05-12T06:12:02Z
14TGsQeEkfGkgVpUDf5CsRLiEA43gpFAFb, u, 12, 0, 1, 82, 400000, 2016-05-12T06:01:00Z
14PRsVTf4Lv2GqfKwXMvR79sobQsZPVpd2, u, 43, 0, 1, 69884, 100000, 2014-04-07T13:49:40Z
14J59ebyE8x7DymETy9xSsrq5uyGsEGXb1, u, 13, 0, 1, 84664, 390000, 2016-05-12T06:21:52Z
14Hmj3RyQvMgRmDML17o8ZGHNRhR4qcr1q, u, 54, 0, 2, 59119, 2000, 2013-05-31T10:26:53Z
14C2UFWr6VtEHAcvEsJXw812npHggRZ3mC, u, 75, 0, 1, 2358, 30000, 2016-02-01T02:40:06Z
14BwAbCRHJ7xbvG7GQFuxPgErJw6zXQdxQ, u, 35, 0, 1, 0, 100000, 2015-03-28T22:31:53Z
149hCA7bdagX7A4mz2TipRWzEUcBYPZjNy, u, 50, 0, 1, 82953, 10000, 2013-11-19T17:15:56Z
149LB8VYaT1BdMLyQUL92Kj6KrJfNwcp64, u, 44, 0, 1, 77513, 10000, 2014-10-26T12:33:41Z
148PPUzqJqyjfb4sPidDnskPNtef7975aS, u, 10, 0, 1, 3902, 150000, 2012-05-17T13:55:17Z
148Ffmeu45NAdAVi7eGMwNXZXgLEVdvPHp, u, 8, 0, 1, 56140, 20108, 2014-08-17T14:03:00Z
1471sK8xNsCGSwBNAKAZKsUGnWxe6h61xV, u, 8, 0, 1, 78217, 20108, 2014-08-17T14:00:48Z
1441SynW4zJidgZA4JFZcgrpCU7Q7zoxpg, u, 5, 0, 1, 43638, 40000, 2016-07-21T00:06:47Z
1439zNkGLaNgswcxSFHxgjh6BJaMABqRCR, u, 22, 0, 2, 59368, 2020000, 2014-08-29T21:19:25Z
13xPEC3Q3GV1oswpvBdANmrpd5PbCGkA5t, u, 10, 0, 1, 5768, 10000000, 2015-07-21T22:22:32Z
13wdJwL1KVH7v1M3PLiHxdTi5qm3nMJjsz, u, 10, 0, 1, 6300, 10000000, 2015-07-22T00:50:40Z
13wTfYbLceXJp3re57LFmrenpvW7NLUX7K, u, 16, 0, 1, 9252, 4590, 2013-12-03T10:08:44Z
13vcob8E5mY3ycx6RfkFcRXUsHQtA1HzVX, u, 10, 0, 1, 3906, 984028, 2015-07-21T12:08:34Z
13tPZJYMWNwGm5cjpfS4QFZioFRvF6V8Sx, u, 13, 0, 1, 84331, 390000, 2016-05-12T06:27:25Z
13t4HUqjDsRAt1TSFyWhWtwLdZ8gDzhzPm, u, 10, 0, 1, 36296, 90000, 2015-07-21T21:49:47Z
13s4cPCYNL5mhwmfvhjvqXEsET1qxfKusi, u, 11, 0, 1, 18790, 20108, 2014-08-17T14:00:48Z
13pNwRUYB4f5pYdFdcXHftanK9xQb1eVLv, u, 7, 0, 1, 55912, 30000, 2014-12-26T21:00:14Z
13m5miwRTq6rYY3MKXxfxSakhY1dqB7yjz, u, 10, 0, 1, 12707, 10000000, 2015-07-21T20:00:37Z
13k7je8NJeUTnvYFeSxizG47b6KdwygBqP, u, 8, 0, 1, 58861, 15103, 2015-03-01T23:58:27Z
13gVFsY4sLAkgWjrR97NVhexhpYnEN7drQ, u, 96, 0, 1, 70873, 200000, 2013-10-13T02:05:28Z
13cKHMgLphDNRaU5oWs4wVWAzwGjNvTd46, u, 10, 0, 1, 56427, 38000, 2016-03-14T08:38:39Z
13bjohhEbDnZhpsDQxEiyWdWzJrqA15xNo, u, 10, 0, 1, 23354, 290000, 2015-07-21T23:38:18Z
13bZsZvApmKEnb1hJvSJ7yWacQxcikLXt5, u, 13, 0, 1, 84221, 390000, 2016-05-12T06:29:15Z
13a27PEgkh9r7H3TH6wqStzXEUtjv2yqQj, u, 10, 0, 1, 4843, 10000000, 2015-07-21T22:22:32Z
13XfQDb4oj23m7cJvEpMQzgjuwZwPkoV7W, u, 13, 0, 1, 84552, 390000, 2016-05-12T06:23:44Z
13XURhK5UzvhiLrtjdK3K3BexZn4FzQsHi, u, 17, 0, 2, 38813, 118100, 2015-09-20T11:19:01Z
13WWUy2ew3qhnNWR7ofwbrsqULtJwKDz3A, u, 11, 0, 1, 4514, 100000, 2013-03-23T18:07:46Z
13WUd9Z2cLu2icTbhGFogG4jMMXSUC9vEg, u, 7, 0, 1, 3828, 5000, 2015-07-29T15:48:13Z
13UUr4e5mEVDtkbugYB95Fe6qxMfDA9HQP, u, 6, 0, 1, 15516, 20108, 2014-08-17T14:00:48Z
13U9QWyWzXc9kFtPoTZ2nH4wbULj91ayVZ, u, 5, 0, 1, 44443, 20108, 2014-08-17T14:00:48Z
13SgjrqH4XUdKjwvwjjM1kCcXzsxnB5odx, u, 12, 0, 1, 9252, 4590, 2013-12-03T10:08:44Z
13QrE2XtF14gjD1MKezMPqx24nG1cAXSJn, u, 10, 0, 1, 4749, 10000000, 2015-07-22T00:50:40Z
13QjjdCrA6D82hMj7spuwZQzyAqL5DScxj, u, 60, 0, 1, 66327, 1500000, 2013-10-31T21:02:15Z
13JKKPtSS1jHKXroh1sx3kdSpuoJ5sW5PX, c, 11, 0, 1, 4483, 373000, 2015-08-28T06:40:39Z
13HtT7aXmN3RdzFnJVsAesxVH7pLE1q9P4, u, 19, 0, 1, 0, 100000, 2014-12-06T21:23:53Z
13HVUWdzTuXBPFKaymyF7q4HygL37zkH46, u, 40, 0, 1, 1818, 100000, 2013-01-19T15:16:05Z
13EXDbWczwLzfjEbjjByyUX4onVVkxs4Hn, u, 10, 0, 1, 47119, 1390000, 2015-07-21T20:42:03Z
13ApwiSfVuGnoaDJvXDpHNXupeeLp1ZyrD, u, 13, 0, 1, 0, 400000, 2016-05-12T06:10:13Z
139ht4Zm8rq2CEja2BiA9Mm6yKdP9e33gL, u, 8, 0, 1, 50483, 100000, 2013-07-29T23:30:02Z
139Z7CcL1XbgX818bVtvL3BYL7yi7tHxuo, u, 38, 0, 8, 4647, 19829524981, 2012-01-19T15:12:27Z
139GhXYQbEJf5HYCuWhnDWGciAT5Y16iq8, u, 13, 0, 1, 84918, 380000, 2016-05-12T06:17:38Z
136xSWCKghMBzMuidPcGTm7YLMErPJteyd, u, 13, 0, 1, 85254, 400000, 2016-05-12T06:12:02Z
134GFppLFEwypouKFRDAGCP9YfGPAT99iP, u, 52, 0, 1, 569, 1000000, 2015-10-12T09:38:52Z
12xULr4rQqgwR3KUjQFx7wWzXz9Yx9Q8Bv, u, 13, 0, 1, 84779, 390000, 2016-05-12T06:19:57Z
12xQEQSGdEECXbwv9AHwzfLxVgE9cifGvt, u, 9, 0, 2, 75174, 215000, 2015-07-20T12:15:41Z
12vAC7Wsrhgt248MifRbPBxeLZKDDy6vBc, u, 64, 0, 1, 85721, 500000, 2016-07-26T22:38:35Z
12tw77jR3XcRusMuwHAAKUmwGUoKoWtAHT, u, 327, 0, 1, 72224, 10000000, 2011-08-14T14:37:39Z
12tW78HjKo14dwzPB2zKqaaBfd7KDotcFB, u, 26, 0, 2, 794, 110000, 2012-07-14T21:08:44Z
12rNUwY6WhEJz5FQP9AnbRAWkP2fufvQhP, u, 8, 0, 2, 23097, 140000, 2012-12-26T17:30:18Z
12p3HUmci9rgULGtNaa6gzqGPyMKJAyuHS, u, 10, 0, 1, 37438, 90000, 2015-07-21T21:20:33Z
12mbQ3zcUk1fByxa4r21PEh1TY1cagXLEe, u, 21, 0, 1, 128, 114955, 2013-12-11T23:32:15Z
12k7reC2HFZC8aEAVtHwrcKAjGvme4WUaA, u, 14, 0, 1, 38065, 10000, 2013-11-09T11:43:00Z
12jabAZxhpwBhoJrSCnfX7kZ9FSzE4Z3CM, u, 13, 0, 1, 0, 380000, 2016-05-12T06:13:53Z
12hH9T9ibbUcH3tqG7PQkcL9z8pSbiTyke, u, 86, 0, 1, 37892, 11000, 2016-05-25T03:29:53Z
12g7Be8HaZCy5JzViwp3WwGFxSVoykewPf, u, 7, 0, 1, 57959, 10, 2013-09-13T19:47:52Z
12f7UrMnvwEL2LCWjuxTmMjs7epQ4GJ8x2, u, 9, 0, 1, 2944, 200000, 2015-07-20T15:48:22Z
12dCWAQJSo82qtLS7vqqTvSd7UU959iDdD, u, 165, 0, 1, 71143, 200000, 2013-10-13T02:21:45Z
12c1ARbGEruvs3KNN5Lii2iA26TfLKb4CW, u, 8, 0, 1, 65529, 20108, 2014-08-17T14:00:35Z
12bUF9JjvHRhDeBLzbvxdW33BGu9YtKDcv, u, 11, 0, 1, 68971, 9990000, 2015-07-23T04:37:18Z
12b6kcUTicMCUyA7VZexk49NqbV7N2ZifH, u, 6, 0, 1, 3, 251930, 2013-09-15T08:27:32Z
12ZLS7PqYAzXNWqzsepyXhNJ32iwBupcz3, u, 8, 0, 1, 248, 30000, 2017-01-15T10:40:09Z
12VtW1Zgd7s8p7SkLHv2S6smuyDoeMcoDN, u, 28, 0, 2, 44850, 20000000, 2015-07-08T20:27:32Z
12U1nzGxzUSZNSHj2qFQ5mQNmN7xMp96nm, u, 9, 0, 1, 55666, 40000, 2015-12-20T15:53:54Z
12FbeY2Uf4PJ4x3vx2AX6gfh3Y6pPYAkmW, u, 91, 0, 1, 71158, 200000, 2013-10-13T02:20:40Z
12D9r9cbxCNG1h7kZPUg18A5hM64ZWNyKi, u, 10, 0, 1, 22573, 290000, 2015-07-21T23:51:19Z
12C5rBJ7Ev3YGBCbJPY6C8nkGhkUTNqfW9, u, 22, 0, 17, 0, 218396219, 2015-05-20T15:01:20Z
12BcJ2oPHFzEx3HtX7ZP6rzZcoDgVhAd1s, u, 15, 0, 1, 0, 4000000, 2015-01-26T16:38:24Z
127j9xit1t8w7PnANwCGiT2fcLCHn3yhSR, u, 10, 0, 1, 5362, 974028, 2015-07-21T13:13:40Z
127Ud68NCmnf61Z7ZLHkzqiBtKFGxdvi5t, u, 12, 0, 1, 86369, 1000000, 2013-08-30T06:53:26Z
122FNS8CK4tsqkzQXmz74kfQ5AaZCb96bC, u, 10, 0, 1, 74985, 20108, 2014-08-17T14:00:35Z
11BWwo7k9MQafugaEHTzkPZFmTvjSAPvq, c, 9, 0, 1, 170, 28393, 2015-03-29T16:00:01Z


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: LoyceV on August 09, 2023, 06:47:18 AM
So, I was wondering if there is anyone that cracked all or most of the remaining 611 addresses (list below).
Probably. But they have no incentive to share the private keys, they're just quietly waiting for a deposit to be the first one to snatch it.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on August 09, 2023, 08:15:57 AM
Probably. But they have no incentive to share the private keys, they're just quietly waiting for a deposit to be the first one to snatch it.
If revealing private keys is too much to ask for, revealing just cracked addresses would be great :)


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on August 09, 2023, 08:24:30 AM
Hi,

As been discussed many times before using a Brainwallet is a bad idea. I ran some test myself and found 18.509 BTC-addresses based on a brainwallet which also has been used in the blockchain before.

I tried to compare my results with the results of other researchers but could not find any lists online at all. I found some examples but not a comprehensive list. So I published my own results over here: https://eli5.eu/brainwallet

Please note: all published addresses have a balance of 0 so this is not a list for robbers :). There are also a lot of extra datasets I haven't used this far so I expect the numbers to go up once I use them as well (I'm in the middle of perfecting my own tooling and blockchain parser so this will take some more time first).

I love to get some feedback and if you have results to share which I missed in this round I'm more than happy to hear from you and include them.

TA
I wonder if OP has new content to update his website? :)

or maybe almightyruler?
This brain wallet hasn't been used for several years, but even back in 2013 it held a substantial amount of funds (USD $6k+), protected by a weak passphrase:

https://www.blockchain.com/btc/address/16jLdtAxgXVwcG93MyPcNALXMCv3D6dyDB

The passphrase is "arretonprimaryschool"


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ymgve2 on August 12, 2023, 02:14:03 PM
Here's the majority of your remaining list. Still got 77 missing. To make it more interesting I've masked the first 3 characters of each password:

https://zerobin.net/?25d328abfbe6601d#xmClTcLN8qitoLRO5862qS9Q1fB3NfOrNGU+z9Z+Dj4=

I also see you don't have 145Sph2eiNGp5WVAkdJKg9Z2PMhTGSS9iT on your remaining list. Did someone ever find out what the private key was? I know it's been used as a brainwallet string, maybe you did a mistake and filtered it out because of that.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on August 12, 2023, 10:07:46 PM
Here's the majority of your remaining list. Still got 77 missing. To make it more interesting I've masked the first 3 characters of each password:

https://zerobin.net/?25d328abfbe6601d#xmClTcLN8qitoLRO5862qS9Q1fB3NfOrNGU+z9Z+Dj4=

I also see you don't have 145Sph2eiNGp5WVAkdJKg9Z2PMhTGSS9iT on your remaining list. Did someone ever find out what the private key was? I know it's been used as a brainwallet string, maybe you did a mistake and filtered it out because of that.
Thanks a million! This is useful!

P.S. brainwallet for 145Sph2eiNGp5WVAkdJKg9Z2PMhTGSS9iT is "XXXX was here."


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: PlutonowyPokrzycz on August 13, 2023, 11:08:00 AM
If someone could share 139 characters long passphrase to 1BQmbdHdtdJnGbhNLgnr5w5pKJ4aFghdLp...
https://i.kym-cdn.com/entries/icons/original/000/011/976/That_Would_Be_Great_meme.jpg
Vasek and team have found it on Reddit


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: Sanka555 on November 07, 2023, 05:25:08 AM
So far I've seen only those online lists of brainwallets. I wonder if there are others available?
  • http://eli5.eu/brainwallet/
  • https://privatekeys.pw/brainwallet/bitcoin/1
  • https://privatekeyfinder.io/brainwallet/bitcoin/

Most of you probably know this science paper "The Bitcoin Brain Drain: Examining the Use and Abuse of Bitcoin Brain Wallets" (Marie Vasek, Joseph Bonneau, R. Castellucci, C. Keith, T. Moore). It is available from this link: https://tylermoore.utulsa.edu/fc16.pdf

Authors do not reveal brainwallets in clear text. However, I've found this resource that contains files that are attachments to this paper: https://dataverse.harvard.edu/dataset.xhtml;jsessionid=3b3325c3157850e2d961cf61dfb1?persistentId=doi%3A10.7910%2FDVN%2FRZHL3X&version=&q=&fileTypeGroupFacet=&fileAccess=Public&fileSortField=type

The most interesting files are probably: brainmaster.tab and attacksrc.tab files. They contain a list of more than 19k addresses identified to be protected with a brainwallet (again, no brainwallets in clear text, just information about the length of string). There are still many addresses in Vasek's list that you will not find on the websites mentioned in the beginning.
Some people that participated in this topic have their own lists of brainwallets. I wonder if there is anyone who cracked all addresses from Vasek's list? Probably not. Then, how many of them remain a mystery to you, still?

Are there other lists like this from Vasek? I mean, just addresses without brainwallets revealed?
Has anyone parsed the list of brain phrases from these lists?  maybe just a text file?  so that I don’t have to do stupid work a second time.  I just need a list of words-address. Without xxx.   thank you very much in advance


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: ymgve2 on February 14, 2024, 04:43:13 PM
I noticed a while back that a lot of the brainwallets in the collection were filled with exactly 20108 satoshis, with phrases ranging from single words to some random seeming passwords. The repeated amount seemed weird, and I then discovered that someone back in 2014 had filled 456 addresses with exactly 20108 satoshis each.

I suspect this is some form of challenge/canary where each address is a different brainwallet, with varying levels of complexity in the phrase. Here are the transactions I've found so far:

https://www.blockchain.com/explorer/transactions/btc/16df5eed4c8d7ff965cf9d3676c7b71d80398714727792e71b7118abe3e16b03
https://www.blockchain.com/explorer/transactions/btc/b17d08f6b945a6a9edb526f2faaef9b825eaa27c14f454bd53bb423e44750e16
https://www.blockchain.com/explorer/transactions/btc/70ff6fc9ef96c80a435a0595477708630d092285ebeca30aa899d4dd409b1b45
https://www.blockchain.com/explorer/transactions/btc/16e72e11bfefe3222e5a3876d1038e49aaec8bc7c247212f8917c94e5b6fff49
https://www.blockchain.com/explorer/transactions/btc/594a3757b99943d4789fc588167cb40fd44e57f131f3822a3c9af2930ee01f52
https://www.blockchain.com/explorer/transactions/btc/4b07f21a2d9c408af5542288554aec49ac49195cf10295f1b17aa829d701a3dc
https://www.blockchain.com/explorer/transactions/btc/b71a1a9dc95319eae181d64865b16bf34deabdee0a689176df8aba450df34081
https://www.blockchain.com/explorer/transactions/btc/280933eae25e17a7a7274c4b672880b7c488c929872394dbc6ccacf9f68fc7c3
https://www.blockchain.com/explorer/transactions/btc/34b56d4dac1d43c8a7b8f922e044424094670445b1388fb89b79a0b607a2a28f
https://www.blockchain.com/explorer/transactions/btc/151f1b9dc77e7dfd77e2f23790d5dc6f8026602553fe64ff2ec4d641e644f9a8
https://www.blockchain.com/explorer/transactions/btc/c03fa7f40dc185e29b64c4ae421544364d9600fc1e960b1e0406b5fc1efc1843
https://www.blockchain.com/explorer/transactions/btc/78b5acfa93abd3d6761806dbcc88a82d9efc070bc798edf9cf70d75a8803351c
https://www.blockchain.com/explorer/transactions/btc/06f34556aa9fa495ae31fbb8134a66997f2a9672261a0d20c39d6eaa99ae323c
https://www.blockchain.com/explorer/transactions/btc/ccfd4b7ac82ef4dd944ab6174c77cef4cd80f12c3333443dbfd30133b9e4849f
https://www.blockchain.com/explorer/transactions/btc/39142cb1fce6109333c8672b00fa53cf1d75f4d5b23aac6204aae868df56bd65
https://www.blockchain.com/explorer/transactions/btc/5160e527cca3d98bcea61b70519d4d434df9e7da8f7bef62c114ce369747ab58

Now, to the real reson for the post - I just noticed that after almost a year of no activity, someone has started draining a few of these addresses again. I wonder if this means some more optimized brainwallet cracker has been developed, or someone has built a cracking machine that's much faster than previous attempts. The curious thing is that the drained coins go to both standard and segwit addresses, so it might indicate there are multiple people working on this cracking.

And as always, if you use a standard SHA256 brainwallet, this is another indication that your coins will be taken sooner or later.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: whanau on February 16, 2024, 03:08:00 AM


Now, to the real reson for the post - I just noticed that after almost a year of no activity, someone has started draining a few of these addresses again. I wonder if this means some more optimized brainwallet cracker has been developed, or someone has built a cracking machine that's much faster than previous attempts.

There was a brainflayer3 program which was supposed to have been much quicker. However it seems to have disappeared from github.

I wasn't able to compile it as there were 3 or 4 differences in the make file. I fixed 3, but the last one defeated me.
If you want the code, I will send it to you.


Title: Re: Collection of 18.509 found and used Brainwallets
Post by: TheArchaeologist on March 14, 2024, 10:21:48 AM
Based on some questions I got above or in DM:

There is a plaint text file that lists all the addresses as mentioned on eli5.eu/brainwallet: https://eli5.eu/brainwallet/btc_brainwallet_v18569.txt (https://eli5.eu/brainwallet/btc_brainwallet_v18569.txt). Only addresses.

TA