Skip to content

update invariants to improve wording#2088

Open
RensR wants to merge 1 commit into
mainfrom
fix-invariants
Open

update invariants to improve wording#2088
RensR wants to merge 1 commit into
mainfrom
fix-invariants

Conversation

@RensR
Copy link
Copy Markdown
Collaborator

@RensR RensR commented May 21, 2026

Improves the wording to properly convey that the default pool does not validate finality config on dest, but pools must get enough params to do this validation if they wanted to.

@RensR RensR marked this pull request as ready for review May 21, 2026 11:33
@RensR RensR requested a review from a team as a code owner May 21, 2026 11:33
Copilot AI review requested due to automatic review settings May 21, 2026 11:33
@github-actions
Copy link
Copy Markdown

Metric fix-invariants main
Coverage 70.0% 69.7%

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the invariants documentation around pool finality handling to more precisely describe that the default TokenPool implementation does not re-validate requested finality on the destination chain (inbound releaseOrMint), while still requiring the interface to carry enough information for alternative pool implementations to enforce destination-side policy if desired.

Changes:

  • Expands INV-POOL-8 to clarify where allowed-finality is enforced and how inbound finality is used by the default pool.
  • Renames and rewrites the pool-finality enforcement section in FINALITY_INVARIANTS.md to describe optional inbound enforcement by pool implementations.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
chains/evm/contracts/invariants/TOKEN_POOL_INVARIANTS.md Clarifies V2 pool interface behavior and default inbound finality handling.
chains/evm/contracts/invariants/FINALITY_INVARIANTS.md Refactors the “pool enforcement” invariant wording to reflect default vs optional inbound enforcement.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread chains/evm/contracts/invariants/TOKEN_POOL_INVARIANTS.md
Comment thread chains/evm/contracts/invariants/FINALITY_INVARIANTS.md
@RensR RensR enabled auto-merge May 21, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants