v0.11.2.x Testing

UdjinM6 said:
Oh.. Though it's just testing but...
Wallet will now save additional information about known masternodes to masternode.dat file.
IF YOU HAVE WALLET NAMED MASTERNODES.DAT RENAME IT BEFORE UPGRADING TO V0.11.2.x OR YOU WILL LOSE YOUR COINS
Click to expand...

Ever heard of magic numbers?

Only Windows(yuck) uses extensions to recognize a file type
 
Propulsion said:
Should change it from .dat just to avoid confusion and to avoid the one person who does have a masternode wallet saved as masternode.dat

How about mncache.log?
Click to expand...
masternodes.dat :wink:
Every database here is .dat .... wallet.dat, peers.dat, blk00000.dat .... why .log??

EDIT: however I agree there can be some more specific name that (almost) no one will use as a wallet name - mndb.dat maybe?
 
Last edited by a moderator:
UdjinM6 said:
masternodes.dat :wink:
Every database here is .dat .... wallet.dat, peers.dat, blk00000.dat .... why .log??

EDIT: however I agree there can be some more specific name that (almost) no one will use as a wallet name - mndb.dat maybe?
Click to expand...

Yeah, it does break the naming convention. How about placing it in a directory under darkcoin like blocks or chainstate but named cache?
 
UdjinM6 said:
masternodes.dat :wink:
Every database here is .dat .... wallet.dat, peers.dat, blk00000.dat .... why .log??

EDIT: however I agree there can be some more specific name that (almost) no one will use as a wallet name - mndb.dat maybe?
Click to expand...
+1

mndb.dat is way less conflicting than masternodes.dat
I imagine loads of people have named their wallet masternodes.dat after start-many came :)
 
Propulsion said:
Yeah, it does break the naming convention. How about placing it in a directory under darkcoin like blocks or chainstate but named cache?
Click to expand...
Well.. While this can be done for sure I don't see why would we need to store it alone in some separate folder. Its nature is very close to peers.dat: it holds information about current masternode list, peers who asked us for full masternode list, peers we asked for full masternode list and vins of individual masternodes we asked some peers for. We should move peers.dat too then... :rolleyes:
 
I started a fresh masternode, and right after i made the 1000drk vout, a message appeared in the log (before any confirmations):

CActiveMasternode::ManageStatus() - Input must have least 15 confirmations - -2147468777 confirmations
just a cosmetic log bug, but eh! Another one is when the selected vin list is logged, there are no spaces between the coin amounts in the list.
 
Any ideas why my testnet masternode shows a current balance of:

Code: 
  [
        [
            "xwcfDFxfjLvvxG8KMTzy6G21aXNHZ8mjcS",
            1091.60000000,
            "0"
        ]
    ]

But test.drk.mn shows a different balance:

108.61.119.55:19999Open (1h1m3s)0.11.2xwcfDFxfjLvvxG8KMTzy6G21aXNHZ8mjcS[1]1,122.20016h1m48s22m13s
us.png
United StatesActive (100%)

No other addresses listed with the "listaddressgroupings" command.

Code: 
    "version" : 110200,
    "protocolversion" : 70067,
    "walletversion" : 61000,
    "balance" : 1091.60000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 15009,
    "timeoffset" : 0,
    "connections" : 124,
    "proxy" : "",
    "difficulty" : 0.11887853,
    "testnet" : true,
    "keypoololdest" : 1425501155,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""

Block explorer is confirming test.drk.mn's balance as well: http://test.explorer.darkcoin.fr/address/xwcfDFxfjLvvxG8KMTzy6G21aXNHZ8mjcS

So where are the extra 30.6 coins on the masternode (paid in block 14929)? Blockheight is already 15009 so it show show those coins. It has clearly been paid in the past, reflective of the balance increasing by 91.6. Thoughts?


EDIT: Nevermind, it's adjusted now. Silly me needing to wait for it to roll into available.
 
Last edited by a moderator:
***************************** Please update to 11.2.1 *****************************

This update is for everyone on testnet (Normal clients, masternodes, miners, etc)

Updates:
- Version/protocol bump
- Fixed shared key usage, there were lots of "Downgrades" happening, which results in lower anonymity. (eduffield)
- Masternode cache updates, reject older masternodes from the cache (UdjinM6)
- Translation updates (Vertoe)
- Masternodes.dat verification (UdjinM6)
- Improved comments(mkinney)
- Max rounds changed to 6, DS rounds are more than 100x more secure, so even 4 should be incredibly secure. (eduffield)

Source: https://github.com/darkcoin/darkcoin/tree/v0.11.2.x

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/...34/gitian-win-darkcoin-bin/32/darkcoin-qt.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...n-osx-darkcoin-dist/darkcoin-0.11.2.1-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...34/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...34/gitian-linux-darkcoin-bin/bin/64/darkcoind
 
eduffield said:
***************************** Please update to 11.2.1 *****************************

This update is for everyone on testnet (Normal clients, masternodes, miners, etc)

Updates:
- Version/protocol bump
- Fixed shared key usage, there were lots of "Downgrades" happening, which results in lower anonymity. (eduffield)
- Masternode cache updates, reject older masternodes from the cache (UdjinM6)
- Translation updates (Vertoe)
- Masternodes.dat verification (UdjinM6)
- Improved comments(mkinney)
- Max rounds changed to 6, DS rounds are more than 100x more secure, so even 4 should be incredibly secure. (eduffield)

Source: https://github.com/darkcoin/darkcoin/tree/v0.11.2.x

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/...34/gitian-win-darkcoin-bin/32/darkcoin-qt.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...n-osx-darkcoin-dist/darkcoin-0.11.2.1-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...34/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...34/gitian-linux-darkcoin-bin/bin/64/darkcoind
Click to expand...

Updated. Still hasn't populated under masternode list protocol as 70068, getinfo returning 70068.

./darkcoind masternode list protocol | grep 70068
"128.127.106.235:20004" : 70068,
"128.127.106.235:20005" : 70068,
"128.127.106.235:19999" : 70068,
"128.127.106.235:20000" : 70068,

Removed peers.dat and issued masternode stop before issuing masternode start.
 
Last edited by a moderator:
Code: 
root@vultr:~# ./darkcoind getinfo
{
    "version" : 110201,
    "protocolversion" : 70068,
    "walletversion" : 61000,
    "balance" : 1122.20002000,
    "darksend_balance" : 0.00000000,
    "blocks" : 15058,
    "timeoffset" : 0,
    "connections" : 14,
    "proxy" : "",
    "difficulty" : 0.11966519,
    "testnet" : true,
    "keypoololdest" : 1425501155,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
root@vultr:~# ./darkcoind masternode list protocol | grep 108.61.119.55
    "108.61.119.55:19999" : 70067,
 
30kgeuo.jpg


Updated masternodes to the latest version, and these appeared. Can't recall seeing "Conflicted" transactions before. Also the date is strange, as the MN and the wallet was created after 2/2/2015.
 
illodin said:
30kgeuo.jpg


Updated to the latest. Can't recall seeing "Conflicted" transactions before. Also the date is strange, as the MN and the wallet was created after 2/2/2015.
Click to expand...
I have these conflicted since the first 12x version.

EDIT: I`ve changed the name of the old wallet, started the client again to get new file wallet.dat of course deleted all peers, blockchains and blocks and now the grey conflicted tx are not there anymore.
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top