Skip to content

chore: Update examples #1942

Open
fabianhug wants to merge 1 commit into
mainfrom
fabianhug/dvn-example-rework
Open

chore: Update examples #1942
fabianhug wants to merge 1 commit into
mainfrom
fabianhug/dvn-example-rework

Conversation

@fabianhug
Copy link
Copy Markdown

to require at least 2 DVNs for production OApps; added warnings and documentation links in config files and README.md files across multiple examples.

…s; added warnings and documentation links in config files and README.md files across multiple examples.
@fabianhug fabianhug requested a review from St0rmBr3w May 6, 2026 19:40
@cursor
Copy link
Copy Markdown

cursor Bot commented May 6, 2026

PR Summary

Medium Risk
Mostly documentation/config template changes, but several example layerzero.config.ts pathways now include a <SECONDARY_DVN> placeholder in requiredDVNs, which can break copy-paste wiring until replaced with a real provider.

Overview
Adds prominent production safety warnings across many example README.md files stating that OApps (including read OApps) must use at least two DVNs, with links to DVN provider addresses and the single-DVN migration guide.

Updates multiple example config files to reinforce this requirement: some add TODO comments near requiredDVNs, while others change pathway definitions from a single ['LayerZero Labs'] DVN to ['LayerZero Labs', '<SECONDARY_DVN>'] (and annotate that production confirmations are typically 15+).

Reviewed by Cursor Bugbot for commit ff25bbf. Bugbot is set up for automated code reviews on this repo. Configure here.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Reviewed by Cursor Bugbot for commit ff25bbf. Configure here.

Comment thread examples/oapp/layerzero.config.ts
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

🧪 E2E Test Status

E2E tests are non-blocking and validate real blockchain interactions. Failures may occur due to network issues, RPC rate limits, or external service downtime.

Test Runs (Newest First):

  • Run #6755 - Passed - 2026-05-06 19:47 (UTC)

@fabianhug
Copy link
Copy Markdown
Author

@St0rmBr3w please check the above & approve so we can close this

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.

1 participant