In our last sprint, the team focused on OneExplorer bug fixes and enhancing the data stream for the OneExplorer. We also worked on the One-Click Deployment, Chain Driver Engine and streamlining the Smart Contract Deployment.The list of changes includes:
OneExplorer
Features
- OneExplorer to use web-sockets
- Update Payment Transaction Screen
- Started work on a DB to house accounts and transactions
OneExplorer Bug Fixes
- Spinner Icon image doesn’t show when explorer is loading a lot of data
- KPIs show boxes, when home page loads slowly
- Remove Swap Data from front-end
- Fix front-end for Account Screen transactions to show all information in the payload
OneExplorer Known Bugs
- Drop down on the Search bar sticks and you must select an option for it to disappear
- OneExplorer isn’t optimized for mobile devices
Protocol
Features
- Created a new identifier for Smart Contracts, to mitigate dependency on Tendermint
- Completed Integration for Smart Contracts, with a new hash identifier
- Chain Driver Engine: Decoupled accounts from the protocol layer and managed them in an Accounts DB, this includes ETH and BTC Accounts for the Full Node owner
- Chain Driver Engine: Enabled Signing mechanism in Chain Driver Engine for ETH and BTC
- Chain Driver Engine: Funding for BTC Account
In the next sprint, we will complete the work for managing the Explorer Data in the new DB to help facilitate faster queries. The Chain Driver will have the ability to create Smart Contracts on ETH and BTC, we are starting work on the micro-services layer for the OneWallet, working on drawing up the complete architecture for the Side Chains and Channels, and completing One-Click Deployment to be tested in our Devnet.