Topic: New 64 Bit Random Search Pool Project (Read 367 times)

You could just say uploading .exe to GitHub repository (instead of Mediafire or similar website) could give few people false sense of security (since few people treat GitHub as safe place to download software directly from the developer).


Alternatively you could provide AppImage file which should work for most linux distro.

P.S. Nvidia GPU popular among Linux users becuase it offer better price/performance and exclusive feature (such as CUDA which frequently used on heavy computer science software).

I actually trust Mediafire and co. less than other platforms because there's an abundance of malware on there as a result of it being used to host piracy warez.


Can confirm.

---

Basically, it's in our interest to open-source the 64-bit random pool code so that Linux users can run it (you won't believe how many Linux users got nvidia cards attached despite the poor graphics support). I think the sensitive parts are limited to a few lines of code and variables, I'll see if we can just feed that information through a makefile and #define constants to hide those parts.

Mediafire is an example, sites like that are for sharing any type of files including .exe files such as yours while github is first and foremost a "code" sharing platform even though it has no restrictions on file types being uploaded.

I was addressing you and NF, in the same post; he mentioned "giving more credibility" if x y and z compiled it.

I have no issues hanging it anywhere as there is no malicious code in it. I do not know about mediafire, can you elaborate on the differences vs github?

I never said such a thing and that is not what open source means.

Being open source means anyone can see the code and compile it for themselves if they choose to. Otherwise trusting X over Y with an already complied binary is the same problem all over again no matter who X and Y are or how much merit they have!
For example do you think I run Electrum because I trust Thomas. V.? Absolutely not. I use it because I can see every single line of code and can compile it myself for my own use.

Bottom line is that there was a big elephant in the room that needed to be addressed and I would have probably never said anything if the .exe was uploaded anywhere else like mediafire instead of github.

None of the software does an auto pay out. That will all be done manually.

If you know what the pool is about and understand how the client works in its original form and how the actual cracking software works in its original form, you can conclude how easy it would be to manipulate work done, i.e. your percentage of work done to receive more than your fair share or flat out take the private key and claim all the BTC for yourself.

Some people have already tested the programs. I can see how many people use a different cracking software to try and run with the client software. But without the version on github, they can run their program all day but receive zero credit because it is "fake" work/not validated. That is because there are 2 fail safes built into the software that detect bad actors and does not give them credit. One on the client side and one on the cracking side. If either are exposed, then the pool is worthless.

If you have ever ran TDs 64 bit pool and actually watch what is going on when your machine is running the program, which by the way, it is also closed course (hmmmm, I wonder why), you can see the vulnerabilities in it. But you have to pay attention...

I will discuss options with NotATether in private to see if their is a viable solution.

Clearly. I hope that I didn't offend you, but I've learned to be very careful with what I install/run.
It's not only about merit, it's also about the fact he's older here, more active, I interacted more with him than you... and higher ranked by the forum.
Usually the lower the rank, the higher the chance it does something fishy. It doesn't mean that you did or you will do that, clearly. It's just chances and numbers.

As I said, a higher rank can give more credibility to everything and attract more people to the project. Whether you do that or not, it's entirely your choice.



That's good to know. I'm still a bit wary about the client though.

Alright, to touch on your comments more. I get what you are saying and it is what it is. But I know you are an intelligent person pooya, and if you would just think about things regarding this thread and the nature of the pool, I would hope you would understand why it has to be closed source. There are details in the first post that elude to the "why" if you read it closely.

Trust is a serious thing. It is earned, I get that. But that works both ways. Why would I trust you or NotATether with the source code? Because maybe if you compile it people will be more receptive because you have x number of merit? Nah. Who's to say you wouldn't show it or give it to someone? Or who says you won't take the code and tweak it for your own benefit?

Trust...maybe I can put my own spin on that. People who do join the pool can trust and know that there is only one person who has the source code and it will not get passed from person to person, and maybe they can rest easier knowing that you or someone else who I could possibly give the code to, didn't pass it on to their friend, and their friends friend, etc. and one of those persons manipulated the code for their own benefit.

The bottom line, I am the only one with the source code. I have tried to think of every angle to keep someone from manipulating the pool and taking away from people who are actually participating in the pool.

Again, it's not about the money for me. It's about the concept. About doing something that mostly everyone says can't be done or will take a long time.

I have people who will vouch for me when it comes to being genuine. I send people eth/BTC just for helping out with things; even though they didn't expect it, because I know time is precious for everybody. Just last night, I tried to send a brilliant programmer some eth just for chatting with me for 30 minutes or so about how their particular program works and why they felt another program tasked the CPU more than this other one...just for sharing their thoughts and listening to mine. So yeah, it's not about the money for me. As Doc Holliday said, "It's about the reckoning." lol

People will make a choice to join the pool and run the program, or they won't.  But I at least hope they understand why it has to be closed source and won't trust me any less just because a few people with a lot of merit say I might as well keep it all, or lump me in with some individual from another project, etc.

And this is your choice, if you do not join because I don't have enough numbers by my merit, that is fine. But I will leave you with this, just because you sit in a garage, doesn't mean you're a car.

In fact I'm the one who modified and compiled the Kangaroo #120 server (more details in the discord server linked in the OP)

I think that if it would be you at least compiling the source it would give more credibility to the project (then I may even consider joining in when I could, although my NVidia card is on a laptop).

I'm working with the OP and two other people in our group DM on discord - I'll ask the other two if they've seen the source (@yoyodapro is the one compiling so he should at least know about it).

Well this is a closed source .exe file and the fact that it is uploaded to github doesn't mean it is safe to run. OP might as well be keeping 100% of any puzzle that the users may solve or worse the file could be doing a similar thing to the other puzzle solver (Large Bitcoin Collider) and execute any arbitrary scripts on users computers to do whatever...

Highly unlikely it would be in the 8 range. So far with all the found keys there have been no duplicates. Beginning with 137 only 8 and B have been used, therefore if anything it's more than likely in either 9, A, C, D, E, F ranges.

1378
134E
124A
126C
135D
125D
136D
137B
1349
124E
126E
126A
127E
1269
127F
137

Yeah, it would be our luck everyone sticks to the C D E F ranges and the key is in the 8 range lol

I'll make a 2-of-4 multisig wallet and each of you can get a key (the fourth person being dlystyr)


zahid888 exhausted part of a range IIRC and didn't find anything, I think you'll end up just wasting ports, than when everybody's throwing their hashpower at the full range.

Since this proof of concept project does offer a reward, .04 BTC for the key finder, I've been thinking about opening different ports up for different ranges.

That way people can search in whichever range they feel the key is in.

I'm willing to do 8, one for each top range.

Example:

port 80 = 800...8FF
port 81 = 900...9FF

all the way down to

port 87 = F00...FFF

What say you?

Or at least 2 ports, 1 for 800...BFF and 1 port for C00...FFF, since most people think the key lies in the C to F range.

Well I am not sure who would hold the "developer fee". I'm not interested in the money to be honest; for me it's about the challenge, the proof of concept.
I don't want to take money out of people's pockets for helping out in the hunt. If there is to be a developer fee, I'll gladly donate 2% of my earnings so all the hunters out there can keep hunting and not worry about fees.

If we ever move forward out of proof of concept, maybe then everyone can discuss what they deem as fair for any maintenance fees such as server costs, domain names, etc.

I agree, that or 0.5% from all users as a developer fee to contribute towards hosting, development, etc.

@WanderingPhilospher We should probably keep 2% of the remaining funds after the privkey finder bounty is accounted for so that we have (at least a little) funding for maintaining projects like this.

Yeah, well I doubt that as many have tried modding bitcrack to work properly with AMD cards / openCL. But hey, who knows, maybe someone knows of a version that actually works.

Right, it uses CUDA. From what I've read, not even experienced programmers have created a reliable "bitcrack" using openCL or openCL coupled with AMD cards. If someone knows of a program that actually works and actually finds keys, I will look into that program to see if we can adapt it for the pool

Thank you for the interest, but at this time, only Nvidia cards work with the program 

Sounds cool, I'm in! Will set it up asap when I get around to doing that   (prob. on RX5700XT)
BTW: OC helps? I run that card slightly undervolted and underclocked when mining Ethash tbh., since it makes little difference in hash & big difference in power draw. Does it make a significant difference in your algorithm for the 32BTC challenge? Not sure how exactly that operates, tbh. since I was out of the loop on this challenge for a lot of years 

This pool is great for all types of setups but works really well for the person with only 1 or 2 GPUs as well. Even smaller and older cards like a GTX 1060 3GB or 6GB. So if you have some of the older 1060 3GB cards laying around collecting dust, point them to the pool and let them do work.  Small and older cards get through a range just as fast as a RTX 3090 so you will receive the same credit.

If you are a gamer, point your gaming rig at the pool when not in use.

If you are a miner, point your rig at the pool for a few minutes each day.

The more GPUs we have running, the faster we check every range and start going back through the ranges!

Reserved for OP/stats...
as of 18 Sep:

We have the same pool running, but with a new client and cracking program.

Come see the new thread:  https://bitcointalksearch.org/topic/m.57985360




A new project to test bitcoin's key security attacking the BTC challenge. You can read more about the challenge here:
https://bitcointalksearch.org/topic/bitcoin-challenge-transaction-1000-btc-total-bounty-to-solvers-updated-5218972

This project is considered a proof of concept, and we are testing the concept now.

Information links:
Discord server
https://discord.gg/5CyApZHgUu
Discord channel
https://discord.com/channels/871109371805962240/879196557067558913
Github
https://github.com/WanderingPhilosopher/64-Bit-Random-Pool

We are also working on a website to show live, real-time stats (in works now).

We have created a random searching pool in search of the #64 BTC challenge...in search of .64 bitcoin.

How is this pool different than TDs 64 bit pool?
TD has a great pool. The entire 64 bit range is broken up into 2^27 ranges, each range is 2^36 bits in size.
Users help search and complete each range in its entirety. Meaning once connect to the pool and run your rig,
you have to search a complete 2^36 bit sized range. The idea is a 100% key by key search. Hopefully the key
is found before reaching the 50% mark.

This pool is different. I have broken the entire 64 bit range into 2^44 ranges. Larger ranges than the above,
but we will NOT be searching every key sequentially. Once connected to the pool, you will be assigned a range.
Your GPU will generate random points throughout the range and then start searching for the private key in that
range. Once started, your GPU will check x amount of keys or run for x amount of time. I have it currently set
up that the maximum amount of time a single GPU will be in a range is 30 seconds. So your GPU gets assigned a range,
jumps in the range and generates random starting points, starts searching, runs for x amount of keys or 30 seconds,
whichever happens sooner. This way we are going in and out of ranges and at least searching in every possible range
within a limited time frame.

Depending on how many people/GPUs join the pool, we will search in every possible range in x days.
Example:
if we have 100 GPUs running 24/7
each GPU would check 2,880 ranges a day [1,440 minutes in a day, 2 ranges per minute (1 range every
30 seconds)]
2^19 ranges divided by 288,000 (100 GPUs x 2,880 ranges per day) = 1.82 days
every 1.82 days we will have searched every possible range
if we have 200 GPUs running 24/7 = every .91 day we will have searched every possible range

Example of ranges:
8000000000000000
80000FFFFFFFFFFF

8000100000000000
80001FFFFFFFFFFF

8000200000000000
80002FFFFFFFFFFF

all the way to

FFFFF00000000000
FFFFFFFFFFFFFFFF

How can you join?

Download the 2 files (discord channel) or at https://github.com/WanderingPhilosopher/64-Bit-Random-Pool/releases .
Place them in the same folder.
Create a batch file such as:

Client.exe -d 0 -name username

If you have multiple GPUs on a single PC/rig, use the -d flag to signify which GPU to use. -d 0 for GPU 0, -d 1 for GPU 1, etc.

Replace the -name username with your actual username, such as for me, -name wanderph
I wanted to be able to use a BTC address but the database is case insensitive and at this time, that won't work
But please only use one username whether you have 1 GPU or 1,000 GPUs. Keep the username the same.
Example if using two GPUs:
GPU 0 = Client.exe -d 0 -name wanderph
GPU 1 = Client.exe -d 1 -name wanderph

If you have multiple GPUs, it is better to run each one on a separate/different instance versus running them together. If you
have 2 GPUs, let them run the program separately, it helps the pool check each range quicker and gives you credit for 2 ranges
versus 1 range.

The username is how the program tracks how many ranges you have been assigned and completed. This is IMPORTANT because this is
how we know who to pay and how much to pay them.
Users will be paid based on their work. Your total ranges checked divided by total ranges checked equals your payout.
Example:
You checked 125,000 ranges and it took us 1,000,000 ranges checked to find the key then your amount would be
125,000 divided by 1,000,000 = .125 percent of ranges checked. Now multiply that by the amount of BTC we will find, .60
so your BTC payout would be .125 multiplied by .60 = .075 BTC.

Wait, what? .60 ?? I thought it was for .64 BTC? I am glad you are paying attention! .04 will go to the user who
finds the private key. Yes, the program allows me to see who actually found the key. So overall, the pool will split, based on
amount of work each user does, .60 BTC and the private key finder will get .04, in addition to their equal share. So if user
is owed .055 BTC based on their work, and they find the key, they will get .055 + .04 = .095 BTC. So make sure you run your
GPUs as often as you can.

While we are searching for the key, you can message me your BTC address so I will have a record of it when we do find the key!
Once we find the key, I will message everyone who participated and sent me their BTC address to verify the address is correct.

And that's pretty much it. The who why when what.

The idea is if we visit every range every 1-2 days, the odds of us finding the key will be increased versus searching every range,
key by key. TDs pool has been operational for some time, and it's like any type of pool, it depends on how much hashing power
is pointed at it that determines progress. That pool has 134,217,728 ranges to search through and they are a little over 10% completed.
Where as this pool will be in the actual range the private key lies in, every x amount of days, depending on hashing power pointed at
the pool.

For now, this is just open to Windows users with Nvidia GPUs. Once I can figure out/precompile for Linux users, I will post.

I am sure I will add to or edit this as things change.

I have ran 2 days of tests with the server and client program without a hitch, but that was with limited GPUs running. So if
some glitch does occur, bare with me and I'll get it fixed.

Kudos go to:
Jean Luc Pons and Telariust for original and modded Vanity Search.
I modded their work to create random points in specific ranges, each and every time.
Etar / Etayson for the client and server program groundwork.
I made a few tweaks to his program but really great work by him!
@dlystyr for his python experience and ability to write a python script in 3 seconds.
Also for his "ear", to listen to some of my crazier ideas regarding this BTC challenge.
@yoyodapro for his motivation and for setting up the discord channel to bring us all together.
And helping me test, work out any bugs.
and @bigvito for hitting me up every few weeks to work on the random feature until I finally
said dang, alright lol! But I got the idea while building him out a random version.

Stay tuned to the channel/here for important updates and stats.

This project will help us determine how random range and points compares to range by range sequential key searches and will give us data to use
in moving forward to keys #66, 67, 68, etc.

WP