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.
Finished tasks
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 https://api.steemkeychain.com/rpc
.
Keychain's backend is of course opensource, and you can find its code on this Github repository
Refactor
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.
Power Up
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.
Next steps
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
Feature requests
We are listening to the community. Do not hesitate to drop feature requests on our Github repository or contact me on Discord (@stoodkev#8281)
Thank you!
On behalf of our team, a big thank you to the community for helping us fund Steem Keychain through SPS.
@yabapmatt : Founder - Witness
@aggroed : Founder - Witness
@nateaguila : UI/UX
@stoodkev : Lead Developer - Witness
thanks for your work!!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
!trdo
Keep up the great work!
!giphy thanks
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Congratulations @lightcaptured, you successfuly trended the post shared by @steem-keychain!
@steem-keychain will receive 0.30132000 TRDO & @lightcaptured will get 0.20088000 TRDO curation in 3 Days from Post Created Date!
"Call TRDO, Your Comment Worth Something!"
To view or trade TRDO go to steem-engine.com
Join TRDO Discord Channel or Join TRDO Web Site
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
giphy is supported by witness untersatz!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Congratulations @steem-keychain, your post successfully recieved 0.30132 TRDO from below listed TRENDO callers:
To view or trade TRDO go to steem-engine.com
Join TRDO Discord Channel or Join TRDO Web Site
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Congratulations @steem-keychain! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :
You can view your badges on your Steem Board and compare to others on the Steem Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOP
Vote for @Steemitboard as a witness to get one more award and increased upvotes!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit