V12 Testing Thread

 
I'd like to suggest eduffield point us to this link to find the latest build: https://dashpay.atlassian.net/builds/allPlans.action so he and flare don't have to waste time to copy and paste the download files.

- From that link, click on "02_Develop" of your OS choice.
- Next screen, click on the top number on the left (the latest build) or wait for the next build if you see the dev is compiling....



upload_2015-7-6_16-58-42.png


- Next screen, click on "Artifacts"

upload_2015-7-6_17-1-25.png



- Next screen, click on the "gitian... dist" file (in this example, "gitian-win-dash-dist"

upload_2015-7-6_17-3-54.png


And the next screen will show you the download file. That's it.
 
Last edited by a moderator:
Please update to - v0.12.0.10

Sorry about the bad links, here's updated links + a few minor fixes that should help stability

- Version bump / more fixes
- Clear expired proposals / added mnbudget check
- Fixed GetVoteCommand

v0.12.0.9: Monster update! Lot's of improvements in this version

Vastly improved proposal management implementation - eduffield
- Syncing now happens in stages. Masternodes and Sporks, then Masternode winners, then proposals. Some of these require the masternode signatures, otherwise there are race conditions within the syncing process itself.
- Resigning - When a proposal is sent to the network initially it's signed by a masternode, if that masternode goes inactive the proposal becomes invalid. Resigning allows other masternodes to update proposal keep it valid with the coming and going of masternodes.
- Resigning compatibility - non masternodes will scan and flag proposals as invalid to accept updated owners.
- Invalid votes are now actively removed from the proposals when they go inactive
- Remove budgets with negative votes of more than 10% of network
- Only allow proposals into budget that have more than 10% of network support
- Faster removal of inactive masternodes
- show voting commands for proposals in mnbudget show
- Only sync masternode assets after new block (with timestamp in the last minute)
- mnbudget show now shows "VoteCommand" for easy copy and pasting

Many other changes:
- fix CFinalizedBudget::AutoCheck() crash - Udjin
- Wallet Window Title: minor changes - crowning
- User configurable Wallet Window Title - crowning
- Added CleanAndRemove for Proposal votes - Evan Duffield
- Smarter algorithm for finding the nHeight for the last block - Evan Duffield
- nHeight calculation for BlockValue checking - Evan Duffield
- Rebuild coinbase cache when needed - Evan Duffield
- Popup information on first mixing - crowning
- Persist Date and Type filters in "Transactions" tab - crowning

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:
IX is not as fast as it was with the first version Evan posted.

Pablo.
 
fuzzyduck said:
Yey! Prefabricated pi2 builds! Thx flare:cool:
Click to expand...
Sorry to be so erratic here but the demands on me are somewhat difficult.:oops: I have been checking in as I have been able. Oh, and thanks to the folks who sent me the tdash a while back.:smile:

A quick question concerning the Pi-build; What is the OS this is aimed at, I am assuming Raspian? The reason I ask is that I have been running my node quite happily with Arch Linux on a pi-2. This seems much more secure to me as can update it as frequently as I see fit, and I can install it as a bare-bones secure system without the non-essentials that come pre-installed for the pi. Also Dash can be compiled from git as part of the normal upgrade system command.

Not sure if this is the proper place to post this,:confused: but in view of the above; is their any reason for preferring the pi build mentioned here, over the regular Linux-64 build compiled for Arch on the pi?:what:
 
eduffield said:
First thing we should do is clear everything out so we can start with just a few proposals. Once they have +10% no_count-yes_count, the new software should clear all of them out and actually delete them. Please run this:

http://pastebin.com/8v97wVxA
Click to expand...
On the console, the response for every vote-many command is "Voted successfully 0 time(s) and failed 0 time(s)."
Is this what it should be?

EDIT: Got this solved.. my MNs were down and I didn't know. Results now: "Voted successfully 2 time(s) and failed 0 time(s)."
 
Last edited by a moderator:
strix said:
Sorry to be so erratic here but the demands on me are somewhat difficult.:oops: I have been checking in as I have been able. Oh, and thanks to the folks who sent me the tdash a while back.:smile:

A quick question concerning the Pi-build; What is the OS this is aimed at, I am assuming Raspian? The reason I ask is that I have been running my node quite happily with Arch Linux on a pi-2. This seems much more secure to me as can update it as frequently as I see fit, and I can install it as a bare-bones secure system without the non-essentials that come pre-installed for the pi. Also Dash can be compiled from git as part of the normal upgrade system command.

Not sure if this is the proper place to post this,:confused: but in view of the above; is their any reason for preferring the pi build mentioned here, over the regular Linux-64 build compiled for Arch on the pi?:what:
Click to expand...
It's compiled against gnu-libc, so it should work on all Linux flavours on Pi.

And no, there is no reason to prefer binary builds - i just added them for convenience as Pi builds take a long time on a Pi and during test phase we are producing MANY artifacts :)

You can use gitian to produce the native binaries from source for your Pi on a more powerful machine by yourself though. Follow this guide to get you started https://dashtalk.org/threads/how-to-gitian-build-dash-under-debian-jessie-using-lxc.5397/
 
flare said:
It's compiled against gnu-libc, so it should work on all Linux flavours on Pi.

And no, there is no reason to prefer binary builds - i just added them for convenience as Pi builds take a long time on a Pi and during test phase we are producing MANY artifacts :)

You can use gitian to produce the native binaries from source for your Pi on a more powerful machine by yourself though. Follow this guide to get you started https://dashtalk.org/threads/how-to-gitian-build-dash-under-debian-jessie-using-lxc.5397/
Click to expand...
OK, thanks! I only have one pi, and it is busy running my MN. Arch compiles from git in the background so time is not a concern there. For testing I am just using my poor little laptop.:oops:
 
eduffield said:
First thing we should do is clear everything out so we can start with just a few proposals. Once they have +10% no_count-yes_count, the new software should clear all of them out and actually delete them. Please run this:

http://pastebin.com/8v97wVxA
Click to expand...

Not sure where we supposed to run that pastebin... dashcmd not recognized in win cmd console, and debug console says method not found.
I did change dashcmd to dash-cli and it seemed to work in windows console.
 
bertlebbert said:
Not sure where we supposed to run that pastebin... dashcmd not recognized in win cmd console, and debug console says method not found.
I did change dashcmd to dash-cli and it seemed to work in windows console.
Click to expand...
Example on the MN wallet console:
mnbudget vote electrumdash http://www.dashpay.io/one.json 10 80000 y5pkDas8sEgGkw288mZ1TPViPPnujsvBCT 1500 no

To vote-many:
mnbudget vote-many electrumdash http://www.dashpay.io/one.json 10 80000 y5pkDas8sEgGkw288mZ1TPViPPnujsvBCT 1500 no

EDIT: I'm not sure how to do this list all at once in windows command-line.
UdjinM6 do you know how to do this whole list all at once in windows?
http://pastebin.com/8v97wVxA
 
Last edited by a moderator:
moli said:
Example on the MN wallet console:
mnbudget vote electrumdash http://www.dashpay.io/one.json 10 80000 y5pkDas8sEgGkw288mZ1TPViPPnujsvBCT 1500 no

To vote-many:
mnbudget vote-many electrumdash http://www.dashpay.io/one.json 10 80000 y5pkDas8sEgGkw288mZ1TPViPPnujsvBCT 1500 no

EDIT: I'm not sure how to do this list all at once in windows command-line.
UdjinM6 do you know how to do this whole list all at once in windows?
Click to expand...

Here's what I did, it seemed to work:
1. Copy whole pastebin to txt editor
2. Use "Replace all" to change 'dashcmd' to dash-cli.
3. Copy and paste whole doc (121 lines) into Win cmd console.
4.Press Enter

Watch each of 121 votes get cast.

Edit: Oh ya, make sure there is a copy of dash.conf in your Dash user folder... same as the one for MN you're voting... it needs the rpcpassword. Or there is probly a command option to specify a datadir, but that kind of a pain in the... to use here.
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top