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

V12 Testing Thread

w8 a bit...
You can wait, they're still dead links. Let's teach testers how to fish... i mean where to get the downloads...

1. Go to https://dashpay.atlassian.net/builds/allPlans.action
2. Click on "02_Develop" of your choice OS
3. Click on the top build number (in green color, meaning successful build) under "Recent history" on the left side.
4. Click on tab "Artifacts".
5. Click on "gitian-[linux/mac/win]-dash-dist".
6. Download your file.
 
Last edited by a moderator:
You can wait, they're still dead links. Let's teach testers how to fish... i mean where to get the downloads...

1. Go to https://dashpay.atlassian.net/builds/allPlans.action
2. Click on "02_Develop" of your choice OS
3. Click on the top build number (in green color, meaning successful build) under "Recent history" on the left side.
4. Click on tab "Artifacts".
5. Click on "gitian-[linux/mac/win]-dash-dist".
6. Download your file.
Moli why I didn`t know that before? :) Great that is usefull!
 
Win-32bit v0.12.0.27-12d4519 seems much better, haven't seen wallet hanging when shutting down. DS mixing seems really fast. And so far I haven't got a failed IX transaction. But one of my wallets is stuck at block 88804 after I sent 10 IX payments in one transactions (but the receiving wallet is not stuck), plus 3 IX transactions before this one. Not sure if sending too many IX transactions so fast could make the wallet stuck?

upload_2015-7-23_23-8-14.png


EDIT: The receiving wallet is at the current block with http://test.insight.dash.siampm.com/ which is 88829 right now.
 
I'm sorry to ask this again, but I haven't seen anyone answer:

How does the budget know if we're voting for more projects that we can afford? We're only using 10% of the rewards, what if a bunch of projects are approved, is there a system that rejects them, or postpones them until other budgets before it are paid off? And if so, is it first come first served, or will we have budgets that were started then cancelled because another project comes along with more votes?

If the former happens, it would be chaos :)
 
woo-hoo!! wonder what's on the menu this time... Just bought 6 new low end servers, should be fun...

"version" : 120027,
"protocolversion" : 70095,
"walletversion" : 61000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 89084,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.00496241,
"testnet" : true,
"keypoololdest" : 1437751616,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"errors" : ""
 
So I haven't received a payment for Tante Stefana's Cherry farm, though we've past my payment start block

"TScherryfarm" : {
"URL" : "http://www.dashpay.io/ts.json",
"Hash" : "678333ef5ee35e7d13b531eae9a0ca0ab250a77493c7f3d9dcc54d74ee8a6f29",
"FeeHash" : "238a5a8e9f7d3ed957fd8177bac5f4bed63f3e8f8c3557e23a5f66959a91481a",
"BlockStart" : 89000,
"BlockEnd" : 89775,
"TotalPaymentCount" : 15,
"RemainingPaymentCount" : 13,
"PaymentAddress" : "yL7WTtehXs7w5wsyqGMpkdESM9W1ejHRvi",
"Ratio" : 1.00000000,
"Yeas" : 9,
"Nays" : 0,
"Abstains" : 0,
"TotalPayment" : 7500.00000000,
"MonthlyPayment" : 500.00000000,
"IsValid" : true,
"fValid" : true

Is this because I was too late with my proposal and the budget dropped due to insufficient funds? or is this because my yeas went down to 9 from over 60? If we lose votes every time someone reboots their masternode, this could mess up projects. Why is this happening?

Now I didn't record the votes anywhere so I might have misread my yea score, but I'm pretty sure it was over 60...
 
Couldn't we put the votes in a .CONF file like vote.conf to store our 'votes'??
 
Couldn't we put the votes in a .CONF file like vote.conf to store our 'votes'??

You know, a solution like this may not sound secure, but would it be insecure? It could definitely keep all your votes as a masternode owner valid, even if you change things around. It would be like revoting after your vote was cancelled due to removals or changes. You just can't arbitrarily throw everything in your dash folder out the window all the time, LOL., like we do on testnet (saving only wallet.dat) It could also be a dat file. Hell, could it be part of the wallet.dat file? That way nobody'd mess with it.
 
As long as I have a way to STORE/EDIT and RESUBMIT Vote(s) upon MN restart, easily....
 
I just issued mnbudget show and only got 4 results

B33r4Cr0wning
Rpi_4_flare
greek-island -> seriously, this is the best idea eeeeever :eek: :tongue: :cool:
NewMac4Udji

What happened to all the previous one's? From QT

"version" : 120026,
"protocolversion" : 70094,
"walletversion" : 61000,
"balance" : 10293.36728877,
"darksend_balance" : 0.00000000,
"blocks" : 89234,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 0.00434370,
"testnet" : true,
"keypoololdest" : 1437682179,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"errors" : ""
}

Also, tried to "getblock hash 89234", but the syntax is wrong. I completely forgot how to find the hash of a block to compare with others and determine if we're on the same chain or not. Help?

.
 
I just issued mnbudget show and only got 4 results

B33r4Cr0wning
Rpi_4_flare
greek-island -> seriously, this is the best idea eeeeever :eek: :tongue: :cool:
NewMac4Udji

What happened to all the previous one's? From QT



Also, tried to "getblock hash 89234", but the syntax is wrong. I completely forgot how to find the hash of a block to compare with others and determine if we're on the same chain or not. Help?

.
getblockhash 89234

^^^^ one word
 
getblockhash 89234

^^^^ one word

I was pretty sure that was it, goddammit, with one word... I tried it a few times and got "code -5" or "-1" ... I just tried again and it worked. Seriously, not kidding. Must have been a recurrent typo or something. never-mind...

00:10:39
getblockhash 89260
00:10:39
0000007ddbb0b2123a452d5cb0d2f3118ea094558b15c2d1beeb75c120c319f5
 
v0.12.0.28

Links should work this time! THis should also fix some syncing issues and consensus between the winners list.

Filter SigTime modes / version / proto bump
remove sync forcing and count already seen as a success instead
Improve portability of mn ranking algos
Fix syncing issues …
Safer calcscore implementation
Added calcscore cmd
limit mnw votes-per-mn
changed min ver back to 70066
do not sync while IBD
delete comment
protocol bump
Various improvements …


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
 
Is anyone else having issues staying with the current chain or is it just moli?

No problems on win7 64bit version
Code:
17:57:38

{
    "version" : 120028,
    "protocolversion" : 70096,
    "walletversion" : 61000,
    "balance" : 1403.60586065,
    "darksend_balance" : 0.00000000,
    "blocks" : 89307,
    "timeoffset" : 26,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 0.00651688,
    "testnet" : true,
    "keypoololdest" : 1435036349,
    "keypoolsize" : 1002,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}
Still working on the linux ... brb
 
Yup, my two linux servers are stuck at 89299

I'll try re-indexing

BTW windows version is moving up, so seems fine.
 
Back
Top