I'm not asking anybody to trust me. I'm just telling you all that you should see something in your ~/.Diamond/debug.log about 193.68.21.19 misbehaving. If that made it in my debug.log it should be in others. Here it is again look, look for it in your debug.log:

ProcessBlock: ORPHAN BLOCK, prev=000000000302b0af011c
received block 000000000302b0af011c
ProcessBlock: ORPHAN BLOCK, prev=0000000004e6b27a0790
received block 0000000000d652bceaa2
connection timeout
ProcessBlock: ACCEPTED
received block 00000000078b6cf20c99
Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING
disconnecting node 193.68.21.19:17771
ERROR: ProcessBlock() : block with too little proof-of-work

Does nobody else see this in their logs? I'd say it's just a bug in my version diamondd but given that the whole damn block chain forked around the time this was logged, it wasn't just me.

It was not a bribe. The DMD he proposed were actually coins that I did NOT see coming to my wallet one day while mining in his pool. No transaction happened during a period of 6 hours when in fact transaction were supposed to happen every hour.  We never really figured out why but he was fast to claim that it might have been my internet, my miner etc etc. What I wanted was a clear explanation. Never had it.

At least he proposed which somehow was a nice thing to do but I didn't want to take the coins as it was not crystal clear what the problem really was.

Not getting this at all.

Please read: https://bt.irlbtc.com/view/580725.msg8115151#msg8115151

What is your diamond.conf config? Please post it here.

There are no hidden fees!
The hashrate is multiplied by the (100% - fee). So you are getting paid for the value displayed in your grs-sgminer. Period.

PS: The pool is on the latest code from github and has blockchain from dmdchain20140731-fast.zip.

You are getting the assertion error where the index.dat file gets corrupted due to a flood of orphans. Other nodes you are connected to are feeding you crap.

Obviously you also need to replace the blockchain with the one provided in the OP. Then start the wallet. The index file is corrupted so making those changes to the .conf is useless if you don't replace the blockchain files first. Basically delete all files except your wallet.dat and the diamond.conf files and replace with the one in the OP.

Using connect=IP and listen=0 makes you indeed a "leecher" if I may say so but this is temporary. You can then revert and change to addnode=ip and listen=1 later on. This is TEMPORARY.

The index corruption issue is not something specific to Diamond. A lot more coins have the same problem and to this date there has been no fixe.

Cryptsy is not a measure for the correct chain. It will be very unfortunate if they are on a fork, but this has happened many times before and was sorted out. Frustrating, yes.

They can't be on both chains, correct.

Dev,pls work harder and bring us to da moon!

danbi



Wallet 2.0.3
I'm on the right chain
Difficulty in a wallet it is equal difficulty on dmdpool.digsys.bg
conf file:
listen=0
noirc=1
connect=193.68.21.19

but why there are a lot of not accepted?

I suppose those not accepted are minted. Correct?

Correct