🧹 simplify read examples

[St0rmBr3w]

No description provided.

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/view-pure-read/package.json pnpm-lock.yaml	⚠︎
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/view-pure-read/package.json pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What are unpopular packages?

This package is not very popular.

Unpopular packages may have less maintenance and contain other problems.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@layerzerolabs/[email protected]
• @SocketSecurity ignore npm/@layerzerolabs/[email protected]

[janjakubnanista]

Just some small stuff

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@layerzerolabs/[email protected]	None	+1	1.4 MB	layerzero-bot

View full report↗︎

Resolved

[ryandgoulding]

Fixed pnpm-lock.yaml. Running through CI pipeline.

[nazreen]

This PR is awesome. when can we have this in main ?

MIA

[shankars99]

not review but why doesnt OAppRead set self peer? in lzRead we always self peer dont we?

[St0rmBr3w]

OAppRead shouldn't override setPeer since than if you used it for just messaging you wouldn't be able to.

[shankars99]

fuzz here because a+b could overflow

[St0rmBr3w]

Think this is unnecessary since this is an example contract, there will likely be edge cases that cause a + b to overflow.