I doubt that it'll be thousands. Maybe a few hundred...It'll probably cost us hundreds to thousands of dollars a month
As for the first part, you are right. For less than 100 a month you can get pretty high-end dedicated server with uncapped data and DDOS protection. They are no different to operate the VPS that most of us use now. For your second point, I disagree. The increase in USD price of DASH is what made me switch off of node40. Pricing the service in DASH per month made it cost prohibitive and worth the trouble of actually running my own MN. When MN income becomes a larger part of my monthly income in the future, why would I leave money on the table by going with a more expensive centralized service?I doubt that it'll be thousands. Maybe a few hundred...
Unlike mining hardware, which is a vertical market where the manufacturer charges whatever the market will bear, cohosting is priced from a much broader market. We can use this to our advantage, while the shitcoin miners can't, and wouldn't even know how if you told them... They can plug in toasters. Anything beyond that is more than they can handle... Enter 3rd party MN services to consolidate and undermine the network...
Leave money on the table now.As for the first part, you are right. For less than 100 a month you can get pretty high-end dedicated server with uncapped data and DDOS protection. They are no different to operate the VPS that most of us use now. For your second point, I disagree. The increase in USD price of DASH is what made me switch off of node40. Pricing the service in DASH per month made it cost prohibitive and worth the trouble of actually running my own MN. When MN income becomes a larger part of my monthly income in the future, why would I leave money on the table by going with a more expensive centralized service?
Thanks. To be honest i'm awaiting this pull to do some testing onNew version out in case nobody saw/checked![]()
where?New version out in case nobody saw/checked![]()
New version out in case nobody saw/checked![]()
Indeed. I follow the LastestSuccessful builds. I.e., Last build was "Jan 30, 2017 8:31:50 AM":where?
this build even tho dated 2nd feb has a timestamp of 1st Jan
https://bamboo.dash.org/browse/DASHW-DEV/latestSuccessful/artifact/JOB1/gitian-win-dash-dist/
Yup. I have an update script that reaches into the https://dashpay.atlassian.net/ as I mentioned above. And it stopped on the 30th. I figured, for hardening.OK, so if any of you have an update script or something, like me, you will need to notice that these updates are now located at a different place. You can see it was updated on page 1. We are now on protocol 70206 and latest update is today (Feb 2) Just FYI because I know a lot of people lurk and this thread is being ignored(slack is better)
Okay. Just so we have completeness. Flare posted in a chat channel the change the other day.Yup. I have an update script that reaches into the https://dashpay.atlassian.net/ as I mentioned above. And it stopped on the 30th. I figured, for hardening.
Um... what's the difference between the https://dashpay.atlassian.net/ latest builds and the https://bamboo.dash.org/ lastest builds?
We just had to move to a dedicated server because Atlassian Bamboo Cloud is EOL --> https://confluence.atlassian.com/bamboocloud/bamboo-cloud-eol-827125716.htmlOkay. Just so we have completeness. Flare posted in a chat channel the change the other day.
Atlassian strives to provide high quality and evolving products to our customers. With this in mind, we've made the decision to discontinue our Bamboo Cloud offering on 31 January 2017.
Just to clarify; this refers to the data on memory consumption and not the data in ~/.dash/ vs ~/.dashcore/Holding on to any old data is meaningless. You may as well apply the metrics of running a full node of a totally different coin.
@eduffield has said there will be a significant financial incentive to upgrading MNs ASAP.@qwizzie Related to your third question, https://www.dash.org/forum/threads/details-on-the-feb-5th-update.12874/
There will be a grace period where both 12.0 and 12.1 are allowed. Maximizing masternode payment is a bit tricky. On one hand you want to upgrade when the majority of the miners shift from 12.0 to 12.1. But you also need to consider the masternodes' place in the queue.
All in all there is not a huge difference in payout, so just relax and do it when it suits you best(as long as it's within a few days)
I was referring to statistical data gathered on resource usage.Just to clarify; this refers to the data on memory consumption and not the data in ~/.dash/ vs ~/.dashcore/
From what I understand you may very well keed the blockchain files from 12.0. No need to re-download the whole thing. Considering how many will update in a short period of time we might want 12.1 automatically copy from ~/.dash/ when first started to not cause havoc?
Yup. Maybe if you own a huge amount of MNs. We can be pretty sure there will be a few hundred MNs that will upgrade within an hour. In one hour there are only about 24 blocks. So unless you have a significant portion of those early upgraders, you are not likely to get that many extra payments.@eduffield has said there will be a significant financial incentive to upgrading MNs ASAP.
OK, if you say so. I know that Evan said something completely different, but maybe that's changed. Cheers!Yup. Maybe if you own a huge amount of MNs. We can be pretty sure there will be a few hundred MNs that will upgrade within an hour. In one hour there are only about 24 blocks. So unless you have a significant portion of those early upgraders, you are not likely to get that many extra payments.
And that's with the assumption that all miners will upgrade immediately. They won't. And miners on 12.0 will pay MNs on 12.0. So, that's why I previously said that one should only upgrade after a majority of the miners do. And of course you need to consider your place in the payment queue.
I'll pass on the recommendation moocowmoo gave me in my thread; Hold of your upgrade if your node is in the front of the payment queue, but a day or two tops. Otherwise upgrade asap.
1. We should be able to move the blocks and chainstate folders to .dashcore from .dash. Nothing else takes that long to update really, and those other things might change or something, so that's what I'm going to do. Hopefully it will go smoothly. At worst, we'll have to -reindex, but with everyone doing that at the same time, it'll probably be a pain in the arse.I have three questions with regards to v12.1 on mainnet per 5 Feb :
1 : with the new path (user/dashcore/etc) in update 12.1 how do we avoid users downloading the whole blockchain again (ending up having duplicate blockchains) and possibly getting into trouble with limited diskspace ?
2 : there is some talk about 1000 MB RAM being minimal requirements for update 12.1 ? I have currently no problems with running 756MB RAM on my masternodes, will that change with update 12.1 ?
because frankly i was planning to upgrade my VPS package on a much later date (around the Evolution update).
3 : how fast do we need to upgrade our masternodes version to 12.1 ? Say for example one of our masternodes could be paid in two days (after 5 feb), is it okay to wait for those two days and then upgrade ?
Is there a certain "grace" time period ?
I think the real incentive is to get enforcement on ASAP so the miners can't keep all the rewards, which is what happens every time we spork and enforcement goes off.Yup. Maybe if you own a huge amount of MNs. We can be pretty sure there will be a few hundred MNs that will upgrade within an hour. In one hour there are only about 24 blocks. So unless you have a significant portion of those early upgraders, you are not likely to get that many extra payments.
And that's with the assumption that all miners will upgrade immediately. They won't. And miners on 12.0 will pay MNs on 12.0. So, that's why I previously said that one should only upgrade after a majority of the miners do. And of course you need to consider your place in the payment queue.
I'll pass on the recommendation moocowmoo gave me in my thread; Hold of your upgrade if your node is in the front of the payment queue, but a day or two tops. Otherwise upgrade asap.