Light Client Mode with Main Network Support

[Danie0918]

The main network light client will be released soon and we need to consider support for it when the new version of Neuron is released.

[Danie0918]

#200 PRD

【Network settings optimization 】Support for light client main network and optimization of known issues.

• Requirement Description:

1. [Bug] Currently there is no restriction on linking users to external nodes here, need to add restrictions like light client nodes.
2. [Feature] Support for light client main network.
3. [Feature] Supports main/test network switching for built-in node and light client node.

• Requirement Contents

1. Internal node and light client node support manual switching between main and test network by clicking to switch to the corresponding network.
2. When the currently selected node is an internal node, a popup window is required to report an error when an external node is detected to be enabled.

• When no external network is added, a pop-up prompt directs the user to add a network to enable the external node.
• When external nodes have been added, a list of external nodes is displayed for the user to select, and the user can also choose to add new network nodes.

3. Pop-up window interactions：

• Pop-ups are only detected as alerts when the user opens the software or when switching to an internal network node.
• Click to cancel ignoring alerts and still link internal network nodes.
• Click Confirm only when selecting an external network node or the Add Network option.

[yanguoyu]

1. 【Network settings optimization 】 Internal node and light client node support manual switching between main and test network by clicking to switch to the corresponding network.

Should they choose network type when the users change the node data by settings? And, does this directory show the upper directory that includes mainnet and testnet data?

2. 【Network settings optimization 】 Pop-up window interactions：Click to cancel ignoring alerts and still link internal network nodes.

Currently, if the user starts an external node that uses port 8114, do we need to start with another port and change the display of the internal network URL?

3. 【Network settings optimization 】 When no external network is added, a pop-up prompt directs the user to add a network to enable the external node.
   When external nodes have been added, a list of external nodes is displayed for the user to select, and the user can also choose to add new network nodes.

Should we only show the network that its URL equals the started ckb node URL?

4. Does the light client node also use these interactions? currently, the light client node can use an internal node.

@Danie0918

[Danie0918]

Should they choose network type when the users change the node data by settings? And, does this directory show the upper directory that includes mainnet and testnet data?

The data of different network types of the same node are under the same path by default, however, users can change it manually and change the path in relation to the network type.

Currently, if the user starts an external node that uses port 8114, do we need to start with another port and change the display of the internal network URL?

Yes, need to use a different port and modify the front-end presentation.

Should we only show the network that its URL equals the started ckb node URL?

I'm not so sure about that. Do you have any ideas? @Keith-CY

4. Does the light client node also use these interactions? currently, the light client node can use an internal node.

Yes, light client node is also internal node.

[Keith-CY]

Should we only show the network that its URL equals the started ckb node URL?

I'm not so sure about that. Do you have any ideas? @Keith-CY

Not bad, when there isn't a network matches the URL, users will be directed to add one

[Kirl70]

Design Draft:
https://www.figma.com/file/6XNoimRDbFTTNm016rbIdU/Magickbase?type=design&node-id=28088%3A7597&mode=design&t=yomXbxOwCP9AVfOJ-1

[yanguoyu]

1. Saving the ckb node path as ckbDataPath_${nodeType}, and saving the light client data path as testnetLightDataPath_${nodeType}
2. Only start ckb or light client with monitor when the selected node is readonly. If an external node is running, send a message to UI process and notify users.
3. Add retry start ckb node with other port.

[yanguoyu]

nervosnetwork/neuron#2921

[Keith-CY]

The cancel button in the dialog is confusing, it launches the internal node instead of an action of cancel e.g. do nothing until users select another network option.

I would suggest using a clear label, e.g. connect to the internal node, or launch the internal node

[Keith-CY]

The cancel button in the dialog is confusing, it launches the internal node instead of an action of cancel e.g. do nothing until users select another network option.

I would suggest using a clear label, e.g. connect to the internal node, or launch the internal node

cc @Danie0918

[Danie0918]

The cancel button in the dialog is confusing, it launches the internal node instead of an action of cancel e.g. do nothing until users select another network option.

I would suggest using a clear label, e.g. connect to the internal node, or launch the internal node

1. Change 'Cancel' to 'Ignore external node'.
2. Remove option prioritization and keep leveling.

@yanguoyu @Kirl70

[Kirl70]

The cancel button in the dialog is confusing, it launches the internal node instead of an action of cancel e.g. do nothing until users select another network option.
I would suggest using a clear label, e.g. connect to the internal node, or launch the internal node

1. Change 'Cancel' to 'Ignore external node'.
2. Remove option prioritization and keep leveling.

@yanguoyu @Kirl70

The design draft has been adjusted.

[Keith-CY]

Demonstration on YouTube: https://www.youtube.com/watch?v=Vl2LGRNqnvk