You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whether there are other accounts that also use the same file, which will cause the plot file to only be under one account;
Whether the file is valid. This information can be seen in the file list of the GUI, and the invalid information of the plot file can also be seen in the console log;
Restart miner frequently. Frequent restart of miner will cause the file information to be too late to upload;
Online time is less than 1 hour. Under normal circumstances, it takes 1 hour for files to be found online, and this time needs to be recalculated after restarting Miner;
No contribution points. It may be that the plot file has no signature or no plot files. This problem can be queried through the "online plot" in the user center;
The plot file is online, and the signature is correct, but there is no contribution point. At this time, it may be automatically blocked by the system due to multi-mining. The "master blocked" user can receive a message notification and can query the specific multi-mining height in the income list. Those who use the same public key are currently unable to query. For the specific "blocked" information, if your plot files is generated using the same public key as other users, you may encounter this situation. You can go to the block explorer to check whether your public key is generating blocks at other addresses. It is not recommended to share a public key with others. The target of multi-mining detection is that the files of online plot file are generated in other addresses. Generally, there is no misjudgment. For specifics, you need to contact service. The development channel cannot provide you with more information.
The text was updated successfully, but these errors were encountered:
通常你可能需要确定以下内容:
Usually you may need to determine the following:
The text was updated successfully, but these errors were encountered: