Ok I am following on the range being too small. I will try with a larger range and see if keyhunt works correctly. It would be helpful to know exactly what the minimum range limit is. So since I did not get the results I expected I held off on doing additional tests. A warning in the console would definitely be helpful if you use a range that is too small. Thanks for the quick response too.

How is the "-r" range supposed to work? I ran a test using keyhunt in address mode but set the range limited to 1:10.

I expected keyhunt to find the first 3 address only and stop searching due to the range I set. keyhunt found the first 3 addresses and more! I was confused why it found more than the first 3 addreses and continued searching past the range that was set?

Test:

./keyhunt -m address -f tests/1to32.txt -r 1:10

Thanks for the update the last .gz you had I think was from September.

This project is 3 years old and has security flaws. I do not recommend re-using it unless your know how to fix the security holes and given you cannot install the software I'm not sure you are up for that task. I advise you to look for another solution, you are wasting your time on this one if you intended to use this to launch your own exchange.

I don't have the proof yet but too many things with this game do not add up.

The game is selling for less than 2$. They need to sell at least 5,000 copies to break even to just recover the cost of the BTC they are giving away. That doesn't cover any of the development costs to create the game.

I think this game was build to hijack high end GPU resources from gaming computers. This is only a theory right now I do not have the proof yet. Let me know if you find anything SirArthur.

Interesting. I will know in a couple hours after bitcoin core is done processing blocks on disk if 0.13.2-addrindex returns the correct balance or not. I sure hope it does or my efforts this far have been a waste of time. Also, thanks for that history, I was not aware of Pieter's contribution and the background of this bitcoin core patch.

Running the nodes is not so much a struggle, its just that I want results now and have been trying a few different configurations.

First off in my journey here I ran the latest bitcoin core 0.15.1 and after 2 or 3 days I had the full blockchain. Played around with some of the RPC calls but found even with that I still can't get the information I needed.

So I did some research and found out about 0.13.2-addrindex. One real fucking pain has been that 0.13.2-addrindex and 0.15.1 have different database versions. Getting the full blockchain I downloaded to work with 0.13.2-addrindex was not a struggle but a time consuming process and I am impatient and want results NOW!

So I've finally got 0.13.2-addrindex on what I think are the last stages. I rebuilt the blockchain so it would work with this version. And configured the bitcoin.conf to enable the address indexing. It took forever for the build indexes on disk step. Finally its been processing blocks on disk and is close to completion.

If this doesn't work out I am going to look into porting NBitcoin.Indexer (github.com/MetacoSA/NBitcoin.Indexer) to use local filesystem storage instead of Azure or look into using NBXplorer (github.com/dgarage/NBXplorer)

So yeah. Hopefully this works out. If not you can see I've got a plan B and C already

Is this code open source and how could I get access? In the first post you have a link to https://svn.cryptoguru.org/ which looks like an SVN server but it requires credentials as you mentioned.

Thanks

Wow that's a great graph.

It is funny, it has an export function but it only gives you a number per day.

It would be nice to get the actual addresses.

There were some database changes, which made this a pain.

I first downloaded the full blockchain using 0.15.1.

I looked more into the 0.15.1 documentation and found this:

Downgrading warning
The chainstate database for this release is not compatible with previous releases, so if you run 0.15 and then decide to switch back to any older version, you will need to run the old release with the -reindex-chainstate option to rebuild the chainstate data structures in the old format.

If your node has pruning enabled, this will entail re-downloading and processing the entire blockchain.


I was going to run two nodes and had setup the addrindex patched node to run on a VM. Due to some disk constraints (speed, capacity) I ended up deciding I would just run the patched addrindex node and use whitebind and whitelist in my bitcoin.conf so nobody but I can connect. You raised a point about vulnerabilities. Do you think the addrindex node is protected if I use whitebind and whitelist?

Also, what about the incorrect results you saw? What did you see and was it from this version: bitcoin-0.13.2-addrindex?

Thanks

I am working on a programming project and there is a version of Bitcoin Core which has functionality I need. Specifically there is a fork of Bitcoin Core v0.13.2 which has address indexing.

The latest version of bitcoin core is 0.15.1 currently so the version I was considering using is a little out of date.

Are there any risks or issues I should be aware of if I was to proceed using the v0.13.2 version?

Thanks

This is great, I hope the momentum keeps going. Thanks for sharing.

He came out on top of this one.