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

V12 Testing Thread

AjM said:
Why compiling take so much time?
I mean we are not in the 90's any more with 33 Mhz Pentium :grin:
Click to expand...
Actually this is a 8 core machine - compiling does not take that long, but launching the AWS instance, copying machine images, uploading the results...

And all of that for 6 different targets (Win 32 / Win 64 / Mac OS X / Linux 32 / Linux 64 / RPi )
 
flare said:
Actually this is a 8 core machine - compiling does not take that long, but launching the AWS instance, copying machine images, uploading the results...

And all of that for 6 different targets (Win 32 / Win 64 / Mac OS X / Linux 32 / Linux 64 / RPi )
Click to expand...
Aha, that explains it.
 
moli said:
OK let's read the OP again:

  • 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.

    What I understand is each block payment represents one payment a month... On Testnet we're not going to do this for the next 12 months or more so we just have to imagine that each payment is ONCE A MONTH until all the payment count is up. (eduffield can correct this if I'm wrong)
Click to expand...

So that's the way it works, makes sense... I was definitely curious how and when testnet would count votes, select winners and send payments.

Edit: Is that posted somewhere? Or you just figure it out?
 
bertlebbert said:
So that's the way it works, makes sense... I was definitely curious how and when testnet would count votes, select winners and send payments.

Edit: Is that posted somewhere? Or you just figure it out?
Click to expand...
The OP, Evan's first post of this thread: https://dashtalk.org/threads/v12-testing-thread.5484/

There're still so many questions about this plan, like "how do we know if someone is actually doing the work before they get paid.." etc. But I'm guessing Evan is testing first to see if the superblocks will be able to implement this without forking the main network to hadez... you know what i mean? :)
 
moli said:
The OP, Evan's first post of this thread: https://dashtalk.org/threads/v12-testing-thread.5484/

There're still so many questions about this plan, like "how do we know if someone is actually doing the work before they get paid.." etc. But I'm guessing Evan is testing first to see if the superblocks will be able to implement this without forking the main network to hadez... you know what i mean? :)
Click to expand...
Yep, makes sense :smile:
 
moli said:
The OP, Evan's first post of this thread: https://dashtalk.org/threads/v12-testing-thread.5484/

There're still so many questions about this plan, like "how do we know if someone is actually doing the work before they get paid.." etc. But I'm guessing Evan is testing first to see if the superblocks will be able to implement this without forking the main network to hadez... you know what i mean? :)
Click to expand...

I was curious why those 2 proposals of yours were getting paid (many payments) last night.
 
Dash Testnet Update -- 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:
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:
Click to expand...
Excellent... nay votes on their way (as soon as I update)
 
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:
Click to expand...

Code: 
2015-07-06 20:01:07 CBudgetManager::AddProposal -- updated vin of invalid finalized budget (0000000000000000000000000000000000000000000000000000000000000000-4294967295 to a965b7a1e5533cfc1caada72899b1f5db83e3b6cb74d61302892ec10f11f2692-1)

What does this mean?
 
 
Just making sure, is the version number back to 12.0.8? or is link wrong for win 32 bit ?

Downloaded 2 X
 
eduffield said:
Dash Testnet Update -- 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...an-linux-dash-dist/dash-0.12.0-linux32.tar.gz

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

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

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

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

The links above are outdated, latest build is

Windows:

https://dashpay.atlassian.net/builds/browse/DASHW-DEV/latest/artifact/JOB1/gitian-win-dash-dist/

Mac OX X:

https://dashpay.atlassian.net/builds/browse/DASHM-DEV/latest/artifact/JOB1/gitian-osx-dash-dist/

Linux:

https://dashpay.atlassian.net/builds/browse/DASHL-DEV/latest/artifact/JOB1/gitian-linux-dash-dist/

Raspberry Pi:

https://dashpay.atlassian.net/builds/browse/DASHP-DEV/latest/artifact/JOB1/gitian-RPi2-dash-dist/
 
You must log in or register to reply here.
Back
Top