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

Bug: Pandora test network issues #53

Open
mxmar opened this issue Apr 14, 2021 · 1 comment
Open

Bug: Pandora test network issues #53

mxmar opened this issue Apr 14, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@mxmar
Copy link

mxmar commented Apr 14, 2021

System information

Geth version: Geth/v1.10.1-unstable/linux-amd64/go1.15.2
OS & Version: Linux
Commit hash : 6b77c3292673b86f4c8bd6dbe0a06d15886ffd6d

Expected behaviour

  1. Pandora network is progressing properly.

  2. Network configuration is done and deployed. We provided indexes for interop to make proper validations by own (different) keys.

Actual behaviour

  1. dev-pandora-2 stopped at block height Refactor epic/aura-consensus #27 - we must investigate why and solve it.

obraz

  1. Interop requires indexes because network is not working properly/not progressing properly. Validators are using the same keys to validate now.

Steps to reproduce the behaviour

  1. See http://catalyst.silesiacoin.com/ node states and check node logs.

  2. Provide interop without indexes.

Backtrace

none
@mxmar mxmar added the bug Something isn't working label Apr 14, 2021
@blazejkrzak
Copy link

For 4-node infrastructure it may be common to fork or stall for nodes. We need to have the possibility to resync a node and try to run it as validator after synchronization

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants