What would you like to search for?

Weekly Updates|13 MIN. READ

Elastos Bi-Weekly Update – 15 January 2021

  • SHARE

The last two weeks were packed with updates by the core teams, including the release of Hive 2.0, Trinity Native, and elastOS v1.3.4 for Android.

Let’s recap. 

Technical Dynamics

elastOS
– Released elastOS Android v1.3.4
– elastOS Essentials iOS version test, Native dApp adaptation verification, and related issues fix
– Improved the JWT processing process in Runtime to improve robustness
– Improved the display mode of the application list on Launcher; now reasonably handles empty lists and list sorting
– Launcher now saves the most recently used and most used data, and provides a more customized application list presentation
– Improved the backup and recovery mechanism of installed applications on Launcher; now correctly handling the deletion of applications
– DID dApp now supports scanning code to import DID from getdids.com
– Contacts now supports Hive-based backup and recovery mechanism
– Completed the dApp development template on Trinity CLI
– Added Trinity Native developer documentation
– Improved the reference document of Trinity standard intent
– Improved the function of backing up wallet data to Hive and increase the frequency of backup
– Improved the deployment script of the Trinity development tool chain, making it more convenient for developers to initialize the development environment
– Improved the translation of multi-language resources and supplement the new interface related content
– Released elastOS Essentials for iOS v1.3.3 and v1.3.4
– QR Code scanning function now supports scanning the QR codes in pictures
– Continuously optimizing Hive Plugin/Hive Manager and fixing discovered problems
– Fixed the issue of Wallet Plugin dApp crash and optimized related implementation
– Improved the UI design of credential request intents, provided certain application customization capabilities, and improved readability
– Improved the UI design of DID sign-out and provide better user feedback
– Improved the support of dependent packages, locked specific versions to maintain good compatibility, performed manual upgrades and verified compatibility when needed
– Upgraded Cordova component on Android version of Runtime to solve the problem of abnormal Camera Plugin

Hive
– Improved internal error handling and feedback of error messages on Hive node
– The migration function of Vault between Hive nodes is now complete
– Designed and implemented the internal interaction between Hive node and Backup node
– Hive node has unified the authentication interface and backup interface of “cloud disk” and backup node
– Implemented the Backup/Restore function of Vault data and the migration function of Vault service node
– Released internal alhpa test version for upper elastOS verification use on Java SDK and Swift SDK
– Solved all problems caused by improper usage of CompleteableFuture objects internally on Java SDK
– Improved the client initialization method to optimize the developer’s experience on Java SDK
– Solved the problem of multithreading concurrently triggering user authorization request calls when there are multiple internal Vault objects on Java SDK
– Added the default authentication interface implementation on Java SDK, supported elastOS DID intent authentication, and simplified application development
– Bug fixes in Java SDK development and testing
– Updated the initialization method of Hive Swift client SDK to keep the style consistent with Java SDK
– Bug fixes in Swift SDK development and testing, and code improvement
– Officially released v2.0.0 versions for Hive Node, Java SDK and Swift SDK
– Implemented the migration function between Vault service nodes, and added test cases on Hive node
– Added Easy Auth module interface on Swift SDK
– Organized Hive Java SDK developer documentation
– Wrote Vault data backup/node migration and other functional interface documents for Hive Node
– Fixed a bug in Hive Node when the internal parameters of the downloaded file in Scripting mode were abnormal

DID
– Native SDK has updated Credential interface used for on-chain
– Native SDK new interface now supports updating and deprecation of self-declared Credential
– Native SDK has added test cases to verify multi-signature documents, updated self-declared Credentials, and updated DID Controllers
– Native SDK has added API related to query specific DID credential list from ID sidechain
– Native SDK has added the test cases related with custom DID
– Swift SDK has solved the problem of Antlr dependency exception
– Swift SDK has added debugging and debugging support for source code display for CocoaPod package
– Swift SDK has added bitcode support
– Enhanced internal thread safety support on Swift SDK
– Swift SDK has solved the internal crash problem and releases the new version v1.6 simultaneously
– Java SDK has completed the development of DID 2.0 related features, including custom DID, DID transaction, certificate on-chain, revocation, listing, etc.
– Java SDK has improved the internal caching mechanism to improve the parsing efficiency of DID objects
– Released v1.8 version of Swift SDK
– Updated Elastos DID v2.0 design specification
– Added an optional Issuer parameter to the revoke query interface in Native SDK
– A new interface in Native SDK now supports parsing credential revocation status, and added test cases
– Native SDK has updated the implementation of deactivate DID and added test cases
– Java SDK has optimized the design of Resolver Cache and DID Store Cache
– Java SDK has optimized the uses of a more reasonable Log interface to replace the original Console Log output method
– Java SDK DID Backend module now supports application context input

Carrier
– Released a new version v6.0.1 for Native SDK
– Based on Native SDK v6.0.1, the new version v6.0.1 of Android SDK and Swift SDK are released simultaneously
– Updated the Carrier Trinity plugin implementation according to Carrier v6.0.1, and optimize and modify some interfaces
– Carrier Native SDK and Carrier Bootstrap compatibility verification before the new version is released
– Based on the latest Native SDK interface, updated the implementation code referenced in the Swift SDK
– Optimized the implementation of the dependency on the Native SDK within the Carrier Android SDK
– Updated the CI script of the Carrier Swift SDK warehouse to use the latest Native SDK version
– According to the latest Carrier SDK, updated the WebRTC Extension module code
– Continued to Implement Managed Group features

Mainchain
– Adjusted the situation of sending degenerate transactions to all situations that trigger consensus degeneration
– When consensus degradation is triggered, only transactions related to DPoS consensus can be packaged
– In order to enable the sidechain to perceive changes in the consensus of the main chain, SPV will now push transactions related to consensus degradation and restoration
– SPV has added the GetNextArbiters interface to obtain the next round of rotation node information
– Modified the packaging rules of illegal block transactions to not require that they must be packaged in the next block and take effect after packaging
– The storage method of proposal-related data was adjusted from memory to database
– Adjusted the processing logic of data synchronization from the genesis block after consensus degradation
– Sorted out proposal category coding specifications
– Conducted related tests on consensus degeneration to AuxPOW and recovery to DPoS
– Supported the perception of degenerate transactions through SPV and provided an interface for querying the current consensus status
– Discussed the feasibility of transferring information through cross-chain transactions
– Adjusted the statistical method of Arbiter’s inactive count
– Fixed the issue that may cause node crash under special circumstances
– Solved the issue of transaction hash conflicts for restoring DPoS consensus
– Continued to carry out related tests for consensus degradation to AuxPOW and recovery to DPoS
– Improved the rules for handling fines related to CR committee members performing their duties
– Completed the proposal category coding specification

ETH Sidechain
– Based on the newly added GetNextArbiters interface of SPV, new nodes can now obtain the producers that currently need to create a direct connection, which solved the problem that the blockListener can only obtain the latest block data and cannot obtain NextArbiters.
– ConsensusStatus added WorkingHeight, recorded the height of switching Arbiters, and was used to uniformly calculate the current number of dutyIndex
– Modified verifyConfirm, changed the block header parameter to uint64, and supported the direct transmission of the block height of the main chain
– Incorporated the latest code of blockscout for use in the ETH sidechain browser and resolve conflicts
– Prepared the test environment and test scripts for the ETH side chain to dynamically perceive on-duty nodes, and conduct side chain consensus and deposit and withdrawal tests
– Solved the problem of excessive logs caused by an error in the metadata type of the ETH side chain browser contract
– Solved the problem of Miner error in some transaction details page of ETH side chain browser
– Supported reading the number of miners from the configuration file
– Submitted the version of the ETH sidechain to dynamically sense the duty node for testing
– Solved the problem that the Notify method will cause the ETH sidechain node to crash
– Modified travis configuration to fix the problem of CI test failure
– Fixed the issue of missing transaction records in ETH sidechain browser
– Fixed the issue of incorrect Token transaction quantity in ETH side chain browser
– Fixed the issue of ETH sidechain browser contract parsing error

Elastos Wallet
– SPV SDK has completed the reconstruction of the database storage module and supplements unit tests
– Used the input address of the voting transaction as the output address, and no longer use the new change address
– Adjusted the byte size limit when creating a transaction to the UTXO quantity limit
– Prepared ELA Wallet v1.4.8, which fixes the problem that the wallet cannot be synchronized in some cases
– In order to optimize user experience, SPV SDK initiated the development of multiple P2P data synchronization modes
– SPV SDK has modified ETH sidechain wallet callback, adding 100% progress callback when synchronization is completed
– Fixed the bug on SPV SDK that returns too much information when getting a transaction detail
– Fixes the issue of wallet crash in some scenarios after database reconstruction on SPV SDK

Community News

Hive 2.0 is officially live! This essential upgrade allows developers to create applications where users have more control over how their data is stored and have actual options like choosing their own Vault, linking their data to their DID, creating financial incentives for Hive Nodes, and more.

https://news.elastos.org/hive-2-0-release-announcement/

Our Hive: Introduction is a perfect way to get acquainted with this essential piece of Elastos and learn why it’s a game changer for controlling your data.

https://news.elastos.org/hive-2-0-an-introduction/


Trinity Native is now live, marking another major milestone for #Elastos. Trinity Native allows developers to convert elastOS apps to native apps for Android and iOS, making the ecosystem more accessible than ever.

https://news.elastos.org/trinity-native-1-0-release-announcement/

Elastos Foundation has published a comprehensive introduction on why this developer option is an essential next step for elastOS. Learn about it all here:

https://news.elastos.org/trinity-native-an-introduction/


December 26

The annual Catch-the-trend Golden Ceremony  was held in Sanya. Elastos was awarded the most influential public chain of 2020.


Feng Han, co-founder of Elastos, attended the annual Catch-the-trend Golden Ceremony in Sanya. In the roundtable session, he exchanged views  on network congestion with Wu Ming, co-founder of Conflux, Quan Xujun, CEO of Origin Database, and Henry, Chief Product Officer of Findora.  Han Feng said, “DeFi will continue to move forward in 2021, and the market scale could be up to ten times that of 2020. At present, DeFi projects are still cloning how a bank operates but lack the concept of a user’s credit. The next step is to realize a way to obtain users’ credit with their on-chain and off-chain data.”


January 10

Feng Han was invited to participate in Watt’s live broadcast. He shared his views on how to develop DeFi based on a user’s credit.


Useful links:

  • SHARE

Next Posts

Tech Announcements|3 MIN. READ

Hive 2.0 Release Announcement

Tech Announcements|8 MIN. READ

Trinity Native: An Introduction

Tech Announcements|3 MIN. READ

Trinity Native 1.0 Release Announcement

00:00 / 0:00:00