elements: require 23.3.1 on Liquid#447
Merged
YusukeShimizu merged 2 commits intoJun 19, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Liquid mainnet has activated the ELIP 203 hard fork, which means older Elements nodes cannot reliably follow the post-fork chain. PeerSwap's existing operator guidance still allowed an older Elements release, and an outdated mainnet backend could leave users with unclear sync or swap failures instead of a direct explanation.
This updates the Liquid operator guidance for Elements and LWK-backed setups and adds a fail-fast startup check for Elements RPC on Liquid mainnet when the connected node is older than Elements 23.3.1. The swap protocol, public RPC surface, config schema, and non-mainnet behavior are unchanged.