Over the next 12 weeks - we will be correcting the emissions error (service updating from 4PM GMT today and first updated rewards as of 4AM GMT tomorrow):
Current emissions daily: 54,794.5205 Should be daily: 27,397.2603 Total emissions to date: 1,863,013.6986 Correct emissions to date: 931,506.8493 Amount to be corrected over 12 weeks: 931,506.8493 (11,089.3673 daily)
We’ve changed the emissions to 16,307.8930 daily for the next 12 weeks and then after that point it goes back to the 27,397.2603 for the remainder of the first year.
From next Monday (March 24th), in order to qualify for emissions payments, you will need to be running the latest node version. From then on (unless otherwise stated, in advance), to continue being eligible to receive emissions, you will need to be running the latest, or the previous release before the latest, in order to be eligible to receive emissions.
Also today we are kicking off our external promotion of Impossible Futures via our social channels and have some interesting interview series ahead with industry disruptors. We are excited to get this campaign off the ground and have already seen over a dozen applications from some of you early birds which is great to see! We’ll share more news on this over the coming days and weeks!
This is excellent news- buuut… Why the weeks delay? The problem of nodes running old versions of antnode has been well-advertised for a while now.
Why not make that change to take effect 24 hours from now?
Anyone running any serious no of nodes is monitoring this forum, or if not deserves ZERO respect and consideration.
PLEASE make this change effective from tomorrow at the latest so we can hopefully see some improvements in network performance ASAP.
The abysmal performance of the network is really holding back developers like @happybeing@traktion and @Josh to name only a few from effectively sharing their work with us all.
I understand the desire and share it with you to get everyone on the newest versions. But we want to give the community enough time to make their upgrades and adjustments.
They have had more than two weeks. The rest of us can start the upgrade process in under 5 mins. If someone is running 10s of thousands of nodes its up to them and them alone to manage them efficiently. Especially when their intransigence and laziness is holding us ALL back.
Are you expecting those STILL running antnode v0.3.6 to sue or something?
I find this decision absolutely bizarre and counter-productive. It seems this concession to the community has been squeezed out of “management” most reluctantly.
They have already had more than two weeks to upgrade.
How much longer are we supposed to bend over backwards for the ignorant, indolent and intransigent parasites?
I don’t have to imagine a network where nobody can upload and there is precious little worth downloading.
So there may be a little disruption? Big deal.
And you know fine that allegedly 50% of the nodes are already upgraded to the latest. So it would only be an absolute max of 20 million nodes over several hours.
Nodes which are of sod-all use to anyone except their owners who continue to cream off the emissions.
Nothing is as refreshing as a little network collapse
We’re launched - the network now must withstand some storm out there and we had many mass shutdowns (especially during community nets long long ago) the network shouldn’t care too much
That 45m figure for nodes is UTTERLY MEANINGLESS if we cannot do simple upload/downloads.
And vast numbers of the above 45m will disappear once their free money is cut off.
WTF are we doing giving these operators another week of sponging off the rest of us?
Find some other more relevant statistic about the network to boast about because the 45 million nodes one will fool nobody, nor should it.
I am thinking there is testing to be done and also a upgrade to nodes to include version data in the node’s returned metrics
I’d rather 2 weeks since them realising the error in emission amount (we knew since the first days of emissions) to get it tested and implemented rather than a hasty implementation with further errors.
Just be thankful that after all the alerting of the issue, it only took @Josh to fly off the handle /jk to get the attention needed on the issues. And also a couple of us giving Bux a lesson in how to change a stick into a carrot. Just look further up the stick till you see the carrot hanging off of it
And @rusty.spork@Bux Glad to hear these 2 major issues of emission amounts and carrot/stick approach to upgrading has been adopted
I am not 100% sure. There could be something there. But in any case the emissions for checking it needs testing and the team was back at work for the 1st day after this is identified to be fixed just today/yesterday (Monday)
and we had many mass shutdowns (especially during community nets long long ago) the network shouldn’t care too much 