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

BCH: Failing chipnet sync stops the mainnet sync #69

Open
mainnet-pat opened this issue Jan 10, 2025 · 0 comments
Open

BCH: Failing chipnet sync stops the mainnet sync #69

mainnet-pat opened this issue Jan 10, 2025 · 0 comments

Comments

@mainnet-pat
Copy link

I have a chaingraph instance which tracks two networks: BCH chipnet and mainnet. Recently the p2p enpoint I have chosen some 1.5 years ago randomly turned out to belong to uname who took it down (temporarily?) because of excessive traffic, it became unresponsibele and many errors were to seen in console. All okay but mainnet sync got stalling because of this and my iinstance got out of sync for 2 days until noticed by consumers. As soon as I have switched my chipnet endpoint to communicate with other well-available peer, both chipnet nodes and mainnet nodes started to catch up. Please take a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant