Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is is possible to support to fork the data from mainnet to devnet chain? #284

Open
Daryl-L opened this issue May 27, 2023 · 2 comments
Open
Labels
question Further information is requested

Comments

@Daryl-L
Copy link
Contributor

Daryl-L commented May 27, 2023

After talking with acceptance team, they said that if it is possible to fork the data from mainnet to devnet, it is convenient for developer to build DApps base on the data or scripts from mainnet.

@Keith-CY Keith-CY added the question Further information is requested label May 27, 2023
@Keith-CY Keith-CY moved this to 🆕 New in CKB JS Backlog May 27, 2023
@Keith-CY
Copy link
Member

It's interesting, and has been supported from another perspective in Neuron.

In Neuron, settings => data => ckb node config & storage sets the directory of the node, and allows users to download a synced ckb node from the internet to boost synchronization.

image

Maybe we can expose the directory of devnet node and add a check if it's initialized. If yes, start synchronization directly. Otherwise, the workflow remains the same as before

@yanguoyu
Copy link
Contributor

fork the data from mainnet to devnet chain

Does it mean copy transactions from mainnet to devnet? Or start ckb node from others' data with the same network?

@Keith-CY Keith-CY moved this from 🆕 New to 📋 Backlog in CKB JS Backlog May 31, 2023
@Keith-CY Keith-CY moved this from 📋 Backlog to 🔖 Ready in CKB JS Backlog Jun 7, 2023
@Keith-CY Keith-CY moved this from 🔖 Ready to Hold on in CKB JS Backlog Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: Hold on
Development

No branches or pull requests

3 participants