Topic: Large Bitcoin Collider (Collision Finders Pool) - page 59. (Read 193404 times)

Your README makes no indication of source being available, and I didn't want to download the whole archive to look.

I'm not aware of the person who did the 2^50 search having published any results, I've just inferred it was done. I've got a blog post about that in progress to be posted soon.

My code's up at https://rya.nc/brainflayer, and I think you could use it as-is with a wrapper script. It includes the ability to do search existing addresses for matches. I think I get around 550k/sec on my i7-2600 running on all cores. I always simply include all addresses seen on the blockchain regardless of whether they've got a balance.

A friend and I did a talk at a conference last month which briefly mentions sequential search: https://vimeo.com/177318833.

Vanitygen uses some techniques to generate addresses without computing individual private keys, and is similar to a randomly ordered search. I could probably hack something together that does that style of search against a large list of addresses, though I think it would be a waste of energy to run that.

• Link to previous search project?
• How about reading the README.txt?
• How about contributing your code (and to kill two birds with one stone? ... well 3 actually)

@Jude Austin: congrats.
https://blockchain.info/address/1TinnSyfYkFG8KC3gZ72KpYxBXsxSadD8
Another bounty will be planted.

Rico

FYI, someone already did a search of the addresses of the first 2^50 private keys.

Do you have source code for your tool? Some people don't like running random binaries, and I've already released code that's a lot faster than the speeds you're reporting for doing sequential address searching.

I found the Bounty.

Given the amount of crap you have unloaded so far to the general public (nothing worthy of general public's attention), I think you'll hear it 1st in the news than from me.

Rico

Well, let us know when you find something worthy of general public's attention. Or, rather, let me be the first to know so that I could safely and timely get rid of my Bitcoin stash (however small it might be) before the markets implode on hearing the news...

Or even try to short some coins

Because a Bounty is supposed to be found? Especially if it has been placed/planted intentionally in the pools vicinity?

Next Bounty: https://blockchain.info/address/1TinnSyfYkFG8KC3gZ72KpYxBXsxSadD8


Rico

Why didn't the Bitcoin price crash already?

So far so good.


Which owner? The original owner or the new owner? Transfer where? A new address is needed to transfer.


What period would you see as sufficient to wait? 1 year? More? Less?


Rico



PS: The LBC Pool found it's 1st bounty.

Yes interest, and  if you need i first beta tester

I had the same idea.

I've been searching for a collision for years using a custom address generator that checks against my Insight server.

I had a similar idea for a pool but a little nicer:

Everyone connected searches for a collision.

If a collision is found the private key is sent from the miner to the server encrypted.

Then on the front page of the pool announce the finding, transfer the funds with a message to the owner.

If the owner signs a message with the address their funds are refunded, if not, distributed to the miners.

This way nobody just steals peoples coins if a collision occurs.

I could make a "pool" and "miner" for this but I didn't think people would be interested.

Since when are Hero Members incapable of browsing blockchain.info?

Rico

How great is your "small bounty" actually?

"There is also a small bounty to be found within the next few blocks: 1AKKm1J8hZ9HjNqjknSCAfkLR4GgvCAPjq and when that is found, there will be another one. ;-)"

Should be doable within 24h.

If someone would like to join for the fun of it, I will take my machines down to not hit it accidentally myself. ;-)


Rico

How will windows.exe I would like him to test   

I can try, but have not much experience with Windows. So I would need some really die-hard beta tester for this.

I managed to build a windows version of the Go generate program, and will try to build a standalone Perl App with fatpacker (http://search.cpan.org/~mstrout/App-FatPacker-0.009001/bin/fatpack)

I'll be on vacation soon so I will have some time to meditate on this. 

If anyone feels like testing my trial-and-error of a windows client by the end of the month (or so), feel free to PM me.


Rico

Do you plan to release a client for windows downloads?

Let's cut the crap even more. The project just went into open beta. Let's give it some time for evolution and talk about observations/results then.

Rico

Let's cut the crap. If no one specifically searches for collisions, the actual chances to find one are zero. I guess this can hardly be a point of argument. If someone does, nevertheless, search for these, the chances are what they are, and they could be infinitesimally small (they are not), but they are still some positive number greater than zero (the first case)...

So that's what we have when the dust settles and the sun shines in

I thought about that in similar ways, but ultimately came to a different conclusion.

The project is actually destined to find some private keys from time to time. (see https://blockchain.info/address/1AKKm1J8hZ9HjNqjknSCAfkLR4GgvCAPjq), but for now all these are placed like breadcrumbs in the search space "before" the pool, so some of the clients will inevitably hit these bounties.

Actually there is no way at the moment the pool wouldn't find the private keys to these breadcrumbs.

As for finding private keys that were not placed intentionally in the pools vicinity: I don't dare to make a guess right now. But I think I came to a different conclusion about the depressive effect on Bitcoin price by the mere existence/operation of this project:

It may be shocking for some/many at 1st glance, but I believe that the longer the pool finds nothing (except the placed bounties), the more positive the effect of the pools existence/operation actually might be. I intend to pursue the project in earnest, so whether there may or may not be some clandestine equivalent, I will certainly do my very best to make sure this open project is at least as effective as some hypothetical clandestine endeavor might be.

The results from this project - well communicated - allow the Bitcoin community to actually have a better shot at risk assessment of this threat vector. Right now, the math says the danger is negligible. Should there at some point be evidence or indication of the contrary, then it's still better to have a project like this for analysis/experimentation of this concrete attack vector.


Rico