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

[cryptonit]

looking at the actual POS diff i suggest to everyone use
setstakesplitthreshold 200
in console

and ist not structuring ur coin pile instant to this size
its affecting just that the split at POS wont happen if the result would be lower than 200 dmd
and later on in a few days  it will start try smaller inputs below 200  when finding a POS block
(only inputs older than 5 days are considered to be merged)

if u want to instant split ur coins u need to use the UTXO tool at send coins
i think @shveicar wrote a guide for that already
it will be part of his tipps and tricks DMDv3 page he release soon

[1714872537]

1714872537

[1714872537]

1714872537

[1714872537]

1714872537

[1714872537]

1714872537

[examelon]

All the best to your project!

Masternode is very attractive!

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

Everybody, sorry for disturb. The staking become active, after adding staking=1 into diamond.conf and restarting the wallet.

[tanakan]

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! 

Danbi, cryptonit, can you tell us what's happen?

[cryptonit]

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! 

Danbi, cryptonit, can you tell us what's happen?

analyzing

[Limx Dev]

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!  

Danbi, cryptonit, can you tell us what's happen?

analyzing

We can currently not explain this transaction. Kind Regards Christian

[fairglu]

This screenshot seems to agree with my explorer on the transaction lines (near bottom), note how the input amount is 26.619, but there are three outputs with values 0, 2498 and 0.015275 respectively.

The raw transaction reports the same figures (https://chainz.cryptoid.info/dmd/tx.dws?fd6bf7e7d04899ebd0b900060bc387c933d5eb47791b869fd02666bb9eb688ce.htm, click "raw transaction" or see below)

Not sure why the generated value is reported as 0.0235 in that screenshot, or maybe there is a bug in the raw transaction API ?

Code:

{
   "txid": "fd6bf7e7d04899ebd0b900060bc387c933d5eb47791b869fd02666bb9eb688ce",
   "version": 1,
   "locktime": 0,
   "vin": [
      {
         "txid": "14a17b25a0348d66c35f78ca490291a20a154daa018f2b777cb919dd9f5de71b",
         "vout": 0,
         "scriptSig": {
            "asm": "3045022100d44734a8ed58bc0ad6b7be12fe156b4a17535a2fa27afccdc1a0251c82579f7202201db3a434c9568b312a7212a6d86d552936f0886f88d0adb66b73a67208fd40e201 03c4f0089b134e63511620e153907dc57ecaa792623b8bbf59bcf6ff91dfa94130",
            "hex": "483045022100d44734a8ed58bc0ad6b7be12fe156b4a17535a2fa27afccdc1a0251c82579f7202201db3a434c9568b312a7212a6d86d552936f0886f88d0adb66b73a67208fd40e2012103c4f0089b134e63511620e153907dc57ecaa792623b8bbf59bcf6ff91dfa94130"
         },
         "sequence": 4294967295
      }
   ],
   "vout": [
      {
         "value": 0,
         "n": 0,
         "scriptPubKey": {
            "asm": "",
            "hex": "",
            "type": "nonstandard"
         }
      },
      {
         "value": 2498,
         "n": 1,
         "scriptPubKey": {
            "asm": "03c4f0089b134e63511620e153907dc57ecaa792623b8bbf59bcf6ff91dfa94130 OP_CHECKSIG",
            "hex": "2103c4f0089b134e63511620e153907dc57ecaa792623b8bbf59bcf6ff91dfa94130ac",
            "reqSigs": 1,
            "type": "pubkey",
            "addresses": [
               "dJCtEVEqoBuEy5t5A5faZKSKiUBTwKThEb"
            ]
         }
      },
      {
         "value": 0.015275,
         "n": 2,
         "scriptPubKey": {
            "asm": "OP_DUP OP_HASH160 91257b1e75282903ada3153fdd03d3e5ca12d461 OP_EQUALVERIFY OP_CHECKSIG",
            "hex": "76a91491257b1e75282903ada3153fdd03d3e5ca12d46188ac",
            "reqSigs": 1,
            "type": "pubkeyhash",
            "addresses": [
               "dSekVow8PvDgoSecrJEdAWHwwUeqqHigGt"
            ]
         }
      }
   ],
   "blockhash": "7639e9850499ebba1d50781c45b5bbe1cefed951f2b58c5247ed0e4fe0f26d2a",
   "confirmations": 275,
   "time": 1505793863,
   "blocktime": 1505793863
}

[cryptonit]

better save then sorry we requested bittrex to stop execute deposite and withdraw
while we analyze this

[YGung]

quick confirmation needed please:

I transitioned to DMDV3.0 via the original transition guide using method 2:  http://bit.diamonds/DMD_2.0_to_3.0_guide.pdf

My DMD were transferred over on the 14th, and I've got what I believe to be incoming cloudmining transactions up to the 18th.  My balance is correct and everything looks fine to me, only notable difference to me is that the wallet labels didn't carry over, and my address isn't shown as a receiving address.

Now seeing everyone urged to do the short transition on the OP which is a bit different then method 2 from the original guide.  Do I need to wipe my current DMDV3.0 install and do a clean one now using the short transition guide, or am I good?

[Lionel]

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.

When i first run the wallet i did not change the settings, and the issue was still there.
Without specifying staking=1  my staking is not active.
After specifying it both from the command line and diamond.conf, it is still not active.
These are the contents of my diamong.conf:

Code:

staking=1

And this is my debug.log file: https://1drv.ms/u/s!Ao4pRXNsgcpfimXILp4JsCVCMm7V

Is there some dev that can check it out please?

Maybe i must run it as a masternode??

[Lionel]

Now it is active.
I don't understand why yesterday and the whole last night it wasn't for all the time .

Now i have just restarted and unlocked the wallet with my password and i have waited some time... and magically the staking is active.

Strange..

[cryptonit]

quick confirmation needed please:

I transitioned to DMDV3.0 via the original transition guide using method 2:  http://bit.diamonds/DMD_2.0_to_3.0_guide.pdf

My DMD were transferred over on the 14th, and I've got what I believe to be incoming cloudmining transactions up to the 18th.  My balance is correct and everything looks fine to me, only notable difference to me is that the wallet labels didn't carry over, and my address isn't shown as a receiving address.

Now seeing everyone urged to do the short transition on the OP which is a bit different then method 2 from the original guide.  Do I need to wipe my current DMDV3.0 install and do a clean one now using the short transition guide, or am I good?

hi ygung

its strong suggested u follow the new migration guide
http://bit.diamonds/how_transition_short.pdf
keep using a wallet.dat from old wallet have a risc involved
i dont suggest everyone to take even if it looks like ok on a quick view

important is that u make no transactions or whatever with the old wallet.dat inside
the new DMDv3 wallet to not risc losing coins in addresses u wont have access when the worst case happens and the wallet.dat get corrupted

close the wallet rename the wallet.dat to wallet.dat.old

restart wallet

a new wallet is generated

now u can start import private keys from old DMDv2 wallet following the guide
u can have both clinets the old and the new running same time and just dump and import the keys one by one

after finished u should again have full balance but based on a native v3 wallet.dat

when finished do ur protection and backup work (encrypt wallet and backup wallet.dat )

then u should be ok

[YGung]

^^^^Thanks for the quick response. Followed the instructions you gave as well as the short transition guide and I'm back up and running and everything looks good. 

[New2Crypto2018]

Has anyone Notice the Blockchain is stalled at Block 4480...

[New2Crypto2018]

Hello?? Come on Guys...WTF??!?

[big_coins]

4480 is last of no value blocks. I'm sure the team will sort when they wake up as its very early.

[New2Crypto2018]

Chain is moving again.. How many confirms to start staking??

[shveicar]

Chain is moving again.. How many confirms to start staking??

All the same as before.
640 blocks before the found coins are fully confirmed.

[New2Crypto2018]

ok, how many confirms before fresh coins sent from the exchange are eligible to start staking?? is it still 640 confirms?

[shveicar]

ok, how many confirms before fresh coins sent from the exchange are eligible to start staking?? is it still 640 confirms?

No.
You can start POS minting after one hour after the receipt of your coins in the wallet