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.

Sign up for GitHub

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

Jump to bottom

Why a malicious(might unintentionally) bad block can panic other nodes' tokio-runtime-worker? #483

Closed
hackfisher opened this issue Jul 29, 2020 · 0 comments
Closed

Why a malicious(might unintentionally) bad block can panic other nodes' tokio-runtime-worker? #483

hackfisher opened this issue Jul 29, 2020 · 0 comments
Assignees
@AurevoirXavier
Labels
U-Question [Uncategorized] Further information/discussion is requested

Comments

@hackfisher
Copy link
Contributor

hackfisher commented Jul 29, 2020 •
edited
Loading

Like this: #481

Even though this is a bug caused by non determinism, but how this bad block pass through the pre-validation before importing blocks, does pre-validation use wasm execution or there is no pre-validation?
@hackfisher hackfisher changed the title Why some bad block can panic other nodes' tokio-runtime-worker? Why a malicious(might unintentionally) bad block can panic other nodes' tokio-runtime-worker? Jul 29, 2020
@hackfisher hackfisher added the U-Question [Uncategorized] Further information/discussion is requested label Jul 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AurevoirXavier AurevoirXavier

Labels
U-Question [Uncategorized] Further information/discussion is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hackfisher @AurevoirXavier