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

Thanks for the response. I updated to the newer version in OP thread and it worked out. Received the 15 DMD i had coming to me without a hitch. Now for cryptsy to finish the update so i can move them over there!

I wish I had noticed this coin previously.

VISUALIZATION OF DIAMOND ROLL-OUT PLAN
(TOTAL COINS AND POW/POS COINS PER MONTH)



RED LINE = new coins each month produced by POW (numbers on right side)
GREEN LINE = new coins produced each month by POS (numbers on right side)
TOTAL COINS (numbers on left side)
numbers on bottom of graphic are the months (the graphic represent a 30 year timeline)

i think for now market price is driven by insta-selling miners
daily *1500 diamonds have to be bought if people would sell instant

but keep a closer eye on coin specs and check how coin roll-out will develop over next 30 years

beginning with total coins 450000 a 50% POS will be simultaneous active with the 1 DMD POW reward each block
and start the diamond rush (BLUE CIRCLE) on pic

if u analyze that u can see that this POW mining paradise only last a few months
(to be exact until 1 million total diamond are existing)
later most of coins are produced by POS  (GREEN ARROW) and to do so u need to have diamonds

everyone who sell 1 diamonds instant lose like at least 2 diamonds.....
because every diamond u mine now would at least double if u keep holding and pos it over time

the whole design of diamond is to be a wealth storage coin aimed to be a good investment

i  hope this visualization of coin specs long-term effect of  on coin roll-out
can help u realize how valuable diamonds will be once POW is reduced by 90%
and high POS will be main source of coin creation

that coins are required to create more coins (POS)
will be the reason for lower availability of coins on exchanges and increasing prices
remember only coins in ur wallet gather coin-age and can generate POS rewards

then its shouldnt be that hard
just leave ur wallet open a few days
and remember u need it unlocked to be able take part in minting

some  people like me keep wallet open 24/7 to make sure network always protected by staking coins

other people just open once in a while a few hours

both will work

the advantage of be in mint mode always is only interesting if ya have a significant amount of diamonds

because then another nice pos feature kicks in which if ur coin pile is so big that he even with low age (beween 7 and 30 days) successfull able to mint he is splitted into two coin pile

this way  by coin grouping after 30 days age and coin splitting below 30 days age sooner or later all our wallets contain dmd pile around 100 dmd which is the ideal size in our POS implementation

aaa nice , I got about 180 DMD in my wallet. All in same stack.

I have been holding my wallet open for a few hours now, have not started staking yet. The wallet is fully updated and synced. and I've had the coin in the wallet since 16.05.2014. I have never  received any staking before. It just takes some time the first time?  

Do the POS blocks count towards difficulty calculations? Difficulty has risen pretty sharply, I'm not sure if the network hashrate has risen as much...

I try and load diamond-qt from the op link and it just sits there frozen on loading block index eventually getting an exception error. I downloaded the entire blockchain yesterday from peers rather then from the op. Any suggestions?

The error says

Assertion Failed!
file src/kernal.cpp line 412
expression pindex -> pprev || pindex get blockhash iftestnet ? hashgenesisblock : hashgenesisblocktestnet)...

any clues?

hello i have a problem, unfortunately I can not connect to my rig to the pool dmdpool.digsys.bg:3345 and I can not get no reward as I do

Mind you, I am good at writing scripts and have dozens of different compressors, for the collectors

But need to spend more time with the real fixes....


Unfortunately, due to time limitations, all 2.0.2.2 clients show up as 2.0.2.1 so we can't say who is unprotected, which is sad.
But it turns out not only are there several versions numbers in the wallet code, but also each of these is used randomly on different places and some are critical, as for example making the GUI display "version THIS" would make the code overwrite the database version number in the wallet.dat file with version THIS and make it impossible to open on an "older" version. Even if the version difference is just a cosmetic one....

In any case, once we disconnect the older wallets, they will wake up and come here.

Beat me to the punch LOL my repack does not have a README for instructions .
Glad you are staying on top of things Danbi

Still 24% of the clients are using pre-2.0.2.1 wallets.

Following your recommendations, the block chain archive is repacked. It is still in an ZIP file, slightly better compressed (saved a whooping megabyte), but now unpacks in a folder with the same name as the archive and has README with instructions.