I’m curious, are the satellites capable of sending commands to nodes? Not especialy for migration, I mean in general, for various tasks.
Like… if the devs decides to switch some parameter, or turn something on/off, etc., can they do this through satellites, by sending commands directly to nodes?
Or it’s all done through updates?
There are a request to restore from the trash, GET_AUDIT, GET_REPAIR, online check. I’m not aware of any other.
But yes, adding new features requires a release.
1 Like
So the hashtore migration is activated through updates aswell, I suppose.
This means that once you see the new version installed (136 ?), your node is on active migration?
This also means that all nodes that have v.135, are not on hashtore automigration?
Some operators reported that they seen the migration started on their nodes, but they are on 135. I’m thinking that there were 2 formats of v 135 released, one format with hashtore on, one format with hashstore off… or the operators are mistaken.
1 Like
I just not aware of the exact process, and can ask only on Tuesday (1.09.2025 is a holiday in USA).
None of my 1.135.x nodes has started migration so far, and I don’t have an insides, is it started or not.
+1
1.135.x can work with both hashstore and piecestore code so this could be a hint of how it will proceed. My node too has the flags set at falsebut no migration yet.
I got an answer from the team:
1 Like