A minimalist UTXO tracker for HD Wallets. The goal is to have a flexible, .NET based UTXO tracker for HD wallets. The explorer supports only P2PKH derivation for now but will be able to support more complex generation in near future. (m-n, segwit, p2sh)
This explorer is not meant to be exposed on internet, but should be used as an internal tool for tracking the UTXOs of your own service.
It currently supports:
- Bitcoin
- Litecoin
- Dogecoin
- Groestlcoin
- Dash
- Polis
- BCash (also known as Bitcoin Cash)
- BGold (also known as Bitcoin Gold)
- Monacoin
- Feathercoin
- Ufo
- Viacoin
- Install .NET Core 2.1
- Bitcoin Core instance synched and running (at least 0.16.0).
Read our API Specification.
If you are using Bitcoin core default settings:
On Powershell:
.\build.ps1
On Linux:
./build.sh
Then to run:
On Powershell:
.\run.ps1 --help
On Linux:
./run.sh --help
Example, if you have ltc node and btc node on regtest (default configuration), and want to connect to them:
./run.sh --chains=btc,ltc --network=regtest
Use our image. You can check the sample for configuring and composing it bitcoin core.
If you are on Windows, I recommend Visual Studio 2017 update 3 (15.3). If you are on other platform and want lightweight environment, use Visual Studio Code. If you are hardcore, you can code on vim.
I like Visual Studio Code and Visual Studio 2017 as it allows me to debug in step by step.
NBXplorer supports configuration through command line arguments, configuration file, or environment variables.
If you are not using standard install for bitcoind, you will have to change the configuration file: In Windows it is located on
C:\Users\<user>\AppData\Roaming\NBXplorer\<network>\settings.config
On linux or mac:
~/.nbxplorer/<network>/settings.config
The default configuration assume mainnet with only btc chain supported, and use default settings of bitcoind.
You can change the location of the configuration file with the --conf=pathToConf command line argument.
The same settings as above, for example: dotnet run NBXplorer.dll -- --port=20300 --network=mainnet --nodeendpoint=127.0.0.1:32939.
The same settings as above, for example export NBXPLORER_PORT=20300. This is usefull for configuring docker.
This tool will only start scanning from the configured startheight. (By default, the height of the blockchain during your first run)
This mean that you might not see old payment from you HD key.
If you need to see old payments, you need to configure startheight to a specific height of your choice, then run with again with -rescan.
A better documentation is on the way, for now the only documentation is the client API in C# on nuget.
The ExplorerClient classes allows you to query unused address, and the UTXO of a HD PubKey.
You can take a look at the tests to see how it works.
There is a simple use case documented on Blockchain Programming in C#.
This is easy, from repo directory:
cd NBXplorer.Tests
dotnet test
The tests can take long the first time, as it download Bitcoin Core binaries. (Between 5 and 10 minutes)
First you need to add support for your altcoin to NBitcoin.Altcoins. (See here).
Once this is done and NBXplorer updated to use the last version of NBitcoin.Altcoins, follow Litecoin example.
If you want to test if everything is working, modify ServerTester.Environment.cs to match your altcoin.
Then run the tests.
This project is under MIT License.
Special thanks to Digital Garage for allowing me to open source the project, which is based on an internal work I have done on Elements.
Thanks to the DG Lab Blockchain Team who had to fight with lots of bugs. (in particular kallewoof :p)
Thanks to Metaco SA, whose constant challenging projects refine my taste on what a perfect Bitcoin API should be.