A minimalist UTXO tracker for HD Wallets. The goal is to have a flexible, .NET based UTXO tracker for HD wallets. The explorer supports P2SH,P2PKH,P2WPKH,P2WSH and Multi-sig derivation.
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 has a bunch of feature:
- Can pass arguments via environment variable, command line or configuration file
- Automatically reconnect to your node if the connection goes temporarily down
- An easy to use REST API
- Persistence (via in-file no-SQL datbase called DBreeze)
- Connect via RPC to broadcast transaction instead of using the P2P protocol like this example
- Connect via RPC to your trusted node to get the proper fee rate.
- Altcoin support
- Huge test suite
- Pruning of transaction data (in practice, we don't need to save the whole transaction, only the spent outpoint and received coin for the wallet)
- Multi-wallet
- Flexible address generation schemes (multisig, segwit, legacy etc...)
- Pruning for big wallets (Removal of tracked transaction which do not impact the resulting UTXO set)
It currently the following altcoins:
- BCash (also known as Bitcoin Cash)
- BGold (also known as Bitcoin Gold)
- Bitcoin
- Bitcore
- ColossusXT
- Dash
- Dogecoin
- Feathercoin
- Gobyte
- Groestlcoin
- Litecoin
- Monacoin
- Monoeci
- Polis
- Ufo
- Viacoin
Read our API Specification, or our the internal design of NBXplorer.
- Install .NET Core SDK v2.1.4 (with patch version >= 402)
- 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
Check the API documentation, you can then use any client library:
- NBXplorer.NodeJS for NodeJS clients.
- NBXplorer.Client for .NET clients.
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 in
C:\Users\<user>\AppData\Roaming\NBXplorer\<network>\settings.config
On linux or mac:
~/.nbxplorer/<network>/settings.config
The default configuration assumes mainnet with only btc chain supported, and uses the default settings of bitcoind.
You can change the location of the configuration file with the --conf=pathToConf command line argument.
Please note that NBXplorer uses cookie authentication by default. If you run your Bitcoin/Litecoin/Dash nodes using their daemon (like bitcoind, litecoind or dashd), they generate a new cookie every time you start them, and that should work without any extra configuration.
If you run the node(s) using the GUI versions, like Bitcoin\Litecoin\Dash Core Qt with the -server parameter while you set the rpcusername and rpcpassword in their .conf files, you must set those values for every crypto you are planning to support.
See samples below.
You should use run.ps1 (Windows) or run.sh (Linux) to execute NBXplorer, but you can also execute it manually with the following command:
dotnet run --no-launch-profile -p .\NBXplorer\NBXplorer.csproj -- <parameters>
If you already have a compiled DLL, you can run the executable with the following command:
dotnet NBXplorer.dll <parameters>
Running NBXplorer HTTP server on port 20300, connecting to the BTC mainnet node locally.
--port=20300 --network=mainnet --btcnodeendpoint=127.0.0.1:32939
Running NBXplorer on testnet, supporting Bitcoin, Litecoin and Dash, using cookie authentication for BTC and LTC, and RPC username and password for Dash, connecting to all of them locally.
--chains=btc,ltc,dash --network=testnet --dashrpcuser=myuser --dashrpcpassword=mypassword
The same settings as above, for example export NBXPLORER_PORT=20300. This is usefull for configuring docker.
You can use the dotnet command which is part of .NET Core to run NBXplorer. To run from source you must have the .NET Core SDK installed e.g.
dotnet run NBXplorer.dll
As described above you may add configuration parameters if desired.
If you have a compiled version of NBXplorer you should have a file in your build folder named NBXplorer.dll. This cannot itself be directly executed on the command line as it is not an executable file. Instead we can use the dotnet runtime to execute the dll file.
e.g.
dotnet NBXplorer.dll
This tool will only start scanning from the configured startheight. (By default, the height of the blockchain during your first run)
This means that you might not see old payments from your 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.
Postman is a useful tool for testing and experimenting with REST API's.
You can test the NBXplorer API quickly and easily using Postman.
If you use cookie authentication (enabled by default) in your locally run NBXplorer, you need to set that up in Postman:
- Run NBXplorer and locate you cookie file (NBXplorer will generate a new Cookie file each time it runs in its default data folder)
- In Postman create a new GET API test
- In Authorization select Basic Auth, you should see 2 input boxes for username and password
- Open your cookie file with a text editor e.g. Notepad on windows . You should see a cookie string e.g.
__cookie__:0ff9cd83a5ac7c19a6b56a3d1e7a5c96e113d42dba7720a1f72a3a5e8c4b6c66 - Back in Postman paste the
__cookie__part of your cookie file into username (whatever comes before the :) - Paste the Hex string (after the : ) into the password box
- Click the Update Request button in Postman - this will force Postman to generate the correct HTTP headers based on your cookie details
- You should now see a new entry in the Headers section with a Key of Authorization and Value of Basic xxxxxxxxx where the string after
Basicwill be your Base64 encoded username and password. - Enter the API URL you are going to test
You can also disable authentication in NBXplorer for testing with the --noauth parameter. This makes testing quicker:
- Run NBXplorer with the
--noauthparameter - In Postman create a new GET API test
- In Authorization select No Auth
- Enter the API URL you are going to test
You are now ready to test the API - it is easiest to start with something simple such as the fees endpoint e.g.
http://localhost:24444/v1/cryptos/btc/fees/3
this should return a JSON payload e.g.
{ "feeRate": 9, "blockCount": 3 }
Support has been added for Azure Service Bus as a message broker. Currently 2 Queues and 2 Topics are supported
- New Block
- New Transaction
- New Block
- New Transaction
Filters should be applied on the client, if required.
To activate Azure Service Bus Mesages you should add an Azure Service Bus Connection string to your config file or on the command line.
- To use queues you should specify the queue names you wish to use
- To use topics you should specify the topic names you wish to use
You can use both queues and topics at the same time.
If you use the Configuration file to setup your NBXplorer options:
asbcnstr=Your Azure Service Bus Connection string
asbblockq=Name of queue to send New Block message to
asbtranq=Name of queue to send New Transaction message to
asbblockt=Name of topic to send New Block message to
asbtrant=[Name of queue to send New Transaction message toPayloads are JSON and map to NewBlockEvent, NewTransactionEvent in the NBXplorer.Models namespace. There is no support in NBXplorer client for Azure Service Bus at the current time. You will need to use the Serializer in NBXplorer.Client to De-serialize the objects or then implement your own JSON de-serializers for the custom types used in the payload.
If you receive a 401 Unauthorized then your cookie data is not working. Check you are using the current cookie by opening the cookie file again - also check the date/time of the cookie file to ensure it is the latest cookie (generated when you launched NBXplorer).
If you receive a 404 or timeout then Postman cannot see the endpoint
- are you using the correct Port ?
- are you running postman on localhost ?
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 addresses, and the UTXO of an 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.