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

https://bitcointalksearch.org/topic/m.7247130

Is Diamond still minable or strictly PoS now?

I think the changes should be partly incorporated into the main source three: there are needed changes in the makefile, a couple cpp files and an additional asm file for scrypt arm (+ all the qnap specific things).
when the new sources are available, I'll redo the same, but this time keeping track of all the changes ;-)

i think its not only interesting for dev but anyone who try achieve that or a similar goal
i suggest once new source is released and u repeat that

u supply a "howto compile diamondDD on QNAP NAS" which we add to our github as a guide

thx for your effort to explore new possible plattforms to run diamond onto

I've succesfully compiled the headless wallet on my QNAP NAS (arm processor).
It wasn't trivial, the wallet code assumes x86 in some places.
Devs let me know if you are interested in which changes I made for arm compatibility.

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

update:

we have already some beta user with release wallet on real network and everything works without issues
(POS will kick it at total coins 450000 and at that moment a hardfork is created everyone required to update pre 26.june)
we release wallet to public once we get a reply from cryptsy
that they able update their wallet until total coins 450000 (~26.june)

are u sure on right blockchain?
i suggest wait a few days for 2.0.2 wallet and then resync from scratch (delete old blockchain)

if u urgend wana fix with 2.0.1 wallet then delete blockchain and download blockchain from here and resync
https://mega.co.nz/#!qZxFhRwI!OhpHJXjhWC2F17XkKiiBuXKxvN9Wk4uD_z8Td1MtoBA
(You have to replace all files except wallet.dat in your AppData/Roaming/Diamond folder)
If ya have a old backup of wallet.dat i would replace the wallet.dat with that too
to get rid of any transactions in a possible wrong fork

Thanks but it didnt work... someone else with other idea? Devs?

this error message is a sign of broken local blockchain database
wait for new wallet and resync blockchain

the rare error that was able to corrupt lokal database is one of the fixed issues
u should never suffer again from this problem with new wallet

Have you tried starting the wallet with 'repairwallet or savagewallet' flags? They go through the blockchain and try to rebuild it it helped me a few times to 'claim' my coins back (different coins).

If in Windows, use Command Prompt /cmd/ , go to the folder you have your wallet-qt executable file and launch the software with one of the above flags e.g. " diamond-qt.exe -repairwallet " if then first one doesn't help, use the other one.

The error reported by the other user is not related to your case + I doubt Cryptsy would know anything about your coins. Hope that helps.

Should i write to Cryptsy support? Cause i dont have any error when i open the wallet, even is in sync but the coins i send are unconfirmed since one week...

This is what I get with my regular wallet that is supposedly NOT on testnet, and is supposedly connected to the working network.




Got another one open on another machine that's working fine though . . . it's been open 24 hours a day for over 3 weeks now waiting for a Crypsty resend of coins lost when the wallet went down last time . . .

Hi,

I have the version 2.0.1.0 of the wallet. Send one week ago some diamonds to Cryptsy and still nothing. On my wallet say Unconfirmed. Maybe someone can tell me whats happening? Also 5 of my diamonds went unconfirmed without advice 

Thanks in advance

be on the hunt  

I had the same experience as you. However, after setting up two nodes, and let them sync everything started just fine with the testnet.

Since the NDA is lifted, as a beta tester I can confirm that staking was successful in the beta network (as well as other successful tests).


We're going through more testing sessions to make sure the whole thing is robust and secure.



Good things are coming soon. 

after the understandable price drop because of missing POS feature
the value develops now again in the right direction

http://www.cryptocoincharts.info/v2/pair/dmd/btc/cryptsy/1-month

time to join in early enough

this time we made sure no new show stopper will block us

NDA for betatesters is lifted u can confirm that u staked successful in beta network (which was a fork of real network just a few days ago)

Cryptsy taking so much time was just ridiculous. Considering that new exchange can make it work faster than them.
Great work, guys. Thank you

some technical detail about the POS implementation we did: