I just read an update from Diskcoin they were doing something please wait, Sorry to let you know that the team needs to do further testing and fix some bugs to make sure that there are no problems, so mainnet will be delayed until this weekend. Thank you for your attention to Diskcoin!
The testnet has been updated to the new version, the block height will start from 1. And anyone who wants to participate in the testnet mining, you should download the latest dcminer and wallet through this link: https://github.com/diskcoin-apps-team/wiki/releases/tag/v0714
*) Bugfix : Tx in mempool leak *) Bugfix : Deadlock when loading wallet *) Feature: Ploter id less than uint56(-1) *) Feature: The first test version of diskcoin-qt on linux *) Feature: RPC interface compatible with blagominer version *) Feature: Make a bloomfilter on the POC check and save it to the file for persistence. *) Feature: Zero configuration can be started
its a JOKE .. your PID-tester declares literally ALL existing plotter_IDs as "not applicable" and enforces a rule .. smaller than 18 digits .. smaller than 0xFFFFFFFFFFFFFF+4 .. I have never encountered before - why do that .. if you want to let the people multimine - then dont behave like YOU are the center of the POC world ... most of us have plots .. and especially the bigger miners dont want new wallet addresses / new plotter IDs
Any Ideas on that ?
Any Idea on changing your miner's hashing method to be compatible ? so that we need not run 2 miners stressing our drives ?
Burst/bhd/boom use uint64 PID, the PID that Diskcoin uses is less than uint56, we all use the same POC2 file.
At present, the global POC hashrate is around 2000p, and the hashrate less than uint56 occupies 1/256, less than 10P, which means that everyone needs to replot files. Replot will take time, the advantage of this is that there will be no huge hashrate in DISC mining immediately, which can avoid huge hashrate attacks for Diskcoin, such as 51% attacks or miner-activated softfork (MASF), thus ensuring the safety and stability on the chain. And it will be fairer for everyone.
it is 7/13 now, closed to Mainnet. when the testnet will be lanuched which forced to be PID working ? we need test.
its a JOKE .. your PID-tester declares literally ALL existing plotter_IDs as "not applicable" and enforces a rule .. smaller than 18 digits .. smaller than 0xFFFFFFFFFFFFFF+4 .. I have never encountered before - why do that .. if you want to let the people multimine - then dont behave like YOU are the center of the POC world ... most of us have plots .. and especially the bigger miners dont want new wallet addresses / new plotter IDs
Any Ideas on that ?
Any Idea on changing your miner's hashing method to be compatible ? so that we need not run 2 miners stressing our drives ?
yup, totally agreed. that pid verification is a joke...