NEL May Report

robbie wang
NewEconoLabs
Published in
4 min readJun 5, 2018

NEL

NEODUN

1. The driver function has been basically completed. Now neo’s nep6 wallet has been imported, the WIF import wallet has been entered manually, and the address and firmware have been upgraded and managed. The ability to import wallets with a seed password will be supported in June.

2. Changed the program architecture of NEODUN. NEODUN now operates as a main program with plug-ins to increase the scalability of the hardware wallet. Plug-ins are small programs that can be installed and uninstalled at any time, including plug-ins and functional plug-ins that support each kind of coin or token, such as plug-ins that detect whether a program in the wallet has been tampered with.

3. Added the function of installer sub-package transmission to solve the problem of too large installation package.

4. The communication protocol was modified several times to make the protocol more standardized and extensible. Added the ability to name the wallet address in NEODUN and added an error code that returned a failure to know the failure reason in the driver.

5. Rewrote interfaces to third-party wallets. For security reasons, we temporarily provide only three interfaces for querying NEODUN connection, querying wallet address, and requesting wallet signature. We tested the use of NEODUN’s log-in and transaction on Nel’s Web Wallet Beta to complete the entire transaction process.

6. We have optimized a large number of driver and device experience issues this month, fixed a number of bugs, and this work is still ongoing. After the version is stable we can do some open tests.

Optimized some pages and interaction logic.

ThinSDK

Improved test cases for Sgas and auction contracts

Completed the test case for NNC.

ThinSDK-node accesses scrypt-async

WeChat mini-program

New version update.

New version NEO mini-program development.

Multi-sig tools GUI plug-ins and multi-sig documents.

Blockchain explorer

The files are hard to manage due to the file storage system we used. To solve this problem, We researched the Alibaba Cloud OSS Object Storage Service and transformed it into a separate service that is applicable to other projects. Currently, it has been deployed to Testnet environment, and provides file access services to outside users.

The problem that no data were found when querying blocks on Testnet was fixed.

Wallet Testnet

Added Chinese and English switch

Made it compatible with SEA wallet Login

Realized auction function

Wallet Mainnet

Added Chinese and English switch

Made it compatible with SEA wallet Login

Back-end

Fixed the problem of missing analysis data and added the analysis function and interface to complete the ranking of assets

Completed the nnc rewards activity page and the corresponding back-end interface function

A new milestone for collaboration between O3 Wallet and NEL, and its program back-end is completely switched to a NEL series API that uses the HTTPS transmission protection function to basically cover the necessary operations of the GUI.

Developed a contractNotifyExtractor (code-visible NEL github), a generic contract notification crawler.

It can realize the definition of json file (without modifying any code) to crawl different notification structure of different contracts. It can be called killer Develop a contractNotifyExtractor (code-visible NEL github), a generic contract notification crawler.

It can realize the definition of json file (without modifying any code) to crawl different notification structure of different contracts. It can be called killer communications between contract and external system.

Implemented all crawling tasks asynchronously without affecting each other

Implemented a built-in contract data translation tool that translates ByteArray, Integer, and other data in a contract into intuitive data representations such as String, HexString, Address, and BigInteger (ie, data stored into database can be used directly)

Operations are currently relying on Notify data stored in the NEL core database, will add an independent Notify storage module in future

Submitted 2 suggestions to NEO CLI project

Recommendation #165 on log (notify) storage. It is recommended to use a lightweight database to store the log (notify). To solve the problem, if the CLI log output file is too large, the inode of the Linux system will be exhausted. The NEO development lead has promised to optimize this feature in the next release.

Recommendation #167 on the acceleration of block synchronization verification efficiency. It is recommended to provide fast synchronization without a network (no new fast detection). We observe that if the CLI does not perform network operations, the block synchronization efficiency is several to ten times greater than the network operation. If this function is implemented, it can effectively solve the problem of network height and confirmation of the height difference of tens or hundreds of thousands.

Built a file operation test dedicated server to test the application of NAS and OSS services in file storage

In order to get smart contract class serialization deserialization and some other latest features update the test network CLI version to 2.7.5.0

NPM package is encapsulated for NEL thinSDK nodejs version. Nodejs lovers can easily handle various NEO related requirements as long as “npm i nel-neo-thinsdk”

Optimized the NEL data analysis service call method (eliminated no interval database call), greatly optimized the CPU usage of the NEL core database

--

--