Release v0.110.0 #2688
Merged
Release v0.110.0 #2688
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [eslint](https://github.com/eslint/eslint) from 8.30.0 to 8.31.0. - [Release notes](https://github.com/eslint/eslint/releases) - [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md) - [Commits](eslint/eslint@v8.30.0...v8.31.0) --- updated-dependencies: - dependency-name: eslint dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…ackages/ckb-indexer/eslint-8.31.0
* fix: Use batch rpc to request result. Optimization sql search. 1. For the nerovs dao page, there are many rpc requests, use batch request. 2. Because some users have many relations with others cells, left join twice to search inputs and outputs. 3. Find unlock transactions with the status that equal Dead or Pending.
Add a github action to manage stale issues, a replied issue will be marked stale if no activity for 60 days and closed after 7 days without updates. The task is set to run on UTC 5:30 everyday Ref: Magickbase/neuron-public-issues#94
The option close-issue-reason is an enum of completed and not_planned. I missed it and set it to a custom value which led to ci failure. Ref: https://github.com/marketplace/actions/close-stale-issues#close-issue-reason
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
1. Try to check ckb is alive every 30s. 2. When startCkb try to check the ckb is null.
fix: Sometimes RPC timeout but ckb is living
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: yanguoyu <[email protected]>
Simplified Chinese of "migrate" should be "迁移"
Bumps [undici](https://github.com/nodejs/undici) from 5.13.0 to 5.19.1. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v5.13.0...v5.19.1) --- updated-dependencies: - dependency-name: undici dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
…ndici-5.19.1 chore(deps): bump undici from 5.13.0 to 5.19.1
* fix: Init wallet device. * fix: update electron and @ledgerhq/hw-transport-node-hid 1. support create external buffers with electron/electron#36624 2. node-hid support electron 21 with node-hid/node-hid#486 * chore(deps): update electron version.
1. Remove `debounceTime` because it has `distinctUntilChanged` unless the node connects or disconnects frequently. 2. Remove starting or stopping the sync process from `ckb-runner`, because it has control by `connectionStatusSubject`, when the `ckb` connection status changes, it will stop or start. 3. Add start and stop App logs to find the latest running log.
feat: provide loading for the detail button on the history page
Co-authored-by: Chen Yu <[email protected]>
* fix: Fix deposite dao 1. When refreshing in DAO page, the network is not ready, so ignore 404. 2. Reset deposited DAO capacity when opening dialog. 3. Create a common `generateDaoDepositTx` hook to create a deposit tx whether `despositeValue` change or `suggestFeeRate` change * fix: Fix type error * fix: Fix typo
…2674) * feat: improve the interaction design of the DatetimePicker component * fix: the Calendar component does not navigate to the correct panel when a value is provided
Keith-CY
force-pushed
the
rc/v0.110.0
branch
2 times, most recently
from
46c2973
to
12d8942
Compare
yanguoyu
approved these changes
May 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
0.110.0 (2023-05-31)
CKB Node & Light Client
Caveat
◆ CKB Light Client is only activated on testnet, thus only
light testnetis 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
Assumed valid target
Block before
0xc0c532e10c708852d9586be46a5ed8317b2aa0835c721aa691abffb9bf4a26cd(at height10,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
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):
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
Bug fixes
New Contributors
Full Changelog: v0.106.0...v0.110.0