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

stop and restart a private POS cluster #14165

Open
garyng2000 opened this issue Jun 28, 2024 · 0 comments
Open

stop and restart a private POS cluster #14165

garyng2000 opened this issue Jun 28, 2024 · 0 comments
Labels
Bug Something isn't working custom devnet custom chains

Comments

@garyng2000
Copy link

Describe the bug

following this guide https://geth.ethereum.org/docs/fundamentals/kurtosis, I can start a local POS cluster in docker and was able to extract the genesis information from it. But if I use the same information to start a new cluster, it seems to never work as the block in a POS network is fixed interval. so if the timestamp is X for block 0 and I start the cluster at X + T, won't it consider those block in between is missing and try to get from other peers ? and in this case always fail ?

Has this worked before in a previous version?

noop

🔬 Minimal Reproduction

No response

Error

No response

Platform(s)

No response

What version of Prysm are you running? (Which release)

No response

Anything else relevant (validator index / public key)?

No response

@garyng2000 garyng2000 added the Bug Something isn't working label Jun 28, 2024
@james-prysm james-prysm added the custom devnet custom chains label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working custom devnet custom chains
Projects
None yet
Development

No branches or pull requests

2 participants