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

Update node-offline for N3 #2157

Closed
spencercorwin opened this issue Aug 30, 2020 · 1 comment
Closed

Update node-offline for N3 #2157

spencercorwin opened this issue Aug 30, 2020 · 1 comment
Labels
area/node Categorize issue or PR as node (@neo-one/node) related kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed.

Comments

@spencercorwin
Copy link
Collaborator

See if chain file sync changed

@spencercorwin spencercorwin added the area/node Categorize issue or PR as node (@neo-one/node) related label Aug 30, 2020
@spencercorwin spencercorwin changed the title Update node-offline Update node-offline for N3 Jun 15, 2021
@spencercorwin spencercorwin added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed. labels Jun 15, 2021
@spencercorwin
Copy link
Collaborator Author

Chainfile sync and dump seems to work. Used it while testing our node against a local Neo N3 node. Was able to dump N1 data and sync N1 as well as Neo C# node from it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/node Categorize issue or PR as node (@neo-one/node) related kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed.
Projects
None yet
Development

No branches or pull requests

1 participant