monero-project/monero-docs
monero-project/monero-docs
2
1
Fork 0
mirror of https://github.com/monero-project/monero-docs.git synced 2025-01-03 17:40:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add port numbers to mainnet/stagenet/testnet docs

Browse source
This commit is contained in:
Piotr Włodarek 2018-09-25 12:54:34 +02:00
parent cee3a8c12e
commit 1a75a8452e
2 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
docs/infrastructure/networks.md
View file

@ -13,6 +13,12 @@ Mainnet is the only blockchain where XMR units have value.
Mainnet is what people mean by default.
Default TCP ports (listening):
* 18080 - p2p network
* 18081 - JSON-RPC server
* 18082 - ZMQ server
## Stagenet
Stagenet is what you need to learn Monero safely.
@ -25,6 +31,12 @@ To get started:
* Get free XMR from [stagenet faucet](http://stagenet.xmr-tw.org:38085/)
* Check the [stagenet block explorer](http://162.210.173.150:8083/)
Default TCP ports (listening):
* 38080 - p2p network
* 38081 - JSON-RPC server
* 38082 - ZMQ server
Stagenet was introduced in March 2018 as part of Monero 0.12.0.0.
## Testnet
@ -42,6 +54,12 @@ To get started:
* Get free XMR from [testnet faucet](https://dis.gratis/)
* Check the [testnet block explorer](https://testnet.xmrchain.net)
Default TCP ports (listening):
* 28080 - p2p network
* 28081 - JSON-RPC server
* 28082 - ZMQ server
## Private Testnet
You can also create your private version of the testnet.

2
docs/interacting/monerod/reference.md
View file

@ -82,6 +82,8 @@ The node and peer words are used interchangeably.
|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------
| `--max-concurrency` | Max number of threads to use for a parallel jobs. The default value `0` uses the number of CPU threads.
| `--prep-blocks-threads` | Max number of threads to use when computing block hashes (PoW) in groups. Defaults to 4. Decrease this if you don't want `monerod` hog your computer when syncing.
| `--fast-block-sync` | Sync up most of the way by using embedded, "known" block hashes. Pass `1` to turn on and `0` to turn off. This is on (`1`) by default. Normally, for every block the full node must calculate the block hash to verify miner's proof of work. Because the CryptoNight PoW used in Monero is very expensive (even for verification), `monerod` offers skipping these calculations for old blocks. In other words, it's a mechanism to trust `monerod` binary regarding old blocks' PoW validity, to sync up faster.
| `--block-sync-size` | How many blocks are processed in a single batch during chaing synchronization. By default this is 20 blocks for newer history and 100 blocks for older history ("pre v4"). Default behavior is represented by value `0`. Intuitively, the more resources you have, the bigger batch size you may want to try out. Example:<br />`./monerod --block-sync-size=500`
| `--bootstrap-daemon-address` | The host:port of a "bootstrap" remote open node that the connected wallets can use while this node is still not fully synced. Example:<br/>`./monerod --bootstrap-daemon-address=opennode.xmr-tw.org:18089`. The node will forward selected RPC calls to the bootstrap node. The wallet will handle this automatically and transparently. Obviously, such bootstraping phase has privacy implications similar to directly using a remote node.
| `--bootstrap-daemon-login` | Specify username:password for the bootstrap daemon login (if required). This considers the RPC interface used by the wallet. Normally, open nodes do not require any credentials.