12.1 Testnet Testing Phase Two Ignition

Status
Not open for further replies.
italx said:
What does "WATCHDOG_EXPIRED" in my masternodes tab / status column in the wallet mean?
Click to expand...

On a newly started masternode? That message comes up on the first run and should change as soon as Sentinel runs (to pre-enabled iirc), not really a bug but apparently it'll be changed to something less confusing before release.
 
So it looks like multi-session is an option that is turned off by default. Why is that? Is it less secure?

Unless it is MUCH less secure, this is a feature everyone would benefit from, so I don't understand why 1- we have the option of turning it on / off and 2- why it's not on by default.

Frankly, Dash is getting a bit too complex with it's choices. In open source projects, this becomes the norm - but at the price of losing your users to the dumbed down easier to use options out there. Take my android phone vs my daughter's iphone. Hers functions cleanly and is super easy to understand. Mine has had quite a learning curve, which I'm still on.

What am I saying? Well, we kind of have covered this by making it so you have to turn these extra tabs and options on in the wallet to access them, but it seems that all the useful features are defaulted to off. I think we should make the most useful / fast /easy options the default, and if you want to change those to "more safe" vs "faster", you then have to poke around in the wallet. Because most people in the future will not be so concerned about extreme privacy (the sort you are worried about because you're doing something highly illegal) but rather want general, quick and cheap privacy and ease of use to buy groceries, etc... So make the default settings for those people (whom we'd rather associate with anyway) and leave the obfuscation to those who are motivated by fear to figure out.

Dash has long taken the approach to be for general use. Privacy was always for personal privacy and personal protection against unreasonable search and seizure, etc... So I think keeping the default wallet in line with ease of use for best/fastest/safest against theft and loss features trumps those for ultra anon uses.

Take Crowning's backup feature. The wallet makes a backup each time it's shut down (or is it backed up when started??) anyway, this is priceless for a regular "normal" person. But because I am paranoid and don't want to leave my wallet, though well encrypted, on my computer, I pack up my MN when I have to expose them on the internet, and delete the wallet.dat files in the backup folder each time. But I like the feature, because it still keeps me safe in case I screw something up until I delete it :)
 
One more thing. I tried to consolidate a bunch of inputs, but they were too big (I suppose over the 1 or 2 mb allowed per block). This got me thinking. Lets say you're buying something big and expensive, like a house. But you can't send the funds in one chunk, which makes the transaction messy and multiplies the risks to both parties (you can't just hand over the deed/money instantly (ok, escrow would normally be used BUT)

I was wondering if there could be a feature where the user could prepare for a large purchase by having all their inputs pre-consolidated into one input. So when it's time to pay, they know they can do it in one simple step with minimum inputs.

You could do this manually, but it'd be so much easier if the wallet could do this for you. Especially if there were an algorithm that could determine which inputs to combine to maintain the most privacy for people you've previously mixed with.

Just a thought.
 
stan.distortion said:
On a newly started masternode? That message comes up on the first run and should change as soon as Sentinel runs (to pre-enabled iirc), not really a bug but apparently it'll be changed to something less confusing before release.
Click to expand...

Thanks for the info. Checking back today one has changed to say "ENABLED" and the other two now say "POSE_BAN". No idea what that means. I had reinstalled and setup them all yesterday with newly downloaded versions of dash and sentinel. I'll have to do more investigation when I have some time.
 
TanteStefana said:
So it looks like multi-session is an option that is turned off by default. Why is that? Is it less secure?

Unless it is MUCH less secure, this is a feature everyone would benefit from, so I don't understand why 1- we have the option of turning it on / off and 2- why it's not on by default.

Frankly, Dash is getting a bit too complex with it's choices. In open source projects, this becomes the norm - but at the price of losing your users to the dumbed down easier to use options out there. Take my android phone vs my daughter's iphone. Hers functions cleanly and is super easy to understand. Mine has had quite a learning curve, which I'm still on.

What am I saying? Well, we kind of have covered this by making it so you have to turn these extra tabs and options on in the wallet to access them, but it seems that all the useful features are defaulted to off. I think we should make the most useful / fast /easy options the default, and if you want to change those to "more safe" vs "faster", you then have to poke around in the wallet. Because most people in the future will not be so concerned about extreme privacy (the sort you are worried about because you're doing something highly illegal) but rather want general, quick and cheap privacy and ease of use to buy groceries, etc... So make the default settings for those people (whom we'd rather associate with anyway) and leave the obfuscation to those who are motivated by fear to figure out.

Dash has long taken the approach to be for general use. Privacy was always for personal privacy and personal protection against unreasonable search and seizure, etc... So I think keeping the default wallet in line with ease of use for best/fastest/safest against theft and loss features trumps those for ultra anon uses.

Take Crowning's backup feature. The wallet makes a backup each time it's shut down (or is it backed up when started??) anyway, this is priceless for a regular "normal" person. But because I am paranoid and don't want to leave my wallet, though well encrypted, on my computer, I pack up my MN when I have to expose them on the internet, and delete the wallet.dat files in the backup folder each time. But I like the feature, because it still keeps me safe in case I screw something up until I delete it :)
Click to expand...
To put it simply - "DS MultiSession" is 1+ year old (omg :eek:, I didn't realize that), here is the PR - https://github.com/dashpay/dash/pull/615 (don't be confused by such a small amount of changes in this specific PR, all actual work to clean the code to be able to finally do this was done before it, that one was "the final switch" ;)). It was an experimental and unproved feature back then and could consume all your keypool in few seconds if anything gone wrong. I know, I had these o_O moments few times myself. Obviously, I wouldn't advise any general user to use it back then. I've been using it for mixing all this year (including my mainnet funds) and since then few edge cases/bugs were fixed, few additional safety checks implemented etc. Finally, this https://github.com/dashpay/dash/pull/882 was implemented, so eventually multi-session feature became both proven and quite safe (hopefully). If massive testing of multi-session mixing on testnet won't bring any surprises like rapid keypool depletion or stuck txes or smth like that AND everyone agree it's safe enough I think we can turn it on by default :)
 
If I include the line 'createwalletbackups=0' in dash.conf, it causes mixing to be 'Disabled'... is this by design?
 
bertlebbert said:
If I include the line 'createwalletbackups=0' in dash.conf, it causes mixing to be 'Disabled'... is this by design?
Click to expand...
Yep
Screen Shot 2016-10-28 at 12.56.36.png
 
Yep, that's the screen I get - I had to investigate a bit to determine it's caused by 'createwalletbackups=0' - not sure how those two are related... that's why I figured best check that it's by design. Cool, thanks Udjin :)
 
Open pull requests = 0 :)

I will test commits 4894345 once it gets available for download (meaning i will do some mixing / IS / PS) . Call me optimistic but i get the feeling we are entering a new phase on testnet but i do have a question though :
is there a status update about the superblocks on Testnet ? did you guys manage to have a superblock created on Testnet or do more masternodes need to upgrade ?

edit : does this mean what i think it means ? (version v0.12.1.0-b3f14b3 btw)

e6ZUgzN.png
 
Last edited:
qwizzie said:
edit : does this mean what i think it means ? (version v0.12.1.0-b3f14b3 btw)
Click to expand...

Not sure if this is what you're asking, but superblocks will still be monthly on mainnet. We needed a quicker way to test them on testnet, so testnet superblocks are hourly.

We still need to get testnet stable for now (e.g. no forks and "gobject list" shouldn't take more than a few seconds) before asking lots of people to upgrade at this point. But with the latest commit it's looking a lot better. There are still some governance optimizations coming down the pike that should help a lot. I don't believe we've had an automated superblock yet, but network stability concerns have taken priority ATM.
 
I did some testing on latest build :

v0.12.1.0-4894345
Windows 64bit

Mixing Testing : some of my wallets get slightly over the set target amount of 1000 Dash but that is no big deal. All my wallets stop mixing when they reach 100%
FhcHr4i.png


PrivateSend Testing :

Wallet 4 with privatesend balance of 1100 Dash
* sending 10 Dash with PrivateSend to Wallet 5 :

4EPzc0K.png


Wallet 5 with privatesend balance of 1100 dash
* sending 99.90 Dash with PrivateSend to Wallet 6 :

QT3eXxH.png


Note : trying to PrivateSend amounts ranging between 1 and 99.90 get above error message !!

* sending 100 Dash with PrivateSend to Wallet 5 :

6VNRUBr.png


* sending 99.91 Dash with PrivateSend to Wallet 6 :

IwemeVT.png


PrivateSend Conclusion : Only amounts ranging from 99.91 and higher can be used for PrivateSend ? (i havent tested the upper limit)

InstantSend & PrivateSend Testing :

* 100 Dash with both PrivateSend & Intstantsend on : successfull (5 confirmations)
Status: 5/unconfirmed (verified via InstantSend), broadcast through 21 node(s)
Click to expand...
* 200 Dash with both PrivateSend & Intstantsend on : successfull (5 confirmations)
Status: 5/unconfirmed (verified via InstantSend), broadcast through 15 node(s)
Click to expand...
* 210 Dash with both PrivateSend & Intstantsend on and with PS balance of 1000 dash : error (unable to locate enough PrivateSend denominated funds for this transaction)
Note : could be due to a limit of InstantSend ?
 
qwizzie said:
I did some testing on latest build :

v0.12.1.0-4894345
Windows 64bit

Mixing Testing : some of my wallets get slightly over the set target amount of 1000 Dash but that is no big deal. All my wallets stop mixing when they reach 100%
FhcHr4i.png


PrivateSend Testing :

Wallet 4 with privatesend balance of 1100 Dash
* sending 10 Dash with PrivateSend to Wallet 5 :

4EPzc0K.png


Wallet 5 with privatesend balance of 1100 dash
* sending 99.90 Dash with PrivateSend to Wallet 6 :

QT3eXxH.png


Note : trying to PrivateSend amounts ranging between 1 and 99.90 get above error message !!

* sending 100 Dash with PrivateSend to Wallet 5 :

6VNRUBr.png


* sending 99.91 Dash with PrivateSend to Wallet 6 :

IwemeVT.png


PrivateSend Conclusion : Only amounts ranging from 99.91 and higher can be used for PrivateSend ? (i havent tested the upper limit)

InstantSend & PrivateSend Testing :

* 100 Dash with both PrivateSend & Intstantsend on : successfull (5 confirmations)

* 200 Dash with both PrivateSend & Intstantsend on : successfull (5 confirmations)

* 210 Dash with both PrivateSend & Intstantsend on and with PS balance of 1000 dash : error (unable to locate enough PrivateSend denominated funds for this transaction)
Note : could be due to a limit of InstantSend ?
Click to expand...
Check "inputs..." on send tab, you might not have enough 10dash denoms mixed.
 
FYI. RPMs were built once again (maybe just "watch" the repo in github if you want to know immediately)...

Build 688 (v0.12.1.0-g4894345) Binary RPMs for Fedora, CentOS, RHEL
https://drive.google.com/open?id=18qwFkDKfyZhvecuR5kxiIKmPsjPZjFhRY0EsfHYbD7I

If you are looking for the source RPMs, the SRPM github repo is linked to within that document.
If you are looking for the stable binary RPM packages, those are linked to in there as well.

Happy testing.
 
Last edited:
guys, is there some restrictions for a proposal submission time? I've heard that in v12.0 there is a rule that a proposal can be submitted no later than 3 days before payment. But I can't find any proof of this in the code neither for v12.0 nor for v12.1. Is this rule implemented in the code?
 
So I just checked and saw my masternodes are no longer running. This is the last stuff in my log, but it could be my server was overwhelmed though it has 1024 ram and plenty of storage??:

Code: 
2016-11-06 04:08:45 keypool return 2
2016-11-06 04:08:45 ProcessNewBlock : ACCEPTED
2016-11-06 04:08:45 receive version message: /Dash Core:0.12.1/: version 70202, blocks=97591, us=216.45.55.232:19999, peer=6579
2016-11-06 04:08:52 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:09:40 CMasternodeMan::CheckAndRemove
2016-11-06 04:09:44 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 3, nDsqCount: 17355
2016-11-06 04:09:44 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:10:07 keypool reserve 2
2016-11-06 04:10:11 keypool return 2
2016-11-06 04:10:44 CMasternodeMan::CheckAndRemove
2016-11-06 04:10:44 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 3, nDsqCount: 17355
2016-11-06 04:10:44 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:11:46 CMasternodeMan::CheckAndRemove
2016-11-06 04:11:46 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 3, nDsqCount: 17355
2016-11-06 04:11:46 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:12:11 keypool reserve 2
2016-11-06 04:12:11 keypool return 2
2016-11-06 04:12:46 CMasternodeMan::CheckAndRemove
2016-11-06 04:12:47 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:12:47 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:13:48 CMasternodeMan::CheckAndRemove
2016-11-06 04:13:48 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:13:49 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:14:13 keypool reserve 2
2016-11-06 04:14:13 keypool return 2
2016-11-06 04:14:13 Timeout downloading block 0000000cc4abe9b810c69e467701afb1bebf60dde714aa474b387123ffc62fd3 from peer=6565, disconnecting
2016-11-06 04:14:13 CActiveMasternode::SendMasternodePing -- Relaying ping, collateral=CTxIn(COutPoint(0717c4027953ac1f56b679415ba60fdb6d3776bb95d1a2c8e07f1da099161375, 1), scriptSig=)
2016-11-06 04:15:12 CMasternodeMan::CheckAndRemove
2016-11-06 04:15:12 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:15:13 CMasternodePayments::CheckAndRemove -- Votes: 40123, Blocks: 4012
2016-11-06 04:16:02 Timeout downloading block 000000c11a3bea478845ced3768bd72db319564f35b00bc3daf79e0901013123 from peer=6575, disconnecting
2016-11-06 04:16:07 receive version message: /darkcoin-seeder:0.1.2/: version 70201, blocks=0, us=[2607:fcd0:100:4d00::c6a7:ea8c]:19999, peer=6584
2016-11-06 04:16:07 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:07 receive version message: /Dash Core:0.12.1/: version 70201, blocks=98039, us=[2607:fcd0:100:4d00::c6a7:ea8c]:19999, peer=6585
2016-11-06 04:16:07 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:09 receive version message: /darkcoin-seeder:0.1.2/: version 70201, blocks=0, us=216.45.55.232:19999, peer=6586
2016-11-06 04:16:11 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:11 ProcessMessages: advertising address 216.45.55.232:19999
2016-11-06 04:16:11 receive version message: /Dash Core:0.12.1/: version 70202, blocks=98039, us=216.45.55.232:37642, peer=6587
2016-11-06 04:16:11 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:13 CMasternodeMan::CheckAndRemove
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 CMasternodePayments::CheckAndRemove -- Votes: 40138, Blocks: 4014
2016-11-06 04:16:22 UpdateTip: new best=0000000cc4abe9b810c69e467701afb1bebf60dde714aa474b387123ffc62fd3  height=98032  log2_work=43.004882  tx=128926  date=2016-11-06 04:04:33 progress=0.999929  cache=0.1MiB(85tx)
2016-11-06 04:16:22 keypool reserve 2
2016-11-06 04:16:22 keypool return 2
 
TanteStefana said:
So I just checked and saw my masternodes are no longer running. This is the last stuff in my log, but it could be my server was overwhelmed though it has 1024 ram and plenty of storage??:

Code: 
2016-11-06 04:08:45 keypool return 2
2016-11-06 04:08:45 ProcessNewBlock : ACCEPTED
2016-11-06 04:08:45 receive version message: /Dash Core:0.12.1/: version 70202, blocks=97591, us=216.45.55.232:19999, peer=6579
2016-11-06 04:08:52 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:09:40 CMasternodeMan::CheckAndRemove
2016-11-06 04:09:44 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 3, nDsqCount: 17355
2016-11-06 04:09:44 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:10:07 keypool reserve 2
2016-11-06 04:10:11 keypool return 2
2016-11-06 04:10:44 CMasternodeMan::CheckAndRemove
2016-11-06 04:10:44 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 3, nDsqCount: 17355
2016-11-06 04:10:44 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:11:46 CMasternodeMan::CheckAndRemove
2016-11-06 04:11:46 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 3, nDsqCount: 17355
2016-11-06 04:11:46 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:12:11 keypool reserve 2
2016-11-06 04:12:11 keypool return 2
2016-11-06 04:12:46 CMasternodeMan::CheckAndRemove
2016-11-06 04:12:47 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:12:47 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:13:48 CMasternodeMan::CheckAndRemove
2016-11-06 04:13:48 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:13:49 CMasternodePayments::CheckAndRemove -- Votes: 40122, Blocks: 4012
2016-11-06 04:14:13 keypool reserve 2
2016-11-06 04:14:13 keypool return 2
2016-11-06 04:14:13 Timeout downloading block 0000000cc4abe9b810c69e467701afb1bebf60dde714aa474b387123ffc62fd3 from peer=6565, disconnecting
2016-11-06 04:14:13 CActiveMasternode::SendMasternodePing -- Relaying ping, collateral=CTxIn(COutPoint(0717c4027953ac1f56b679415ba60fdb6d3776bb95d1a2c8e07f1da099161375, 1), scriptSig=)
2016-11-06 04:15:12 CMasternodeMan::CheckAndRemove
2016-11-06 04:15:12 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:15:13 CMasternodePayments::CheckAndRemove -- Votes: 40123, Blocks: 4012
2016-11-06 04:16:02 Timeout downloading block 000000c11a3bea478845ced3768bd72db319564f35b00bc3daf79e0901013123 from peer=6575, disconnecting
2016-11-06 04:16:07 receive version message: /darkcoin-seeder:0.1.2/: version 70201, blocks=0, us=[2607:fcd0:100:4d00::c6a7:ea8c]:19999, peer=6584
2016-11-06 04:16:07 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:07 receive version message: /Dash Core:0.12.1/: version 70201, blocks=98039, us=[2607:fcd0:100:4d00::c6a7:ea8c]:19999, peer=6585
2016-11-06 04:16:07 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:09 receive version message: /darkcoin-seeder:0.1.2/: version 70201, blocks=0, us=216.45.55.232:19999, peer=6586
2016-11-06 04:16:11 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:11 ProcessMessages: advertising address 216.45.55.232:19999
2016-11-06 04:16:11 receive version message: /Dash Core:0.12.1/: version 70202, blocks=98039, us=216.45.55.232:37642, peer=6587
2016-11-06 04:16:11 AdvertiseLocal: advertising address 216.45.55.232:19999
2016-11-06 04:16:13 CMasternodeMan::CheckAndRemove
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 CMasternodeMan::CheckAndRemove -- Masternodes: 73, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 2, nDsqCount: 17355
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 ProcessNewBlock : ACCEPTED
2016-11-06 04:16:15 CMasternodePayments::CheckAndRemove -- Votes: 40138, Blocks: 4014
2016-11-06 04:16:22 UpdateTip: new best=0000000cc4abe9b810c69e467701afb1bebf60dde714aa474b387123ffc62fd3  height=98032  log2_work=43.004882  tx=128926  date=2016-11-06 04:04:33 progress=0.999929  cache=0.1MiB(85tx)
2016-11-06 04:16:22 keypool reserve 2
2016-11-06 04:16:22 keypool return 2
Click to expand...
If that's a very old one it could be that it was killed by the system because of a very high CPU usage. This was fixed recently.
 
UdjinM6 said:
If that's a very old one it could be that it was killed by the system because of a very high CPU usage. This was fixed recently.
Click to expand...
Not unless a new version was released and not posted here? I'm on the latest posted here :)

It was probably my server? Although it was still running (the server) just Dash had shut down....?

If the debug log shows nothing suspicious other than suddenly stopping, then it was my server service.

Speaking of which, what are you all guestimating our specs ought to be for a 12.1 MN?
 
Status
Not open for further replies.
Back
Top