| sip | title | description | author | status | type | category | created |
|---|---|---|---|---|---|---|---|
46 |
Secure solo mining setup |
Introduce a proxy pool setup for solo miner |
jjos, frank_the_tank |
Final |
standard |
SRC |
2022-11-17 |
This SIP will allow solo miners to use a proxy pool for signing the blocks. If the passphrase that generates this block signing leaks, the miner can simply register a new one. This way, a miner can forge solo blocks without using the original account passphrase.
Signum offers a simple setup to start solo mining. Currently, only a full node and the miner software are needed. BTDEX also provides a solution for solo mining. From a security perspective, the only downside to running a solo miner is that you have to leave the passphrase in the clear text either in the node's configuration or in the mining software.
With the present SIP, we would like to solve this problem using the existing Reward Assignment Transaction and enable the node to handle proxy pools for solo miners.
A proxy pool account must be created (fresh new account or repurposed) to function as a proxy pool on the Signum chain. The solo miner account (used to create plot files and possibly with committed coins) should set the reward assignment to the proxy pool account. The assignment will be active after 4 blocks, as usual.
In the node configuration, the proxy pool's passphrase needs to be set for signing the blocks.
This new passphrase will be placed under the config entry RewardRecipientPassphrases in the structure of accountId1:passphrase1;accountId2:passphrase2;....
The accountId's are taken from the solo miner accounts (usually just one, but not limited to).
The passphrase is the passphrase of the proxy pool account.
Example:
RewardRecipientPassphrases = 1234596885:soul wing belt zoom board helm zero two four
The config entry SoloMininingPassphrases will be commented out by default.
The reward will be paid to the proxy pool account if a block gets forged.
This proposal is backwards compatible. There are no protocol changes.
The setup can be implemented by minor changes in node code, including the changes to handle the RewardRecipientPassphrases and to properly sign blocks.
Copyright and related rights waived via CC0.