– Continued UI/UX development for Essentials 3.0.
– Multi-signature accounts supported recharge transactions from the main chain to the side chain
– Optimized developer-related features for the new multi-network mode
– Improved the confirmation page of cross-chain transactions to facilitate users to confirm transaction information
– Improved in-app browser injection mode and WalletConnect connection stability and user experience for non-EVM networks
– Improved the support of DID applications in multi-network switching mode to maintain a smooth user experience
– Added check for bluetooth connection during use of Ledger hardware
– Fixed several bugs of BTC network and improved the stability of BTC support
– Released Hive Node 2.9.1 and JS SDK 2.9.1/2
– JS SDK uses ts-retrofit library to optimize JS SDK internal implementation
– Added test cases in JS SDK to count the efficiency of encryption/decryption implementation and the time impact on file operations of different sizes
– Optimized and improved the wrapper implementation of Hive Node’s encryption interface for DID Native as needed
– Designed the way Hive Node displays statistics to node owner and vault owner
– Validated the HiveHub webApp in the test environment, and fixed bugs found internally
– Optimized HiveHub’s NodeRegistery contract
– Solved the compatibility problem of Peer in Native DHT
– Tests to verify value-related collaboration between Native DHT and Java DHT
– Optimized the iterative process of FindPeer and FindValue of Java SDK to reduce data traffic requirements during the period
– Fixed Java SDK’s issues found in testing
– Optimized the implementation of the Python Wrapper interface of the Native SDK
– Added support for checking for null and empty strings in credentials subject and service property json in Native SDK
– Started the development of Schnorr multi-signature support for CR registration and other related functions.
– Continued to conduct functional tests of DPoS 2.0 consensus in test environments such as Testnet, and fixed issues found in the tests. DPoS 2.0 is an important upgrade of the elastos main chain consensus, which is conducive to improving the decentralization of the Elastos network and increasing the stability and security of the consensus network.
– Developed DPoS 2.0 operation documents for community participation in DPoS 2.0 functions.
– Supplemented test cases, and conducted test case coverage statistics through Github action.
– Completed the development of the main chain browser’s Richlist to display all addresses and the development of new transaction types of DPoS 2.0, and started testing.
ESC Side Chain
– Located and fixed issues found during ELink stress testing. ELink is a decentralized oracle network that allows other smart contracts to securely access data such as identities and credentials on the EID side chain, opening up the data link between DID identity data and dApp applications, and meeting the needs of dApps to obtain DID and credential information.
The ELA Buyback Program to Support DPoS 2.0 is complete. Read the full statement here: https://news.elastos.org/ela-buyback-program-to-support-dpos-2-0-is-complete/
DPoS 2.0 is coming to the Elastos Main Chain!
But first, Testnet.
Looking to run a supernode? We’ve got you covered. The Gelexy Team has provided a comprehensive breakdown of all the steps for running a Testnet supernode. Read our guide here: https://elastos.info/blog/registering-a-dpos-2-0-supernode-on-testnet-complete-instruction-manual/