New home for keychanger? Not quite yet.

While working on The best key changer tool for hive we were asked to put it in the official hive repo on gitlab, I guess people feel like it's pretty good. :)

I guess I don't have permission!

In the meantime if someone wants to see how it's done or audit it: It's in Github. When I figure out what I did wrong, it will live here on the Hive Gitlab, unless they want it somewhere else, not super familiar with gitlab or the core dev team's specifics.


I'm honoured people like it, honestly. I feel like it's a pretty simple thing, but I guess there wasn't a safe and easy way to do it without fear of losing your account. So, I made an effort to make it as verbose and user friendly as I could, while maintaining security as much as possible. Owner keys are no joke.

A little bit about it for those that are curious:
The entire app lives in the browser, there is no cookies, the keys are not in the DOM anywhere, if you leave the window open for too long it will clear the keys (you have to start over, but if you are away for 30 minutes, likely something came up and you would want to anyway). The keys are masked on generation, to keep prying eyes off your goods. There is toggles to look at or copy to clipboard if you want to do it manually, but most likely, you just want to save the file and put it somewhere safe.

I settled on JSON format, it's plain text, universally understood, and fairly simple to read. Once the keys are downloaded, then you can change the keys to match the new ones, if it fails, you can start over, you can even use the same seed phrase, but it will tell you why it failed. (Likely wrong key or node issue, which I ran into testing, which is why there is a node selector now.)


I'm more than happy to keep building tools that people use, even ones that others may see as trivial, but there is a need for user friendly tools of convenience. Plus, I rather enjoy working this kind of thing.

As always,
Michael Garcia a.k.a. TheCrazyGM



0
0
0.000
0 comments