Building a public server for the Bitcoin Puzzle Transactions | Kangaroo/Bitcrack

[yoyodapro]

Hey all!

I am aware of TTD's 64 server for BitCrack but is there any reason why no one has created a public server for Kangaroo?

There are a few PoW programs available on Git that work with BitCrack and was wondering if anyone had the time & experience to help me modify or create a program that could distribute ranges and record proof of work for the puzzle transactions?  I have experience building websites, and I've been teaching myself various programming languages for the last 8 months to create my BitCrack/BSGS hybrid program.

Working together we could all solve this program relatively quickly.

Thoughts?

[BitcoinADAB]

Hey all!
...

Working together we could all solve this program relatively quickly.

Thoughts?

Hi yoyodapro,

that could be more intersting: Calculating Satoshi's coins https://bitcointalk.org/index.php?topic=5347791.0

[WanderingPhilospher]

Hey all!
...

Working together we could all solve this program relatively quickly.

Thoughts?

Hi yoyodapro,

that could be more intersting: Calculating Satoshi's coins https://bitcointalk.org/index.php?topic=5347791.0

yoyo; yeah take a look at ADAB's post.  You will quickly realize why it's not a fair and equitable pool idea and to make any money you probably have to buy some "sketchy" tokens and their main focus is on probable Satoshi mined coins.

If the kangaroo pool is kept private, meaning only those who ask to join/you trust, then you could use the built in server/client in JLPs original Kangaroo program. The only drawback to a pool for Kangaroo is the overhead that would be created, however, you could break the overall range into smaller chunks to minimize the overhead.

I think the overall idea for the kangaroo pool is a good one, it just needs thought out to minimize overhead. If one wanted to use CPU only, with a python script, that would be easier to help minimize the overhead. The pros: minimize overhead easier, most everyone has a CPU. The cons: it will be slower than GPU version but if enough people joined, that could close the gap in search time.

[yoyodapro]

Hey all!
...

Working together we could all solve this program relatively quickly.

Thoughts?

Hi yoyodapro,

that could be more intersting: Calculating Satoshi's coins https://bitcointalk.org/index.php?topic=5347791.0

yoyo; yeah take a look at ADAB's post.  You will quickly realize why it's not a fair and equitable pool idea and to make any money you probably have to buy some "sketchy" tokens and their main focus is on probable Satoshi mined coins.

If the kangaroo pool is kept private, meaning only those who ask to join/you trust, then you could use the built in server/client in JLPs original Kangaroo program. The only drawback to a pool for Kangaroo is the overhead that would be created, however, you could break the overall range into smaller chunks to minimize the overhead.

I think the overall idea for the kangaroo pool is a good one, it just needs thought out to minimize overhead. If one wanted to use CPU only, with a python script, that would be easier to help minimize the overhead. The pros: minimize overhead easier, most everyone has a CPU. The cons: it will be slower than GPU version but if enough people joined, that could close the gap in search time.

WP; I took a look at ADAB's post and it didn't really pique my interest.

The pool would have to be on an invitation basis only as it would require opening up ports and such to the public. I can facilitate quite a large overhead with my current hardware, I would ideally like to create a website for users of the pool to be able to monitor their stats as well.

The only problem I foresee is people leaving then rejoining the pool; power failure, working on another project, gaming, etc. It could result in the addition of Kangaroos and the creation of more overhead. we may have to split up the ranges and agree to solve them for a specified time.

[WanderingPhilospher]

The only problem I foresee is people leaving then rejoining the pool; power failure, working on another project, gaming, etc. It could result in the addition of Kangaroos and the creation of more overhead. we may have to split up the ranges and agree to solve them for a specified time.

Exactly. Smaller ranges could work to help minimize the overhead. If running smaller ranges for x amount of time and not allow rejoins, would minimize the overhead.

You could also use the save kangaroos to server (if powerful enough server CPU/RAM) to eliminate overhead.

You could also run x amount of members on Tame only. I mean once you find one Wild DP, it's collision counterpart, the Tame, is in the range somewhere.

A BSGS pool might be better. I've always imagined a central server CPU to run the baby steps and multiple GPUs/CPUs running the giant steps. So the central server stores the baby steps and then the pool members run the giant steps with a GPU or CPU. And as you know, running BSGS you can run multiple keys and save time on having to rerun the baby steps; saving lots of time overall.

[yoyodapro]

I am willing to use a 24 core cpu and 64GB of RAM to facilitate the operation of this pool if running at smaller ranges, would that suffice?

[yoyodapro]

A BSGS pool might be better. I've always imagined a central server CPU to run the baby steps and multiple GPUs/CPUs running the giant steps. So the central server stores the baby steps and then the pool members run the giant steps with a GPU or CPU. And as you know, running BSGS you can run multiple keys and save time on having to rerun the baby steps; saving lots of time overall.

BSGS would be the way to go honestly, I would just have to find the people willing to help me modify the code of the Bitcrack PoW program and we may be able to pull this off!

[yoyodapro]

I have working public pool for kangaroo, if anyone would like to Join please PM me for more info!

Also, @WanderingPhiloshper I figured out a way to solve the issue of people leaving and rejoining. All the Kangaroos will be reported and recorded by the server. anyone can leave and join as they wish.

[NotATether]

In my free time, I'm planning to build a PoW server + combined methods for searching from other projects, from scratch once I'm finished with my current (private, unrelated to private keys) project, given BitCrack is MIT licensed of course you can expect me to release the source. The GPU version needs some more tuning esp. the OpenCL version if we are to see any serious usage of these programs.

Also things that haven't been seen before like WIF character matching are very fascinating to see a working (as well as fast!) implementation for.

On the running side of things I am not actively brute-forcing right now, so no point in me actually running this program except maybe for debugging.

[yoyodapro]

Please let me know if I can do anything to assist on your project!

[NotATether]

Please let me know if I can do anything to assist on your project!

Well the good news about this is now that I finally have access to Vast.ai rigs I can finally do my testing without going around constantly knocking on people's doors to borrow their GPUs.

Also this project (well, a very similar variant at least that involves mining) is sponsored by my employer so I should have no problem getting funding for this project, they can also provide some of the bigger clusters to me for free if I need them for testing.

But yeah I'll be happy to let you know if I need anything from you, particularly source.

[dlystyr]

I actually wondered with regards to TTD's 64's pool (I use btw). I am not saying this is happening at all, unlikely but think of the scenario

We mine to a pool like TTD. in the background TTD is receiving back all addresses and private keys. They could potentially have a bloom filter with a list of all addresses with a balance. checking every key against that. Basically making a cracking pool. I know the odds are still astronomical but it could be done. but would it ever be profitable? searching for more keys than just a single puzzle tx?

I am not condoning this btw, I would never steal, it's just a theory.

[BitcoinADAB]

I actually wondered with regards to TTD's 64's pool (I use btw). I am not saying this is happening at all, unlikely but think of the scenario

We mine to a pool like TTD. in the background TTD is receiving back all addresses and private keys. They could potentially have a bloom filter with a list of all addresses with a balance. checking every key against that. Basically making a cracking pool. I know the odds are still astronomical but it could be done. but would it ever be profitable? searching for more keys than just a single puzzle tx?

I am not condoning this btw, I would never steal, it's just a theory.

If they http://www.ttdsales.com/64bit/login.php are trying to solve #64 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN: It is possible

Other addresses ~#256: It is impossible

[yoyodapro]

I actually wondered with regards to TTD's 64's pool (I use btw). I am not saying this is happening at all, unlikely but think of the scenario

We mine to a pool like TTD. in the background TTD is receiving back all addresses and private keys. They could potentially have a bloom filter with a list of all addresses with a balance. checking every key against that. Basically making a cracking pool. I know the odds are still astronomical but it could be done. but would it ever be profitable? searching for more keys than just a single puzzle tx?

I am not condoning this btw, I would never steal, it's just a theory.

If they http://www.ttdsales.com/64bit/login.php are trying to solve #64 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN: It is possible

Other addresses ~#256: It is impossible

The beautiful thing about the built in server functionality of kangaroo, is that you can only search one public key at a time preventing any potentially criminal cracking activity from happening. the pool is currently open, we just need to have the discussion of how to fairly split the 120 prize.

[dlystyr]

I actually wondered with regards to TTD's 64's pool (I use btw). I am not saying this is happening at all, unlikely but think of the scenario

We mine to a pool like TTD. in the background TTD is receiving back all addresses and private keys. They could potentially have a bloom filter with a list of all addresses with a balance. checking every key against that. Basically making a cracking pool. I know the odds are still astronomical but it could be done. but would it ever be profitable? searching for more keys than just a single puzzle tx?

I am not condoning this btw, I would never steal, it's just a theory.

If they http://www.ttdsales.com/64bit/login.php are trying to solve #64 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN: It is possible

Other addresses ~#256: It is impossible

The beautiful thing about the built in server functionality of kangaroo, is that you can only search one public key at a time preventing any potentially criminal cracking activity from happening. the pool is currently open, we just need to have the discussion of how to fairly split the 120 prize.

This is what I was meaning. It's a fun idea. I have a couple of 3070's id be tempted to put towards a puzzletx

[yoyodapro]

Send me a message if you want to join the pool!

[bigvito19]

So why did you redirect me to use this then?

https://github.com/iceland2k14/Kangrand

[yoyodapro]

So why did you redirect me to use this then?

https://github.com/iceland2k14/Kangrand

Kangrand uses a faster multiplication thats still safe, ive tested it on all known addresses on the puzzle list and it finds them much faster than the original JLP Kangaroo.

[WanderingPhilospher]

So why did you redirect me to use this then?

https://github.com/iceland2k14/Kangrand

Kangrand uses a faster multiplication thats still safe, ive tested it on all known addresses on the puzzle list and it finds them much faster than the original JLP Kangaroo.

I do not see a different (nor faster multiplication) that iceland has builtin/using in his code. All I see is a start stop and a random bit addition.