Skip to content

Commit 88d1335

Browse files
MrNaif2018gitbook-bot
authored andcommitted
GITBOOK-87: change request with no subject merged in GitBook
1 parent 5fb8386 commit 88d1335

File tree

2 files changed

+44
-0
lines changed

2 files changed

+44
-0
lines changed

SUMMARY.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@
2424

2525
## Guides
2626

27+
* [Default nodes/your own node](guides/default-nodes-your-own-node.md)
2728
* [One domain mode](guides/one-domain-mode.md)
2829
* [Backups](guides/backups.md)
2930
* [Lightning Network](guides/lightning.md)

guides/default-nodes-your-own-node.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# Default nodes/your own node
2+
3+
You may have a question: which servers does Bitcart use by default? It depends on the coin!
4+
5+
## Default nodes
6+
7+
### BTC-based coins
8+
9+
If using BTC-based coins where we use Electrum or it's forks, it is connected to a network of electrumx/fulcrum servers, which are indexers of the blockchain. It connects to multiple servers, verifying with SPV (Simple Payment Verification) that the results acquired are valid. It is reliable enough and can handle any load. This is the same list you would see if you downloaded Electrum wallet yourself and connected to the network
10+
11+
### Other coins (ETH-based, TRX, XMR)
12+
13+
For other coins we don't have something like electrum existing, and we also don't have a network of blockchain indexers.
14+
15+
That's why for those coins Bitcart daemons require at least 1 full node RPC to be configured. In coins like ETH free RPCs are widespread and have good rate limits. So the defaults will always use some free RPCs which should be good enough for Bitcart to run
16+
17+
{% hint style="info" %}
18+
New since Bitcart v0.9.0.0: it is now possible to use multiple nodes, so if one RPC fails, it will use the next one in the list and so on, allowing to specify as many servers as possible, archieving unbreakable stability
19+
{% endhint %}
20+
21+
{% @github-files/github-code-block %}
22+
23+
Defaults are usually set in docker compose components.
24+
25+
**NOTE**: Since Bitcart v0.9.0.0, seed server feature was launched. Servers are no longer hardcoded in yml files, so in case some RPC breaks, users won't need to update each of their instances, we can edit it in the seed server and the daemon will update links at maximum in 1 hour. This is the default behaviour inside docker deployments now. To disable it, set `COIN_SERVER` to some specific server, just as it was done before.
26+
27+
If you want to view the current list of servers used for each specific coin, you can call seed server directly, for example:
28+
29+
{% embed url="https://seed-server.bitcart.ai/eth" %}
30+
31+
## Your own node
32+
33+
### BTC-based coins
34+
35+
In order to run your own node, first you need to run the actual full node, like [bitcoin core](https://github.com/bitcoin/bitcoin).
36+
37+
Then you need to run an indexer compatible with Electrum protocol, so either [ElectrumX](https://github.com/spesmilo/electrumx) or [Fulcrum](https://github.com/cculianu/Fulcrum) (recommended).
38+
39+
Then you can point Bitcart to it via `COIN_SERVER`. You can force to connect to only your server and not others via `COIN_ONESERVER`.
40+
41+
### Other coins (ETH-based, TRX, XMR)
42+
43+
Just run the full node of the coin you selected, and then set `COIN_SERVER` to the RPC url of your node.

0 commit comments

Comments
 (0)