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

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: GoldTiger69 on March 28, 2017, 01:27:09 AM

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. Wink

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

palawan

sr. member

Activity: 386

Merit: 250

Quote from: rico666 on March 28, 2017, 01:03:35 AM

Quote from: palawan on March 28, 2017, 12:48:51 AM

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

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...

GoldTiger69

hero member

Activity: 583

Merit: 502

Quote from: rico666 on March 28, 2017, 12:37:25 AM

Quote from: GoldTiger69 on March 27, 2017, 11:44:15 PM

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--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

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: palawan on March 28, 2017, 12:48:51 AM

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

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

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

Rico

palawan

sr. member

Activity: 386

Merit: 250

Quote from: Jude Austin on March 27, 2017, 11:57:35 PM

Quote from: palawan on March 27, 2017, 10:34:45 PM

Quote from: rico666 on March 27, 2017, 07:18:17 AM

.....

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

palawan

sr. member

Activity: 386

Merit: 250

Quote from: Jude Austin on March 28, 2017, 12:19:26 AM

Quote from: GoldTiger69 on March 28, 2017, 12:15:26 AM

Quote from: Jude Austin on March 27, 2017, 11:49:12 PM

Quote from: GoldTiger69 on March 27, 2017, 11:44:15 PM

Quote from: Jude Austin on March 27, 2017, 11:24:13 PM

Quote from: GoldTiger69 on March 27, 2017, 11:12:58 PM

Quote from: Jude Austin on March 27, 2017, 10:06:01 PM

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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...

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: GoldTiger69 on March 27, 2017, 11:44:15 PM

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--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

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: GoldTiger69 on March 28, 2017, 12:15:26 AM

Quote from: Jude Austin on March 27, 2017, 11:49:12 PM

Quote from: GoldTiger69 on March 27, 2017, 11:44:15 PM

Quote from: Jude Austin on March 27, 2017, 11:24:13 PM

Quote from: GoldTiger69 on March 27, 2017, 11:12:58 PM

Quote from: Jude Austin on March 27, 2017, 10:06:01 PM

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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.

GoldTiger69

hero member

Activity: 583

Merit: 502

Quote from: Jude Austin on March 27, 2017, 11:49:12 PM

Quote from: GoldTiger69 on March 27, 2017, 11:44:15 PM

Quote from: Jude Austin on March 27, 2017, 11:24:13 PM

Quote from: GoldTiger69 on March 27, 2017, 11:12:58 PM

Quote from: Jude Austin on March 27, 2017, 10:06:01 PM

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: palawan on March 27, 2017, 10:34:45 PM

Quote from: rico666 on March 27, 2017, 07:18:17 AM

.....

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

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: GoldTiger69 on March 27, 2017, 11:44:15 PM

Quote from: Jude Austin on March 27, 2017, 11:24:13 PM

Quote from: GoldTiger69 on March 27, 2017, 11:12:58 PM

Quote from: Jude Austin on March 27, 2017, 10:06:01 PM

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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?

GoldTiger69

hero member

Activity: 583

Merit: 502

Quote from: Jude Austin on March 27, 2017, 11:24:13 PM

Quote from: GoldTiger69 on March 27, 2017, 11:12:58 PM

Quote from: Jude Austin on March 27, 2017, 10:06:01 PM

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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.

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: GoldTiger69 on March 27, 2017, 11:12:58 PM

Quote from: Jude Austin on March 27, 2017, 10:06:01 PM

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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.

GoldTiger69

hero member

Activity: 583

Merit: 502

Quote from: Jude Austin on March 27, 2017, 10:06:01 PM

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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

palawan

sr. member

Activity: 386

Merit: 250

Quote from: rico666 on March 27, 2017, 07:18:17 AM

.....

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?

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: GoldTiger69 on March 27, 2017, 04:38:28 PM

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?

GoldTiger69

hero member

Activity: 583

Merit: 502

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.

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: unknownhostname on March 27, 2017, 09:21:29 AM

Quote from: rico666 on March 27, 2017, 07:37:44 AM

I believe these 4 x K80 machines could still deliver more than 70 Mkeys/s each (machine).

What about 32 vCPU , 8 x K80 machines ?

I believe the 8 x K80 machines do have 64 vCPU? else even the new generator cannot saturate 8 K80 with "only" 32 vCPUs.
Still, the speedup and GPU usage is way better with the new GPU generators. Speedup between 2.5x and 3.1x is to be expected.
With the 4 x K80 32vCPU machines one can expect the CPUs to almost saturate the GPUs. (Now less than 50%)

All in all - with the new generators we should be able to significantly lower the time until #51. Even worst case it should be 10 days less than what the stats show now. (edit: I see we have almost 40% of the #51 search space covered)

Rico

unknownhostname

member

Activity: 62

Merit: 10

Quote from: rico666 on March 27, 2017, 07:37:44 AM

I believe these 4 x K80 machines could still deliver more than 70 Mkeys/s each (machine).

What about 32 vCPU , 8 x K80 machines ?

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: unknownhostname on March 27, 2017, 07:34:34 AM

Quote from: rico666 on March 27, 2017, 07:18:17 AM

It's official, the on-GPU bloom filter code is not working on Nvidia Tesla K80. Angry

So what do u want me to put on those GPU k80 servers ?

The new version I will write especially for these servers. It's PITA, but it would be a shame to not have a keyrate doubling.
So wait for it (1-2 days). I believe these 4 x K80 machines could still deliver more than 70 Mkeys/s each (machine).

Rico

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