hello all
For the questions that you have paid more attention to recently, I will answer briefly

1 How to start multi-core mining on a single machine?
Considering that a single node is mining at a medium luck value, more power consumption is wasted. For machines with multiple cores and large memory, we recommend that you start multiple nodes, and each node runs the mining program independently, which is equivalent to the way that each independent program occupies one core. The method of starting multiple nodes on a single machine is as follows:
Linux: Specify different ports and different data directories when starting the process luck --port=<PORT_X> --datadir=<DATADIR_X>. Note that to start multiple processes on a single machine, make sure to specify different ports and different data directories.
Windows: After decompressing the wallet file, you will see the luck/luck.exe file, which is a binary command-line program whose operation is the same as that of the Linux system and requires you to operate in the command-line mode. For example, you enter luck.exe --datadir=<DATADIR_1> --port=<PORT_1> in a command line terminal, and then open another terminal and enter luck.exe attach <DATADIR_1>/luck.ipc. For specific commands, please refer to https://github.com/luck-coin/luckcoin/blob/master/wiki/luck_linux.md.

2 How to optimize the mining network to increase the winning rate?
Since all mining nodes are now connected to the seed nodes, all messages are transfered through the seed nodes. With the gradual increase of network nodes, the transfer efficiency of seed nodes will continue to decline, which will affect the stable operation of mining nodes, especially for miners with multiple nodes. For miners with multiple nodes, it is recommended to deploy a transit node to connect to the seed nodes. The internal nodes directly interact with the transit node. If these nodes are on an intranet, this will greatly increase the message forwarding speed.
Start the wallet node directly, and connect directly to the seed nodes by default. If you want the node to connect to your own transit node by default, you need to specify in the command line parameter --bootnodes=lnode://<NODE_1>@<IP_1>:<PORT_1>, where NODE_1 is your transit node ID, you need to use admin.nodeInfo to view it on the transit node. IP_1 is the IP of your transit node. If it is on the internal network, it is recommended to use the internal network IP. PORT_1 is the port of the transit node, which is 30009 by default. In the Linux system, you only need to add the command line parameter. Under windows system, you need to start your wallet node in command line terminal mode to specify the --bootnodes parameter. In order to confirm that you are indeed connected to your transit node, you can check the connection through the command admin.peers.