[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%

[cryptonit]

hi all i have minited 13 times on the 18th, i thought i was on a fork, so i re-downloaded twice, resynchronized from clean chain, and still those 13 minted coins are still all good??? dose this sound right?? it was on only 180dmd

thats ok

when POS time reduced from 600 to 100 sec that mean people will create 6x more pos blocks

but the reward stay the same its just split into more blocks

50% POS reward each year (~42 each month for 1000 DMD u own)

Quick question about the POS my wallet has been running almost the entire 3 day period for maturing my coins but then my stupid windows did an update on its own where it had to restart my computer so does my POS starting time start all over again because the wallet was closed for like 10 mins???

u gather coin-age no matter if online or not
but u can claim to mint the coin-age only when online and in minting mode

claiming ur coin-age converted into rewards thats "prove of stake" POS

[cryptonit]

DMD Diamonds lot active wallets
around the whole globe nice to see special that we expand to new places
last time south america was empty

china is weak india is empty africa is empty

i think in that regions is potential to expand

africa have lot business related to diamonds

the brand should have power there

china one superpower in BTC trading volume is for DMD extreme underdeveloped

someone with ability to speak/write chinese should explore the communication hubs there and spread ther word about DMD

india i think could be a new upcomining crypto market

[winmkx]

I noticed that DMD is in Top100 coinmarketcap. Sounds like a very good achievement.

[crazyivan]

I noticed that DMD is in Top100 coinmarketcap. Sounds like a very good achievement.

Top 100 s nothing. We re going up to 50.

[cryptonit]

we dedected some issues with pos and analyzing it

shame on us to not dedected this one in our tests


pos will once network run out of old coins stop
network will run on pow only mode

we will release a wallet with fix and a trigger when fix go active so all have enought time to upgrade

positive sideeffect this wallet will also contain some of the performance optimisations daniel did work on already

yes like u all im unsatisfied that one major bug found its way into tlast wallet release

but we will make the best out of the situation

at least we can show again that we have a active dev team able dedect and fix issues

[utahjohn]

Regarding POS bug: Should I close wallet until next release?  Been sick for a few days and not looked at forum ...  POW seems to have dropped to around 1/4 ...

[cryptonit]

Regarding POS bug: Should I close wallet until next release?  Been sick for a few days and not looked at forum ...  POW seems to have dropped to around 1/4 ...

as long as people have old coins age before 13.04 (find out with coin control)  keep wallet open is helpful for network to create pos blocks

once u out of old blocks u can close wallet until fix is released

[utahjohn]

@Danbi what exactly is POS problem so I can examine it ...
@Cryptonit OK I have shutdown wallet, only have 2 large piles and they have staked.

[big_coins]

@Danbi what exactly is POS problem so I can examine it ...
@Cryptonit OK I have shutdown wallet, only have 2 large piles and they have staked.

they won't stake anymore until new wallet comes out.

[danbi]

@Danbi what exactly is POS problem so I can examine it ...
@Cryptonit OK I have shutdown wallet, only have 2 large piles and they have staked.

I am far away and not available for code modifications (without annoying a lot of influencial people), but I don't believe there is a problem with code -- it is more like less people keep their wallets online and open for staking.

So a trivial way to resolve it would be to put your wallet online and let it stake :-)

Until couple of days, when I will be able to confirm if there is a code problem or not.

PS: I also advise people to make use of setchangeaddress= setting in the wallet, to avoid creating too many small piles with 'change' that will have hard time staking by themselves, and won't be 'vacuumed' by PoS, because PoS group stakes only amounts in the same kernel (address). Cryptocurrency terminology is weird at times, as so many people from different cultures and linguistic envoronments contributed over the years.
setchangeaddress= is useful when you send coins, to specify where the change should be sent. Usually, you set it to your 'main' or 'change' address -- which might be in the same or different wallet. You could for example set it to your staking address as well. For example, if you have an 500.001 DMD pile and send 200 DMD somewhere, you will end up with an 300 DMD pile (0.001 will go for the fees) and if you have setchangeaddress= setting, that 300 DMD will go to the specified address. If you don't set it, usually a new address will be created in your wallet and the 300 DMD change will be sent there. Which might be a problem, as you will then have to backup the wallet after that transaction, or risk losing those 300 DMD if you damage the wallet.dat file. Things like that.

[cryptonit]

i can understand busy between two business meetings far away of home
daniel was not able to analyze the problem and did see that some POS is still happening
once he returns from this business trip he will im afraid have to agree with me that we have a issue that need a code update

but this is a case where i would love to be wrong and daniel is right that everything works fine

[cryptonit]

PS: I also advise people to make use of setchangeaddress= setting in the wallet, to avoid creating too many small piles with 'change' that will have hard time staking by themselves, and won't be 'vacuumed' by PoS, because PoS group stakes only amounts in the same kernel (address). Cryptocurrency terminology is weird at times, as so many people from different cultures and linguistic envoronments contributed over the years.
setchangeaddress= is useful when you send coins, to specify where the change should be sent. Usually, you set it to your 'main' or 'change' address -- which might be in the same or different wallet. You could for example set it to your staking address as well. For example, if you have an 500.001 DMD pile and send 200 DMD somewhere, you will end up with an 300 DMD pile (0.001 will go for the fees) and if you have setchangeaddress= setting, that 300 DMD will go to the specified address. If you don't set it, usually a new address will be created in your wallet and the 300 DMD change will be sent there. Which might be a problem, as you will then have to backup the wallet after that transaction, or risk losing those 300 DMD if you damage the wallet.dat file. Things like that.

idea:

what if by default the first (oldest) address in a wallet file will be the change address
if not configured different in diamond.conf

[Star65]

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.....

[crazyivan]

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.....

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.

[cryptonit]

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

[cryptonit]

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

[danbi]

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.

[cryptonit]

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

[cryptonit]

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

[Star65]

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!