• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12 Testing Thread

eduffield said:
Please vote yes on the following!

dash-cli mnbudget vote f069240c45d7fe0e3952059c72225f133420be3ff8e764600a1cd4de2f5d4ccc yes
dash-cli mnbudget vote c782b9b9cc2c8bd8346f5300ecf0b88ec7c96ec483185fd5645a129efef34093 yes
dash-cli mnbudget vote a4830da09f674af25e8c68494344228c5bc4cd605cac009a9a0b76b2e86339a4 yes
dash-cli mnbudget vote 73409160b4e97ed712e67757ea6ff9cc6b32fc8087aeb41b355c3b2a635b8ffe yes
Click to expand...

6 yes votes for each from me
 
eduffield said:
Please vote yes on the following!

dash-cli mnbudget vote f069240c45d7fe0e3952059c72225f133420be3ff8e764600a1cd4de2f5d4ccc yes
dash-cli mnbudget vote c782b9b9cc2c8bd8346f5300ecf0b88ec7c96ec483185fd5645a129efef34093 yes
dash-cli mnbudget vote a4830da09f674af25e8c68494344228c5bc4cd605cac009a9a0b76b2e86339a4 yes
dash-cli mnbudget vote 73409160b4e97ed712e67757ea6ff9cc6b32fc8087aeb41b355c3b2a635b8ffe yes
Click to expand...
I'm just curious why only the first one on this list is showing under "mnbudget show"" when all of them got the votes:
22:07:57

mnbudget show


22:07:58

{
"test-multisig" : {
"URL" : "https://www.dashpay.io/one.json",
"Hash" : "73409160b4e97ed712e67757ea6ff9cc6b32fc8087aeb41b355c3b2a635b8ffe",
"FeeHash" : "61ecfe11f19ea73832ab9791554505f9c7bf5ea1b514e4cdb532fb97de34d78a",
"BlockStart" : 1000,
"BlockEnd" : 4001025,
"TotalPaymentCount" : 80000,
"RemainingPaymentCount" : 78332,
"PaymentAddress" : "8mpnk9qM9fX7NWvz8Huhp8YivP6SYCSPkb",
"Ratio" : 1.00000000,
"Yeas" : 93,
"Nays" : 0,
"Abstains" : 0,
"Amount" : 100000000000,
"IsValid" : true,
"fValid" : 1
},
"evan-fund" : {
"URL" : "http://evan-fund",
"Hash" : "f069240c45d7fe0e3952059c72225f133420be3ff8e764600a1cd4de2f5d4ccc",
"FeeHash" : "37e26212c3a4744deaa35656cf0b65688cf177c1f634cf80a0f3a54b7b52cd4d",
"BlockStart" : 80000,
"BlockEnd" : 130025,
"TotalPaymentCount" : 1000,
"RemainingPaymentCount" : 912,
"PaymentAddress" : "yGpT7in1jCAx9xrdsQ2NZ45NaTGbmWLrW8",
"Ratio" : 1.00000000,
"Yeas" : 91,
"Nays" : 0,
"Abstains" : 0,
"Amount" : 314159265359,
"IsValid" : true,
"fValid" : 1
}
}
Click to expand...
 
strix said:
This may or may not be relevant; I have been working on upgrading my technical prowess in the area of Linux security and just started running the Grsecurity kernel and PaX on my Arch Linux Lenovo T400 laptop. My .11.2.23 wallet runs fine but the last two test wallets fail with the following:

(dash-qt:3552): GLib-ERROR **: file gthread-posix.c: line 1182 (g_system_thread_new): error 'Operation not permitted' during 'pthread_create'
Trace/breakpoint trap (core dumped)

I suspect this is caused by running the compiled test executable from my desktop as opposed to /usr/bin/ but am posting this in case the devs think this is something that warrents their attention. In the meantime I am out of testing until I figure things out on my end.:mad::oops:
Click to expand...
All is well--I am posting this for posterity in case anyone else runs into this problem. Seems my hypothesis was more-or-less correct. The solution from the ArchWiki (https://wiki.archlinux.org/index.php/PaX#PaX_exceptions) :

PaX exceptions
Some of the PaX exploit mitigations prevent certain applications from running and require the executables to be marked with exceptions. Extended attributes can be used to exclude executables from one or more of the features. For example, to disable the MPROTECT and RANDMMAP features:

$ setfattr -n user.pax.flags -v "emr" /Path to test Dash-qt

Now back to testing. :grin:

Carry on... :cool:
 
2 votes each from me. BTW, I voted actually several times on that last one but got no error, and though I doubt that I actually was given more than one vote, it would kind of be nice to get feedback "you already voted yes on this proposal" or "your vote was changed to no for this proposal" or some kind of confirmation. Just my opinion, ;) It's nice to have feedback ;)
 
eduffield said:
New Version : v0.12.0.17

This restructures the proposals so that the invalid ones are kept rather than being erased, for debugging purposes. Also syncing has been heavily refactored and should work much better overall.

Linux32:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux32.tar.gz

Linux64:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux64.tar.gz

Mac:
https://dashpay.atlassian.net/build...n-osx-dash-dist//dash-0.12.0-osx-unsigned.dmg

Win32:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip

Win64:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win64.zip
Click to expand...

Captain, I canna vote,windows version not found..
 
just found all my (linux 64) nodes stuck on block 84451 000000069e4c361acc087ca7fef2d3b2fde3646db560a55503353d56e7c3b39b

they think they're started: 'masternode successfully started'

my desktop qt is on block 84613 000000f46dac98807c23817f06937fdb68d28ca68f99adfffd535180a2008acb

and shows zero masternodes online (masternode count)
 
eduffield said:
You mean vote-many didn't work properly? What's the output look like?
Click to expand...
I voted "yes" for those 4 hashes, they each also got 69 votes from moocowmoo but only the first one on the list shows up on my console, like now:
10:07:48

mnbudget show


10:07:49

{
"test-multisig" : {
"URL" : "https://www.dashpay.io/one.json",
"Hash" : "73409160b4e97ed712e67757ea6ff9cc6b32fc8087aeb41b355c3b2a635b8ffe",
"FeeHash" : "61ecfe11f19ea73832ab9791554505f9c7bf5ea1b514e4cdb532fb97de34d78a",
"BlockStart" : 1000,
"BlockEnd" : 4001025,
"TotalPaymentCount" : 80000,
"RemainingPaymentCount" : 78326,
"PaymentAddress" : "8mpnk9qM9fX7NWvz8Huhp8YivP6SYCSPkb",
"Ratio" : 1.00000000,
"Yeas" : 21,
"Nays" : 0,
"Abstains" : 0,
"Amount" : 100000000000,
"IsValid" : true,
"fValid" : 1
},
"DASHpay1" : {
"URL" : "http://www.dashpay.io/one.json",
"Hash" : "ce55919e4557477d6201d270f624daa98a00584bccf41ecbf7be762147ee908a",
"FeeHash" : "b29cf54366ccd3f03b197ea50621d1c8844112974748af6afe44e63461103cc1",
"BlockStart" : 84600,
"BlockEnd" : 85125,
"TotalPaymentCount" : 10,
"RemainingPaymentCount" : 8,
"PaymentAddress" : "y6TTAYK7MP2e67AKVisiFqye8bnqyJSoZB",
"Ratio" : 1.00000000,
"Yeas" : 15,
"Nays" : 0,
"Abstains" : 0,
"Amount" : 100000000000,
"IsValid" : true,
"fValid" : 1
},
"evan-fund" : {
"URL" : "http://evan-fund",
"Hash" : "f069240c45d7fe0e3952059c72225f133420be3ff8e764600a1cd4de2f5d4ccc",
"FeeHash" : "37e26212c3a4744deaa35656cf0b65688cf177c1f634cf80a0f3a54b7b52cd4d",
"BlockStart" : 80000,
"BlockEnd" : 130025,
"TotalPaymentCount" : 1000,
"RemainingPaymentCount" : 906,
"PaymentAddress" : "yGpT7in1jCAx9xrdsQ2NZ45NaTGbmWLrW8",
"Ratio" : 1.00000000,
"Yeas" : 19,
"Nays" : 0,
"Abstains" : 0,
"Amount" : 314159265359,
"IsValid" : true,
"fValid" : 1
}
}
Click to expand...
EDIT: I'm running v0.12.0.17-f139dbb - windows32.
EDIT: Actually it was showing the first and last on the list.. My bad...
 
Last edited by a moderator:
moli said:
I voted "yes" for those 4 hashes, they each also got 69 votes from moocowmoo but only the first one on the list shows up on my console, like now:

EDIT: I'm running v0.12.0.17-f139dbb - windows32.
Click to expand...

I noticed this last night and tracked it down, v0.12.0.18 addresses the issue by having the transaction index default to enabled. The problem was, it's impossible to lookup some of these transactions after the client is restarted. I think it's actually a problem for DS/IX also, so this should help things significantly for everything we're doing.
 
NEW Version : V0.12.0.18

---- Rather Large Change Included -----

This update enables the transaction index by default on all nodes. This should improve the way DS, IX and the Budget System functions. Actually everything should work much better with this change, I might have been causing minor annoyances everywhere and inconsistencies throughout our network.

To update, you'll need to remove ~/.dash/testnet3/budget.dat, otherwise you'll probably get stuck syncing. Then restart with --reindex. Please try out DS and IX with this update, I'm curious to see how much faster/better they perform.

Evan:
- Force txindex when a Mastenode / default to enabled otherwise
- Version / proto bump
- Fixed prepare -- shouldn't check collateral
- Added CBudgetManager::ToString
- Test feeTX in IsValid

Linux32:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux32.tar.gz

Linux64:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux64.tar.gz

Mac:
https://dashpay.atlassian.net/build...n-osx-dash-dist//dash-0.12.0-osx-unsigned.dmg

Win32:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip

Win64:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win64.zip
 
Last edited by a moderator:
UdjinM6 said:
Yes, anyone can pay proposal fee and create a proposal (linked to tx with fee payment) after that from any wallet. But only MNs can vote.
Click to expand...
That is quite the divergence from teh original plan? Let the script kiddies proposals start flowing. Not sure I agree with this one.
 
coingun said:
That is quite the divergence from teh original plan? Let the script kiddies proposals start flowing. Not sure I agree with this one.
Click to expand...

It's going to cost at least $1 to submit and we can just remove any spam by down-voting them. I doubt we'll have much of a problem. Also, masternode operators can use masternode.conf and vote-many without bringing the actual coins online, so it shouldn't take many people to remove spam (~280 votes currently). We could even change that to require ~140 votes, which is even easier (5% of the masternode count). It's kind of like the way reddit works, except there's a fee to submit.
 
I have submitted the 4 votes but mnbudget show gives an empty result, is it because we only have 3 masternodes ?

Edit: am seeing a lot of different versions on the peers ..
 
eduffield said:
NEW Version : V0.12.0.18
To update, you'll need to remove ~/.dash/testnet3/budget.dat, otherwise you'll probably get stuck syncing. Then restart with --reindex. Please try out DS and IX with this update, I'm curious to see how much faster/better they perform.
Click to expand...

Not sure if I was too impatient and didn't wait long enough (~3minutes) but I got stuck at block 79391 until I deleted peers.dat and restarted. All is well now.

Also, haven't fully tested DS yet but it does seem quicker. It hit 18% almost immediately and 30% 1-2 minutes into it.
 
You must log in or register to reply here.
Back
Top