Before we get into the details, a quick note about version names. The version introducing blockchain integration was originally planned to be named 1.2. Although there’s no change in the order or speed of operations, we decided we wanted to get a couple of specific features into production ASAP, so we decided to sneak in an extra release with a very small scope, which will be called v1.2. The following release (with blockchain integration) will be called v2.0. Please note this reshuffling of names is also not yet reflected in the milestones page or tracker - as of this moment both still show Ethereum integration and many accompanying tasks and features under v1.2. Please bear with us until we get everything reorganized!
Completed
Here are the main items we’ve knocked out since the last update:
eWallet Update February 18, 2019: the “We're Vikings, it's an occupational hazard” edition
Before we get into the details, a quick note about version names. The version introducing blockchain integration was originally planned to be named 1.2. Although there’s no change in the order or speed of operations, we decided we wanted to get a couple of specific features into production ASAP, so we decided to sneak in an extra release with a very small scope, which will be called v1.2. The following release (with blockchain integration) will be called v2.0. Please note this reshuffling of names is also not yet reflected in the milestones page or tracker - as of this moment both still show Ethereum integration and many accompanying tasks and features under v1.2. Please bear with us until we get everything reorganized!
Completed
Here are the main items we’ve knocked out since the last update:
Improvements:
Bug fixes:
/*.get
endpoints returning error 500 when not provided withid
#773NODE_NAME
interfering with deploy. #792In review
These tasks have been completed, pending review by wallet team admins:
Improvements
In progress
These are the tasks we’re focusing on right now:
As always, you can also follow our progress on the eWallet Waffle board and in our GitHub Milestones page.