Start mining.
Build with the squad.

Before you mine: create and protect your wallet

Use the Linux, macOS or Windows wallet-creation instructions with a verified DGL build for your computer. Back up your recovery words privately before using the receiving address. Secure offline and encrypted backups can preserve your recovery path if a local password is forgotten; a public address cannot restore a wallet. This website never needs your words, keys or password.

1. Get approved VPN access

The gateway's UDP port 51820 is for WireGuard, not XMRig. VM1 remains the mining host. Its own WireGuard listen port is not the public client endpoint. On VM1 itself, XMRig can use 127.0.0.1:3333.

Request device access and approved mining software → Send your operating system, DGL public receiving address and your device's WireGuard public key. If you need a key, follow the next section first. Keep private keys, private profiles and wallet recovery words on your device.

2. Set up WireGuard on your mining computer

If you already have a complete, approved profile, go to your operating system’s connection steps. For a new device, install WireGuard from the instructions for Linux, macOS or Windows first.

In the WireGuard app on Windows or macOS, choose Add Empty Tunnel, name it dgl-miner, and copy the displayed public key. On Linux or macOS with the CLI installed, generate the key on the mining computer and print its public half:

(
  set -e
  umask 077
  dir="$HOME/.config/dgl-vpn"
  mkdir -p "$dir"
  chmod 700 "$dir"
  if [ ! -e "$dir/private.key" ]; then
    device_key=$(wg genkey)
    set -C
    printf '%s\n' "$device_key" > "$dir/private.key"
  fi
  wg pubkey < "$dir/private.key"
)

Send the public key to the operator using the request link above. After approval, the operator supplies your assigned address. In the app, keep its generated PrivateKey line and add Address = ASSIGNED_IP/32 under [Interface]. Add the public peer fields below the interface. For a CLI-generated key, use the profile command below instead.

[Peer]
PublicKey = WNPh1zNBjARGDbayaFF3PqfxcK7TpgVFdYnBVMDMZiU=
Endpoint = 167.99.107.30:51820
AllowedIPs = 10.77.0.3/32
PersistentKeepalive = 25

This client route selects VM1, rather than all of your Internet traffic. For clients behind NAT, the operator can include PersistentKeepalive = 25 when needed; see WireGuard's guidance.

If you generated the key in Terminal, run this block and enter the assigned IPv4 address without /32. It saves the profile on your device and preserves any profile with the same filename.

printf 'Operator-assigned VPN IPv4 address: '
read -r dgl_ip
(
  set -eC
  umask 077
  dir="$HOME/.config/dgl-vpn"
  {
    printf '[Interface]\nPrivateKey = '
    cat "$dir/private.key"
    printf 'Address = %s/32\n\n' "$dgl_ip"
    printf '[Peer]\nPublicKey = WNPh1zNBjARGDbayaFF3PqfxcK7TpgVFdYnBVMDMZiU=\n'
    printf 'Endpoint = 167.99.107.30:51820\nAllowedIPs = 10.77.0.3/32\nPersistentKeepalive = 25\n'
  } > "$dir/dgl-miner.conf"
)

Keep the completed dgl-miner.conf profile on your mining computer. A recent WireGuard handshake confirms the gateway connection. Test the pool port separately before starting XMRig.

3. Mine through the DGL pool with XMRig

Set up your DGL wallet and back it up before mining. Get the DGL-approved XMRig build for your operating system and processor from the operator. Use XMRig’s official downloads when the operator confirms a compatible build. Extract the archive into your Downloads folder. In each example, replace XMRIG_FOLDER with the extracted folder name and YOUR_DGL_WALLET with your public receiving address.

Linux Terminal

Open Terminal. On Ubuntu or Debian, install the tools below. For other Linux distributions, follow the official WireGuard instructions and use your distribution’s nc package. Use the path to your approved profile. These commands use the path from the CLI setup above.

sudo apt update
sudo apt install wireguard netcat-openbsd
chmod 600 "$HOME/.config/dgl-vpn/dgl-miner.conf"
sudo wg-quick up "$HOME/.config/dgl-vpn/dgl-miner.conf"
nc -vz -w 5 10.77.0.3 3333
sudo wg show dgl-miner latest-handshakes

Once the pool test succeeds, change to the extracted folder and start XMRig.

cd "$HOME/Downloads/XMRIG_FOLDER" && ./xmrig -a cn/0 -o 10.77.0.3:3333 -u YOUR_DGL_WALLET -p x -t 4

macOS Terminal

Open Terminal with Spotlight. Run uname -m and choose macos-arm64 for arm64 (Apple Silicon) or macos-x64 for x86_64 (Intel). On Apple Silicon, use a native Terminal session for this check. Install Homebrew first if needed. These commands use the approved profile path from the CLI setup above.

brew install wireguard-tools
chmod 600 "$HOME/.config/dgl-vpn/dgl-miner.conf"
sudo "$(brew --prefix bash)/bin/bash" "$(brew --prefix)/bin/wg-quick" up "$HOME/.config/dgl-vpn/dgl-miner.conf"
nc -vz -G 5 10.77.0.3 3333
sudo "$(brew --prefix)/bin/wg" show all latest-handshakes

You can also import and activate your profile in the official WireGuard app, then run the pool test in Terminal. Once the test succeeds, start XMRig.

cd "$HOME/Downloads/XMRIG_FOLDER" && ./xmrig -a cn/0 -o 10.77.0.3:3333 -u YOUR_DGL_WALLET -p x -t 4

Windows Command Prompt

Open Start, type cmd, and choose Run as administrator for tunnel setup. Install the official WireGuard client. To activate a saved approved profile from CMD, use its private path in the first command below. If you already activated it in the app, start with the status check.

"%ProgramFiles%\WireGuard\wireguard.exe" /installtunnelservice "%USERPROFILE%\dgl-miner.conf"
sc query "WireGuardTunnel$dgl-miner"
powershell -NoProfile -Command "Test-NetConnection -ComputerName 10.77.0.3 -Port 3333"
"%ProgramFiles%\WireGuard\wg.exe" show dgl-miner latest-handshakes

Look for TcpTestSucceeded : True. Then open a regular Command Prompt and run:

cd /d "%USERPROFILE%\Downloads\XMRIG_FOLDER" && xmrig.exe -a cn/0 -o 10.77.0.3:3333 -u YOUR_DGL_WALLET -p x -t 4

Use -t 4 as a starting thread count and adjust it for your computer. The -p x flag is the pool’s placeholder field. Check for accepted shares in XMRig to confirm the pool is receiving work. If your tunnel connects but the pool test fails, ask the DGL operator to check your device’s pool route. For approved LAN mining or mining directly on VM1, use the applicable endpoint in Network access.

Press Ctrl+C to stop XMRig. Deactivate the tunnel in WireGuard, use down in place of up for the Linux or macOS CLI, or run sc stop "WireGuardTunnel$dgl-miner" in Administrator CMD for the Windows tunnel service. WireGuard Windows commands

The homepage command builder can fill in your address, thread count and platform locally. Official XMRig command-line documentation explains the flags; DGL-specific compatibility is established by the project.

4. Synchronize your own DGL daemon

Use the DGL daemon binary DarkGangLumonold. This LAN example connects exclusively to VM1 at its DGL peer port and keeps the client node’s RPC on loopback. A pool-only VPN profile does not grant P2P or RPC access; remote node operators need separate approval:

On Linux or macOS, open Terminal. Change to the folder containing the verified daemon executable, then run:

cd "$HOME/Downloads/DGL_FOLDER" && ./DarkGangLumonold --data-dir ./dgl-chain --add-exclusive-node 192.168.12.230:38080 --p2p-bind-port 38080 --rpc-bind-ip 127.0.0.1 --rpc-bind-port 38081

On Windows, open Command Prompt and use:

cd /d "%USERPROFILE%\Downloads\DGL_FOLDER" && DarkGangLumonold.exe --data-dir dgl-chain --add-exclusive-node 192.168.12.230:38080 --p2p-bind-port 38080 --rpc-bind-ip 127.0.0.1 --rpc-bind-port 38081

Replace DGL_FOLDER with the extracted folder name. Remote node operators should use the endpoint assigned by the DGL operator.

For an existing node, retain its usual --data-dir path. The ./dgl-chain directory is a new-node example. Keep the working chain and approved binaries; this guide does not require a chain reset.

Wait until the daemon is synchronized before starting mining or using it for payment verification. The DGL network uses its own chain and settings. Obtain DGL software through onboarding rather than substituting a standard Monero daemon.

Running a daemon supports node participation. Current lottery credits come from confirmed pool-mined blocks attributed to a miner; running a node or solo mining is not automatically imported into the pool lottery.

5. Keep payouts and NFT credits clear

DGL coin payouts: the pool tracks valid mining work by miner login wallet. Payment amounts and timing follow the pool’s actual accounting, block maturity, configured thresholds and payment rules. Obtain the current payout terms from the operator.

NFT credits: one confirmed, canonical pool-matured block attributed to your wallet equals one credit. Accepted shares, share difficulty and DGL coin amounts are not converted into NFT block credits.

Link your mining wallet to your DGL app account during onboarding. Multiple linked wallets combine under that account. Qualification uses a closed 25,000-block window, with regular miner NFT eligibility beginning at 1,000 credits. Series 02 also requires an earlier confirmed Genesis miner-lottery receipt.

Read the complete NFT rules →