A minimalist UTXO tracker for HD wallets. The goal is to provide a flexible, .NET-based UTXO tracker for HD wallets. The explorer supports P2SH, P2PKH, P2WPKH, P2WSH, Taproot and multi-signature derivations.
It works on a pruned node and indexes only what you track.
This explorer is not intended to be exposed to the internet; it should be used as an infrastructure tool for tracking the UTXOs of your own service.
You start by Creating a wallet (hot wallet), or Tracking a derivation scheme (cold wallet).
Second, Get the next unused address to get paid.
Listen to events through Polling, Long Polling or Web Sockets.
You can then List transactions, List UTXOs, or Create a PSBT for your app to sign.
When the transaction is signed, Broadcast it.
You can also track multiple derivation schemes or individual addresses by Creating a group.
It currently supports the following altcoins:
Read our API Specification.
Use --postgres flag to setup the connection string. See schema documentation.
Read our API Specification.
If you are using Bitcoin core default settings:
On Powershell:
On Linux:
Then to run:
On Powershell:
On Linux:
Example, if you have ltc node and btc node on regtest (default configuration), and want to connect to them: (see documentation for other options in the postgres connection string)
./run.sh --chains=btc,ltc --network=regtest --postgres "User ID=postgres;Host=127.0.0.1;Port=5432;Database=nbxplorer"
Check the API documentation, you can then use any client library:
Here is a small C# example showing a 2-2 multisig with Alice and Bob that you can run on 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 2022 (17.8.0). 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 2022 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 --[crypto]startheight to a specific height of your choice, then run it again with --[crypto]rescan, e.g. ./run.sh --chains=ltc --ltcrescan --ltcstartheight=101
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:
__cookie__:0ff9cd83a5ac7c19a6b56a3d1e7a5c96e113d42dba7720a1f72a3a5e8c4b6c66__cookie__ part of your cookie file into username (whatever comes before the :)Basic will be your Base64 encoded username and password.You can also disable authentication in NBXplorer for testing with the --noauth parameter. This makes testing quicker:
--noauth command line argument or the environment variable NBXPLORER_NOAUTH=1You 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
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.
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 to
Support has been added for RabbitMq as a message broker. Currently 2 exchanges supported;
Filters can be applied on the client by defining routing keys;
For transactions;
transactions.# to get all transactions.transactions.[BTC].# to get all [Bitcoin] transactions.transactions.[BTC].confirmed to get only confirmed [Bitcoin] transactions.transactions.[BTC].unconfirmed to get only unconfirmed [Bitcoin] transactions.transactions.*.confirmed to get all confirmed transactions.transactions.*.unconfirmed to get all unconfirmed transactions.For blocks;
blocks.# to get all blocks.blocks.[BTC] to get all [Bitcoin] blocks.To activate RabbitMq mesages you should add following settings to your config file or on the command line.
If you use the Configuration file to setup your NBXplorer options:
rmqhost= RabbitMq host name rmqvirtual= RabbitMq virtual host rmquser= RabbitMq username rmqpass= RabbitMq password rmqtranex= Name of exchange to send transaction messages rmqblockex= Name of exchange to send block messages
Payloads are JSON and map to NewBlockEvent, NewTransactionEvent in the NBXplorer.Models namespace. There is no support in NBXplorer client for message borkers 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.
For configuring serializers you can get crypto code info from BasicProperties.Headers[CryptoCode] of RabbitMq messages or UserProperties[CryptoCode] of Azure Service Bus messages. Examples can be found in unit tests.
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
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)
How to add support to my altcoinFirst 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.
What about alternatives to NBXplorer?Electrum wallet requires an unpruned node with indexing, which is space-intensive and may be difficult to sync.Electrum wallet only supports a single cryptocurrency on a single server. If you are an exchange, you would end up running multiple versions of barely maintained Electrum instances.Personal Electrum Server supports only a single wallet.Electrum protocol is cumbersome for HD wallets.Bitcoin Core RPC is inflexible and difficult to use. It also scales poorly when a wallet has too many addresses or UTXOs.Bitcoin Core RPC supports multiple wallets but isn't designed to handle thousands of them. Having too many wallets will not scale.This project is under MIT License.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4