Large Bitcoin Collider (Collision Finders Pool) - page 50.

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

After giving it some more thought, I would like to revisit this:

Quote from: ryanc on October 12, 2016, 10:06:34 AM

Well, this result demonstrates that only the outputs of that puzzle transaction were searched by whoever did that, which only mildly surprises me.

The alleged mode of search of whoever did the search for the PKs in the puzzle transaction was discussed
in https://bitcointalksearch.org/topic/m.16348760 ff.
between you and donGeilo

We have found #45 (https://bitcointalksearch.org/topic/m.16430637), but have not yet found #46 (https://blockchain.info/address/1F3JRMWudBaj48EhwcHDdpeuy2jwACNxjP).

The fact, that we have found 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg in-between, which a) pre-dates the puzzle transaction, b) seems to be there before (in terms of key value) 1F3JRMWudBaj48EhwcHDdpeuy2jwACNxjP indicates, that whoever searched for the puzzle funds, did not perform a search such as both you and donGeilo assumed. Which - honestly - should take the mildness from your surprise.

Only explanation I have (which is consistent with the observations so far) , would be that the searches were performed backwards (i.e. for #46 starting at bit47, then decrementing PK values) and rest of the search space is skipped when puzzle transaction is found (starting again at bit48 for search of #47). IMHO this is the only way how 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg could have remained unseen in that search.

Alternative explanation could be that 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg was seen, but not bothered to touch. Not sure how probable that is.

Rico

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: Jude Austin on September 08, 2016, 06:27:20 PM

Maybe I am being super duper optimistic but on the Statistics page of your website there should be a column for "Collisions" next to "Blocks done" for the client ID.

"Super duper optimism" is relative. What ~2981793 seconds ago sounded "super duper", may today seem common.

http://lbc.cryptoguru.org:5000/trophies

Rico

ginky

newbie

Activity: 44

Merit: 0

Quote from: rico666 on October 12, 2016, 12:35:20 PM

I will be updating the LBC manual, so make sure you have a look from time to time.

Quote from: ginky on October 12, 2016, 11:43:47 AM

Intel i5 4690 @ 3.5 - 441 799 keys/s per CPU core

duly noted

Quote

WSL Win10

Good to see, that the VM solution under Windows has superb performance. I do not feel great pressure to push a native Win-version right now and will probably focus more on a GPU client.

Rico

Change "gen-hrdcore-avx2-linux64" to "gen-hrdcore-sse42-linux64".
Agree with you about gpu client

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

I will be updating the LBC manual, so make sure you have a look from time to time.

Quote from: ginky on October 12, 2016, 11:43:47 AM

Intel i5 4690 @ 3.5 - 441 799 keys/s per CPU core

duly noted

Quote

WSL Win10

Good to see, that the VM solution under Windows has superb performance. I do not feel great pressure to push a native Win-version right now and will probably focus more on a GPU client.

Rico

ryanc

member

Activity: 105

Merit: 59

Quote from: rico666 on October 12, 2016, 10:19:00 AM

Quote from: ryanc on October 12, 2016, 10:06:34 AM

If someone posts in this thread a different private key that also works out to 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg, I'll pay them 5BTC.

Now that's an incentive. I wonder if there would be a better place to announce that than here.
As nrg1zer wrote here: https://bitcointalksearch.org/topic/m.16523769
even if the owner of 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg sees (and cares about) that drain, how should he know where to look?

Rico

Actually, let's make that 5BTC or $3000 worth of BTC based on CoinDesk's bitcoin price index at the time of claim, whichever is more. I'm sure otherwise, someone will claim I'm assuming that me having to pay would crash the price.

If blockchain.info still has the feature that allows a "public message" to be added to a transaction, that would be a good option for signaling. A message could also be encoded in a series of vanity addresses.

For the fellow who figured "how much wood could a woodchuck chuck if a woodchuck could chuck wood" would make for a good brainwallet password, I was able to track him down via his transactions, but luck was a major factor in my ability to do that.

This problem was actually discussed somewhat by a fellow who went by "btcrobinhood" on reddit, see here: https://github.com/btcrobinhood/bips/blob/master/bip-1337.mediawiki (note that I have no opinion on that proposal at this time).

ginky

newbie

Activity: 44

Merit: 0

@rico

That works Wink

Intel i5 4690 @ 3.5 - 441 799 keys/s per CPU core

WSL Win10 Grin

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Second guess would be you have no internet connection, or port 20/21 (FTP) is filtered.
Other than that, I have no idea.

You can beat it manually to do your bidding. Also known as "Clubbed to death" method:

Download

ftp://ftp.cryptoguru.org/LBC/generators/161008-1d02144cdfbf81767255c040e0b7861c.gen-hrdcore-sse42-linux64.bz2

bunzip2, rename to gen-hrdcore-sse42-linux64

download

ftp://ftp.cryptoguru.org/LBC/blf/161011-4a9d2c4412e667d864bbfdfa5927bc79.blf.bz2

bunzip2, rename to funds_h160.blf

Try again.

Hope, that helps..

Rico

ginky

newbie

Activity: 44

Merit: 0

Quote from: rico666 on October 12, 2016, 10:45:51 AM

ls -al would have been more enlightening, but my guess is:

LBC directory belongs to root, you are user "ginky", therefore have no write permission in LBC, therefore no generator and no blf file can be downloaded.

Rico

The LBC folder have drwxrwxrwx permissions. LBC script same

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: ginky on October 12, 2016, 10:28:17 AM

@rico

ls -al would have been more enlightening, but my guess is:

LBC directory belongs to root, you are user "ginky", therefore have no write permission in LBC, therefore no generator and no blf file can be downloaded.

Rico

ginky

newbie

Activity: 44

Merit: 0

@rico

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: ryanc on October 12, 2016, 10:06:34 AM

Well, this result demonstrates that only the outputs of that puzzle transaction were searched by whoever did that, which only mildly surprises me.

I agree with the surprise-level. As I wrote further above in the thread (soemewhere discussing the days until the #51 puzzle) I already suspected this, which is why I kept the pool forefront where it is.

Quote

If someone posts in this thread a different private key that also works out to 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg, I'll pay them 5BTC.

Now that's an incentive. I wonder if there would be a better place to announce that than here.
As nrg1zer wrote here: https://bitcointalksearch.org/topic/m.16523769
even if the owner of 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg sees (and cares about) that drain, how should he know where to look?

Rico

ginky

newbie

Activity: 44

Merit: 0

Quote from: rico666 on October 12, 2016, 10:09:31 AM

Quote from: ginky on October 12, 2016, 09:49:13 AM

'gen-hrdcore-sse42-linux64' not found/executable.

Hmm...

Is it executable? (chmod a+x gen-hrdcore-sse42-linux64)
If you are running LBC as a different user - do the files belong to that user?

If all of this is ok, try a

export PATH=$PATH:.

then start LBC. If that works, there is a ./ missing somewhere.

Rico

The client folder is empty, only LBC script here.

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: ginky on October 12, 2016, 09:49:13 AM

'gen-hrdcore-sse42-linux64' not found/executable.

Hmm...

Is it executable? (chmod a+x gen-hrdcore-sse42-linux64)
If you are running LBC as a different user - do the files belong to that user?

If all of this is ok, try a

export PATH=$PATH:.

then start LBC. If that works, there is a ./ missing somewhere.

Rico

ryanc

member

Activity: 105

Merit: 59

Quote from: rico666 on October 12, 2016, 12:44:52 AM

Quote from: ryanc on October 11, 2016, 10:13:49 PM

It is far more plausible that this was a "challenge" someone made, to see how long it would take to be solved

Ryan... I take that statement and put it on my stack, where it remains together with your statement, that the 1st 50bits have been searched already.
Both statements will have the same weight on my stack for the time being.

Rico

Well, this result demonstrates that only the outputs of that puzzle transaction were searched by whoever did that, which only mildly surprises me.

If someone posts in this thread a different private key that also works out to 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg, I'll pay them 5BTC.

The explanation is either a deliberately weak key or bad generation code, and I'm saying that deliberately weak seems more likely because I can't come up with a good explanation of how bad generation code would result in that particular key.

ginky

newbie

Activity: 44

Merit: 0

./LBC -x

Will use 2 CPUs.
Best generator chosen: gen-hrdcore-sse42-linux64
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... 'gen-hrdcore-sse42-linux64' not found/executable.

./LBC -u

Finished update run - system up to date.

What is the problem?

becoin

legendary

Activity: 3431

Merit: 1233

Quote from: rico666 on October 12, 2016, 08:18:53 AM

@becoin: *plonk* - I'm really too busy now and cannot put additional effort in your education on top of all that. Sorry.

It's okay. Never mind.
You're so obsessed in finding a collision that I have to ask out of curiosity. Which one is true - you've already sold out all your bitcoins or you never had one?

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: shifty252 on October 12, 2016, 08:25:11 AM

@rico

Just updated LBC and got this message
./LBC -x
Will use 2 CPUs.
Best generator chosen: gen-hrdcore-avx2-linux64
New generator found. (DL-size: 0.51MB)
BLF patch found. (DL-size: 31.90MB)
Patched file has wrong MD5: fefeeedcbbb1521f6ca9f1d8f4dae9cd

I'll have a look. You can download the newest .blf from here

ftp://ftp.cryptoguru.org/LBC/blf/

obviously the file is

-.blf.bz2

bunzip2 it, rename to funds_hash160.blf and off you go.

That process should be transparent and done by LBC ... *sigh* Jarvis-IQ is still not there. Wink

Fortunately, if I update LBC, your LBC should auto-update and be magically fixed.
In theory. Wink

edit:

Quote

NVM, i deleted the funds blf file and ran LBC again, now it's working.

Auto-healing FTW! Cheesy

Rico

shifty252

full member

Activity: 177

Merit: 101

@rico

Just updated LBC and got this message
./LBC -x
Will use 2 CPUs.
Best generator chosen: gen-hrdcore-avx2-linux64
New generator found. (DL-size: 0.51MB)
BLF patch found. (DL-size: 31.90MB)
Patched file has wrong MD5: fefeeedcbbb1521f6ca9f1d8f4dae9cd

NVM, i deleted the funds blf file and ran LBC again, now it's working.

this what i get on i7-4510U:

Your maximum speed is 399643 keys/s per CPU core

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Or at least anyone who would/could try it?

There is now a generic 32bit HRD-core available and the newest LBC is aware of it.
If you look at the Generator Speeds, that should give your client a nice bump in the keyrate. Also, the memory requirement is now also around 550MB for the Linux 32bit client.

Also, feel free to PM me with your CPU Ids and keyrates, so I can update that table.
I'd be especially interested in AMD CPUs performance as I have no experience with these so far.

Rico

@becoin: *plonk* - I'm really too busy now and cannot put additional effort in your education on top of all that. Sorry.

becoin

legendary

Activity: 3431

Merit: 1233

Quote

I do not require you to prove this NOT being a collision.

Of course, you don't. You just say I'm talking BS if I can't prove this is NOT a collision...

Quote

you made the statement "This is NOT a collision" which you cannot prove, so your statement is bullshit.

See? The DK level stays the same.

Topic: Large Bitcoin Collider (Collision Finders Pool) - page 50. (Read 193484 times)