@Diskcoin

whats up with your testnetwork ? We cant sync our local wallets anymore - including our testpool ? Though people mine obviously .. as blocks are forged ? or did you turn it into some VIP service ?

wouldnt fiddle too much .. dcminer is blago .. a seriously retarded miner that cant "comprehend" URLs ....

only address:port  - this calls usually for a mining proxy


192.168.1.109 ... cannot really be the server - except this is where your proxy runs ...

do you have "applicable" plotter_id = plotfile names ?

also possible your mining start came right about at the time where the dev restarted / reset the testnet

Lack of communication .. Would it have hurt to inform people about testnet reset ?

SERIOUSLY DISKCOINDEV - you give us a rewind - and for whatever reason YOUR testers are blocked ? .. cant even get blockchain nodes to sync my wallet

this practially a week after planned release ^^

another service .. when do you finally offer a "useful" communication channel ... like discord

@jecsoon2

the full block reward is always 20 disk
unpledged you receive 8 as forger - and 12 go to the dev-wallet - like in bhd or boom

if you pledge you receive more ... but unfortunately there was never revealed how much per TByte must be pledged to receive full reward  
we tested on 0708 an 0710 with some sheath of hand and pledged our testpool to some 100 k disk -
which made us earn even above "ceiling" of 20 disk

the actual payment seems to hint to some asymptotic graph .. with moderate pledge of ~400 we get over 10 disk


but when ever you check your earnings vs pledge keep in mind that earnings are "delayed" by 100 blocks until they are "mature" ... depending on blocktime this can take some hours  
 

yea .. unfortunately DC miner is Windows only, which is especially laughable since the wallet is still linux only

but at least together with a mining proxy like Archon or Foxy-Proxy you can use your "general" linux miner

https://github.com/BloodReaver/Archon
https://github.com/felixbrucker/foxy-proxy
https://github.com/PoC-Consortium/scavenger

cleared the wallet problem .. thought I had overwritten anything with 0714 but since the devs chose a new distribution method .. the release contained a subdirectory previously not present ..
- stop hanging wallet >./diskcoin-cli stop
overwrite all files with v0714
- start resync >bash ./start.sh

blockchain seems frozen .. 1126 / 1127 .....

any clue what I should do if my wallet doesnt find the correct chain ? .. keep trying to resync with the old chain that reached block 9156  :

3 days left for you to change your mind about this nonsensical plotterID limitation .. that can lead to collisions in the based hashing function  ..

burst wallet does generate 19 digits or more exactly to "fight" the possible collisions

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

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 ...

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 ...

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

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

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

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

@Oxus:
I'm going to ignore your last content - because I'm not raging ..


Renaming plotfiles doesnt help - because of the contained data - IF you want to do it in diskcoins favor you'd need to replot unfortunately (and yes .. shitgates got their nickname not for jokes)
 

Instead let me tell you .. the blockchain still doesnt verify (at least they didnt do until our testpool wallet was blacklisted for the 2nd or 3rd time) your plotter_id to be lower than said 0xFFFFFFFFFFFFFF+4 - so you can continue testing with your existing plotfiles - as I do^^

I find it hilarious that the blockchain keeps blacklisting our testpool's wallet ...  

Maybe Diskcoin can enlighten us why?

Another Joker ? .. POC#2 ... so we CAN use existing plotfiles .. you only force us to generate new address and plotter_ID - which are  probably intentional Bigger than 0xFFFFFFFFFFFFFF ...

Did you sit together with the disk-coin devs over a tea and discussed how to share the new POC world ?

 

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 ?

windstore2020
NewBI is a POC project too，It’s friendly to new miners or small miners. :

I cant believe it ... please have them fix their wallet-address and numerical account ID generation first - this is the first poc-coin I met that generates incompatible IDs to burstcoin

I wont replot my drives for a new vapour coin ... please FIX this ..
and while you are at it .. where does your customized version of jminer send the deadlines and stuff ?
so that I can replace it with my existing combo of multimining proxy and scavenger