docs: add Chainlink CCIP partnership disclaimer to cross-chain tokens guide#906
Merged
Conversation
… guide Adds a top-of-page warning noting that the bridging architecture and recommendations describe the pre-CCIP setup, following the Lido DAO adoption of Chainlink CCIP as the official default cross-chain infrastructure for wstETH. Removes the previous NEC disclaimer, whose role is superseded by the Chainlink partnership.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the cross-chain tokens adoption guide to warn readers that the described bridging architecture reflects a pre-CCIP setup, in light of Lido’s strategic partnership with Chainlink and adoption of CCIP as the default cross-chain infrastructure for wstETH.
Changes:
- Replaced the previous NEC disclaimer with a new top-of-page warning about CCIP adoption and the guide being pre-CCIP.
- Added a link to the forum announcement describing the Chainlink CCIP partnership.
- Applied markdown whitespace normalization (tabs → spaces, list spacing).
Comments suppressed due to low confidence (1)
docs/token-guides/cross-chain-tokens-guide.md:349
- Same ambiguity here: the L2 bridge endpoint permissions reference
Emergency Brakes Multisig, but the notation defines separateEmergency Brakes L1 Multisig/Emergency Brakes L2 Multisig. It would be clearer to reference the L2-specific multisig in this section.
- Deposits pausable by
- `L2 Governance Executor`
- `Emergency Brakes Multisig`
- Deposits resumable by
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…e permissions - 'one-time disposable pauser contact' -> 'contract' - Replace ambiguous 'Emergency Brakes Multisig' with 'Emergency Brakes L1 Multisig' in the L1 Custom Bridge Endpoint section and with 'Emergency Brakes L2 Multisig' in the L2 Custom Bridge Endpoint and L2 Token Bridged sections, matching the notation defined above.
TheDZhon
requested changes
May 25, 2026
Contributor
TheDZhon
left a comment
TheDZhon
left a comment
There was a problem hiding this comment.
Almost there, thanks!
Just some factual clarity that worth ironing out 🙏
Co-authored-by: Eugene Mamin <TheDZhon@gmail.com>
TheDZhon
approved these changes
May 25, 2026
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
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.
Summary
docs/token-guides/cross-chain-tokens-guide.mdnoting that the bridging architecture and recommendations describe the pre-CCIP setup.The diff also includes whitespace normalization (tabs → spaces, blank lines before lists) applied automatically by the project linter when the file was saved.
Test plan