Masternode Operators do not "buy" software to generate them revenue. They're rewarded for a service. It is expected they take proper measures to insure the network is maintained.
We have had testnet for months, where everything has been layed out. Numerous questions and answers are brought up daily.
There is no responsibility by the dev team, who are volunteers, to produce a step-by-step direction for MN Op. It is expected MN OPs keep up with changes. There is absolutely nothing new or radically different, just adaptation to bitcoin core v.10.
Fair enough. But in that case, I suggest everyone have very reasonable expectations about the speed with which the network will update. I don't recall ever seeing such a small percentage of masternodes updated after this many days. Usually enforcement goes on within 2-3 days, and we're still sitting on 25% updated. Some is probably due to the weekend, but some is due to the fact that many of us can't figure this thing out.
I would like to thank qwizzie for his very helpful guide.
I'm sorry you feel that way, but I really believe your reasoning is off. Most haven't updated because they are well aware of what's happening, and that inicial launch could have (and did) have little mainnet quirks, that the devs quick as always came to solve. Service providers seldom update on launch, as these situations are expected. Veteran MN OP's are already "tired" of updating 2, 3 4 times in one day. Most will wait for a final "ok, this is it, this one is gold".
Plus it's August, when most people in the northern hemisphere are on holidays.
The network is steadily udpating. .v45 really does seem like it is it, as far as I can tell, and I have no doubt the majority of the network will update shortly. Service providers are always last to udpate to avoid service disruption to their clients, in case of expected bugs and quirks. Testnet is a sterile environment while mainnet is a jungle.
If "many of you" can't figure this out, the simple solution is to head over to
www.dashpay.io and ask for help. Or just stroll through the last half dozen pages of testnet, or better still, the v.12 official release thread.
ddlink, I really don't want to antagonize you or anything, but the way you write makes it seem like there is a responsibility by the dev team to push out simple to follow tutorial for noobs. That is certainly not the case! It is their responsibility to
answer the end user any questions they have. And we did have many many questions over the past months. And nothing world changing has happened for MN Ops anyways.
Everything is "exactly" as it has always been in terms of use and MN setup, except slight difference that now you should use the RPC client dash-cli, which behaves exactly as dashd.
start the daemon with "./dashd", from there on use "./dash-cli" for RPC, for example, "./dash-clip help"
Sure, all those things are factors. But I'm sure there are a lot of people whose update scripts are broken now, or who manually update and aren't exactly sure what to do or where everything goes.
I know you aren't trying to antagonize me--no hurt feelings, no worries. It *does* seem like software is more likely to be used if you publish instructions on how to use it. Perhaps somebody in the community could write a quick guide, like qwizzie just did, and Evan could link it in the "Official Launch" post next time. It seems more efficient than trying to dig through multiple pages of multiple threads.
It's not that it's anybody's JOB, it's just that it would be really useful to have =) It's been a LONG TIME since the MN updating process changed even slightly! (The last I recall was when the binaries started being hosted on the website rather than at github.)
