Large Bitcoin Collider (Collision Finders Pool)

[Jude Austin]

I just updated my  LBC and now I'm getting this: Server doesn't like us. Answer: too fast.
I'm using and AMD FX 4300 with ./LBC -c 2 (I even tried -c 1, same result).
Thanks in advance.

What generator is LBC trying to use?

I see this file there: gen-hrdcore-sse42-linux64

Did you try a benchmark test? Append -x and see what happens.

This is the result:

./LBC -x
Will use 2 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 3720003547 keys/s per CPU core.

What size is your BLF file?

[1715408253]

1715408253

[1715408253]

1715408253

[1715408253]

1715408253

[1715408253]

1715408253

[Jude Austin]

.....

Code:

2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x5e
02e62151191a931d51cdc513a86d4bf5694f4e51:c:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x65
9d74ffdb31068ca2a1feb8e34830635c0647d714:u:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c
3d6871076780446bd46fc564b0c443e1fd415beb:c:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c

Rico

Hello, how is the private key converted to normal format?

Eeasy:

f9001 + f8c = 1019905 + 3980 = 1023885

1023885 / 128 = Directory.io Page # 8000 round up to whole number (7999.1015)

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

9d74ffdb31068ca2a1feb8e34830635c0647d714

[GoldTiger69]

I just updated my  LBC and now I'm getting this: Server doesn't like us. Answer: too fast.
I'm using and AMD FX 4300 with ./LBC -c 2 (I even tried -c 1, same result).
Thanks in advance.

What generator is LBC trying to use?

I see this file there: gen-hrdcore-sse42-linux64

Did you try a benchmark test? Append -x and see what happens.

This is the result:

./LBC -x
Will use 2 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 3720003547 keys/s per CPU core.

What size is your BLF file?

536870912 mar 18 20:39 funds_h160.blf

[Jude Austin]

I just updated my  LBC and now I'm getting this: Server doesn't like us. Answer: too fast.
I'm using and AMD FX 4300 with ./LBC -c 2 (I even tried -c 1, same result).
Thanks in advance.

What generator is LBC trying to use?

I see this file there: gen-hrdcore-sse42-linux64

Did you try a benchmark test? Append -x and see what happens.

This is the result:

./LBC -x
Will use 2 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 3720003547 keys/s per CPU core.

What size is your BLF file?

536870912 mar 18 20:39 funds_h160.blf

I had this happen before and I just made a new LBC directory and did a clean install.

[rico666]

This is the result:

./LBC -x
Will use 2 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 3720003547 keys/s per CPU core.

When this happens, something went wrong with calling the generator.
Is it there? Is it executable? Is the blf file there?

do a

Code:

time gen-hrdcore-<yourtype>-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 1

If it gives the correct output (the 4 lines). If not, LBC -x will fail too - paste the result of this command here.


Rico

[palawan]

I just updated my  LBC and now I'm getting this: Server doesn't like us. Answer: too fast.
I'm using and AMD FX 4300 with ./LBC -c 2 (I even tried -c 1, same result).
Thanks in advance.

What generator is LBC trying to use?

I see this file there: gen-hrdcore-sse42-linux64

Did you try a benchmark test? Append -x and see what happens.

This is the result:

./LBC -x
Will use 2 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 3720003547 keys/s per CPU core.

What size is your BLF file?

536870912 mar 18 20:39 funds_h160.blf

I had this happen before and I just made a new LBC directory and did a clean install.

I struggled with this "toofast" problem when I was using the generic 1.031-LBC.bz2 and renaming it.
I got it fixed by downloading 170220-b3dc4e1346c597c75b6a879dbc00c9a5.gen-hrdcore-avx2-linux64.bz2  and also  170305-ffb5593f2260d1b4cb0f7e4a990af9e8.blf.bz2    but that's using an AWS EC2 that's running Intel CPU so probably need a different gen-hrdcore file...

[palawan]

.....

Code:

2d17543d32448acc7a1c43c5f72cd5be459ab302:u:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x5e
02e62151191a931d51cdc513a86d4bf5694f4e51:c:priv:0000000000000000000000000000000000000000000000000000000000000001 + 0x65
9d74ffdb31068ca2a1feb8e34830635c0647d714:u:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c
3d6871076780446bd46fc564b0c443e1fd415beb:c:priv:00000000000000000000000000000000000000000000000000000000000f9001 + 0xf8c

Rico

Hello, how is the private key converted to normal format?

Eeasy:

f9001 + f8c = 1019905 + 3980 = 1023885

1023885 / 128 = Directory.io Page # 8000 round up to whole number (7999.1015)

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

9d74ffdb31068ca2a1feb8e34830635c0647d714

Thank you!  So complicated...  lol.  When I do a dumpprivkey on bitcoin, I'm getting a very different type of number   L2NLwmubxxxxxdMsHxxxxxxxxxxxxxxxxxx

[rico666]

Thank you!  So complicated...  lol.  When I do a dumpprivkey on bitcoin, I'm getting a very different type of number   L2NLwmubxxxxxdMsHxxxxxxxxxxxxxxxxxx

It's easier if you stay in the hexadecimal and use tools:

f9001 + f8c = f9f8d (one can do this without a calculator)

and then:

Code:

$ ./bitcoin-tool --output-format base58check --public-key-compression uncompressed --network bitcoin --input-type private-key --input-format hex --output-type private-key-wif --input <here your hex key the LBC found>

Where bitcoin-tool is https://github.com/matja/bitcoin-tool

=> KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rJ5fpCVagTwW (compressed)
=> 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEtSyptnrHKD (uncompressed)

Rico

[GoldTiger69]

This is the result:

./LBC -x
Will use 2 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your maximum speed is 3720003547 keys/s per CPU core.

When this happens, something went wrong with calling the generator.
Is it there? Is it executable? Is the blf file there?

do a

Code:

time gen-hrdcore-<yourtype>-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 1

If it gives the correct output (the 4 lines). If not, LBC -x will fail too - paste the result of this command here.


Rico

It happened after I upgraded it (calling LBC -u). Everything went fine, I even did the LBC -x and no problem. But when I called it for LBC -c 2 -id xxx -s xxx, it said ... Answer: too fast.

Yes, LBC is there and the .blf file is there too: 536870912 mar 18 20:39 funds_h160.blf

The result of the test:

time ./gen-hrdcore-sse42-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 1
but the first key must be in the range:
1  -  fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8ccf364141
Please retry with another key

real   0m0.002s
user   0m0.004s
sys   0m0.000s

[palawan]

Thank you!  So complicated...  lol.  When I do a dumpprivkey on bitcoin, I'm getting a very different type of number   L2NLwmubxxxxxdMsHxxxxxxxxxxxxxxxxxx

It's easier if you stay in the hexadecimal and use tools:

f9001 + f8c = f9f8d (one can do this without a calculator)

and then:

Code:

$ ./bitcoin-tool --output-format base58check --public-key-compression uncompressed --network bitcoin --input-type private-key --input-format hex --output-type private-key-wif --input <here your hex key the LBC found>

Where bitcoin-tool is https://github.com/matja/bitcoin-tool

=> KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rJ5fpCVagTwW (compressed)
=> 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEtSyptnrHKD (uncompressed)

Rico

Thank you, Rico.  I have another dumpprivkey value that starts with Kxxxx  so it's similar.  I'll grab that tool on github and play around with it.

I'm mining under boholIsland  userID.
I think this is a great project to test out the limits of our trust in bitcoin cryptography.  Even if I find a private key to a $10M wallet, I have no plans to take any part of it.  I would not turn down a gift-reward, though, but no conditions attached for the return.

Better to have a public project than a secret one...

[rico666]

It happened after I upgraded it (calling LBC -u). Everything went fine, I even did the LBC -x and no problem. But when I called it for LBC -c 2 -id xxx -s xxx, it said ... Answer: too fast.
...

real   0m0.002s
user   0m0.004s
sys   0m0.000s

I doubt LBC -x went through without a problem. Because the benchmark claims your computer did 16M keys in 0.002s, so either your computer is from the future or something went wrong. 

Code:

The result of the test:

time ./gen-hrdcore-sse42-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 1
but the first key must be in the range:
1  -  fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8ccf364141
Please retry with another key

Something went wrong. The generator failed internally somewhere. For diagnosis send me

The distro (name, version) you use
output of ls -al of the collider directory
output of cat /proc/cpuinfo
output of free


Rico

[GoldTiger69]

It happened after I upgraded it (calling LBC -u). Everything went fine, I even did the LBC -x and no problem. But when I called it for LBC -c 2 -id xxx -s xxx, it said ... Answer: too fast.
...

real   0m0.002s
user   0m0.004s
sys   0m0.000s

I doubt LBC -x went through without a problem. Because the benchmark claims your computer did 16M keys in 0.002s, so either your computer is from the future or something went wrong. 

Code:

The result of the test:

time ./gen-hrdcore-sse42-linux64 -I 0000000000000000000000000000000000000000000000000000000000000001 -c 10000 -L 1
but the first key must be in the range:
1  -  fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8ccf364141
Please retry with another key

Something went wrong. The generator failed internally somewhere. For diagnosis send me

The distro (name, version) you use
output of ls -al of the collider directory
output of cat /proc/cpuinfo
output of free


Rico

output of free?

[rico666]

output of free?

Yes. Something like this:

Code:

$ free
              total        used        free      shared  buff/cache   available
Mem:       16299924     1650300    12482160     1056560     2167464    13303548
Swap:             0           0           0

[rico666]

Oh wow - someone has been reading Reddit:

https://cointelegraph.com/news/ultimate-white-hat-hacker-large-bitcoin-collider-passes-1000-trillion-addresses

"Ultimate white hat hacker" - take that becoin!

For da Germans:
https://www.btc-echo.de/der-large-bitcoin-collider-erreicht-eine-billiarde-adressen/


Rico

[unknownhostname]

Oh wow - someone has been reading Reddit:

https://cointelegraph.com/news/ultimate-white-hat-hacker-large-bitcoin-collider-passes-1000-trillion-addresses

"Ultimate white hat hacker" - take that becoin!

For da Germans:
https://www.btc-echo.de/der-large-bitcoin-collider-erreicht-eine-billiarde-adressen/


Rico

read the news with 1000 trillion addresses more than on 10 websites  ...you're going to be a star :>

[icanscript]

Hi,

I have almost finished a bootable iso image using arch, has lbcuser account and collider/LBC @ home dir. Currently booting with Nvidia drivers. I am just trying to work around a kernel hook that can determine the card you have and select a proprietary driver from either nvidia or amd/ati as currently its failing to boot using both. Currently this is working from an x64 version of arch.

I will also create i686 for 32-bit computers with GPU access.

[rico666]

I have almost finished a bootable iso image using arch, has lbcuser account and collider/LBC @ home dir. Currently booting with Nvidia drivers. I am just trying to work around a kernel hook that can determine the card you have and select a proprietary driver from either nvidia or amd/ati as currently its failing to boot using both. Currently this is working from an x64 version of arch.

Great progress. I will be happy to check it out.

I will also create i686 for 32-bit computers with GPU access.

Don't. Spare the energy - there will be no 32bit clients.


Rico

[rico666]

read the news with 1000 trillion addresses more than on 10 websites  ...you're going to be a star :>

Yeah - hooray.

In a burst of vanity attack, I checked mentions on the internet and found out, that the LBC user manual is being used as reference in cyber investigations articles: http://mccann-cyber.com/anonymity-cryptofraud-blockchain/

The theory part of the manual (see footnotes). Now the LBC has to run forever, else cyber investigators might get a 404. 

Rico

[becoin]

LBC user manual is being used as reference in cyber investigations articles

This user manual must be titled something like "Stealing from Amateur Thieves" lol

[rico666]

This user manual must be titled something like "Stealing from Amateur Thieves" lol