I noticed an issue with the automated install script. When we need to re-run the install script (or update), it automatically generates a new validator key and completes the bonding process before we get a chance to import our old keys. This leaves 'ghost' dormant validators on the Explorer. It would be great if the script could ask: 'Do you want to generate a new key or import an existing one?' before doing the automated bonding.
@joshmilkson is it possible to implement a base reset command in the CLI at the very start of the script while saving the validator keys, something like a CLI flag or similar?
@Asentum I don't want to be boring in my posts, but I think I should report any irregularities in the work of the node and the network. Thank you for your excellent cooperation.
@joshmilkson while waiting for the announcement about the upgrade, a bot pops up that breaks my nerves from the beginning, that's the price that has to be paid...
I just wanted to confirm that I have successfully migrated the validator to the new VPS in Helsinki. Everything is running smoothly, the node is synced and active. I am continuing to monitor operations from here.
@Asentum Most crypto projects hide their bugs and pretend everything is perfect. @Asentum publishes them.
Reading through 42 devlog entries about midnight genesis resets, code drifts, and DNS bottlenecks is refreshing. This is what real engineering looks like. 🛠️
No team approval. No override." This is what true Web3 governance looks like.
Giving every $ASE holder a real seat at the table to vote on protocol parameters without master-key overrides shows that @Asentum is built for the long haul.
"Asentum: a protocol born immune to quantum attacks." 🛡️While older blockchain networks will have to face complex and risky hard forks to upgrade their security, Asentum is built from the Genesis block with post-quantum cryptography (ML-DSA-65).The countdown to Q-Day (2029)....