From b31fa111b4641afecfb24ba80d1e316ec21a8ae6 Mon Sep 17 00:00:00 2001 From: "nicolas.dorier" Date: Fri, 29 Nov 2024 10:00:25 +0900 Subject: [PATCH] Add doc --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index bdd45793..2444d3ea 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,16 @@ 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. +## What about alternatives to NBXplorer? + +1. `Electrum wallet` requires an unpruned node with indexing, which is space-intensive and may be difficult to sync. +2. `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. +3. `Personal Electrum Server` supports only a single wallet. +4. `Electrum protocol` is cumbersome for HD wallets. +3. `Bitcoin Core RPC` is inflexible and difficult to use. It also scales poorly when a wallet has too many addresses or UTXOs. +4. `Bitcoin Core RPC` supports multiple wallets but isn't designed to handle thousands of them. Having too many wallets will not scale. +5. While NBXplorer exposes an API, it also allows you to query the data using the most expressive and flexible language designed for this purpose: `SQL`. + ## Typical usage You start by [Creating a wallet (hot wallet)](https://dgarage.github.io/NBXplorer/#tag/Derivations/operation/GenerateWallet), or [Tracking a derivation scheme (cold wallet)](https://dgarage.github.io/NBXplorer/#tag/Derivations/operation/Track).