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

V12 Release

minersday said:
have you tried getting the bootstrap?
https://github.com/UdjinM6/dash-bootstrap
Click to expand...

I have not tried that yet with this update. Maybe the process will use less RAM indexing from the single bootstrap file than reindexing the existing blocks in the folder from v11. It is worth a shot, thanks for the reminder.

If that does not work, I might just have to increase my VPS' RAM size. Not that I'm complaining. I've always expected the cost and complexity of operating a MN to go up along with features-adoption-dashprice. Eagerly anticipating the day it costs $100/month in VPS fees just to run a single masternode.:D
 
Bridgewater said:
I have not tried that yet with this update. Maybe the process will use less RAM indexing from the single bootstrap file than reindexing the existing blocks in the folder from v11. It is worth a shot, thanks for the reminder.

If that does not work, I might just have to increase my VPS' RAM size. Not that I'm complaining. I've always expected the cost and complexity of operating a MN to go up along with features-adoption-dashprice. Eagerly anticipating the day it costs $100/month in VPS fees just to run a single masternode.:D
Click to expand...

If I am not completely mistaken, the latest bootstrap file is already reindexed?, just start the daemon up.
 
Updated my servers to v45, although one of them crashed twice during the reindex, but weirdly can't get my local wallet (either qt or daemon) to sync past block 278961, tried multiple times. Will retry with v46.

(all linux 64)

edit: v46 looking better.
 
Last edited by a moderator:
New Payment Logic

The masternode payments system is entirely rewritten for v12, in a way that doesn't require the reference node to run. However, a lot has changed and it might get confusing if you don't understand what's going on, so I thought I would make a post to show how it works.

SPORK_10_MASTERNODE_PAY_UPDATED_NODES

When this is enabled on the network it means that the masternode network will only elect newer versions to get paid. This has nothing to do with enforcement and payments can still be stolen while this is enabled

In the next stage we wait till the network looks like there is consensus of the order of masternodes to pay. When the network has not gained consensus the masternode winners list will look something like this:

Masternode Winners:
"321180" : "XuDo92RYbczPF4SEqc2sQBBVpwnmcZcoa6:103, XyF3zWTxhiGSSsTWPEAHrpRziNgKBbHjN5:1, XjADcow5Eh6f1PVunNsLZSQWhRjDpPqotH:1",
"321181" : "Xavn5tKg212Ltth65bifKqeXufxQzQaTLZ:3, XqYPAzpGwAHH7Q7ozMLxSyKvn31ZZkF2q9:100",
"321182" : "XeWoZQMkbvTZANs2Ywcp7bhHceGGXi6bH7:102, XeKYSFMsPxAffVhoeFcqXfedqWT4FXzYpr:4",
"321183" : "XqbDtmSTmWnuT2kNZD1HcK2maLw4UQAnUn:2, XtS1xMniqFqZvoPspr7FkFKBQcfRPevvYi:102",
"321184" : "XihbR3csJZsaeqobm7NHiUqHh2ZhcFiWka:2, XrVGd3bQB8hTVsvcw7w8UR5XuHQedWchds:101, XfVHwktZCHtTasWcuS3CFw7M5dhuA65SqT:1",
"321185" : "XysfSw23X4dn6oXnyDtj8Pa2tYUVLgqcjA:101, XnG1dkS8EV2pMPTk6JDE4AvTesQa4a3FjT:1, XcTQLKTjRvCyK4G7UinxgACUHx4rJfMU1H:1",
"321186" : "XfajLUm5qLt7YB8mQAcAU33bE1LSqDWRx6:1, XnJUfQUuvNjWZt7DnDUqG6WDV6PktvmVGw:105",
"321187" : "Xapxp1FT36CMtNbCYfyarCfXm8Hf9nUUtF:6, XpYpxwDhtKDH2otCK66XL625uwPdhF8tsu:100, XqzqXnQ1pc2cCTogRFe1GK86ecKxejooaK:1",
Click to expand...

If you look at "masternode winners" right now on mainnet, we have gained consensus and are ready to enforce! When the payment system has consensus it will look like this:

masternode winners
"321955" : "XjstqTzwMjhcf6Bk5LaQefdRtFeepfTFxQ:109",
"321956" : "XwVWU2dZPqJhgf68bkkHRcUioGhRt6UJBM:110",
"321957" : "XdxavYxuiKNiUemRShhqQ6gQgxaPbtBPFj:110",
"321958" : "XqKxPPh5ZRDpbV2dCsV1pdZoxALSrk7WgG:110",
"321959" : "XbBAqmiLdcpQEmdsw1FvJkWZ8cREZEMMzC:110",
"321960" : "XwKkDJnmUMc3UYYFUS6oyUkKbBwYgFaR4i:110",
"321961" : "XdgRA2YUFv7KtnnBzbLi1XKtUZ338XNjWR:110",
"321962" : "XpZvFwgREvx2q3QBwzuRy4jJ9qk7tuxcc7:110",
"321963" : "XhHXQ21BtPMNumw6KZJ7EjaJhqbLm7TRMj:109",
"321964" : "Xy8w86e6HDxNp2pUrXmessMgEAhAM8DHxX:110",
"321965" : "XfgroFvaP7dFv4ZXKQA197rCif1Vw3QgmX:109",
"321966" : "XeNUeQXys7hyQ6T7j5MtqK5Fxt3aNL3dNN:110",
"321967" : "Xaor98Mu5iZAAvT2LaxaYGjjRZMtNqAVm3:110",
"321968" : "XwtjDE351G562UrCsEpqRebCbF194H8cKy:109",
"321969" : "XwVWU2dZPqJhgf68bkkHRcUioGhRt6UJBM:110",
"321970" : "XdhfQJfU9B5DVcaQjmWdSCaPWqjuNGXE8f:110",
"321971" : "XqhudhXB57eUS7pYKb47TEeHAN9pXiCPxX:110",
"321972" : "XyahDigH4KJ5DN7YbxnzBL2zbU7XiFDX98:110",
"321973" : "Xby8QPP9rGqw8Y9fHLvf8ReLH8dtGRmFh3:110",
"321974" : "XyGTH7d48eQHP8cXfkMVrrEvRuFv4JUqwF:109",
"321975" : "XjQMr8yZQZ9gQgPbD2jqEP8EukrcbDaQP8:108",
Click to expand...

Other new things about the masternode payment system:
- When you restart your masternode, you are forced to the back of the queue. When you update from v11 to v12, this goes into effect and you will not be paid for the first payment period.
- The network prefers to pay people that are not subject to this penalty, meaning that when we upgrade the first nodes to upgrade will get substantial rewards when SPORK_10_MASTERNODE_PAY_UPDATED_NODES gets activated due to the small amount of qualifying nodes. Over time the rest of the network will also qualify for payment and the payment period will extend until it is normal again. This is our new "fast upgrade" incentive system, the faster you upgrade the more you get :wink:
- Multiple payments in a row are possible and OK. There should be about a 1/100 chance of this happening and you will not skip your next payment, it's something like the daily network lottery.
 
minersday said:
If I am not completely mistaken, the latest bootstrap file is already reindexed?, just start the daemon up.
Click to expand...

I could not get it to work - ugh - even after following the directions and speaking with Uj
Not sure why.... hummmm
Have to look at it again.
 
When you restart your masternode, you are forced to the back of the queue

What does the masternode "restart" mean exactly in this context?
 
Hello!
I would suggest that you return to the previous structure of tar, when the file and the folder is called in the same way (Its better for updaters script)
 
DonQuijote said:
Hello!
I would suggest that you return to the previous structure of tar, when the file and the folder is called in the same way (Its better for updaters script)
Click to expand...
Changing one variable is not so hard. I would suggest not to change all the times the structure of tar, don't touch it again :smile:
 
illodin said:
When you restart your masternode, you are forced to the back of the queue

What does the masternode "restart" mean exactly in this context?
Click to expand...

I'm pretty sure they mean, when you restart for the first time, between versions 11 and 12. But also, if you don't update fast enough and fall off the network. I don't think there should be any problems updating Dash v12 of any version. You don't have to reindex going from 12.45 to 12.46 for example. That shouldn't take more than 2 minutes to update and you won't fall off the network for.... what is it? 50 minutes? I can't remember.
 
updated my windows wallet to v0.12.0.46 and the process went really smooth. The prompt asking to reindex is awesome. great work. thumbs up to all of you.
 
TanteStefana said:
I'm pretty sure they mean, when you restart for the first time, between versions 11 and 12. But also, if you don't update fast enough and fall off the network. I don't think there should be any problems updating Dash v12 of any version. You don't have to reindex going from 12.45 to 12.46 for example. That shouldn't take more than 2 minutes to update and you won't fall off the network for.... what is it? 50 minutes? I can't remember.
Click to expand...

I guess what I'm asking in a round about way is how long does a node have to be DoS:ed for it to drop to the back of the queue.
 
I have this same problem on Ubuntu, since testing - as has someone else, but I never saw a post explaining why or what to do:

https://bitcointalk.org/index.php?topic=421615.msg12182210#msg12182210

I've been opening a terminal to execute dash-qt because of this. And this is not an issue with having the executable box checked in properties. It's simply not looking or acting like a double clickable executable. Did a setting get messed up? It's annoying not to be able to use it GUI style. This happens on my laptop and ubuntu box.

Since it's not just me, I'd appreciate the help, so I can help others, thanks.
 
TanteStefana said:
I have this same problem on Ubuntu, since testing - as has someone else, but I never saw a post explaining why or what to do:

https://bitcointalk.org/index.php?topic=421615.msg12182210#msg12182210

I've been opening a terminal to execute dash-qt because of this. And this is not an issue with having the executable box checked in properties. It's simply not looking or acting like a double clickable executable. Did a setting get messed up? It's annoying not to be able to use it GUI style. This happens on my laptop and ubuntu box.

Since it's not just me, I'd appreciate the help, so I can help others, thanks.
Click to expand...
I don't use ubuntu, but you should be able to double click it and choose: run in terminal...
 
You must log in or register to reply here.
Back
Top