I think it will be found this about one week
ps I use http://btcdirectory.azurewebsites.net/1 instead directory.io
Topic: Large Bitcoin Collider (Collision Finders Pool) - page 53. (Read 193484 times)
Hi I stay gift on the secret page directory.io for check
I think it will be found this about one week
ps I use http://btcdirectory.azurewebsites.net/1 instead directory.io
I think it will be found this about one week
ps I use http://btcdirectory.azurewebsites.net/1 instead directory.io
Hi Bro,
...
Would you please guide me how to replicate your source code and Super Vanitygen for building a Collider Pool for ETH/ETC and also leverage Brainwallet by hooking into it.
...
I look forward to hearing from you.
...
Would you please guide me how to replicate your source code and Super Vanitygen for building a Collider Pool for ETH/ETC and also leverage Brainwallet by hooking into it.
...
I look forward to hearing from you.
Yo man...
... You can hire me for 0.1BTC/h but that's only the special bitcointalk.org rate for my ngah brethren. Usually its 0.3BTC/h.
For ETH/ETC projects it's of course at least 0.3BTC/h
Rico
Hi Bro,
I really find your Collision pool fascinating. But I want to target Ethereum chains, both ETH and ETC instead of BTC. I am a Python developer having three years experience with some knowledge of C/C++. I don't know Perl at all. Would you please guide me how to replicate your source code and Super Vanitygen for building a Collider Pool for ETH/ETC and also leverage Brainwallet by hooking into it. I assume Brainwallet can be used as it is without any major changes for all altcoins including ETH and ETC not just Bitcoin.
I look forward to hearing from you.
I really find your Collision pool fascinating. But I want to target Ethereum chains, both ETH and ETC instead of BTC. I am a Python developer having three years experience with some knowledge of C/C++. I don't know Perl at all. Would you please guide me how to replicate your source code and Super Vanitygen for building a Collider Pool for ETH/ETC and also leverage Brainwallet by hooking into it. I assume Brainwallet can be used as it is without any major changes for all altcoins including ETH and ETC not just Bitcoin.
I look forward to hearing from you.
We had a nice surge of search power last (Europe's) night.
Huh? Do you have a power plant working for you?Doesn't the power plant work for everyone?
Anyone who uses electricity anyway...
Most power plants work for profit and most people pay for the electricity they use. Obviously, some people have access to free (or paid by taxpayers) electricity and can experiment with projects like this one.
We had a nice surge of search power last (Europe's) night.
Huh? Do you have a power plant working for you?Doesn't the power plant work for everyone?
Anyone who uses electricity anyway...
We had a nice surge of search power last (Europe's) night.
Huh? Do you have a power plant working for you?
Awesome!
Will see if I can get my second machine up today.
So busy with work these days :/
Will see if I can get my second machine up today.
So busy with work these days :/
Huh? 209 days in just 24 hours? http://lbc.cryptoguru.org:5000/stats
We had a nice surge of search power last (Europe's) night.
I don't mind to do the time warp again.
Rico
edit:
Right now, I could shortcut the time to roughly 201 days by putting the pool forefront at 2^50. I won't do that, however, because I assume this is exactly what the guy(s), who emptied the previous addresses of that transaction, did: After each find, skip the search space.
It may very well be possible, that by doing this, they overlooked a far more interesting address...
https://gyazo.com/26edcedf34a1294b389ff55a1ce9210a
My small collider that runs at 1m keys pr sec.
Someone get a GPU "miner" going and ill get my machine going with CPU and GPU.
My small collider that runs at 1m keys pr sec.
Someone get a GPU "miner" going and ill get my machine going with CPU and GPU.
eyyy, I am nr 7 on the stats page 
I remember a time, when being nr 15 on stats page meant you had 8 blocks (0.008 GKeys) done
Actually not so long ago.
I do not intend to extend the top20 list, but the next LBC release will have a -query parameter where the client can actually ask the server about itself (a.k.a. how the server sees the client), one information being blocks/keys done.
That way, even those not in the top20 can check if their work "arrives" or how far they are away from being in the top20.
Rico
Just a little LBC Pr0n...
eyyy, I am nr 7 on the stats page
#45
https://blockchain.info/address/1NtiLNGegHWE3Mp9g2JPkgx6wUg4TW7bbk
Rico
https://blockchain.info/address/1NtiLNGegHWE3Mp9g2JPkgx6wUg4TW7bbk
Code:
Fetching adequate work... got block interval [19063782-19076773]
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
oooooooooooooooooooooooooof0225bfc68a6e17e87cd8b5e60ae3be18f120753:c:
(hex)priv:0000000000000000000000000000000000000000000000000000122fca143c05
oooooooooooooooooooooooooooooooooooo
...
Rico
Work of a whole day gone
500 Can't connect to 62.146.128.45:5000
500 Can't connect to 62.146.128.45:5000
The work is not entirely gone (for you), as your client checked the (manually given) range, so you know the result of something being in there or not.
It's just that on communication with the server, the server recognized the id of your client being blacklisted (there was a history) and refused connection. So in that case, the 500 was to be expected.
If anything, the work is lost for the pool, but as is, it takes only PoWs of clients it trusts...
Rico
Working on it, documentation sucks ass for go-opencl.
Might use PyOpenCL. Very documentation, much information: https://documen.tician.de/pyopencl/
All I need to do is output the private key in bytes for compressed and uncompressed, correct? And in order...which is simple.
You need to output the two hash160es in bytes for compressed and uncompressed public keys (of a private key which gets incremented).
Well - it'd be a start, I could probably continue from there. We still would need the checking against either a bloom filter or a normal associative array of the funds be done on GPU also as the CPU couldn't keep up.
Every effort counts - same as relay race.
Rico
If anyone knows WTF they are doing with Go and OpenCL please feel free to help, haha.
Trying to make an OCL version of LBC for teh fast.
Trying to make an OCL version of LBC for teh fast.
This would be tremendous to have. And very much needed:
(screenshot courtesy of my development server)
Let me spell it out for you: https://blockchain.info/address/1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS
Rico
Working on it, documentation sucks ass for go-opencl.
Might use PyOpenCL. Very documentation, much information: https://documen.tician.de/pyopencl/
All I need to do is output the private key in bytes for compressed and uncompressed, correct? And in order...which is simple.
Thanks,
Jude
If anyone knows WTF they are doing with Go and OpenCL please feel free to help, haha.
Trying to make an OCL version of LBC for teh fast.
Trying to make an OCL version of LBC for teh fast.
This would be tremendous to have. And very much needed:
(screenshot courtesy of my development server)
Let me spell it out for you: https://blockchain.info/address/1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS
Rico
It almost seems like he is only allowing 1 connection per host.
Unfortunately, the current client is very brittle handling timeouts. If the server doesn't answer within a few seconds you get this 500.
Currently new code is already in place that handles this gracefully and does 3 retries within 90 seconds.
Maybe I'll make that even configurable.
edit:
Done. (configurable)
And the sleeping is done like Ethernet anti-collision strategies: Progressive random waits.
Code:
# LBC -c 1 -t 1
Problem connecting to server (500 Can't connect to 128.0.0.1:5000). Retries left: 2
Sleeping 6.965 s...
Problem connecting to server (500 Can't connect to 128.0.0.1:5000). Retries left: 1
Sleeping 19.968 s...
Problem connecting to server (500 Can't connect to 128.0.0.1:5000). Retries left: 0
500 Can't connect to 128.0.0.1:5000
I believe with this the "500" should be a thing of the past.
Rico
Work of a whole day gone
500 Can't connect to 62.146.128.45:5000
500 Can't connect to 62.146.128.45:5000
+1 that has happened to me multiple times.
I noticed that will happen if you are on the website at the same time the client tries to get new work.
It almost seems like he is only allowing 1 connection per host.
Work of a whole day gone
500 Can't connect to 62.146.128.45:5000
500 Can't connect to 62.146.128.45:5000
+1 that has happened to me multiple times.
Jump to: