You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| gui | string | Information to identify which app, tool or product is using the API, e.g. `AtomicDEX iOS 1.0.1`. Helps developers identify if an issue is related to specific builds or operating systems etc. |
22
-
| netid | integer | Nework ID number, telling the AtomicDEX-API which network to join. 7777 is the current main network, though alternative netids can be used for testing or "private" trades as long as seed nodes exist to support it. |
22
+
| netid | integer | Nework ID number, telling the AtomicDEX-API which network to join. 8762 is the current main network, though alternative netids can be used for testing or "private" trades as long as seed nodes exist to support it. |
23
23
| passphrase | string | Your passphrase; this is the source of each of your coins private keys. [**KEEP IT SAFE!**](https://www.youtube.com/watch?v=WFpxVbTqhB8)|
24
24
| rpc\_password | string | For RPC requests that need authentication, this will need to match the `userpass` value in the request body. |
25
25
| allow\_weak\_password | boolean | Optional, defaults to `false`. If `true`, will allow low entropy rpc\_password. If `false` rpc\_password must not have 3 of the same characters in a row, must be between 8-32 characters in length, must contain at least one of each of the following: numeric, uppercase, lowercase, special character (e.g. !#$\*). It also can not contain the word "password", or the chars `<`, `>`, or `&`. |
26
26
| dbdir | string | Optional, defaults to a subfolder named `DB` in the path of your `mm2` binary. This path will store the AtomicDEX-API database data. |
27
27
| rpcip | string | Optional, defaults to `127.0.0.1`. IP address to bind to for RPC server. |
28
28
| rpcport | integer | Optional, defaults to `7783`. Port to use for RPC communication. |
29
29
| rpc\_local\_only | boolean | Optional, defaults to `true`. If `false` the AtomicDEX API will allow rpc methods sent from external IP addresses. **Warning:** Only use this if you know what you are doing, and have put the appropriate security measures in place. |
30
-
| i\_am\_seed | boolean | Optional, defaults to `false`. Runs AtomicDEX API as a seed node mode (acting as a relay for AtomicDEX API clients). Use of this mode is not reccomended on the main network (7777) as it could result in a pubkey ban if non-compliant. On alternative testing or private networks, at least one seed node is required to relay information to other AtomicDEX API clients using the same netID. |
30
+
| i\_am\_seed | boolean | Optional, defaults to `false`. Runs AtomicDEX API as a seed node mode (acting as a relay for AtomicDEX API clients). Use of this mode is not reccomended on the main network (8762) as it could result in a pubkey ban if non-compliant. On alternative testing or private networks, at least one seed node is required to relay information to other AtomicDEX API clients using the same netID. |
31
31
| seednodes | list of strings | Optional. If operating on a test or private netID, the IP address of at least one seed node is required (on the main network, these are already hardcoded) |
32
32
| hd\_account\_id | integer | Optional. If this value is set, the AtomicDEX-API will work in only the [HD derivation mode](/atomicdex/api/v20-dev/hd_wallets_overview/), and coins will need to have a coin derivation path entry in the `coins` file for activation. The `hd_account_id` value effectively takes its place in the full derivation as follows: `m/44'/COIN_ID'/<hd_account_id>'/CHAIN/ADDRESS_ID`|
33
33
| message\_service\_cfg | object | Optional. This data is used to configure [Telegram](https://telegram.org/) messenger alerts for swap events when running using the [makerbot functionality](/atomicdex/api/v20/start_simple_market_maker_bot/). For more information check out the [telegram alerts guide](/atomicdex/api/v20/telegram_alerts/)|
@@ -40,7 +40,7 @@ When running the AtomicDEX API via commandline with the `mm2` binary, some basic
| gui | string | Information to identify which app, tool or product is using the API, e.g. `AtomicDEX iOS 1.0.1`. Helps developers identify if an issue is related to specific builds or operating systems etc. |
79
-
| netid | integer | Nework ID number, telling the AtomicDEX API which network to join. 7777 is the current main network, though alternative netids can be used for testing or "private" trades as long as seed nodes exist to support it. |
79
+
| netid | integer | Nework ID number, telling the AtomicDEX API which network to join. 8762 is the current main network, though alternative netids can be used for testing or "private" trades as long as seed nodes exist to support it. |
80
80
| passphrase | string | Your passphrase; this is the source of each of your coins private keys. KEEP IT SAFE! |
81
81
| rpc\_password | string | For RPC requests that need authentication, this will need to match the `userpass` value in the request body. |
82
82
@@ -92,7 +92,7 @@ We also need to create an MM2.json file in the same directory as the `coins` fil
92
92
The MM2.json configuration commands can also be supplied at runtime, as below:
Replace `YOUR_PASSPHRASE_HERE` and `YOUR_PASSWORD_HERE` with your actual passphrase and password, and then execute the command in the terminal.
@@ -120,9 +120,9 @@ You should see output similar to the following:
120
120
06 10:26:38, atomicdex_gossipsub::behaviour:147] INFO Adding peer 12D3KooWGrUpCAbkxhPRioNs64sbUmPmpEcou6hYfrqQvxfWDEuf to explicit relay list
121
121
06 10:26:38, atomicdex_gossipsub::behaviour:147] INFO Adding peer 12D3KooWEaZpH61H4yuQkaNG5AsyGdpBhKRppaLdAY52a774ab5u to explicit relay list
122
122
06 10:26:38, atomicdex_gossipsub::behaviour:147] INFO Adding peer 12D3KooWAd5gPXwX7eDvKWwkr2FZGfoJceKDCA53SHmTFFVkrN7Q to explicit relay list
123
-
06 10:26:38, mm2_libp2p::atomicdex_behaviour:762] INFO Dialed /ip4/79.228.173.231/tcp/38890
124
-
06 10:26:38, mm2_libp2p::atomicdex_behaviour:762] INFO Dialed /ip4/84.82.76.214/tcp/38890
125
-
06 10:26:38, mm2_libp2p::atomicdex_behaviour:762] INFO Dialed /ip4/69.178.128.39/tcp/38890
123
+
06 10:26:38, mm2_libp2p::atomicdex_behaviour:762] INFO Dialed /ip4/79.228.173.231/tcp/42845
124
+
06 10:26:38, mm2_libp2p::atomicdex_behaviour:762] INFO Dialed /ip4/84.82.76.214/tcp/42845
125
+
06 10:26:38, mm2_libp2p::atomicdex_behaviour:762] INFO Dialed /ip4/69.178.128.39/tcp/42845
126
126
06 10:26:38, mm2_main::mm2::database:26] INFO Checking the current SQLite migration
127
127
06 10:26:38, mm2_main::mm2::database:30] INFO Current migration is 9, skipping the init, trying to migrate
128
128
06 10:26:38, mm2_main::mm2::database:119] INFO migrate_sqlite_database, current migration 9
@@ -137,7 +137,7 @@ If you see something similar, the AtomicDEX API is up and running!
137
137
When using the AtomicDEX API on a VPS without accompanying tools such as `tmux` or `screen`, it is recommended to use [`nohup`](https://www.digitalocean.com/community/tutorials/nohup-command-in-linux) when launching the AtomicDEX-API. This will ensure that the AtomicDEX-API instance is not shutdown when the user logs out.
0 commit comments