LayerZero V2: control-plane safety record
3 indexed control-plane surfaces for LayerZero V2, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x1a44076050125825900e736c501f859c50fE728c, 0xbB2Ea70C9E858123480642Cf96acbcCE1372dCe1.
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: layerzero-v2-endpoint-immutable-s25: EndpointV2 0x1a44076050125825900e736c501f859c50fE728c (Ethereum; Sourcify match): EIP-1967 implementation slot = 0x0 (not a proxy)
- Timelock floor
- Not determined · No enforced admin delay in the published records
- Signer quorum
- Not determined · No signer quorum in the published records
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Strong · Chain matches or is stronger than the documentation
Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.
Check it live (free)
The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x1a44076050125825900e736c501f859c50fE728c"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x1a44076050125825900e736c501f859c50fE728c"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x1a44076050125825900e736c501f859c50fE728c"})EndpointV2: not a proxy; its code cannot be replaced
Observed onchain. EndpointV2 0x1a44076050125825900e736c501f859c50fE728c (Ethereum; Sourcify match): EIP-1967 implementation slot = 0x0 (not a proxy); the Base endpoint at the same address is also not a proxy.
Documented. docs.layerzero.network (endpoint): 'The LayerZero Endpoint is the immutable, permissionless protocol entrypoint for sending and receiving omnichain messages.' / 'The LayerZero Endpoint is the single, immutable entry and exit point for cross‑chain messaging, built on five core modules:'
cast storage 0x1a44076050125825900e736c501f859c50fE728c \ 0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Endpoint owner: a 5-of-9 LayerZero multisig that sets default libraries
Observed onchain. EndpointV2 0x1a44076050125825900e736c501f859c50fE728c: owner() = OneSig 0xBe010A7e3686FdF65E93344ab664D065A0B02478 (threshold() = 5 of totalSigners() = 9), which registers message libraries and sets default libraries and configurations without a timelock; the Base endpoint owner is OneSig 0xa0392d116D71ED3b75086194aBa6De3CD1e39B7E (5 of 9, the same signers).
Documented. docs.layerzero.network (defaults): 'You should always set your DVN configuration explicitly. Defaults are placeholder configurations — they may be Dead DVNs that prevent message delivery, may include only a single DVN, and may change without notice.' / 'This default configuration can vary per channel, changing the placeholder block confirmations, the X‑of‑Y‑of‑N thresholds for verification, the Executor, and the message libraries.' / 'Once an application defines its channel’s X‑of‑Y‑of‑N security settings, those parameters are enforced at the protocol level indefinitely. Only the application delegate can update these configurations. There is no governance, upgrade mechanism, or external actor that can alter or disable a channel’s configuration once set, guaranteeing that security guarantees persist without relying on LayerZero.'
cast call 0x1a44076050125825900e736c501f859c50fE728c \ "owner()" \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Ethereum to Base default pathway: send and receive require the same 4 DVNs
Observed onchain. SendUln302 0xbB2Ea70C9E858123480642Cf96acbcCE1372dCe1 default to Base (eid 30184): 15 confirmations, 4 required DVNs (0x380275805876Ff19055EA900CDb2B46a94ecF20D, 0x589dEDbD617e0CBcB916A9223F4d1300c294236b, 0xa4fE5A5B9A846458a70Cd0748228aED3bF65c2cd, 0xa59BA433ac34D2927232918Ef5B2eaAfcF130BA5), 0 optional; Base ReceiveUln302 0xc70AB6f32772f59fBfc23889Caf4Ba3376C84bAf default from Ethereum (eid 30101) at Base block #58641783: 15 confirmations, 4 required DVNs (0x554833698Ae0FB22ECC90B01222903fD62CA4B47, 0x9e059a54699a285714207b43B055483E78FAac25, 0xa7b5189bcA84Cd304D8553977c7C614329750d99, 0xcd37CA043f8479064e10635020c65FfC005d36f6).
Documented. docs.layerzero.network (security stack): 'For a configuration to be considered valid, the Send Library configurations on Chain A must match the Receive Library configurations on Chain B.'
cast call 0xbB2Ea70C9E858123480642Cf96acbcCE1372dCe1 \ "getAppUlnConfig(address,uint32)" 0x0000000000000000000000000000000000000000 0x75e8 \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Embed Live Control-Plane Badge
Show LayerZero V2's Base-EAS-attested Aligned control-plane status in a README, docs page or forum post. The badge links back to this record.
[](https://pacta.wtf/protocols/layerzero-v2/)
<a href="https://pacta.wtf/protocols/layerzero-v2/"><img src="https://pacta.wtf/badges/layerzero-v2.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/layerzero-v2.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/layerzero-v2.svg (5-minute cache).
Operating LayerZero V2? Add Continuous Monitoring
Continuous Monitoring ($1,500 USDC / month) re-checks your control plane after governance proposals, signer rotations and timelock upgrades, and refreshes the dossier and attestation. It does not buy a status: the result can still be Delta whenever docs and chain diverge.