v0.110.0

[Keith-CY]

0.110.0 (2023-05-31)

CKB Node & Light Client

• [email protected] was released on May. 17th, 2023. This version of CKB node is now bundled and preconfigured in Neuron.
• CKB Light [email protected] was released on May. 28th, 2023. This version of CKB Light Client is now bundled and preconfigured in Neuron

Caveat

◆ CKB Light Client is only activated on testnet, thus only light testnet is enabled in Neuron. CKB Light Client on Mainnet requires a hardfork on the mainnet in the future.
◆ [email protected] requires data migration, which is irreversible. Be cautious to start the migration without a backup. How to back up data of ckb node

On the other hand, we strongly recommend you to back up the old data before migrating, the ckb node data path can be found by clicking preference -> Data -> CKB Node Config & Storage. Because once the migration starts, the data will be no longer compatible with all older versions of CKB.

Assumed valid target

Block before 0xc0c532e10c708852d9586be46a5ed8317b2aa0835c721aa691abffb9bf4a26cd(at height 10,004,892) will be skipped in validation.(#2689)

---

Light Client Mode

YouTube: https://youtu.be/tQm9YvgG7iE

---

We are thrilled to introduce our new feature: Light Client Mode. This feature makes Neuron more practical and convenient, allowing you to manage your digital assets more easily. Please note that it is currently only available on the testnet, as activation on the mainnet will require a hardfork.

What is the light client model?

Light Client Mode is a connection mode of Neuron that connects to a built-in CKB Light Client. Compared to a full node, it downloads a portion of the blockchain data to obtain necessary information. This allows Neuron to access the CKB blockchain faster.

Light Client Mode Advantages

1. Higher synchronization speed: Light Client Mode enables faster synchronization of blockchain data, saving users' time and network bandwidth.
2. Less disk usage: Light Client Mode requires only a fraction of the blockchain data to be stored, resulting in less storage space requirement compared to a full node.

Using a MacBook Pro (13-inch, M1, 2020) device as an example, we conducted a realistic test of synchronization from block 0 to the latest block 9,380,828 (2023/05/22 Pudge network data):

• Light Client Mode: The synchronization process consumed about 5.5 hours and approximately 45MB of disk space during running. (The disk usage is related to the transaction count, and this test included 782 transactions.)
• Full Node Mode: It took about 36 hours to synchronize 107.8GB of data. (Excluding the time to find an assumed valid target block.)

In the above test scenario, using a light node compared to a full node reduced synchronization time by 84.7% and disk usage by 99.9%. (Please note that these numbers are for reference only and may vary depending on different equipment, network conditions, and account data.)

Light Client Mode Usage Scenarios

Compared to full nodes, light nodes require less disk space and network bandwidth, making them suitable for users who want to quickly access blockchain information without needing the full blockchain data. However, please note that for transactions containing time locks, Cheque contracts, or other operations that require full node data verification, you will need to switch to full nodes.

---

New features

• feat: Adapt ckb light node (#2590) #2615: Adapt ckb light node.(@yanguoyu)
• Feat/implement dynamic fee rate based on fee rate statistics #2599: Implement dynamic fee rate based on fee rate statistics.(@jeffreyma597)
• feat: update ckb node version and assume valid target #2689: Upgrade ckb node to v0.110.0.(@Keith-CY)
• feat: download ckb_aarch64 for neuron-arm64 #2627: Download ckb_aarch64 for neuron-arm64.(@Keith-CY)
• feat: Add dialog warn for migrate date to 0.108 #2651: Add dialog warn for migrate date to 0.108.(@yanguoyu)
• feat: Set allowToChangeInstallationDirectory for windows. #2567,feat: Set allowToChangeInstallationDirectory for windows. (#2567) #2568: Set allowToChangeInstallationDirectory for windows.(@yanguoyu)
• feat: improve the interaction design of the DatetimePicker component #2674: Improve the interaction design of the DatetimePicker component.(@WhiteMinds)

Bug fixes

• fix: Use batch rpc to request result. Optimization sql search. #2530: Batch request to improve performance of nervos dao records.(@yanguoyu)
• fix: Sometimes RPC timeout but ckb is living #2574: Improve heart beating check of built-in ckb node.(@yanguoyu)
• fix: Remove old indexer data and fix typo. #2565: Remove obsolete indexer data.(@yanguoyu)
• fix: Init wallet device. #2581: Skip password requirement when interact with a hardware wallet.(@yanguoyu)
• fix: messages.codes.SQLITE_MISUSE (#2575)  #2609: Upgrade leveldown to fix SQLITE_MISUSE.(@devchenyan)
• fix: Restart or stop sync process by connectionStatusSubject. #2595: Fix latency of switching networks.(@yanguoyu)
• fix: Fix when enter over 8 decimal crash. #2629: Fix crash when enter over 8 decimal.(@yanguoyu)

New Contributors

• @kuzirashi made their first contribution in Fix typo in hardware wallet message #2559
• @mortoys made their first contribution in Refactored Calendar component to remove dependency of primereact. (#2592 #2592
• @devchenyan made their first contribution in fix: messages.codes.SQLITE_MISUSE (#2575)  #2609
• @WhiteMinds made their first contribution in fix: failed to connect to ckb rpc after upgrading electron to v23 #2652
• @homura made their first contribution in docs: proxy when install #2657

Full Changelog: v0.106.0...v0.110.0

Downloads

OS	Arch	Package	SHA256 Checksum
Windows	x64	exe	0d3ef750f48494e4114d582d9199998da89f4e0a6ecb7809cc3d7d0a7121194a
macOS	x64	zip	69ed2efa29e570b73abb4129e7a0b5b186161cbcd12cbc56e96df4c1ed255294
macOS	arm64	zip	db0e794796deae1818eb33c2775b03cc4dace9baa7d5b9ca3a7e27df858ed64c
macOS	x64	DMG	7099908ba8442fc9f394c0033c8925abce66601e8d4e42105efe46979b4fa228
macOS	arm64	DMG	42a50772bfdf83b7ca1cfa457cd938805b1d8fba3547766771da59ec91bb0e65
Linux	x64	AppImage	baf615f4de292a83237fc6598437182456e35e4a5485092fbe691ae0fa37f6c9

---

This discussion was created from the release v0.110.0.