Pages:
Author

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

legendary
Activity: 1120
Merit: 1037
฿ → ∞
Sorry, noob here. This doesn't look like a private key and when put into bitcoin address it says invalid. What am I missing?

In the trophies section, it is all well prepared. If you put the hash160 in the blockchain.info search, you end up on

https://blockchain.info/address/12CiUhYVTTH33w3SPUBqcpMoqnApAV4WCF
which is the same page as
https://blockchain.info/de/address/0d2f533966c6578e1111978ca698f8add7fffdf3

and if you convert the private key to a WIF, its 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEXxDuJBiUbiVA9e

I don't see an "invalid" anywhere.

More info: https://lbc.cryptoguru.org/man/user#found-

Rico
legendary
Activity: 1140
Merit: 1000
The Real Jude Austin
My CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz

Ok. It seems the GPU generator is working on Broadwell, Skylake and Kaby Lake.
I'm working on compiles for the older architectures too and will post here when they're available.

Rico


Patiently waiting, hehe.
full member
Activity: 149
Merit: 100
Good morning!

HeavenlyCreatures found #49


Code:
From	XXX
To [email protected]
Date Today 08:02
Hi,

I found #49

0d2f533966c6578e1111978ca698f8add7fffdf3:c:priv:000000000000000000000000000000000000000000000000000174176b015001
+ 0xf4c

Looking at the PK, the pool must have found it GMT: Sat, 11 Feb 2017 04:32:26 GMT

edit: trophies update.

cheers!

Rico

Sorry, noob here. This doesn't look like a private key and when put into bitcoin address it says invalid. What am I missing?
legendary
Activity: 1120
Merit: 1037
฿ → ∞
My CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz

Ok. It seems the GPU generator is working on Broadwell, Skylake and Kaby Lake.
I'm working on compiles for the older architectures too and will post here when they're available.

Rico
legendary
Activity: 1932
Merit: 2077
I was thinking, if sha256/ripemd160 is too fast compared to CPU pk generation, you could search for P2SH "addresses" too.

For example, with only 3 pubkeys, you could generate about 20 addresses (probably more):

6
Code:
{2 [pubkey1] [pubkey2] [pubkey3] 3 OP_CHECKMULTISIG}

+6
Code:
{1 [pubkey1] [pubkey2] 2 OP_CHECKMULTISIG}

+3
Code:
{1 [pubkey1] 1 OP_CHECKMULTISIG}


newbie
Activity: 31
Merit: 0
So what? What does this matter? by the time you use quantum computers or asics and start finding tens and tens of collisions, bitcoin will worth 1 dll because people will move to other one more secure.

Have you ever thought about this?

No I haven't. I have sworn to myself to pull this project off without any thinking at all.


Rico


Well let's see how the LBC evolves, thankyou.
member
Activity: 114
Merit: 11
after following your instruction


1st run
Code:
Illegal instruction (core dumped)

And we are sure the CPU is AVX2 capable?


Rico


My CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
full member
Activity: 177
Merit: 101
aaand I got blacklisted while using the beta build only on CPU.

How could you use the GPU client if you have no GPU auth?

I had a look at the logs: Shortly after you said here "top30 here I come", your client started to churn invalid blocks to the server, so the server blacklisted you and the contributed 278,8 Gkeys got invalidated.

As it should be - IMHO.


Rico


i ran it like this: ./LBC --id shifty252 --secret xxxxxxx -c 4

then it started and said no gpu found, will use 4 cpus but it also threw about 4 error lines about an unknown command "-L"  but it went on asking for work so I let it be.
legendary
Activity: 1120
Merit: 1037
฿ → ∞
So what? What does this matter? by the time you use quantum computers or asics and start finding tens and tens of collisions, bitcoin will worth 1 dll because people will move to other one more secure.

Have you ever thought about this?

No I haven't. I have sworn to myself to pull this project off without any thinking at all.


Rico
legendary
Activity: 1120
Merit: 1037
฿ → ∞
aaand I got blacklisted while using the beta build only on CPU.

How could you use the GPU client if you have no GPU auth?

I had a look at the logs: Shortly after you said here "top30 here I come", your client started to churn invalid blocks to the server, so the server blacklisted you and the contributed 278,8 Gkeys got invalidated.

As it should be - IMHO.


Rico
newbie
Activity: 31
Merit: 0
When the International Quantum Computing Society inaugurates it's Cryptocurrency Hacker of the Year award in 2025, will it be called the Rico in honor of the pioneer in collision computing?

I don't know. Quantum computing is only 4th on my TODO list.

1. Full-GPU client
2. FPGA implementation
3. ASIC
4. Quantum Computing


Rico


So what? What does this matter? by the time you use quantum computers or asics and start finding tens and tens of collisions, bitcoin will worth 1 dll because people will move to other one more secure.

Have you ever thought about this?
full member
Activity: 177
Merit: 101
aaand I got blacklisted while using the beta build only on CPU.

anyway to lift the ban so i can get back to regular LBC ?
full member
Activity: 177
Merit: 101
So, the beta is available to top30 and paying users? or for everyone with OpenCL installed?

OpenCL is necessary but not sufficient.
The beta (and then the production client) is available to everyone, but it wikl work only for users who have a gpuauth: 1 attached to their id.

How does that gpuauth=1 happen?

  • You are a top30 Gkeys contributor
  • You fork out 0.1 BTC - which are distributed among all pool members (except me) who have a BTC address set
  • You get a gpuauth set to 1 by decree (i.e. for special services)


Rico

Thanks for clarifying. Top30 here I come, unless I stumble upon 0.1 BTC....
legendary
Activity: 1120
Merit: 1037
฿ → ∞
So, the beta is available to top30 and paying users? or for everyone with OpenCL installed?

OpenCL is necessary but not sufficient.
The beta (and then the production client) is available to everyone, but it wikl work only for users who have a gpuauth: 1 attached to their id.

How does that gpuauth=1 happen?

  • You are a top30 Gkeys contributor
  • You fork out 0.1 BTC - which are distributed among all pool members (except me) who have a BTC address set
  • You get a gpuauth set to 1 by decree (i.e. for special services)


Rico
full member
Activity: 177
Merit: 101
So, the beta is available to top30 and paying users? or for everyone with OpenCL installed?
legendary
Activity: 1120
Merit: 1037
฿ → ∞
When the International Quantum Computing Society inaugurates it's Cryptocurrency Hacker of the Year award in 2025, will it be called the Rico in honor of the pioneer in collision computing?

I don't know. Quantum computing is only 4th on my TODO list.

1. Full-GPU client
2. FPGA implementation
3. ASIC
4. Quantum Computing


Rico
legendary
Activity: 1120
Merit: 1037
฿ → ∞
after following your instruction


1st run
Code:
Illegal instruction (core dumped)

And we are sure the CPU is AVX2 capable?


Rico
legendary
Activity: 1638
Merit: 1001
When the International Quantum Computing Society inaugurates it's Cryptocurrency Hacker of the Year award in 2025, will it be called the Rico in honor of the pioneer in collision computing?
member
Activity: 114
Merit: 11
after following your instruction


1st run
Code:
root@RetardPunk:~/LBCGPU# ./LBC --id JXXXXX --secret XXXXXXXXXX --gpu -t 5 -l 1
GPU authorized: yes
Will use 4 CPUs.
Best generator chosen: gen-hrdcore-gpu-linux64
New generator found. (DL-size: 0.72MB)
Benchmark info not found - benchmarking... ./gen-hrdcore-gpu-linux64: /usr/local/cuda-8.0/lib64/libOpenCL.so.1: no version information available (required by ./gen-hrdcore-gpu-linux64)
Illegal instruction (core dumped)
done.
Your maximum speed is 22471793 keys/s per CPU core.
Ask for work... Server doesn't like us. Answer: toofast.

2nd run
Code:
root@RetardPunk:~/LBCGPU# ./LBC --id JXXXXX --secret XXXXXXXXXX --cpus 8 --gpu -t 5 -l 1
GPU authorized: yes
Best generator chosen: gen-hrdcore-gpu-linux64
Ask for work... Server doesn't like us. Answer: toofast.

run with -x
Code:
root@RetardPunk:~/LBCGPU# ./LBC --id JXXXXX --secret XXXXXXXXXX --cpus 8 --gpu -x
GPU authorized: yes
Best generator chosen: gen-hrdcore-gpu-linux64
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... ./gen-hrdcore-gpu-linux64: /usr/local/cuda-8.0/lib64/libOpenCL.so.1: no version information available (required by ./gen-hrdcore-gpu-linux64)
Illegal instruction (core dumped)
done.
Your maximum speed is 64860036 keys/s per CPU core.
./gen-hrdcore-gpu-linux64: /usr/local/cuda-8.0/lib64/libOpenCL.so.1: no version information available (required by ./gen-hrdcore-gpu-linux64)
legendary
Activity: 1120
Merit: 1037
฿ → ∞
Ok guys - this is it:

Everyone who has a working OpenCL install, is authorized for GPU, has an AVX2 capable CPU (I will provide sse42 GPU clients later) and feels bold enough, please download the beta from.

https://lbc.cryptoguru.org/downloads/beta/LBC

Will the GPU client work in a VM? No. So if any of this is not met, please do not bother right now, you'd only find pain and sorrow.

Attention! This LBC client is too advanced for your CPU generator (except you have a Skylake CPU and its newest generator)
so keep your older LBC somewhere or be prepared to delete this new one if you plan to use a CPU client again.


Maybe you would like to have your GPU experiment in another folder. Let's say you have a folder "collider", so copy it
Code:
$ cp -a collider gcollider

In the folder gcollider remove bench.pst, LBC and your gen-hrdcore-avx2-linux64 and eventually a present diagnostics-OpenCL.txt
and put the beta LBC in that folder
Code:
$ cd gcollider
$ rm -f bench.pst LBC gen-hrdcore-avx2-linux64 diagnostics-OpenCL.txt
$ wget https://lbc.cryptoguru.org/downloads/beta/LBC
$ chmod a+x LBC

Ok, hour of truth:

upon 1st invocation you should see:
Code:
$ ./LBC --gpu -t 1 -l 0
OpenCL diagnostics written.
GPU authorized: yes
OpenCL program written.

LBC will end here and you'll see two new files in your directory (diagnostics-OpenCL.txt and hash160_deparsed.cl) you keep both of them where they are.

upon the 2nd invocation (and all subsequent), you should fly:

Code:
$ ./LBC --gpu -t 1 -l 0
GPU authorized: yes
Best generator chosen: gen-hrdcore-gpu-linux64
New generator found. (DL-size: 0.72MB)
Benchmark info not found - benchmarking... done.
Your maximum speed is 2098648 keys/s per CPU core.
Ask for work... got blocks [416958585-416959096] (536 Mkeys)
oooooooooooooooooooooooooooooooo (8.06 Mkeys/s)

In theory.  Wink If you remove the -l 0, it will not end after one iteration and you may want to ramp up the time, so

Code:
$ ./LBC --gpu -t 5
GPU authorized: yes
Best generator chosen: gen-hrdcore-gpu-linux64
Ask for work... got blocks [419776761-419779192] (2550 Mkeys)

Nice numbers - eh?



Also in the news, user manual under https://lbc.cryptoguru.org/man/user extended with topics about Id, security, setting BTC address, GPU and defaults-file.

check back often, I will update this as we go.


Rico
Pages:
Jump to: