As promised in the Steem Keychain proposal, we will post monthly updates to show our progress.
This one comes a bit late because we wanted the new version to be live first and Chrome took a while to review and accept the update.
Here s what we achieved in December.
Remote Default RPC
We haver seen some nodes down in the past, and users had to manually try other nodes to make Keychain work again. To fix this issue, we added a new
DEFAULT node. Keychain is basically calling the backend to know which node it should use. For now, we are using Steemit's node, but if it goes down we can quickly change it to any working node.
Steem Keychain backend
For this default RPC feature to work, we had to create and host a simple backend. For now it's only route returns the current default rpc node. You can check it here at
Keychain's backend is of course opensource, and you can find its code on this Github repository
We kept going with a big refactor that simplifies greatly how accounts are handled. This was necessary for two reasons. First, it makes the application faster through a better management of asynchronous requests. Second, we plan to add support to shared authority accounts and it will be easier and cleaner to implement after this refactor.
So far, it was only possible to power up to the same account using Keychain. After this update, you will be able to power up to other accounts.
In January, we will continue going down the list of features detailed in the SPS proposal, with a particular focus to the following :
- Give support to multiple languages on Keychain through localization
- Give support to Keychain integration to Communities
We are listening to the community. Do not hesitate to drop feature requests on our Github repository or contact me on Discord (@stoodkev#8281)
On behalf of our team, a big thank you to the community for helping us fund Steem Keychain through SPS.