During the last week Igor successfully integrated the
safex_offer into the blockchain as a transaction. He has also achieved coding the creation and edit of
safex_offers in the command line interface so he has already been able to put offers into the blockchain. Igor started the pulling of the offer list from the blockchain methods so that we can then freely parse the blockchain and pull out offers to evaluate and be able to interact with them.
Up on deck is the purchasing flow: so the ability to send money to an offer and settle the delivery of a product. There are a few directions that we can take that expose different levels of advantages such as anonymous buying (no account needed to buy), and the ability to provide different methods of shipping, and how we can expose more rails of the protocol to add more dynamism to the marketplace experience.
In the past week we’ve made progress integrating the Bitcoin keys and systems associated with making transactions. Alongside that development Mirjana has been continuing with the refactor to make the wallet efficient, to reduce lag and load times. This refactoring will continue through this week with a goal to finalize in this week.
During our testing of the wallet we uncovered some bugs related to transaction forming in the golang module, and this bug is being investigated since Friday when it was reported. While we resolve the refactor on the wallet application this bug should be addressed and fixed during this week so that we can wrap up sfx and sft transactions and move onto adding the marketplace functionality into the wallet.
Intermittent Safex Wallet Outages
On Thursday the Omni node that services the safex wallet (v7) and migration system tripped an edge case in the Omni client. After an unsuccessful resync into Friday, Daniel took measures to update the software that was released in May by the Omni team which addresses the issue. Alongside this version update we also upgraded and deployed to new hardware with more resources.
Furthermore, into the weekend a number of assets that service the safex wallet (v7) and the orbiter wallet were attacked by a sophisticated ddos exploit utilizing high amounts of resources putting stress to the systems preventing synchronization. Daniel had spent the better part of the weekend singlehandedly setting up the security protocols on these assets to prevent unauthorized access by the attackers.
We will continue monitoring the environment to quickly prevent further outages of this duration.
Additionally, redundant nodes are in progress synchronizing to combat these issues in the future. Also, in the future version of the safex wallet (sails wallet) there is an option to set your own blockchain node, so if the provided one is knocked out or you prefer to use your own full node you will be able to set it yourself and continue uninterrupted.
All services should be operational as usual.
We have not yet received an updated response regarding the previous patch we have provided to the wallet rpc.
The next migration run will be October 21, 2019. Remember that the last day of Migration will take place on November 30, 2019 (6 weeks from now).
The Safex Development Community