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

too often occurs is a fork...

I'm betting some staking wallets out there were never messed with after the POW reduction hit.  Oh well, poor guys.

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.

fork?
danbi diff, Block: 38.57, 893,073;
chainz.cryptoid.info diff, Block: 16.6, 893106.
I on chainz.cryptoid.info.

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!

@cryptonit thank you for your reply I just question if my investment was worth it.  I put a great deal of time into working with reaslhet on kernel and also bringing donkeypool online.  I think there are several points of failure/exploit.  PoW reduction for one, and secondly not enough wallets open for PoS. 

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.

Hey guys, here's a link to my show, Coin of the Week. Sunday night I talked about DMD. It's more of a show for new people, New investors - so they can get acquainted with a coin and it's properties.

https://soundcloud.com/supernetradio/coin-of-the-week-episode-2-diamond-dmd

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

I have to agree with Cryptonit.  The coin change is not a real problem and can be fixed very simple by using original address.  Large coin piles are not staking as expected  I still think "reactor" is the real cause of this problem.  The forking issues were CAUSED by Danbi's pool gaining greater than 51% and even high as 65% of network.  The importance of PoW pools and solo mining is even greater now.  

I certainly do not give a F about mining DMD anymore and rate is steadily falling as ppl realize not profitable.  I have also quit buying.  DMD is going to die if drastic measures are not taken.  PoW should be restored to a minimum of 0.5 or u are soon to lose all PoW support, PoS is broken again as Cryptonit says.  Just another failed coin where I lose my money   Step up and fix it before I lose again

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

That PoS guestimate is very wrong. It takes into account all the coin piles you have (and sums their chances), while it is possible for only one pile to PoS. We should fix this soon.

Well, let's wait and watch. It may be all right. When Danbi comes back and he'll have the time let him look on this, please:

"Minting.
"Your weight is 33833.
Network weight is 8234.
Expected time to earn reward is 24 second(s)."

He-he! 

ok we have a first explaination what happend

the min age is set to 3 days correct but there is a so called "stake modifier" in code
which need some time  to adapt towards the new min age

so everything seems to be fine network need just some POS cycle to adapt

more people who keep their wallet open in POS mode help us get the transition done

code state

nStakeMinAge = 60 * 60 * 24 * 3; // min age is lowered from 7 to 3 days

but what we did experience now is that big coin pile started to POS nearly exactly 9 days after they did POS the first time after trigger

we should just watch how it behave now

i mean if by some reason the min time is now higher than expected but the network adapt to it and run smooth

then i see no reason to change it

so lets keep monitoring POS behavior

good part is we have no hurry and need no emergency fix


dont be afraid little polar bears the DMD Diamond mint again

I probably scared it. Found some safe place to try investigate the issue, and put few tracing prints to find out where it decides it has no coins to stake... but lunch time came -- you need to be aware that at meetings, the informal networking is most important and one cannot miss lunch.

Now, with a full belly and completed social duty I sit down and see wallets PoS all around (and the explorer is staled, but everything has it's price).

So the PoS code apparently got ashamed and decided to behave. Nothing can beat good food anyway.  

PoS might need some adjustment anyway. We were apparently over-optimisting about the amount of coins available for stake. If more people won't start opening their wallets for staking, we might end up in a similar situation again. The PoS code is very complex and has many variables. My debug code identified that it was not finding suitable checkpoint back in time, old enough to enable staking -- even if it had plenty of 'mature' coins available for staking.

Since our primary goal is stability, if it is not sufficiently broken, we won't "improve" it -- especially if that would create new fork.

On the other hand, I already have some positive improvements on the reduction of CPU usage "during normal operation" and there is plenty of code optimisation that can still be done.

since 20 min
pos seems to work again with big coin pile created after trigger
dont ask me why

happy minting open ur wallets again

still we have to analyze why it behave as it behave

but good part it looks like POS wont run out of pile to mint

i did see now the first POS block who minted which was created after the trigger

so maybe daniel is right

pos network might be able recover without code change

still its a miracle why with a POS min age of 3 days it needed 9 days until the first POS minted block was able to POS again

lets watch this carefull

No need to panic people, the team s aware of this and it should be fixed as soon as possible. Until then, just chill and let your coins collect age.
It is unfortunate this issue arises at the time the price started going up but no worries, we ll fix this problem the same way we ve managed to fix everything else.

Just relax and please give us some time to this, after all, we are all in the same boat.

100% we have a problem. POS does'nt work as it should. Every day is getting worse, now staked only the small piles, large piles do not staked, perhaps the algo (code) does not divide the pile into large and small, but considers them to be the same or something else.
dPZCvVCY9CseU5bhro4Hufh94K27XpMTf7 for examle. In recent days only 0,00000.....