🔥🔥[ANN][DISC]Diskcoin|open source|CPOC|Hardisk mining|No ICO|No premine

[eagle275]

plotterID should only exist between miner and pool - as Diskcoin copied BHD's "feature" of only supporting pool mining as to my knowledge

[1713993255]

1713993255

[1713993255]

1713993255

[1713993255]

1713993255

[Diskcoin]

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.

[eagle275]

Anyone with appropriate rights online that can resync / restart the testnet explorer's wallet - its hung on blockheight 8299 while the chain is at 8353

@Diskcoin .. you seem to "forget" a few things .. Replotting is only one side of the coin ... but we get (forced) new wallet addresses ... need to rebind other pools which poses problems in case of the big BHD pools - Hdpool / Hpool co-op .. as both only accept new bindings with sufficient pledge ...  And again it rises the question why YOU and your new vapour coin demand this step from miners interested ....

I feel reminded of AMD vs Intel in the early 90's - do you know what would have happened if AMD said "fuck Intel" WE now set the rules for 80x86 processors? Exactly we wouldnt know about AMD aside from early 90's stock exchange notices

[minerja]

Anyone with appropriate rights online that can resync / restart the testnet explorer's wallet - its hung on blockheight 8299 while the chain is at 8353

@Diskcoin .. you seem to "forget" a few things .. Replotting is only one side of the coin ... but we get (forced) new wallet addresses ... need to rebind other pools which poses problems in case of the big BHD pools - Hdpool / Hpool co-op .. as both only accept new bindings with sufficient pledge ...  And again it rises the question why YOU and your new vapour coin demand this step from miners interested ....

I feel reminded of AMD vs Intel in the early 90's - do you know what would have happened if AMD said "fuck Intel" WE now set the rules for 80x86 processors? Exactly we wouldnt know about AMD aside from early 90's stock exchange notices

hmmmm
Whilst you may want to dual / triple mine with the other crappy POC coins, i'd much rather start from scratch with a coin that can only be singularly mined.
Gives real people with a spare 1 - 2 TB a real chance, instead of all the massive 1PB+ rigs mining Burst/BHD/etc
After all the whole point of crypto is decentralisation...you know the hands of the many, not the few....

As for you AMD/Intel argument, who knows, if AMD had said "FCUKU" then perhaps Intel would be just a vague memory....only history will tell

J

[eagle275]

hate to break it to you - but with 1 or 2 TB you wont win anything on Diskcoin .. not even a honorary mention 

[minerja]

hate to break it to you - but with 1 or 2 TB you wont win anything on Diskcoin .. not even a honorary mention  

Why's that?
Brand new chain.
Should be open to all miners

I used to win blocks on Burst with 1 TB (obviously not now)

[jecsoon2]

How to use the Linux wallet?

[changesl]

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.

[frntman]

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.

Must admit, I was excited to get in on a new project from the beginning however, the chance of me "replotting" is zero. I will continue following the project to see if someone can get it to support our existing poc2 plots.

[eagle275]

How to use the Linux wallet?

extract it to a new folder - enter said folder

>bash ./start.sh

because a dumb developer put in a forwarding command that gives error with sh ^^^

>./diskcoin-cli getinfo
>./diskcoin-cli getblockcount
>./diskcoin-cli getpeerinfo

very interesting command - use data from getinfo / getblockcount and verify against getpeerinfo to see
- if you see more than 1 peer (hint that you could be blacklisted if only 1 or 0 peers)
- your height is the same as that of most peers (synced-height)
- check for hanging peers (have lower synced-height than others ....)

>./diskcoin-cli getnewaddress

once that all works without errors - copy the address-string into your miner's config - its your receiving address

then mine .. and wait for the surprises of wallet-forks, rewinds

see also https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list for a comprehensive list of most commands ... some dont work anymore since the bitcoin cash wallet used here is younger ...


small hint to the devs ... if you "testnet" .. why set "testnet": false in your wallet ? ROFL

EDIT

from Version 0713 onward .. the wallet includes a QT-driven application .. so if you have a "klickibunti" on your linux
just run ./diskcoin-qt &  and have fun

[eagle275]

hate to break it to you - but with 1 or 2 TB you wont win anything on Diskcoin .. not even a honorary mention  

Why's that?
Brand new chain.
Should be open to all miners

I used to win blocks on Burst with 1 TB (obviously not now)

even the 5 testminers  I see "regularly" have above 14 TB .. one even hitting 350 TB . but sure if your 1...2 TB are fast you can have luck ...

[jecsoon2]

Anyone with appropriate rights online that can resync / restart the testnet explorer's wallet - its hung on blockheight 8299 while the chain is at 8353

@Diskcoin .. you seem to "forget" a few things .. Replotting is only one side of the coin ... but we get (forced) new wallet addresses ... need to rebind other pools which poses problems in case of the big BHD pools - Hdpool / Hpool co-op .. as both only accept new bindings with sufficient pledge ...  And again it rises the question why YOU and your new vapour coin demand this step from miners interested ....

I feel reminded of AMD vs Intel in the early 90's - do you know what would have happened if AMD said "fuck Intel" WE now set the rules for 80x86 processors? Exactly we wouldnt know about AMD aside from early 90's stock exchange notices

What time is Win wallet on July 15?

[jecsoon2]

Community and Resource Links

Homepage: https://diskcoin.org/
Github: https://github.com/diskcoin-apps-team/
Twitter: https://twitter.com/Diskcoinorg

When Discord/Telegram for community?

Are there any official mining steps?

[Diskcoin]

Update:

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

filename: dcminer.0714.zip & diskcoin.0714.tbz

If you have any questions, please feedback to us.

----

234af8cac5a345b0ed8f290a66165e13  diskcoin.0714.tbz
9d998c94d99ebd4dce32fb7d116e1336  dcminer.0714.zip

diskcoin0714

*) 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

miner0714

*) Bugfix : Memory error
*) Bugfix : Json parse error
*) Feature: Reports the miner capacity.
*) Feature: No unzip password.

[Diskcoin]

Anyone with appropriate rights online that can resync / restart the testnet explorer's wallet - its hung on blockheight 8299 while the chain is at 8353

@Diskcoin .. you seem to "forget" a few things .. Replotting is only one side of the coin ... but we get (forced) new wallet addresses ... need to rebind other pools which poses problems in case of the big BHD pools - Hdpool / Hpool co-op .. as both only accept new bindings with sufficient pledge ...  And again it rises the question why YOU and your new vapour coin demand this step from miners interested ....

I feel reminded of AMD vs Intel in the early 90's - do you know what would have happened if AMD said "fuck Intel" WE now set the rules for 80x86 processors? Exactly we wouldnt know about AMD aside from early 90's stock exchange notices

What time is Win wallet on July 15?

When the mainnet online. Aroud July 15 , not the exactly date.

[jecsoon2]

The main network may not be online on July 15, right?

[heigua2]

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.

So why not re-design the encrypt methord as new coin?

[changesl]

Update:

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

filename: dcminer.0714.zip & diskcoin.0714.tbz

If you have any questions, please feedback to us.

----

234af8cac5a345b0ed8f290a66165e13  diskcoin.0714.tbz
9d998c94d99ebd4dce32fb7d116e1336  dcminer.0714.zip

diskcoin0714

*) 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

miner0714

*) Bugfix : Memory error
*) Bugfix : Json parse error
*) Feature: Reports the miner capacity.
*) Feature: No unzip password.

wow,  new wallet is great, mining on testnet very well.
should be very closed to the mainnet.

[eagle275]

nothing is great ..

still incompatible hashing methong that fiddles around with gensig

your forced small plotterID even makes "your" chinese people puke ... see github

I give you props for the qt-wallet and the sped up sync process ...

[eagle275]

so "Zero configuration" .. and then I only see not synced nodes ... NICE work Diskcoin