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

So how's a guy who's just got a wallet, not mining, suppose to keep up with this crap?  Kind of thinking about a future for a coin that doesn't include you super geeks changing codes/programming/forks/wallets, not notifying somehow thru the wallet that it MUST be updated.  What's the point if only for your experimentation.   I'm I missing something here?

Then You can restore the backup file wallet.dat (eg a week ago) and then these uncommitted transactions will disappear.
but it can be done if your wallet has only one address,  otherwise some coins may be lost.

I did that earlier today.  I still have 184 unconfirmed transactions in my wallet and I can't get rid of them.  Is there an answer on how to remove those transactions?

Hi.
Please read carefully this section https://bit.diamonds/community/index.php/topic,97.msg631.html#msg631
Download all the necessary files. Replace the wallet to the new version 2.0.55
Remove all old files wallet (except file wallet.dat) and extract the files from the archive danbischain20150408.zip to the folder beside with a file wallet.dat

it looks like found blocks on donkeypool are not confirming.  Can anyone verify that?  Is there still a problem?  Should people stop mining DMD? 

Hey guys, got a question. I was busy and I didn't update until a short time ago. I had my old wallet running and apparently it ran away on a fork and staked 2 blocks. I downloaded the blockchain from the link: HTTP March/08/15 from the OP and replaced my existing one.

I restarted the wallet with -repairwallet, and the stakes that went on the fork are now 'Generated but not accepted', which should be fine - right? But it didn't return the blocks, so now my balance is way off.

Is there something else I need to do to get these coins back to the correct place?

Thanks

I tried solo mining and out of 5 blocks found, 3 were orphaned. 

At one point Danbi's pool was the only one that appeared to be functioning.  When miningfield went down, some people switched to donkeypool so when donkey was acting up, there was only one pool left to go to.

but we want to prepare for next time

do we have longterm community member with static IP servers / virtual servers who wana host additional backbone nodes?

ideal would be virtual server where we get remote access

if that not possible u need to  join our dmd community chat on skype so we have easy communication ways

thats the spirit!
never give up

We have checkpointing server running.

That's why we are able to push one version of the chain over another knowing that it's not compromised.

Checkpointing server cannot prevent forks from happening but makes harder for them to take place.

It's a shame some people miss out by mining on the worng chain, but it's better to miss out than compromise the whole network.

Whoever is disturbing the network is quite determined, but not as determined as us to keep it running in order.

DonkeyPool is back for one more try.
Hopefully, some minor changes via cryptonit do the trick.

Why not add a checkpoint server to stop any future forks?

well done guys!

network stabilizing

we gain grounds!

The easiest solution would be to stop danbi's pool.

But, this will not make most of the miners move away. People just leave their miners at the pool and resume mining the moment it comes up again. The network will remain with less miners, lower difficulty and more vulnerable.

Activity at danbi's pool is higher than normal. All typical miners now mine more. Others have returned after being away for long time. Some miners are with impressive hashrates.... It is best that they move to other pools or solo mine.

By the way, while you are at the pool, please withdraw your coins. You could mint those coins and earn more of them. The coins sitting at the pool does not gain anything for anybody.

It has been repeated so many times. If you are an block generating node, please use

listen=0
noirc=1 (this is very important, strange things lurk on IRC!!!)
connect=

This will ensure your blocks propagate faster, than if you send them to other random nodes. You will see less orphans. It will also reduce the likehood of your node getting garbage.

remember this:
http://247cryptonews.com/diamond-2-0-the-pheonix-of-cryptocurrency/
we still the same people the same mindset
no one can make us stop keep dmd going forward

back in battle formation soldier
u not just a infantry man
u drive a tank we need ya 

Yup, this is a problem.
DonkeyPool will be suspending DMD mining until this is sorted.
All blocks mined on DonkeyPool are orphaned, regardless.
Over ~90days, DonkeyPool has generated over 5000DMD with very few issues, it's a shame to have to shut it down.

I'll be dividing-up the remaining pool wallet balance based-on a percentage of payout amounts to past and present miners.
I hope to do this tomorrow or sat.

I'll monitor this thread and see if anything changes, feel free to msg me with questions, etc.

interesting times.....

at our team 4-6 people are busy analyze and counter ur attempts

how big is ur team?
what exactly u try to achieve?

u know we never give up since close to 2 years?

try to break dmd before code changes go active?

u will have no luck

just a bit over 6000 blocks
3 days

u cant stop us



in times like this a community have to stay close side by side
thx for ur support

sure additional pools would be welcome
not because of over 50% hashrate because thats no issue
the pool is managed by our main dev
but because its a single point to attack

more pools are welcome where is miningfield and donkeypool
get ur pools up again and people distribute ur hashrate across the pools

what users can do help our efforts in this battle?

u can change bantime=36000
the old 600 setting was helping against other attack pattern
but actual its more damaing than helping because
the bad block sending nodes only get banned for 10 min each time

if u have good node try get a listen=1 and addnode config running and support network relay good data
but adapt bantime=36000

but with that config u need to check that ur node stay on right chain if u land in fork u have no chance rejoin mainnet becaiuse u will them block all good nodes for to long

people who have no time active monitor their wallet and support our battle

why not just stop ur wallet and wait until weekend when trigger is over and victory will be visible

for now worst case u act as helper of an attack by relay bad blocks if u not able active watch ur wallet

again thx for support of community

we gave a lot for u please give us back a bit

at least moralic support in middle of battle

and dont cry  bullshit unstable network
because any non active maintained coin would be broken since 2 days.......
we stand and fight and no way we can lose the battle

If it is true then it proves why master node is a bad idea.

https://chainz.cryptoid.info/dmd/# - You can see here how to Danbi's pool "overwrites" blocks found in other places.