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

[cesmak]

AS a reminder on how to prepare yourself for transition from DMD 2.0 to DMD 3.0. It's not recommended using any other method.

Exporting and Importing Private Keys

https://bit.diamonds/how_transition_short.pdf

So the other method to use directly the wallet.dat of DMD 2 is no longer valid ?

[cryptonit]

AS a reminder on how to prepare yourself for transition from DMD 2.0 to DMD 3.0. It's not recommended using any other method.

Exporting and Importing Private Keys

https://bit.diamonds/how_transition_short.pdf

So the other method to use directly the wallet.dat of DMD 2 is no longer valid ?

we had people who had issues with corrupted wallets and their passwords not working if the base was a old wallet form DMDv2

we dont want anyone to risc lose access to a maybe new private key where he send coins towards because of that

the only save way we suggest is import private keys into a new DMDv3 wallet.dat

[cryptonit]

hint someone told me community on slack already joins the release network 
in the process of slow increase wallets in network and be able support all questions the best way
the identical to final release wallet is spread in community slack first

DMD Slack
Slack Invite

[markm]

That little guide only talks about importing one single key (at a time), a years old wallet likely has how many, hundreds, maybe more likely thousands?

Isn't there some kind of bulk export of all keys and bulk import of all keys?

Previous instructions I saw did have simply using existing wallet, the "problem" of password difficulties is easily solved by saving an ununcrypted copy of the wallet so that is how I had been planning to proceed since it also meant not worrying about shutting down before the snapshot as whatever state the snapshot caught my wallet would have all the needed keys.

Meanwhile, git pull is still saying already up to date, where are people getting the new code if not via git?

-MarkM-

[NoxX]

That little guide only talks about importing one single key (at a time), a years old wallet likely has how many, hundreds, maybe more likely thousands?

Isn't there some kind of bulk export of all keys and bulk import of all keys?

Previous instructions I saw did have simply using existing wallet, the "problem" of password difficulties is easily solved by saving an ununcrypted copy of the wallet so that is how I had been planning to proceed since it also meant not worrying about shutting down before the snapshot as whatever state the snapshot caught my wallet would have all the needed keys...

-MarkM-

It's one key per address, not per transaction. Ideally, you want to send all coins to one address before exporting the key.

[cryptonit]

That little guide only talks about importing one single key (at a time), a years old wallet likely has how many, hundreds, maybe more likely thousands?

Isn't there some kind of bulk export of all keys and bulk import of all keys?

Previous instructions I saw did have simply using existing wallet, the "problem" of password difficulties is easily solved by saving an ununcrypted copy of the wallet so that is how I had been planning to proceed since it also meant not worrying about shutting down before the snapshot as whatever state the snapshot caught my wallet would have all the needed keys...

-MarkM-

It's one key per address, not per transaction. Ideally, you want to send all coins to one address before exporting the key.

send coins to one address is to late it was part of the preparation guide and it was only able to do this pre snapshot

[markm]

It's one key per address, not per transaction. Ideally, you want to send all coins to one address before exporting the key.

That would have had to have happened before the snapshot. Given that using existing wallet had supposedly been one of the three methods, and seemed the most complete one with least chance of missing a key, I planned for that one.

Aren't there perl scripts or something like bitcoin had years upon years ago for ripping all keys out of a wallet and stuff like that?

Again, I am talking about deliberately not-encrypted wallet...

-MarkM-

[CHAOSiTEC]

Diamond was added on list of hosted masternodes - Welcome to Node-VPS

[NoxX]

It's one key per address, not per transaction. Ideally, you want to send all coins to one address before exporting the key.

That would have had to have happened before the snapshot. Given that using existing wallet had supposedly been one of the three methods, and seemed the most complete one with least chance of missing a key, I planned for that one.

Aren't there perl scripts or something like bitcoin had years upon years ago for ripping all keys out of a wallet and stuff like that?

Again, I am talking about deliberately not-encrypted wallet...

-MarkM-

I believe pywallet can do things like that. It is quite old now but I have used it recently to clean a wallet.dat of unconfirmed transactions:

https://github.com/jackjack-jj/pywallet

EDIT see also here: https://bitcointalk.org/index.php?topic=34028.0

[Limx Dev]

Diamond was added on list of hosted masternodes - Welcome to Node-VPS

Thank you !

Kind Regards Christian

[danbi]

It will probably depend on how bloated/messed up your wallet.dat is.

I have sucessfully imported an wallet.dat file created in 2013, with the new wallet complaining only one public/private key pair was unreadable. But the balance was the same, so v2 software likely just silently ignored that key anyway.

However, I only did this as an experiment! As cryptonit wrote many times, it's not safe procedure and if possible should be avoided.

The process of exporting / importing the keys can of course be scripted. The v2 and v3 wallets provide RPC interfaces where you can query for the list of addresses in the wallet, then for their private keys, build a list and then similarly feed the private keys to the new wallet.

A piece of cake, just few lines of shell code 

[mitchellmint]

It will probably depend on how bloated/messed up your wallet.dat is.

I have sucessfully imported an wallet.dat file created in 2013, with the new wallet complaining only one public/private key pair was unreadable. But the balance was the same, so v2 software likely just silently ignored that key anyway.

However, I only did this as an experiment! As cryptonit wrote many times, it's not safe procedure and if possible should be avoided.

The process of exporting / importing the keys can of course be scripted. The v2 and v3 wallets provide RPC interfaces where you can query for the list of addresses in the wallet, then for their private keys, build a list and then similarly feed the private keys to the new wallet.

A piece of cake, just few lines of shell code 

That's a brilliant IDEA!

[CHAOSiTEC]

It will probably depend on how bloated/messed up your wallet.dat is.

I have sucessfully imported an wallet.dat file created in 2013, with the new wallet complaining only one public/private key pair was unreadable. But the balance was the same, so v2 software likely just silently ignored that key anyway.

However, I only did this as an experiment! As cryptonit wrote many times, it's not safe procedure and if possible should be avoided.

The process of exporting / importing the keys can of course be scripted. The v2 and v3 wallets provide RPC interfaces where you can query for the list of addresses in the wallet, then for their private keys, build a list and then similarly feed the private keys to the new wallet.

A piece of cake, just few lines of shell code 

That's a brilliant IDEA!

this comes to mind:
https://github.com/prof7bit/wallet-key-tool

but alas do your own research, i have not checked this code

[stillontop]

The list of mining pools should be removed from the first posting, could lead to confusion otherwise.

Is the suggested diamond.conf still valid for DMD v3?

Can't wait to migrate

[cryptonit]

dont use old diamond.conf file

[cryptonit]

regarding DMD multipool and DMD cloudmining i did test all with new wallet already
its working we only need to wait until bittrex open gates again
so i can withdraw DMD and spread them

[cryptonit]

everyone who want to join network now join our slack
or wait a few more hours then official links are spread on all channels

hint someone told me community on slack already joins the release network 
in the process of slow increase wallets in network and be able support all questions the best way
the identical to final release wallet is spread in community slack first

DMD Slack
Slack Invite

[TimC]

everyone who want to join network now join our slack
or wait a few more hours then official links are spread on all channels

hint someone told me community on slack already joins the release network 
in the process of slow increase wallets in network and be able support all questions the best way
the identical to final release wallet is spread in community slack first

DMD Slack
Slack Invite

Thanks. I download the V3 wallet and got my keys imported and send 10000 DMD to another wallet and start a master node. Seems like it is up and running now just waiting to see it I get some rewards.

[cryptonit]

Thanks. I download the V3 wallet and got my keys imported and send 10000 DMD to another wallet and start a master node. Seems like it is up and running now just waiting to see it I get some rewards.

up to block 4480 rewards are just symbolic and reduced by 99%
so all the guys have enough time set up their nodes and prepare for the real start of earning

[danbi]

As announced earlier, hosted masternodes will be provided as service to the community. The rationality is you have the funds (DMD), I have the resources to run it and the inclination to fiddle with compiling code and administering servers. You don't have to do any of that.

The service will be provided for a fee. I was educated it's not nice to provide free services
Today, the fee is 5 DMD/month.

The procedure to rent a masternode is as follows (short instruction):

1. You contact me, with your order. Use PM here.
2. I provide you with an address where to pay the fee.
3. You pay the fee.
4. I provide you with the IP address/port and key of the masternode.
5. You send 10k DMD to your own address. You then obtain the transaction output, with the following console command:

masternode outputs

6. In the masternode.conf file in the directory where your wallet.conf is located, you enter:

LABEL IP:PORT KEY TRANSACTION INDEX

The label is anything you care to remember. The IP:PORT and KEY you get from me, and the last two pieces come from "masternode outputs"
(you may have more than one, if you sent more than one 10k pile to yourself).
7. Restart your wallet.
8. You then open the Masternodes tab, where your new masternode will be visible under "My Masternodes". An inactive masternode is with status "MISSING". Click the "Start Missing" button or right-click each "MISSING" entry and select "Start-Alias".
Important: Wait at least 15 blocks after step 5. A masternode collateral needs to be at least 15 blocks old in order to start the masternode. Don't worry -- it will eventually start all by itself, later.
9. In a while (such as after 15 blocks), check your Masternode list again -- Active should be ticking. If you don't intent to actively stake with that wallet, lock it up and shut it down.
You are done. Enjoy DMD pour in your wallet.
10. You might want to set up MultiSend to make the earned coins go to your "main" staking address and be grouped with/staking with the rest of your DMD.

Please note, that it is advisable to do steps 5 and 6 one by one, because after seeting the transaction in masternode.conf upon start, the wallet locks it, so it's less likely you re-send the same 10k over and over.

When other hosted masternode services start appearing, they will use pretty much the same procedure, so if someone finds ways to improve this instruction, please feel free to contribute.