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

V12 Testing Thread

eduffield

eduffield

Core Developer
Hello Everyone!

Development of v12 has been ongoing now for some time and we’re finally ready to begin public testing! All of the new features seem to work as far as we can test them in our development environment and now we’d like to start testing with more users.

There are lots of new features available and this document will serve as an initial guide on how to use these new features. As we release new versions, we will try to keep it updated and reflect the changes we are making.


Implementation and activation of the budgeting system


Per the result of the masternode vote, the governance and funding system will be activated with 10% of the rewards. This is coming out of the rewards that were originally planned for masternodes, emission and inflation remain the same. It will be activated and applied in 1 hard fork/spork.

  • This means that starting around july/august(depending on when we launch) there will be 8640 DASH available for budgeting per month (about $24000 currently) for the best ideas we can come up with to develop and grow the Dash ecosystem.
  • The block reward will be lowered by 10% a week or two after the release of v12, in preparation for budget proposals however, the budget doesn’t have to use all of this funds if there are not proposals with community support the coins are just not minted.
  • Budgets will be paid once per month in many consecutive blocks, 1 per approved proposal.

Budgeting Software


v12 has two brand new commands for the network for our budgeting needs. mnbudget and mnfinalbudget.


Code: 
mnbudget - create or vote budget proposals:


Available commands:
vote-many  - Vote on a Dash initiative
vote-alias  - Vote on a Dash initiative
vote  - Vote on a Dash initiative/budget
getvotes  - Show current masternode budgets
getinfo  - Show current masternode budgets
show  - Show all budgets


mnfinalbudget - schedule and consolidate budget items into a finalized budget per month:

Available commands:
suggest  - Suggest a budget to be paid
vote-many  - Vote on a finalized budget
vote  - Vote on a finalized budget
show  - Show existing finalized budgets


mnbudget is used for the proposal system. You can send a proposal for the network to vote on, how many payments should be paid, the amount of payments and a good deal of meta data. The network uses a vote-by-hash system for security, so each masternode will enter all of the data needed to vote on a specific entry, which is then hashed. Any change to the meta data will cause the hashes not to match.


Code: 
dash-cli NAME URL PAYMENT_COUNT BLOCK_START DASH_ADDRESS DASH_AMOUNT YES|NO|ABSTAIN'

dash-cli mnbudget vote proposal-one http://www.dashpay.io/one.json 100 58381 y7B3r6SBi1E1RN39DS5WFJpdeS9EifDjMB 1000 yes

This will hash to 22a7fab3765b0aca926f71117114b5019ab616dda3d6bae520a27d76912228dd. Any change will create a new proposal for security reasons.

Showing the newly created budget:

Code: 
dashc_t mnbudget show

{
"proposal-one" : {
"URL" : "http://www.dashpay.io/one.json",
"Hash" : "22a7fab3765b0aca926f71117114b5019ab616dda3d6bae520a27d76912228dd",
"BlockStart" : 58381,
"BlockEnd" : 63375,
"TotalPaymentCount" : 100,
"RemainingPaymentCount" : 100,
"PaymentAddress" : "y7B3r6SBi1E1RN39DS5WFJpdeS9EifDjMB",
"Ratio" : 1.00000000,
"Yeas" : 1,
"Nays" : 0,
"Abstains" : 0,
"Alloted" : 348214275,
"TotalBudgetAlloted" : 348214275
}


After this anyone can vote on the proposals. The network will use the “Finalized Budget” logic automatically to consolidate the proposals into one object that will allow them to be paid at the end of the month. You can see these with “mnfinalbudget show”. For a proposal to make it into the finalized budget, it will require 10% of the masternode votes on mainnet. This should help combat masternode voting apathy, if masternodes don’t want something with that little support to be paid, they’ll have to vote on a competing proposal.


Budgets are paid each 50 blocks on testnet/regtest to allow us to make lots of changes and have many pay periods to test with. On mainnet it will be every 16616 blocks.


Reference Node


The reference node is officially gone! v12 seems to be working great from testing without it using quorums of masternodes to select the winning masternodes instead. You can see these votes by using the “masternode winners” command, which has a slightly different output now:

Code: 
"874" : "yKambaR3Gb5vXJCFrtGFfy1xG9kc6CnDhy:10000000000:0",
"875" : "yFwaockv34Cy3BHV7M3Bme4C1Vcq4jPpqH:4020000000:0",
"876" : "Unknown",
"877" : "Unknown",


Masternode API

All masternode API commands now use the inputs as the main identifier and not the ip-address as they used to.


Code: 
masternode list:

{
"e466f5d8beb4c2d22a314310dc58e0ea89505c95409754d0d68fb874952608cc-5" : "ENABLED",
"e466f5d8beb4c2d22a314310dc58e0ea89505c95409754d0d68fb874952608cc-2" : "ENABLED",
}


Sporks


We’ll have two new sporks, one for the budgeting system as a whole and one for the new masternode payment system.


Proposal Application


We’ve had a developer working on the proposal viewing/submission website now for a couple of months. It’s going great and we’ll open that application up for testing after we’re happy with the v12 software.

Downloads:


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:
Outstanding Evan! So much work I can see has been done.

Re this:
eduffield said:
Hello Everyone!
After this anyone can vote on the proposals. The network will use the “Finalized Budget” logic automatically to consolidate the proposals into one object that will allow them to be paid at the end of the month. You can see these with “mnfinalbudget show”. For a proposal to make it into the finalized budget, it will require 10% of the masternode votes on mainnet. This should help combat masternode voting apathy, if masternodes don’t want something with that little support to be paid, they’ll have to vote on a competing proposal.
Click to expand...

Does this mean a proposal only needs to have a 10% of MN's voting Yea to get up and start being paid, or are you saying that only 10% of MNs need to vote and within that 10% as long as there is more than 50% 'Yea' (so more than 5% of the total MNs) the proposal will start being paid?

And...
if masternodes don’t want something with that little support to be paid, they’ll have to vote on a competing proposal
Click to expand...

...wouldn't MNs simply vote 'nay' for the specific proposal as opposed to needing to vote for something else?
 
Awesome! Didn't think this day would ever come! Tweeted, officially and unofficially. This release is huge, this is the first day of the bright DASH future.
Happy testing, mates!
 
gotta laugh :grin:

upload_2015-6-16_23-5-48.png
 
First problem, updated ok until 0 hours then got stuck and will NOT sync! (on mainnet, elbereth version works)
will do the usual delete peers and reload blockchain to see if that sorts it out .

Testnet stuck as well, doesn't like the tip of the chain, can't see anything in debug ..
 
Last edited by a moderator:
HDD drive
Dash Windows 32 bit

Syncing period : 40 weeks
Total time to sync : 8 minutes
Number of connections : 6

During sync sometimes heavy processor use : up to 79% on an Intel i7 860 3.37 GHz quad core processor
RAM Memory in use : 73 MB

Stuck on 0 hours behind but most likely waiting for next block to clear ??

edit :

Current block 68822, from some 8 minutes ago
Masternode count 10/11
 
Last edited by a moderator:
qwizzie said:
HDD drive
Stuck on 0 hours behind but most likely waiting for next block to clear ??
Click to expand...

Main net is the same.
And deleting the whole folder and starting from scratch does not work either!
 
Last edited by a moderator:
i will try solo CPU mining : setgenerate true (to stop : setgenerate false)
"difficulty" : 0.00434444,

Edit :

* wow, cool options at Wallet Repair !! (under Tools)
* received first 9 tdash through solo mining :)
* i'm totally synced now.. right after starting that solomining and receiving first tdash
* i stopped solomining, dont like my CPU getting 80 degrees c .. received 46 tdash in total.
 
Last edited by a moderator:
Sub-Ether said:
First problem, updated ok until 0 hours then got stuck and will NOT sync! (on mainnet, elbereth version works)
will do the usual delete peers and reload blockchain to see if that sorts it out .

Testnet stuck as well, doesn't like the tip of the chain, can't see anything in debug ..
Click to expand...
It's problem with your clock on your PC :smile:
 
I've gotta update my faucet it's wallet is all fucked was all fucked. Fixed now.

Code: 
evan82@klaus:~/bin$ dash-cli getinfo

{
    "version" : 120000,
    "protocolversion" : 70077,
    "walletversion" : 61000,
    "balance" : 392356.97562047,
    "darksend_balance" : 0.00000000,
    "blocks" : 68824,
    "timeoffset" : 0,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 0.00058166,
    "testnet" : true,
    "keypoololdest" : 1423432147,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."
}

Faucet is confirmed working!
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top