---
title: Enable Your Node
slug: signum/enable-your-node
docTags: 
createdAt: 2025-04-13T11:37:25.136Z
---

Once you've followed the guide to install your node and confirmed that it's running on **mainnet (**[Running on mainnet](docId\:xGLj7dunpT_7_Dzptt8l7)) only two small changes are needed in the node's configuration file in the Mining section to enable solo mining: 

```ini
#### MINING ####

## List of semicolon-separated passphrases to use when solo mining. When mining solo, if you enter your passphrase here,
## you can set your miner to pool mining mode and avoid sending your passphrase over the wire constantly.
## Do not use on public facing nodes or nodes that are accessible (filesystem or API server) by others, as it could
## cause your passphrase to become compromised or allow others to mine on your behalf without your knowledge

# SoloMiningPassphrases=passphrase1;passphrase2;passphrase3;

## List of semicolon-separated passphrases to use when solo mining but with a reward recipient set.
## Your miner account is the one you provide only the id, while the account which you set
## your reward recipient is the one you provide the passphrase here.

# RewardRecipientPassphrases=id1:passphrase1;id2:passphrase2;id3:passphrase3;

## Allow anyone to use the "submitNonce" API call. This call can be abused to force your node to perform lots
## of work in order to effectively mine for others. Enabling this option will only allow accounts whose passphrases
## are in SoloMiningPassphrases to mine through this node.

# AllowOtherSoloMiners=false
```

### AllowOtherSoloMiners=true

:::CodeblockTabs
ini

```ini
AllowOtherSoloMiners=true
```
:::

### ➡️ What to do

Uncomment the line AllowOtherSoloMiners (remove the # and set to true) to allow your node to accept solo mining requests, including from your local miner. 

##  🔐 Secure Solo Mining Setup 

In the past, you had to include the **passphrase of your main mining account** (the one used for plotting) directly in your node configuration. This posed a significant **security risk** — if your setup was ever compromised, your funds and mining account were at risk.

Although it's still possible to use this method by setting:

```ini
SoloMiningPassphrases=word1 word2 word3 ... wordX;
```

…it’s **strongly recommended** to use the **secure solo mining setup** introduced with [SIP-46](https://github.com/signum-network/SIPs/blob/master/SIP/sip-46.md). 

### 🛡️ How to Set Up Secure Solo Mining 

1. **Create a proxy pool account**
   - This can be a brand new Signum account or a repurposed one.
   - This account will sign blocks on your behalf, keeping your main wallet safe.
2. **Assign your reward recipient**
   - From your solo miner account (used for plotting), assign the **Reward Recipient** to the **proxy account**.
   - This step requires a transaction with a **minimum fee of 0.01 SIGNA**.
3. **Use your wallet to make the assignment**
   - Open either the **Phoenix Wallet** or **Classic Wallet** 
     (ideally connected to your [local node](http://localhost:8125/index.html)).
   - In the **Mining section**, use the interface to assign your reward recipient.

✅ After \~4 blocks, the assignment becomes active, and your proxy account can sign forged blocks. 

You need to set the secure solo mining setup in your node config by activating the proxy:

```ini
RewardRecipientPassphrases=id1:word1 word2 ... wordX;
```

**id1 **=  The numeric ID of your solo miner account
**word1 word2 ... wordX **= The passphrase of your proxy account



:::hint{type="danger"}
After you changed your config file (node.properties) you need to restart your Signum node to get the changes activated!
:::

:::hint{type="success"}
By combining a fully synced node with secure solo mining, you maximize your control and security and help decentralize the Signum network. 
:::