75.54% Miner Versions 0.118.0
This has hardly changed in the last few days and weeks. Do we have to wait here until the ravages of time weed out the old miners? Or would it be possible to suggest that the largest manufacturers, whose names are well known, implement a version update function and even make this available to them on demand?
Versions from 0.119.0 and newer contain fundamentally important changes for the network. Or am I misunderstanding this and it is not the ASIC miners themselves that are affected, but only the nodes to which they are connected? In any case, we are clearly lagging behind developments here and this highlights a disadvantage of our ASIC-neutral POW consensus: only a few manufacturers are currently pushing their products onto the market, which is a great pity. Plurality should be promoted here; after all, Eaglesong is open source!
this is the case, an asic manufacturer can push firmware updates for the machines, but the node version is completely separate, it is running on a computer, not the mining machine
These miners have probably decided to only carry out manual node updates. I think this should not be a problem, at least once a month or even every six months. Isn’t a daily automatic system update check standard? I think you could at least set this to once a week. E.g. Sunday 10 a.m. and then you can always check on Sundays whether everything is still running as it should.
An automatic update check is probably not integrated in the Node software? I know this function from the Neuron wallet. However, the update would then also have to be applied. Couldn’t this be activated by default?
In any case, it would be sufficiently conservative for everyone to at least update to 0.119.0. It doesn’t always have to be the very latest version.
there is no automatic update function in the node, mining infrastructure can be complex and is specific to each pool or miner’s operation, it wouldn’t be suitable to automate updates