This repository was archived by the owner on May 19, 2026. It is now read-only.
Update tlbc image to release27370 - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm not sure how you build the images and whether the node image node: image: "node.trustlines.dnp.dappnode.eth:1.0.0" - should maybe be changed to 1.0.1? But this must be something in your release pipline and since there is no documentation in the repo I've left it like this.
Note that I change $PARITY_ARGS to $CLIENT_ARGS as we are now using OE and not parity.
Also important
We are currently experiencing a fork and validators end up on the wrong chain. Even after updating their chainspec file.
It looks like a bug/feature of OpenEtehreum. Since validators didn't receive the correct chainspec they were on a different chain, unfortunately even after applying the correct chainspec OE seems to think that they are on the correct chain, as the chains is maybe the longest.
What helped to get those unstuck nodes on the correct chain was to drop the open ethereum database and let the nodes resync. Then they end up on the correct chain.