Large Bitcoin Collider (Collision Finders Pool)

[rico666]

LBC is certainly not for the faint of heart.
...
Clearly, anyone with Attention deficit hyperactivity disorder would be in the wrong place here. 

Code:

# grep 35.157.195.158 LBC.log 
1491376396  35.157.195.158 SECRET: given != stored (a2ca7a3a3079cc296c3c3fdff6ed8114-65f2)
1491376625  35.157.195.158 SECRET: given != stored (1337Leet-65f2)
1491376683  35.157.195.158 SECRET: given != stored (1337Leet-65f2)
1491376721  35.157.195.158 SECRET: given != stored (1337Leet-65f2)
1491376793  35.157.195.158 Change Secret (1337Leet)
1491376793  35.157.195.158 PUT-NIL: toofast (1337Leet-65f2)
1491376807  35.157.195.158 Change Secret (1337Leet1337)
1491376807  35.157.195.158 PUT-NIL: toofast (1337Leet1337-65f2)
1491376880  35.157.195.158 Change Secret (1337Leet1337)
1491376890  35.157.195.158 PUT-NIL: toofast (1337Leet1337-65f2)
1491376893  35.157.195.158 PUT-NIL: toofast (1337Leet1337-65f2)
1491376901  35.157.195.158 PUT-NIL: toofast (1337Leet1337-65f2)
1491377091  35.157.195.158 PUT-NIL: toofast (1337Leet1337-65f2)
1491377346  35.157.195.158 PUT-NIL: blacklisted (1337Leet1337-65f2)
1491377411  35.157.195.158 PUT-NIL: blacklisted (SetupOfThisShitIsHorrible-65f2)

  Sorry, LBC needs at least 3 3 in 1337

[rico666]

Probably I'm only frustrated, I would really be sorry if we don't hit #51 

There is still hope. Time for frustration is tomorrow 11 a.m. UTC

Unknownhostname just informed me, that he found #51.
And because he has shown me the privkey, I know he's not making it up.

Please stand by for further details...


Rico

[arulbero]

Unknownhostname just informed me, that he found #51.
And because he has shown me the privkey, I know he's not making it up.

VERY GOOOD!!!  

[hodlcoins]

+1 for Leet's last Secret try.

Yay for UHN, his effort's paid in the last end. NOT! 

And a PLUSONE!!! for automatic updating of either executable and Filter file.
Once a day or so, so we all work with the latest data, even on headless machines.

[arulbero]

Unknownhostname just informed me, that he found #51.
And because he has shown me the privkey, I know he's not making it up.

Please stand by for further details...

Why do you move funds from the address to itself? What is the reason?

https://blockchain.info/address/1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS

[rico666]

Why do you move funds from the address to itself? What is the reason?

https://blockchain.info/address/1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS

It's not me.  Don't know if Unknownhostname is experimenting or what.

I do consider all puzzle transaction addresses bounties, so this one does belong to Unknownhostname.
As far as I am concerned it's his.

Rico

[unknownhostname]

Unknownhostname just informed me, that he found #51.
And because he has shown me the privkey, I know he's not making it up.

Please stand by for further details...

Why do you move funds from the address to itself? What is the reason?

https://blockchain.info/address/1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS

I look for a 10k BTC dormant address ^^ ..

who cares when it comes to 0.051 ^^ , you can play with it ... you can even play until you spend all your btc's on fees ^^

#52 I'm coming for you ...


How many days do we need for #52 ?

Btw can someone tell me what space did we searched from a 160 bit ? ... how many % ?

P.S. Need to setup a few more Gkeys/s

[arulbero]

#52 I'm coming for you ...

How many days do we need for #52 ?

Btw can someone tell me what space did we searched from a 160 bit ? ... how many % ?

P.S. Need to setup a few more Gkeys/s

1/2^(161-51)  =  1/2^(110) =  1/(2^10)^11 =  (0.001)^11 =  0.00000...0001  with 33 zeros 


-->   0.00000...001 % with 31 zeros  after the point .

[rico666]

1/2^(161-51)  =  1/2^(110) =  1/(2^10)^11 =  (0.001)^11 =  0.00000...0001  with 33 zeros  

Why 2^161?

1 bit = 2^1 keys (-1)
2 bit = 2^2 keys (-1)
3 bit = 2^3 keys (-1)
...
160 bit = 2^160 keys (-1)

Anyway:

https://lbc.cryptoguru.org/stats
https://lbc.cryptoguru.org/trophies

Rico

[unknownhostname]

#52 I'm coming for you ...

How many days do we need for #52 ?

Btw can someone tell me what space did we searched from a 160 bit ? ... how many % ?

P.S. Need to setup a few more Gkeys/s

1/2^(161-51)  =  1/2^(110) =  1/(2^10)^11 =  (0.001)^11 =  0.00000...0001  with 33 zeros 


-->   0.00000...001 % with 31 zeros  after the point .

thats insane ..

[rico666]

If I was to have per-user keyrate charts (hourly), would you agree them to be public or not?


Rico

[arulbero]

1/2^(161-51)  =  1/2^(110) =  1/(2^10)^11 =  (0.001)^11 =  0.00000...0001  with 33 zeros  

Why 2^161?

Boh, +1 escaped me  . 

ok 1/2^(160-51) but more or less....

2^160 if you want search for the entire space, 2^136 for the first "real" collision (but unknownhostname wants not a simple collision, but a rich collision) ...

[arulbero]

If I was to have per-user keyrate charts (hourly), would you agree them to be public or not?

Rico

For me it's ok.

[unknownhostname]

If I was to have per-user keyrate charts (hourly), would you agree them to be public or not?


Rico

ofc .. u cant always see that some servers dont work ... or have problems when your keyrate goes down.

[rico666]

Boh, +1 escaped me  . 

ok 1/2^(160-51) but more or less....

More or less? 

The difference is 1461501637330902918203684832716283019655932542976 keys to search.

2^160 if you want search for the entire space, 2^136 for the first "real" collision (but unknownhostname wants not a simple collision, but a rich collision) ...

I have the suspicion that more people want that...

By the way: The 6-month grace period for 16cFBcM27DGriyvz5i8SLmd8n5ai8hCTEE will end May, 10th. Then, these funds will go to the LBC pot (= for distribution among clients) and yes, I assume the pot will contain some bonus BTCs also.


Rico

[arulbero]

I would like to look at other keys  (unknownhostname has too much cpu power)

time ./gen-hrdcore-avx2-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 8

what stand for options "-c"  and "-L" ?

[rico666]

I would like to look at other keys  (unknownhostname has too much cpu power)

time ./gen-hrdcore-avx2-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 8

what stand for options "-c"  and "-L" ?

-c is the challenge. 10000 is for testing purposes (normally you can see the challenges if you look at the process table when LBC is running)

-L is the number of loops = number of times 16,7 Mkeys consecutive blocks search to perform

if you want to check individual keys,  LBC -p is a way better option:

https://lbc.cryptoguru.org/man/user#manual-mode

as you can give them in binary form, LBC correctly "snaps" the key range into block boundary form and you can give a from-to range without having to worry about the loops or challenges. You can even mix hexadecimal and binary from-to parameters. And even key and block numbers. I had an attack of genericity when implementing that.

If you are afraid not to give away any information about privkeys, either pull the network plug, or simply give the "to" parameter with some more distance and end the LBC hard with Ctrl+C before it ends.

With the -p parameter, LBC does not even send a promise (to do work) to the server and if you end it hard before the work is done, it does not send its PoW -> as if it never happened.

edit: But not sending PoW will of course freeze your stats. So unless you are testing privkeys you do not want to disclose, send the PoW.


Rico

[rico666]

Search debt from #50 search space:

751927328-999999998 ~240 MBlocks   <--- we are here now ... well 752008095 ... I mean 753478383 ... ah f* it
1000752001-1073740223 ~ 73MBlocks   <-- I'm testing here (so you will see a small 1Mblock jump when done above)

[then sudden jump of 1000 MBlocks ]

Rest of #51 search space:

2004489776-2053318784 ~48 MBlocks
2053937985-2147481087 ~93 MBlocks

Start of #52 search space

2147483649-infinity_and_beyond  


So ~ 450 MBlocks until #52 search space. Let's see if we find something in these. So actually if you get a hit before your client shows 2147483649, it will certainly be a more interesting hit than #52.


Rico

(1 Mblock ~ 1Tkey = 1000 Gkey)

[rico666]

And a PLUSONE!!! for automatic updating of either executable and Filter file.
Once a day or so, so we all work with the latest data, even on headless machines.

So I hope you have set up an "Eternal Run" configuration: https://lbc.cryptoguru.org/man/user#eternal-run



Rico

[hodlcoins]

A few days too late: I'm on holidays for the next 2 weeks.
But thanks anyway, will implement it after that.