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

[cryptonit]

Hi to all.

Have a questions about the v3 walet:
1. As I understand, to begin the stake process, the wallet should be encrypted with password, and it's need to be unlocked to be able to stake?
2. Is there commandline option to automatically unlock the wallet at startup?
3. The old wallet.dat was imported, with the message, that the file is readed, but the transactions and addr.book may be incorrect, so I've take the way via export/import private key. The import was successfull, but my dmd address was changed. Now, the question: what will happen with the DMD cloudmining? The new address is not linked to the old one...
3a) To where the CM paymens will go? (assuming, to the old address)
3b) How to set the new address as the reward recipient for CloudMining?
3c) Is there a way to get rid of the message about the incorrect transactions history and addr.book? This message is stopping the wallet from work, until I close it manually

Thanks.

2. if u wana write ur password into a script u dont need a password at all i would say......
a wallet without password will be always in "unlocked" status

3. dont import old wallet follow this guide to import old address private keys (including the registered at cloudmining key) into a fresh new DMDv3 wallet
http://bit.diamonds/how_transition_short.pdf

3a 3b 3c all solved when u follow the guide and use a native DMDv3 wallet with imported private keys

[1715238447]

1715238447

[1715238447]

1715238447

[1715238447]

1715238447

[1715238447]

1715238447

[danbi]

On your questions.

1. You do not have to encrypt the wallet in order to stake. In fact, the opposite is true. In order to stake, the wallet must not be encrypted (or of encrypted, must be unlocked). You encrypt the wallet for your own security, especially if you use insecure environment or OS.

2. There is no point to encrypt the wallet if it will be unlocked without you entering the password (which only you know). See 1. In such cases, simply do not encrypt the wallet.

3. This is good news. It means that DMDv3 was able to recover all of your keys (and addresses), but becaus ethey are in different format, transactions and address book entries cannot be preserved. In this case, run the wallet with -upgradewallet (or if useing the GUI, the same action is in the Repair Wallet option).
At this point your wallet should behave like normal. But it will still be one large file. In order to shrink it to the minimum, the more agressive -salvagewallet can be used.
Please note both could be unsafe in some circumstances, especially if your wallet was messed up (but the message you cite indicates this might not be the case).
You can export the private keys, with "dumpwallet" (in console) or manually as explained.
Then remove wallet.dat and import them with "importwallet".

If you imported your private key(s), then your addresses are still there, but because you did not import the address book you don't see them. You can verify what addresses your wallet thinks you have (only those that ever received coins) with the command "listaddressgroupings".

3c. It should be gone after -upgradewallet.

PS: As helmut mentioned, if you want to be safe, use only the exported keys and do not use the old wallet.dat file. See "listaddressgroupings" for the list of what addresses you have there.

[dalefrench]

I am just now learning of this new wallet.  Yesterday, I sent five dmd to Bittrexx exchange from old wallet.  Are they lost?  The old wallet says they are sent and the Bittrexx deposit address has not changed since last time I sent there.   They are not in Bittrexxes pending deposits since yesterday.  Please help.  Thanks.

[NoxX]

I am just now learning of this new wallet.  Yesterday, I sent five dmd to Bittrexx exchange from old wallet.  Are they lost?  The old wallet says they are sent and the Bittrexx deposit address has not changed since last time I sent there.   They are not in Bittrexxes pending deposits since yesterday.  Please help.  Thanks.

The snapshot of DMD v2 was taken on the 15th September, any transactions after that are not reflected in DMD v3.

This means your coins are fine, if you export your DMD v2 private key and import into DMD v3 wallet as per the instructions your v3 wallet will show the correct amount including the coins you sent (well, didn't sent) to Bittrex.

[dalefrench]

I am just now learning of this new wallet.  Yesterday, I sent five dmd to Bittrexx exchange from old wallet.  Are they lost?  The old wallet says they are sent and the Bittrexx deposit address has not changed since last time I sent there.   They are not in Bittrexxes pending deposits since yesterday.  Please help.  Thanks.

The snapshot of DMD v2 was taken on the 15th September, any transactions after that are not reflected in DMD v3.

This means your coins are fine, if you export your DMD v2 private key and import into DMD v3 wallet as per the instructions your v3 wallet will show the correct amount including the coins you sent (well, didn't sent) to Bittrex.

Thanks for the quick response!  Must appreciated!

[crazyivan]

I am just now learning of this new wallet.  Yesterday, I sent five dmd to Bittrexx exchange from old wallet.  Are they lost?  The old wallet says they are sent and the Bittrexx deposit address has not changed since last time I sent there.   They are not in Bittrexxes pending deposits since yesterday.  Please help.  Thanks.

The snapshot of DMD v2 was taken on the 15th September, any transactions after that are not reflected in DMD v3.

This means your coins are fine, if you export your DMD v2 private key and import into DMD v3 wallet as per the instructions your v3 wallet will show the correct amount including the coins you sent (well, didn't sent) to Bittrex.

Thanks for the quick response!  Must appreciated!

Please make sure you use this guide to import your wallet to V3.

http://bit.diamonds/how_transition_short.pdf

[sms301]

DM Wallet 3.0 up and running. Got all coins. Can i delete the DMD 2.0 now?

[Rumhurius]

public official masternode how to when ?

[BogdanCo]

What about raspi? I tried to use scripts according to instructions in INSTALL file (in source code) and I got message I haven't proper version of Berkeley DB.

Someone in the slack channel mentioned that you have to use Berkeley DB 4.8 I believe. I haven't had time to test it myself, but this might help:

https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#berkeley-db

Let me know if you have any success!  

Don't waste your time with all these libs like I did . You will get all the libs needed and then the wallet will fail to compile because the CPU is on another architecture (armv7l or something).
Someone posted the builds (wallet compiled) for raspberry Pi on the slack channel, they are working for Raspbian and also for Rokos Core: https://drive.google.com/open?id=0B0NqMbA-2YNVOXlEZXYwYlMwMlk


Thanks a lot dbraford!

PS: we are waiting for the GUI wallet also 

[sirazimuth]

DM Wallet 3.0 up and running. Got all coins. Can i delete the DMD 2.0 now?

Why bother?
Is your hard drive full or something?
I won't delete mine. Its legacy. It has history I may need to ref some day, and doesn't affect anything.

[amd64ever]

How many confirmations needed to start pos generation on dmd v3?

[turdminer]

How many confirmations needed to start pos generation on dmd v3?

mine started to mint within an hour or so of v3 transfer, takes 641 confirmations

[Woody20285]

Thanks to Danbi for the MN setup

[Lionel]

I have 26.39 DMD and i've started the wallet with -staking=1 but the staking is still not active.

Why?

[amd64ever]

I have 26.39 DMD and i've started the wallet with -staking=1 but the staking is still not active.

Why?

my pos staking was not active too until i restart wallet

[shveicar]

I have 26.39 DMD and i've started the wallet with -staking=1 but the staking is still not active.

Why?

If you add this line in the file diamond.conf it should look like as

Code:

staking=1

but in the basic settings, you can and no add this line to the file dimond.conf and your wallet will still have POS minting.

[temp89]

What about raspi? I tried to use scripts according to instructions in INSTALL file (in source code) and I got message I haven't proper version of Berkeley DB.

Someone in the slack channel mentioned that you have to use Berkeley DB 4.8 I believe. I haven't had time to test it myself, but this might help:

https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#berkeley-db

Let me know if you have any success! 

The command from your link (for DMD code source):

./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" # (other args...)

generates error:

C++ compiler cannot create executables

for portable wallet.dat file, you need 4.8 else you can do --with-incompatible-bdb in the ./configure line

After 3 hours (sic!) make command was ended and I even found diamond-qt file but I get error:

This program was compiled against version 2.6.1 of the Protocol Buffer runtime library, which is not compatible with the installed version (3.0.0).

every time when I try to run the program.

Don't waste your time with all these libs like I did . You will get all the libs needed and then the wallet will fail to compile because the CPU is on another architecture (armv7l or something).
Someone posted the builds (wallet compiled) for raspberry Pi on the slack channel, they are working for Raspbian and also for Rokos Core: https://drive.google.com/open?id=0B0NqMbA-2YNVOXlEZXYwYlMwMlk

Too late. I wasted my time yesterday but thanks for info .

Is dbraford trusted person? Can I use files from him/her safely?

[Shivoreun]

danbi
cryptonit
OK, now it's more clear to me, thanks for your answers
I've removed the old wallet.dat, because -upgradewallet option didn't solved the problem with the error message. So, I've started fresh wallet, it have generated new wallet.dat, then imported the private key, and now see the 2 addreses - the old one, and the v3. Ballance is OK... This wallet is not encrypted, and it's not staking
The debug console shows this:

Code:

getstakingstatus

{
    "validtime" : true,
    "haveconnections" : true,
    "walletunlocked" : true,
    "mintablecoins" : true,
    "enoughcoins" : true,
    "mnsync" : true
}

But the diamond icon is gray and hover tooltip says "Staking is not active". If I encrypt the wallet, and get it unlocked by typing a password, the staking is active immediatelly... What should I do, to get wallet staking, without locking it with the password?

Thanks in advance for help.

[temp89]

Date / Time	Blocks	Height	Interval	Transactions	Value Out	Difficulty	Generated+Fees
2017-09-19 Tue	183	3923	-	54	166,014.728 DMD	5569.2 ± 24%	2,475.63589707
2017-09-18 Mon	641	3740	134.8	454	1,058,772.883 DMD	6258.6 ± 53%	14.92628301

Is that possible? We are still in slow startup phase.

https://chainz.cryptoid.info/dmd/address.dws?dJCtEVEqoBuEy5t5A5faZKSKiUBTwKThEb.htm - lucky man; 2,471.381 DMD in one stake .

[eliano]

Date / Time	Blocks	Height	Interval	Transactions	Value Out	Difficulty	Generated+Fees
2017-09-19 Tue	183	3923	-	54	166,014.728 DMD	5569.2 ± 24%	2,475.63589707
2017-09-18 Mon	641	3740	134.8	454	1,058,772.883 DMD	6258.6 ± 53%	14.92628301

Is that possible? We are still in slow startup phase.

https://chainz.cryptoid.info/dmd/address.dws?dJCtEVEqoBuEy5t5A5faZKSKiUBTwKThEb.htm - lucky man; 2,471.381 DMD in one stake .

I suspect a little glitch in the blockchain scanning engine of the site:
https://chainz.cryptoid.info/dmd/tx.dws?8704.htm

Previous transaction shows 26.619 DMD 'in' and 2,498.0 + 0.015275 'out', that's over 9000% stake, YESSSSSS!