the other way around would be wrong too

add 50x 1% chance together and say u have a 50% chance is wrong

but say u have a 1% chance with all ur coin pile is wrong too

but of we state biggest coin pile chance and then say 1% that would be ok

but anyway its a minor issue its not related to any POS mechanic its just a poor atempt to give a overview about ur coin weight

u are not up to date

regarding POS it seems we just didnt take into account
that the complex POS calculations not only relay on min age but also other stuff with history of former POS settings have still impact
and it need some time until the influece of this onto the calculations adapt towards the new 3 days min age
if u check chainz u see pos is alive and pos diff did recover and is again  10x higher than at the lowest point


regarding ur other points i stay silent every reader can paint his own picture about ur hate/love of DMD Diamond

i just have to state that the POW mining diff is far higher than expected so not many people share ur opinion that DMD is not worth to be mined

but yes i agree sure some miners would earn more DMD by using https://multipool.bit.diamonds/ instead of mining DMD direct

Pretty cool.  It's nice to see DMD get a little attention aimed at newer people.

I'd be curious to hear about new investors interest in DMD.  As it is, it's an incredibly easy coin to get involved in -- with or without mining hardware or big pockets.

Do I really have to dig into the diamond wallet code and find what is wrong?  Dev team is responsible for this.  I have enough work to do with NOMP!

Fork...Donkeypool seems to be on the right one - it uses the same (and ONLY the same) master nodes.
Right now we agree with https://chainz.cryptoid.info/dmd/ and the pool is shitting (DMD) like a frat house on Sunday morning.

too often occurs is a fork...

thx

what can we say
what do we see

we are same as u part of dmd community
in december 2013 former dev zuper did go inactive because he created a own social networking service company

since then we try to work in best interest for dmd diamond

same as u we can see actual situation and that there must be a issue
which make forking off mainchain for a high hashrate pool possible

i can just suggest avoid mine on a pool who have close to 40% or more of network hashrate
or set up ur rigs in solo mining mode
until we able identify and fix the orgin of this problem

also i did ask for help community run backbone nodes with static ip which run in listen=1 and addnode to other backbone nodes mode

the 4 nodes we have now are overloaded

latency in block syncing increase possibility of forks happening

we cant do all alone we need ur help

if u able run a backbone node please get in touch with me PM i tell ya the conf u need and we will add ur ip to community nodes list

im in process of set up 2 additional nodes i will pay out of my own pocket

but maybe some of u have access to servers who can act as backbone node too

and please dont run ur wallets in connect and listen=0 mode

this way u ONLY use backbone nodes and no other nodes in network can help our backbone relay blockdata to u

good nodes always important for network
and their dynamic IP will spread by nodes exchange peers lists

but for backbone nodes which are part of suggested diamond.conf
we can use only use nodes who have static IP

Just checking in to make sure this is the correct conf to run still:

listen=1
noirc=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
addnode=193.136.97.30
addnode=193.136.96.30
bantime=3600
maxconnections=50

This is what I have been running.  I am only POS minting since the start of the new wallet.  It has been open 24/7.  Difficulty and blocks seem ok.

Checkpoint:
"synccheckpoint" : "000000000511e16cb3cb67291b7138b50cd32a8dba2875bac77e10eba06f02ea",
"height" : 893619,
"timestamp" : "2015-04-22 11:15:48 UTC"

-pokeytex