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

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

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

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

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

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.

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

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

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!