V12 Release

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
Hello Everyone,

It is with great pleasure that the development team brings you the much anticipated version 12 release of the Dash Core client. This release implements numerous features the Dash community has requested, such as the decentralized budget system and the removal of the reference node. In fact, by virtually any measure this is our most extensive release to date. It also establishes ground-breaking functionality that further differentiates our cryptocurrency and enables an entirely new model for supporting the Dash ecosystem in exciting new ways.

Not only is this the broadest set of changes we’ve ever deployed in one release. It is also the most extensively and methodically tested release we’ve ever done. An extended team of volunteers have been helping the core development team to manage and test this release since long before I even announced public testing on June 12th. While we don’t expect the code to be bug-free (no software ever is) this should be one of the most stable releases we’ve deployed.

Here is an abbreviated list of the enhanced functionality included in the version 12 release:
  • Incorporated Bitcoin Core version 0.10 https://bitcoin.org/en/release/v0.10.0
  • Implemented the first decentralized budget system and ability to fund Dash projects directly from the block rewards (details can be found in the “What is the Decentralized Budget System?” section below)
  • Implemented a new decentralized masternode payment consensus system, which will enable the removal of the reference node that was needed to facilitate fair distribution of masternode rewards
  • Improved the speed and reliability of Darksend anonymization
  • New masternode payment/winners/budgets syncing strategy
  • Platform independent masternode ranking system
  • Masternode broadcasts, pings and winners now use the inventory system
  • Transaction indexing is enabled by default for all clients
  • Improved implementation of Instant Transactions (IX) block reprocessing to find and remove invalid blocks
  • Increased IX success rate to nearly 100% and transaction locks are more secure than before
Who is required to update?

It is imperative that ALL USERS of the dash client update to the most recent version of the client as soon as possible. Users have until September 5th to update. After that date, anyone running an old client will no longer be on the valid chain.

How to update?

QT: When updating the client, you will need to reindex the blockchain. To do this, start the wallet with option ‘-reindex’ in the command line or create a shortcut to the wallet and append “-reindex” to the shortcut target by right-clicking in the shortcut and selecting ‘Properties’.

Daemon: To update the daemon, you will need to restart with the --reindex flag.

In the v12 update, we’ve automatically enabled the transaction index by default. This will allow your client to pull up any transaction from the blockchain. This is mainly used in DarkSend and the decentralized budget system.

What is the Decentralized Budget System?

In decentralized projects like Dash, funding has proven a significant issue. Even the mighty Bitcoin frequently struggles to attract and fund sufficient resources through donations alone. We plan on fixing that in a 100% decentralized and sustainable way. With Bitcoin, 100% of the block reward is allocated to miners. While mining is an important component that secures transactions, it is not the only requirement for a healthy network as Bitcoin’s recent struggles with funding have demonstrated.

We believe that the block rewards belong to the network first, and should be used to fulfill more than just one of the many needs of a healthy network. Developers, miners, masternode operators, legal council, marketing, and merchant services are only some of the potential needs of a healthy network and all deserving of funding when worthwhile projects are identified. With Dash, anyone can now introduce funding proposals directly to the network itself, on which the masternode community (who are essentially the network owners / operators) will vote. Approved budgets are then paid similar to how miners are paid… directly from the blockchain rewards. In accordance with our original proposal that the community approved in May, we will gradually transition the block reward allocations through February to eventually provide for a budget of about 8000 DASH per month to fund proposals.

What’s next?

The Dash development team will initially focus on ensuring a smooth rollout of v12 to the network. We hope with all the testing already performed that the number and severity of bugs will be minimal, but we plan to do extensive testing during and after deployment to remedy any issues that arise.

Next, we plan to test the budgeting system. At the very beginning we will have only the core team submit a few proposals so we can make sure everything works perfect. We are counting on masternode owners supporting this staged deployment procedure… your votes are needed to make this work.

Further down the road, the core team has numerous ideas we are evaluating for the next major release. The budget system enables entire categories of functionality that weren’t possible without it and we plan to take some time to develop a longer-term strategy for the next several releases, in line with Dash’s vision and mission.

I look forward to hearing everyone’s feedback on the new functionality. It has been a challenging yet rewarding few months, and I’ve enjoyed working with everyone that has helped manage the project, supported testing, and contributed ideas. The Dash community is as organized and professional as ever thanks to everyone’s contributions. The next six months will bring new challenges, but I’m excited to see that we are better equipped than ever to tackle them and have both a governance and funding system in place to support entirely new possibilities. I hope you are as excited as I am to see what’s coming next. Enjoy version 12!

Sincerely,

Evan

Full Description Of Budget System:
https://dashpay.atlassian.net/wiki/pages/viewpage.action?pageId=8585240

Can I make a proposal and submit it to the system?

Once the initial proposals have been tested and funded, the budgeting system will be enabled for the entire community. The amount of funds available initially will be relatively low, and we suspect there are a backlog of ideas that community members are hoping to submit. For this reason, getting your proposal funded immediately may be challenging. However, as the allocation away from miners and toward proposals progresses, more and more projects will succeed in obtaining funding.

How to use the budget system:

https://dashpay.atlassian.net/wiki/display/DOC/Masternode Budget API

Downloads:


https://www.dashpay.io/downloads/

Version Updates:

v0.12.0.45
https://dashtalk.org/threads/v12-release.5888/page-11#post-63575

Credits:
--------

Thanks to who contributed to this release, at least:

eduffield
UdjinM6
Crowning
moli
flare
thelazier
adios
poiuty
scratchy
moocowmoo
the-baker
BrainShutdown
Lukas_Jackson
Sub-Ether
italx
yidakee
TanteStefana
coingun
tungfa
MangledBlue
AjM
Lariondos
elbereth
minersday
qwizzie
TaoOfSatoshi
dark-sailor
AlexMomo
snogcel
bertlebbert
oaxaca
cwnage

As well as everyone that helped translating on https://www.transifex.com/projects/p/dash/
 
Last edited by a moderator:

oaxaca

Well-known Member
Foundation Member
Jul 8, 2014
573
832
263
Should there be a win64 version on the download page?
 

aaxx1503

Active Member
Feb 28, 2014
113
106
93
Great job! But seriously do you guys need help updating the icons on the main buttons lol? I'll draw something up
 

nmarley

Active Member
Jun 28, 2014
366
424
133
Are there 64-bit Linux version?

Sorry for not formatting, I have NO IDEA which icon is the "code" icon in this editor:

file ./packages/dash-0.12.0/bin/*
./packages/dash-0.12.0/bin/dash-cli: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=3c9f81bce066679f3ee68132004df373632bd478, stripped
./packages/dash-0.12.0/bin/dashd: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=e340505b9c74380dc11c7fe97bc6296569914455, stripped
./packages/dash-0.12.0/bin/dash-qt: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=f9beb2ae815b77b27986f9efdaa2afb0d2582643, stripped
./packages/dash-0.12.0/bin/dash-tx: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=c7a4bb469ce3fd4fe4e76dd5bf7d3bf7f46021be, stripped
./packages/dash-0.12.0/bin/test_dash: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=ab3f24fc0740dec2cd04bdd43ad57710dbc25a16, stripped
./packages/dash-0.12.0/bin/test_dash-qt: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=e389149ec78bdf52bcae2f904acd46a7af0f65b8, stripped
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
Are there 64-bit Linux version?

Sorry for not formatting, I have NO IDEA which icon is the "code" icon in this editor:

file ./packages/dash-0.12.0/bin/*
./packages/dash-0.12.0/bin/dash-cli: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=3c9f81bce066679f3ee68132004df373632bd478, stripped
./packages/dash-0.12.0/bin/dashd: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=e340505b9c74380dc11c7fe97bc6296569914455, stripped
./packages/dash-0.12.0/bin/dash-qt: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=f9beb2ae815b77b27986f9efdaa2afb0d2582643, stripped
./packages/dash-0.12.0/bin/dash-tx: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=c7a4bb469ce3fd4fe4e76dd5bf7d3bf7f46021be, stripped
./packages/dash-0.12.0/bin/test_dash: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=ab3f24fc0740dec2cd04bdd43ad57710dbc25a16, stripped
./packages/dash-0.12.0/bin/test_dash-qt: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=e389149ec78bdf52bcae2f904acd46a7af0f65b8, stripped
Yes, checkout the downloads page again.
 

pille

Active Member
Feb 18, 2015
268
295
123
is 'masternode start' from hot wallet necessary?

Edit: Argh the dir-name f*cked my update script, archive is 'dash-0.12.0.44-linux64', dir is 'dash-0.12.0'
Edit 2: and 64/32 folders were removed
 
Last edited by a moderator:
  • Like
Reactions: GilAlexander

fible1

Well-known Member
Dash Core Team
Masternode Owner/Operator
May 11, 2014
710
722
163
Can someone post an instruction on how to update on Linux? It's not working for me on ubuntu.

Pablo.
 

LucD88

Member
Aug 15, 2014
75
49
58
Did the "masternode list" parameters change?

It was ./dashd masternode list | grep -e XXX -e XXX -e XXX -e XXX etc. before, changing that to ./dash-cli masternode list | grep -e XXX -e XXX -e XXX -e XXX etc. still doesn't display the status of my nodes. Anyone?
 

MangledBlue

Well-known Member
Jun 28, 2014
1,246
678
183
USA
Did the "masternode list" parameters change?

It was ./dashd masternode list | grep -e XXX -e XXX -e XXX -e XXX etc. before, changing that to ./dash-cli masternode list | grep -e XXX -e XXX -e XXX -e XXX etc. still doesn't display the status of my nodes. Anyone?

you'll have to use dash-cli from now on

dash-cli masternode list | grep -e IP -e IP
 

GilAlexander

Member
Jun 26, 2014
84
23
48
Did the "masternode list" parameters change?

It was ./dashd masternode list | grep -e XXX -e XXX -e XXX -e XXX etc. before, changing that to ./dash-cli masternode list | grep -e XXX -e XXX -e XXX -e XXX etc. still doesn't display the status of my nodes. Anyone?
There're txids now.
Try ./dash-cli masternodelist "addr"