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

v0.5 nodes stuck after high priority alert. #271

Closed
sandakersmann opened this Issue Dec 10, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@sandakersmann

This comment has been minimized.

Copy link
Author

sandakersmann commented Dec 10, 2017

@hrobeers @peerchemist @sunnyking @sigmike Can you guys take a look at this?

@Nagalim

This comment has been minimized.

Copy link
Member

Nagalim commented Dec 10, 2017

Sunny sent a priority 2500 alert and it caused v0.5 clients to drop into safe mode. He has now replaced it with a priority 900 alert, so everything should work now.

@peerchemist

This comment has been minimized.

Copy link
Member

peerchemist commented Dec 10, 2017

resolved.

@hrobeers

This comment has been minimized.

Copy link

hrobeers commented Dec 11, 2017

Was it a hard fork?
It seems the 0.5 clients just got stuck, no fork at all.

I'll update the title for clarity.

@hrobeers hrobeers changed the title The soft fork just turned into a hard fork v0.5 nodes stuck after high priority alert. Dec 11, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment