Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 544. (Read 1260706 times)

Cause we ve been using the same code for months and everything was fine just until few days before the reward reduction. Also, take a look at some earlier posts by Cryptonit.
I have no proof for this but I am 100% sure this is not a mistake on our side. Dev team has spent hours during the last few days to fend off this attack and I think all we need to do is to wait till tonight. The new code should resolve these issues.

DMD Diamond s NOT dead. There are a lot of good people working behind the scene so we can all sit back and relax once the price starts going up. Have a little faith, this coins is not Paycoin.  

What makes you certain this is an attack and not some kind of flaw?

solution? allowed the mining? dmd is dead?

These attacks only show DMD s got bright future. Why would anyone attack DMD if they do not think it s valuable.

Also, we re reaching 1 mil in about 12-16 hours. I hope at that point this problem should go away cause the new code will kick in.

Looks like network has settled on lower diff chain, danbi miners are SOL,  Move from Danbi's to DonkeyPool, we are the Golden Goose laying DMD at a furious rate

Thanks for the quick reply mate! 

I just stop wallet and copy/overwrite database folder, blk0001.dat, blkindex.dat with a backup copy from a few weeks ago before this forking started.  Also delete peers.dat.  Restart wallet and let it catch-up (less than 15 minutes from backup I have)
Changed .conf to addnode= and listen=1 to allow network to decide which chain is the correct one, majority of wallets decides which chain is correct fork when u re-sync ....

John, how you re-sync? "repairwallet"? "wallet check passed" : true - this is ok? Im on DonkeyPool now.

I have re-sync several times today and and end up on lower diff chain each time, DonkeyPool, Solomining and I think Cryptonit said reactor all on same chain as cryptoid explorer.  I agree with Cryptonit, let the chain sort itself out in a de-centralised manner ...

cryptonit says that's the correct fork.  I am trying to mine solo but my wallet keeps jumping to the other fork.  Right now I think mining anywhere is a risk.

Donkeypool seems to be on the same chain as https://chainz.cryptoid.info/dmd/

I have no idea what chain will be declared the correct one.

Mine on DonkeyPool at your own risk.

going to bed at 03:23 local time
another night spend for dmd diamond

would be nice if we can get some support and if its only a few nice words

to power our engine for invest all that time

at days like this

u start to question urself

why......

lets explain situation

we discovered again daniels pool and lot hashrate and some wallets on one fork

and much more wallets including reactor but less hashrate are on other fork (different chains)

last time this happend daniels chain was declared mainchain and lot people had to fix their wallet with backup blockchains

this time and there i take full responsibility we choose the majority of wallets are the main chain

which now in fact create the situation that the main chain have less hashrate because danbi pool just had overwhelming hashrate

its night in bulgaria daniel sleep

so we me and alex had to make a call

i was so pissed with the situation (like i guess everyone else too) that the network fork again that i said

lets go the as much decentralized path as possible

so actual situation is the backbone nodes do sync again

and we try this time use addnode and listen=1 everywhere

and let the network consolidate by itself

the reactor and some other big POS wallets are on the chain that is visible here https://chainz.cryptoid.info/dmd/

at least 34 wallets are sync with that chain

danbi pool and lot hashrate is on other chain

please everyone mining in danbi pool stop mining go solomining

once u resynced with correct chain

or just stop wallet and wait after trigger is done and network stabilized

i strong suggest that after trigger before pools go online again they make a agreement about how they can make sure no one of them go over 40% of network hashrate

to avoid that in future 51%+ pool fork themself away of majority of network wallets

in my opinion this last fork was homegrown and no attack

the first one that happend did show clear sign that go far above some random unlucky event

In fact, my the difficulty I am seeing from my Wallet is bouncing back and forth between the teens and the 60s.   The explorer is showing a pretty constant diffulty in the high teens.

My wallet shows a difficulty of 67 while Donkeypool and the blockchain are in the teens.  I just resynced my wallet for a second time.  What should I do?

please in preparation of trigger which will happen in around 24 hours

all miners go solo mining

and wait until pools after trigger confirm that they adapted  configurations

before u consider if u wana go pool mining again

for any 100 mhash or more miner i strong suggest u stay solo mining

danbi pool forked
check https://chainz.cryptoid.info/dmd/ to see if u are on main chain

Strange things! In my big wallet minting increased a lot, but today everything is working as it was before. Apparently in the troubled days were few active large wallets.

There is no difference between 2.0.4 and 2.0.5.5 until there are 1000000 DMD.

Give it some time, my guess is up to two months. Until stocks are depleted and people start slowly flocking in. We re going to have a great ride in front of us. Just keep mining/buying and hoarding. HAMSTER mentality rules, I hoard everything.