Installing Monero

• Ecosystem installed, its extension enabled and its vault unlocked
• Root on the server, and a non-root user to own the Monero services
• 250 GB of free SSD and headroom — the Monero blockchain grows continuously
• 4 GB RAM free for monerod alone, on top of the platform's own needs
• The purchase code for this product, from your MashDiv dashboard

Initial sync verifies every block. On anything but local SSD it does not finish in a useful amount of time, and once it is running, wallet refreshes go from seconds to minutes — which on this chain means deposits arrive late and withdrawals time out.

sudo apt update
sudo apt install -y wget bzip2

# Replace with the current stable version from getmonero.org
MONERO_VERSION="0.18.3.1"
mkdir -p ~/monero && cd ~/monero
wget "https://downloads.getmonero.org/cli/monero-linux-x64-v${MONERO_VERSION}.tar.bz2"
tar -xf "monero-linux-x64-v${MONERO_VERSION}.tar.bz2"

sudo mv "monero-x86_64-linux-gnu-v${MONERO_VERSION}" /opt/monero
sudo ln -sf /opt/monero/monerod /usr/local/bin/monerod
sudo ln -sf /opt/monero/monero-wallet-rpc /usr/local/bin/monero-wallet-rpc

monerod --version
monero-wallet-rpc --version

The backend holds exactly one RPC username and password — XMR_RPC_USER and XMR_RPC_PASSWORD — and sends it to monerod and to monero-wallet-rpc, and forwards it again as the daemon login when it points the wallet RPC at the daemon.

Give both services the same --rpc-login. Two different logins cannot both work, and the half that fails does so as an HTTP 401 buried in the wallet refresh path, which surfaces as "deposits are not being detected".

data-dir=/home/monero/.bitmonero
log-file=/home/monero/.bitmonero/monero.log
log-level=0

p2p-bind-ip=0.0.0.0
p2p-bind-port=18080

rpc-bind-ip=127.0.0.1
rpc-bind-port=18081
restricted-rpc=false
confirm-external-bind=true

rpc-login=bicrypto_rpc:CHANGE_ME

db-sync-mode=safe
max-concurrency=4
no-igd=true

[Unit]
Description=Monero Daemon
After=network.target

[Service]
Type=simple
User=monero
Group=monero
ExecStart=/usr/local/bin/monerod --config-file=/home/monero/.bitmonero/bitmonero.conf --non-interactive
Restart=always
RestartSec=30

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable --now monerod
sudo journalctl -u monerod -f

curl -s -X POST http://127.0.0.1:18081/json_rpc \
  -H 'Content-Type: application/json' \
  --digest -u bicrypto_rpc:CHANGE_ME \
  -d '{"jsonrpc":"2.0","id":"0","method":"get_info"}'

sudo -u monero mkdir -p /home/monero/monero-wallets

[Unit]
Description=Monero Wallet RPC
After=network.target monerod.service
Requires=monerod.service

[Service]
Type=simple
User=monero
Group=monero
ExecStart=/usr/local/bin/monero-wallet-rpc \
    --rpc-bind-ip 127.0.0.1 \
    --rpc-bind-port 18083 \
    --daemon-address 127.0.0.1:18081 \
    --daemon-login bicrypto_rpc:CHANGE_ME \
    --rpc-login bicrypto_rpc:CHANGE_ME \
    --wallet-dir /home/monero/monero-wallets \
    --trusted-daemon \
    --log-level 1
Restart=always
RestartSec=30

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable --now monero-wallet-rpc

The addon passes an empty password to create_wallet and open_wallet. There is no setting that changes this — XMR_WALLET_PASSWORD is read by no code. If --wallet-dir points at a directory holding wallets some other tool created with a password, the backend cannot open them, and the failure looks like a generic "Failed to open wallet".

Treat the wallet directory as key material. Its file permissions are the only thing protecting every customer's Monero private keys.

XMR_DAEMON_RPC_URL="http://127.0.0.1:18081/json_rpc"
XMR_WALLET_RPC_URL="http://127.0.0.1:18083/json_rpc"
XMR_RPC_USER="bicrypto_rpc"
XMR_RPC_PASSWORD="CHANGE_ME"
XMR_NETWORK="mainnet"

pm2 restart backend

1. Open the Extension Manager. Admin → System → Extension Manager — the page heading is Add-ons & Integrations. On the Blockchains tab (or by searching for Monero) find the Monero Blockchain for Ecosystem Addon card — product ID 54578959 — and click it. Until its licence is activated the card reads Activate and its switch is disabled with the tooltip Activate license first.

   1. The Monero card — click it to open the product page
   2. Its switch stays disabled until the licence is activated

2. Activate the licence. On the product page press Activate License. Paste the purchase code from your MashDiv dashboard, optionally an email address for update notifications, and press Activate License. The screen confirms License Activated! and sends you back to the product page a couple of seconds later. If the server has no outbound access, the License File tab on the same screen takes the licence certificate downloaded from your dashboard instead. Activation writes the machine-bound licence file lic/54578959.lic — the file Troubleshooting points at when the chain refuses to enable with a 403.

   1. Paste the purchase code here
   2. Activate License — then wait for the redirect back to the product page
   3. The offline route, for a server with no outbound HTTPS

3. Install the release. Back on the product page, now licensed, the Overview tab has a release panel. If it offers Install v…, press it; if it says Up to date on a product you have only just licensed, press Check for Updates once, then install whatever it offers. The Releases tab holds the notes for that version — read them first.

   Install downloads the release, verifies it and extracts it over the project root. It runs no migrations, builds nothing and restarts nothing, so finish it from a shell on the server:

   pnpm updator

   That is the finalise chain — stop, dependencies, schema, seed data, frontend build, start. If the panel still says Up to date after the check there is nothing to download; go straight to the next step.

   1. Check for Updates, then Install v… when it is offered
   2. Releases — the notes for the version you are about to install
   3. The Enabled switch — step 4, not yet

4. Switch the chain on. Turn the Enabled switch on — in the product page heading, or on the card on the Blockchains tab, which is usable now that the licence is verified. This is what switches the chain on for the Ecosystem addon.

   PUT/api/admin/ecosystem/blockchain/{id}/statuspermission: edit.ecosystem.blockchain

   Enables or disables a blockchain for the Ecosystem addon, by product ID

5. Watch the backend log on restart. The chain service checks its gates when the backend starts, so give it one more pm2 restart backend once the switch is on. A healthy start prints the wallet RPC version, the daemon height and sync flag, and Monero service initialized successfully, all tagged XMR.

6. Run the diagnostics. Admin → Ecosystem → Blockchains → Requirements → Monero → Test. It probes get_version on the wallet RPC and get_info on the daemon, and compares the daemon's nettype against XMR_NETWORK.

   POST/api/admin/ecosystem/blockchain/requirements/testpermission: view.ecosystem.blockchain

   Runs live read-only probes against a chain and returns per-flow readiness

1. Create the XMR master wallet. Admin → Ecosystem → Wallets → Master Wallets → Create, chain XMR. This calls create_wallet with the filename master_wallet, so a file by that name appears in your --wallet-dir.

   POST/api/admin/ecosystem/wallet/masterpermission: create.ecosystem.master.wallet

   Generates, encrypts and stores a master wallet for a chain

   The mnemonic is encrypted with the Ecosystem vault key before it is stored and is never displayed. If the vault is locked, this fails.

2. Import XMR as a native token. Admin → Ecosystem → Trading → Tokens → Import. Chain XMR, currency XMR, contract type NATIVE, contract left blank, decimals 12.

   POST/api/admin/ecosystem/token/importpermission: create.ecosystem.token

   Registers an already-deployed token without deploying anything

   Twelve decimals is not cosmetic — Monero amounts are handled in piconero and converted by dividing by 10^12 throughout.

   1. Step 1 - choose Import, not Deploy

3. Set the token's withdrawal fee. This is the number the platform charges; the Monero network fee is taken out of it. Read Withdrawals before you pick a value, because a fee below the network fee silently earns you nothing.

4. Create a market if you want XMR traded rather than merely custodied — see Tokens and markets.

#!/bin/bash
set -euo pipefail
DEST="/backup/monero/$(date +%Y%m%d-%H%M%S)"
mkdir -p "$DEST"
rsync -a /home/monero/monero-wallets/ "$DEST/wallets/"