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

V12 Testing Thread

moli said:
I think the first number on the left is the number of the masternodes that have up-to-date protocol version or the same protocol version with your wallet. Last night after I installed the latest version from Atlassian I saw the number was something like 0/16/16, so I started one MN, the number changed to 1/17/17, Right now my wallet shows:
View attachment 1627

This version is on protocol number 70093 but when I do "masternodelist protocol" it shows 7 nodes are still on protocol 70092:
EDIT: So as you can see there are 45 masternodes online but only 38 nodes are up-to-date with the protocol version in this scenario.

The other numbers i think are just how many nodes are active, because all 45 nodes show "ENABLED". I think if a node is removed or expired it will show different numbers.
Click to expand...
You (almost) got it! :smile:
ds-compatible / enabled (will be payed) / all

There supposed to be a range for enabled protocols but we dropped it for now (or it least it was like that in v25, I haven't got time to read v26 code changes yet :grin:)

EDIT: oh, no, it's back again :grin:
 
Last edited by a moderator:
bertlebbert said:
When sending coins I tried to do the following:

click Send > click Inputs > Select all > enter address in "Pay to'" box > click Send > Result: nothing

It doesn't send and displays no error message.
Then after I "unselect all", I can send all my coins by typing the total in Amount box.
Click to expand...
Did you enter amount when you did "select all"? It doesn't fill it when you select all inputs, you still have to enter it manually (because wallet has no idea how many recipients will be there)
 
UdjinM6 said:
Did you enter amount when you did "select all"? It doesn't fill it when you select all inputs, you still have to enter it manually (because wallet has no idea how many recipients will be there)
Click to expand...

Yes that's definitely the issue... I didn't realize I had to enter the amount before selecting All outputs. If the user is unaware of this (like I was), and selects All outputs first, then the amount box disappears, making it seem as if choosing an amount isn't even an option, let alone additional recipients To me, that's confusing :what:

Edit: Turns out this is only an issue if the wallet is sized on the desktop to it's least height... make it full-screen or even just a little taller and the Amount box no longer slides out of view.
Haha, no longer confused :wink:
 
Last edited by a moderator:
AjM said:
And again this LONG block time gap, 14 min.
UdjinM6 do you have any theory about this? This happens also mainnet.

Block Approx. Time Transactions Value Out Difficulty Outstanding Average Age Chain Age % CoinDD
87570 2015-07-21 19:51:51 4 130.84536172 0.05 7530386.89168718 109.274 542.154 13.8218%
87569 2015-07-21 19:37:30 3 423.45828772 0.051 7530363.67740146 109.264 542.144 13.8228%
Click to expand...
Bump.
 
AjM said:
And again this LONG block time gap, 14 min.
UdjinM6 do you have any theory about this? This happens also mainnet.

Block Approx. Time Transactions Value Out Difficulty Outstanding Average Age Chain Age % CoinDD
87570 2015-07-21 19:51:51 4 130.84536172 0.05 7530386.89168718 109.274 542.154 13.8218%
87569 2015-07-21 19:37:30 3 423.45828772 0.051 7530363.67740146 109.264 542.144 13.8228%
Click to expand...
Well, someone just turned off his miner I guess

Code: 
block    date/time                   txes     diff          size
87580    Jul 21, 2015 11:29:08 PM    1        0.02796362    216
87579    Jul 21, 2015 11:28:57 PM    6        0.02853157    15141
87578    Jul 21, 2015 11:24:23 PM    3        0.02969183    4413
87577    Jul 21, 2015 11:23:16 PM    3        0.03057095    7841
87576    Jul 21, 2015 11:18:41 PM    2        0.03083211    4406
87575    Jul 21, 2015 11:17:40 PM    1        0.03039719    216
87574    Jul 21, 2015 11:17:07 PM    3        0.03543821    5135
87573    Jul 21, 2015 11:03:47 PM    4        0.03549578    8676
87572    Jul 21, 2015 11:02:09 PM    1        0.03673003    216
87571    Jul 21, 2015 10:58:07 PM    3        0.04016693    8565
87570    Jul 21, 2015 10:51:52 PM    4        0.05027984    9501
87569    Jul 21, 2015 10:37:11 PM    3        0.05115346    6569

EDIT: for mainnet this could be a large multipool who decided it has more profitable coin to mine now because diff is too high
 
UdjinM6 said:
Well, someone just turned off his miner I guess

Code: 
block    date/time                   txes     diff          size
87580    Jul 21, 2015 11:29:08 PM    1        0.02796362    216
87579    Jul 21, 2015 11:28:57 PM    6        0.02853157    15141
87578    Jul 21, 2015 11:24:23 PM    3        0.02969183    4413
87577    Jul 21, 2015 11:23:16 PM    3        0.03057095    7841
87576    Jul 21, 2015 11:18:41 PM    2        0.03083211    4406
87575    Jul 21, 2015 11:17:40 PM    1        0.03039719    216
87574    Jul 21, 2015 11:17:07 PM    3        0.03543821    5135
87573    Jul 21, 2015 11:03:47 PM    4        0.03549578    8676
87572    Jul 21, 2015 11:02:09 PM    1        0.03673003    216
87571    Jul 21, 2015 10:58:07 PM    3        0.04016693    8565
87570    Jul 21, 2015 10:51:52 PM    4        0.05027984    9501
87569    Jul 21, 2015 10:37:11 PM    3        0.05115346    6569

EDIT: for mainnet this could be a large multipool who decided it has more profitable coin to mine now because diff is too high
Click to expand...
I dont get it.
And mainnet, i think there is plenty mining power all the time?
 
Mainnet example, blocktime 15 min:

Details for Block #306629
Hash 0000000000003c5b85d7b9c344306bd58edc30967fd797bb63da5a13f54c3d6f
Date/Time 2015-07-22 15:06:49 extracted by Mining Pool Hub
Transactions 6
Value Out 12.82594924 DASH
Difficulty 3621.08943747
Outstanding 5,600,656.14351182 DASH
Created 4.64285715 DASH

Details for Block #306628
Hash 000000000006e32d668b081b76eee08a98c72ff33dd6bfea9ecded67e24dfc66
Date/Time 2015-07-22 14:51:16 extracted by Coinmine.pl
Transactions 2
Value Out 7.08061972 DASH
Difficulty 3401.845799
Outstanding 5,600,651.50065467 DASH
Created 4.64285715 DASH
 
AjM said:
I dont get it.
And mainnet, i think there is plenty mining power all the time?
Click to expand...
It works smth like that.
To find a block in 2.5 minutes you need to generate X hashes on average.
But now there is some Y power that was turned off so you can generate only (X-Y) hashes on average but diff still aims for X so you need to find few blocks on a lower power than you previousely had even to simply readjust diff. And on average it might take proportionally more time then designed 2.5 minutes. But sometimes it's not close to average, there's always some luck involved so you might need to generate 2X, 3X etc hashes to find the right one.

Yes, there is quite a large amount of power on mainnet but still 20%+ of extraction is "unknown"
https://dashninja.pl/blocks.html#blocksdetail
https://chainz.cryptoid.info/dash/#!extraction
which in case of "jumping" multipool might mean up to 40-50% of mining power that come and go.
https://chainz.cryptoid.info/dash/#@diff
 
Giving latest Ubuntu 15 a spin, first QT on v12. All good, running fine, going to start mixing as soon as I finish setting up another MN on a VPS for cold/remote testing. (15 seems snappier that 14 under VMware on OSx by the way...)

I can fire up the QT through terminal, but I can't double click it on through the desktop. Allow execute as program is pre-checked unlike before... so I have no clue what's going on. Is this expected behaviour or am I being a ding-dong?

Also.. testnet address can now start with an x ? This was my second generated addy

2JK29Mb.png


.
 
Last edited by a moderator:
UdjinM6 said:
It works smth like that.
To find a block in 2.5 minutes you need to generate X hashes on average.
But now there is some Y power that was turned off so you can generate only (X-Y) hashes on average but diff still aims for X so you need to find few blocks on a lower power than you previousely had even to simply readjust diff. And on average it might take proportionally more time then designed 2.5 minutes. But sometimes it's not close to average, there's always some luck involved so you might need to generate 2X, 3X etc hashes to find the right one.

Yes, there is quite a large amount of power on mainnet but still 20%+ of extraction is "unknown"
https://dashninja.pl/blocks.html#blocksdetail
https://chainz.cryptoid.info/dash/#!extraction
which in case of "jumping" multipool might mean up to 40-50% of mining power that come and go.
https://chainz.cryptoid.info/dash/#@diff
Click to expand...
Ok, thanks for explanation, so everyting is 'normal'.
 
yidakee said:
Giving latest Ubuntu 15 a spin, first QT on v12. All good, running fine, going to start mixing as soon as I finish setting up another MN on a VPS for cold/remote testing. (15 seems snappier that 14 under VMware on OSx by the way...)

I can fire up the QT through terminal, but I can't double click it on through the desktop. Allow execute as program is pre-checked unlike before... so I have no clue what's going on. Is this expected behaviour or am I being a ding-dong?

Also.. testnet address can now start with an x ? This was my second generated addy

2JK29Mb.png


.
Click to expand...

I've had this problem on linux for quite a while. I keep forgetting to say so. Ubuntu 14.04 64 bit, been that way at least a week or two, like I said, I figured it was me, so I just started it up via command line and figured I'd research or ask later.
 
Please vote for my project, it's a very good project, trust me! LOL
dash-cli mnbudget vote 678333ef5ee35e7d13b531eae9a0ca0ab250a77493c7f3d9dcc54d74ee8a6f29 yes
 
flare said:
It is a feature of the forum, which keeps shortening the URL with '....' plus Evan C&P these shortened links^^

In the end the URLs do not change, they always point to the latest build:

latest CI-builds for v0.12.0

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/[/QUOTE]


I plan on getting at least 1-2 more Pi's soon
so I can run my MN 24/7
Play with (1)
and - compile MN's on the other and use for testnet
I have not been able to test your Pi release
I assume you have had good results?
Click to expand...
 
MangledBlue said:
I plan on getting at least 1-2 more Pi's soon
so I can run my MN 24/7
Play with (1)
and - compile MN's on the other and use for testnet
I have not been able to test your Pi release
I assume you have had good results?
Click to expand...
I had no negative feedback so far - i do not own a Pi to test it myself :)
 
TanteStefana said:
I've had this problem on linux for quite a while. I keep forgetting to say so. Ubuntu 14.04 64 bit, been that way at least a week or two, like I said, I figured it was me, so I just started it up via command line and figured I'd research or ask later.
Click to expand...

I don't know... my geek gut instinct tells me some changes forced this to be expected behaviour. I can't even see a Dash icon on there. 2 distros and same behaviour... I suspect we're both a classic case of trosvalding-dongs :tongue:

.
 
Looks like we have consensus with no reference node. I'll turn on enforcement :grin:

"88107" : "yEeSSUjQKPVJKZYeMRtaRiSoUqYuid3Wuv:10",
"88108" : "yJX2hdQG7Uno57yzunutg4pj5xFzK4vJtx:10",
"88109" : "yJX2hdQG7Uno57yzunutg4pj5xFzK4vJtx:10",
"88110" : "y9rsd42F9Fz7ZX9MaKsFkFmofwdft1B5Pn:10",
"88111" : "xw9d7Eibuzzc9ozufqRSnYFZpTBynNVdtY:10",
"88112" : "xxJvLbXTKpta7PdD4zPWfonUyCupCLE4vg:10",
"88113" : "yDspkpxGpaRqbbTr19eBn2nCj9YRhHKHuo:10",
"88114" : "yB4b1XP2mUGVsdiijCkFLqjWjGC4RugcDK:8, yDspkpxGpaRqbbTr19eBn2nCj9YRhHKHuo:2",
"88115" : "y1MbKEcpcLE15vU3k49B7VFSUhNNdNSe8w:10",
"88116" : "xyoxmhKVAeHm4Kdtke7wvQJETt2W2KfGxQ:10",
"88117" : "xyf8F7VRDzAAEmr4ngR765eBZaiEDJhPvk:10",
"88118" : "y4qp9mrZGYWLQFZdd5dM27ZxmXmBEdFnHc:2, yCZRLFwmMeUV256u5jMoJ8gXTP6k6AnBEt:8",
"88119" : "yEzrYaNLEhXrbNrBv9sEQ1tQURb1wM1tU6:10",
"88120" : "y9WXVCkdnCgsc8gSpuvoNRFURxPEhCZCEJ:10",
"88121" : "y2hnkJ6g3y9JqqNH7AJ2J3ZDXQt8QPnWQZ:10",
"88122" : "y2hnkJ6g3y9JqqNH7AJ2J3ZDXQt8QPnWQZ:10",
"88123" : "y4qp9mrZGYWLQFZdd5dM27ZxmXmBEdFnHc:10",
"88124" : "yEwo6J4fZNDe47ypcCausLUKcC5udA9zJB:10",
"88125" : "xyDQpfkqoZUzYSxJP1TDz8F9SxNDs2Kmp7:10",
"88126" : "y4Urkd3z2cVoY1mSGYSMXjUbCSG6wJBfbn:8, y5PN7AUJDPMNR884ZWpns5x2wC2dPsp2dk:2",
"88127" : "yAZdUtUt5w73SiEaWRvTJjoVy3cQf4TUTV:10",

We should see complete consensus in another round or two with all of the nodes online, but even moderate consensus is enough for the enforcement protocol. Also, some double payments are OK, that's working as designed. Think of it as round robin, with a 1% chance of double payment (on mainnet, it's much higher with a lower masternode count). It's going to act kind of like a lottery, it should add some fun to the mix
 
You must log in or register to reply here.
Back
Top