LayerZero Labs Public-Source Startup Diligence Report
Advance only to confirmatory diligence if the investment thesis depends on LayerZero becoming a default interoperability layer for applications, asset issuers and institutions. The thesis requires private proof that usage converts to durable revenue, customers accept multi-DVN best practices, security remediation is complete, ZRO governance is legally robust and valuation is justified by fundamentals rather than crypto-cycle multiples.
LayerZero Labs Public-Source Startup Diligence Report
LayerZero Labs is a highly visible interoperability unicorn with credible public evidence for valuation, institutional fundraising, open-source technical artifacts, developer documentation, a broad supported-chain footprint, named ecosystem users/partners and an active security bounty. Public evidence is insufficient for an investment decision because company financials, cap table, token allocations, customer revenue, material contracts, insurance, governance controls and counsel searches are not public. The 2026 KelpDAO exploit materially elevates security, liveness and reputation diligence needs.
The KelpDAO incident disclosed an approximately $290M exploit tied to a 1-of-1 DVN configuration and RPC spoofing affecting the LayerZero Labs DVN; multi-DVN adoption and remediation must be verified.
Diligence request: Conduct independent forensic/security review, verify all remediation and require customer migration to diversified DVN configurations.
No public audited financials, management accounts, revenue by product/customer, cap table, debt schedule or material contracts were available.
Diligence request: Require full financial/cap-table/customer data room before underwriting.
$3B public valuation is well evidenced historically but may be sensitive to crypto volumes, token prices, security incidents and macro financing conditions.
Diligence request: Re-underwrite valuation using current revenue, retention, incident-adjusted pipeline and comparable multiples.
ZRO fee switch, buybacks, governance, bridging and cross-chain value-transfer products create securities/commodities, sanctions and money-transmission review needs.
Diligence request: Obtain counsel memos, token allocation/treasury controls, sanctions/money-transmission analysis and governance risk assessment.
LayerZero docs state every default Executor across every pathway in every preset network configuration is operated by LayerZero Labs, creating liveness/censorship concentration.
Diligence request: Verify third-party/custom Executor adoption, fallback procedures, monitoring and customer communications.
Named apps, TVL, volume, users and partner logos do not prove paid customers, retention, ARR or concentration.
Diligence request: Request top-customer schedule, contracts, revenue by customer, pipeline and references.
Public sources verify CEO/co-founder and open roles but not full org, board, compensation, turnover, controls or succession.
Diligence request: Request org chart, leadership bios, compensation, turnover and board/governance documents.
Devtools README warns beta status and possible backwards-incompatible changes; public artifacts require code-quality and release-process review.
Diligence request: Review release process, semver policy, issue backlog, audits and customer-impact controls.
Public evidence verifies unicorn financing history, but financial statements, projections, cap table and revenue detail are not public.
not publicly verifiable confidence: high
No audited statements, management reports, sales breakdown, backlog or AR aging were located in public sources.
| item | public status | diligence implication |
|---|---|---|
| Audited annual and quarterly statements | Not located | Cannot assess revenue, margins, cash burn, liabilities or going-concern risk. |
| Revenue by product, customer, channel and geography | Not located | Adoption metrics cannot be converted into revenue quality or concentration. |
| Backlog and accounts receivable aging | Not located | Working-capital and collection risk are not assessable. |
| Tax, accounting policy and revenue recognition | Not located | Token, fee and cross-chain service accounting remain high-priority gaps. |
Public-source absence is not proof the information does not exist privately.
not publicly verifiable confidence: high
Public sources discuss growth markets such as gaming, APAC, asset issuance and institutional products, but no quantified financial projections are public.
not publicly verifiable confidence: high
Public financing sources identify several investors and the Foundation page identifies ZRO activity, but equity ownership, token allocations, debt and dilutive securities are not public.
partially verified confidence: high
Public records support a $135M 2022 round, a $120M 2023 Series B and $3B valuation, but tax positions and accounting policies are not public.
| date or period | event | amount or valuation | public investors or notes |
|---|---|---|---|
| 2022-03-30 | CB Insights unicorn tracker entry | $3B valuation signal; joined unicorn list 3/30/2022 | Andreessen Horowitz, FTX Ventures, Tiger Global Management listed by CB Insights. |
| 2022-03 | Public $135M round | $135M round at $1B valuation | BusinessWire release reported co-leads and strategic investors. |
| 2023-04-04 | Series B | $120M; valuation increased to $3B; over $250M raised to date | TechCrunch reported 33 investors including a16z crypto, Circle Ventures, Sequoia, OpenSea, Samsung Next, Christie's and BOND. |
Public valuations should be reconciled to preferred terms and fully diluted ownership.
Financing amount and valuation are different metrics but both shown in USD millions.
LayerZero's product evidence is strong for protocol design and developer tooling, with material diligence needed on reliability, pricing, customer economics and configuration risk.
verified confidence: high
The public product set includes omnichain messaging, Endpoint/MessageLib infrastructure, OApps/OFTs, Stargate, Nexus/lzAssets, DVNs, Executors and developer tooling.
| product or component | public description | diligence focus |
|---|---|---|
| LayerZero protocol | Omnichain messaging protocol for moving information between blockchains. | Production usage, fees, uptime, incidents and customer contracts. |
| Interoperability infrastructure | 160+ supported blockchains; endpoints send and receive data between chains. | Active endpoint count, production pathways and support obligations. |
| OApp / OFT / ONFT standards | Developer standards for applications and omnichain tokens. | Developer adoption, security reviews and revenue model. |
| Stargate and Nexus/lzAssets | Value-transfer and generalized asset-issuance offerings. | Commercial terms, issuer obligations and regulatory classification. |
Product descriptions are public-source and should be reconciled with internal SKU and revenue data.
| layer | public role | control or risk |
|---|---|---|
| Endpoint | Immutable, permissionless protocol interface deployed on each chain. | Endpoint immutability reduces upgrade risk but makes deployment correctness critical. |
| Message Libraries | Configurable onchain rulesets for verification and delivery. | Library selection and upgrades can affect app-level security. |
| DVNs | Independent verification services with X-of-Y-of-N security stacks. | Single-DVN configurations create a verifier concentration risk. |
| Executors | Deliver verified messages and can be run by anyone, but docs identify default concentration. | Default LayerZero Labs Executor can be a liveness/censorship concentration point. |
| Pricing model | Source gas, security stack fees, executor fees and destination gas purchase. | Cross-chain fee volatility and worker compensation affect UX and margins. |
Control design should be independently reviewed by protocol security specialists.
Simplified from public docs; not a complete production architecture.
LayerZero has visible ecosystem adoption signals, but customer contracts, revenue concentration, retention and supplier economics are not public.
partially verified confidence: medium
Public sources name DEX use cases and asset/institutional partner logos, but not a top-15 customer list or revenue by application.
| signal type | public signal | revenue proof status |
|---|---|---|
| DEX application use | PancakeSwap, SushiSwap, Trader Joe and Uniswap named by TechCrunch. | Does not prove paid revenue or contract terms. |
| TVL / volume / users | 2023 article reported company-claimed $7B TVL, $6B volume and hundreds of thousands of unique users. | Usage proxy only; not revenue. |
| Partner logos / asset issuers | Interop page lists BitGo, Bridge.xyz, Centrifuge, Ethena, Google, Kraken, Ondo, Paxos, PayPal, Tether and Wyoming Stable Token Commission. | Relationship signal; not contract economics. |
Customer references and contracts are required to validate economics.
Values are from 2023 reporting and may be outdated.
partially verified confidence: medium
Strategic relationships are visible through partner logos, Foundation activity, DVN/Executor architecture and integrations, but revenue contribution and agreement terms are not public.
| area | public evidence | missing private evidence |
|---|---|---|
| Top customers | Named applications and partner logos. | Customer list, ARR/revenue, contract status and renewal history. |
| Strategic relationships | Asset issuance, institutional and chain integration messaging. | Agreements, revenue share, exclusivity and termination rights. |
| Suppliers | DVN/Executor/RPC dependencies described in docs and incident statement. | Supplier list, spend, SLAs, security attestations and redundancy plans. |
Public strategic-partner language should not be treated as paid contractual evidence.
not publicly verifiable confidence: high
No public revenue by customer or customers contributing 5% or more of revenue were identified.
inconclusive confidence: low
No complete public schedule of severed relationships was located; the KelpDAO incident implies customer remediation and migration follow-up is necessary.
partially verified confidence: medium
Public docs identify DVNs, Executors and RPC infrastructure as operational dependencies, but supplier agreements and spend are not public.
LayerZero competes in cross-chain messaging, token transfer, asset issuance and interoperability infrastructure, with differentiation based on configurability, chain breadth and developer tooling.
partially verified confidence: medium
Public evidence supports a differentiated architecture but does not quantify market share, pricing power or win/loss versus Wormhole, Axelar, Chainlink CCIP, native bridges or exchange-led rails.
| segment | layerzero positioning | competitive alternatives |
|---|---|---|
| Cross-chain messaging | Permissionless omnichain messaging with endpoint and message-library architecture. | Wormhole, Axelar, Chainlink CCIP, native bridge/messaging stacks. |
| Value transfer | OFT/Stargate value-transfer products across supported blockchains. | Liquidity bridges, exchange deposit rails, native asset bridges. |
| Asset issuance / tokenization | Nexus/lzAssets and institutional asset integrations. | Issuer-built multichain systems, custodians and tokenization platforms. |
| Verification and execution services | Modular DVNs and Executors. | Native verifier networks, light-client bridges, ZK-proof systems and managed relayers. |
Competitive alternatives are an analyst framing and require independent market interviews.
| basis | public evidence | diligence test |
|---|---|---|
| Chain breadth | 160+ supported blockchains claimed on Interoperability page. | Verify active endpoints, production pathways and usage by chain. |
| Configurable security | App-owned security stack and X-of-Y-of-N DVN model. | Review customer DVN configurations and multi-DVN migration. |
| Developer experience | Devtools repository with examples and packages. | Compare adoption, issue resolution, SDK stability and developer satisfaction. |
| Security program | $15M maximum Immunefi bounty and audit directories. | Review audit findings, bounty ledger, incident RCA and insurance. |
A differentiator can also be a risk if customers configure it poorly.
Competitor positions are analyst estimates using public product framing.
LayerZero distributes through docs, open-source tooling, ecosystem partnerships, asset-issuer integrations, foundation governance and business-development hiring; productivity metrics are not public.
partially verified confidence: medium
Public GTM strategy emphasizes developer adoption, asset issuers, institutional assets, geographic expansion and ecosystem governance.
| channel | public evidence | proof gap |
|---|---|---|
| Developer-led adoption | Docs, LayerZero-v2 and devtools repositories. | Developer activation, conversion and paid usage. |
| Asset issuers and institutions | Interoperability page and blog index emphasize institutional/asset issuance partnerships. | Contracted revenue and compliance requirements. |
| Ecosystem governance | Foundation page links fee-switch vote, ZRO buybacks and Bridge ZRO. | Governance participation, token treasury and legal structure. |
| Direct BD and solutions | Open BD, customer success and solutions-architect roles across New York, APAC and Vancouver. | Pipeline, quota and implementation capacity. |
Public GTM signals should be tied to CRM and revenue data.
Private CRM data is required to populate counts.
partially verified confidence: medium
Public major-customer evidence is limited to named integrations and partner logos; pipeline and relationship status are not public.
partially verified confidence: medium
Public evidence points to developer tooling, asset issuers, institutional partners, APAC business development and foundation-led ecosystem activity as primary demand channels.
| avenue | public signal | follow up metric |
|---|---|---|
| APAC expansion | Business development roles for Hong Kong and Japan. | APAC pipeline, bookings, local compliance plan and partner references. |
| Institutional asset integrations | Blog index references institutional assets, Canton, Centrifuge, Worldpay and tokenized assets. | Contracted issuer pipeline and compliance review status. |
| Foundation/token engagement | Fee-switch vote, buybacks and bridging ZRO. | Governance participation, treasury impact and token legal memo. |
Sales productivity cannot be assessed without private CRM and finance data.
not publicly verifiable confidence: high
Sales compensation, quota, cycle length and hiring plan are not public; careers postings only show hiring signals.
not publicly verifiable confidence: high
No public marketing budget or budget-vs-plan data was located.
R&D evidence is strong for public docs, repositories, audit directories and new product announcements, but staffing, costs, roadmap commitments and security backlog are private.
partially verified confidence: medium
Public artifacts show protocol, devtools, audit categories and engineering/security hiring, but R&D org chart and spend are not public.
| artifact | public contents | diligence use |
|---|---|---|
| LayerZero-v2 repository | Protocol contracts, OApp/OFT standards, MessageLib and build/test instructions. | Supports technical reality of core product; needs code review. |
| Devtools repository | Examples, packages, CLI/devtools and beta warning. | Supports developer strategy and identifies release-stability risk. |
| Audits repository | Audit directories for Endpoint V2, DVN, OApp, OFT, ONFT, ZRO, lzRead and related components. | Supports visible security program; requires full findings/remediation review. |
| Immunefi program | Smart-contract critical rewards up to $15M, KYC and OFAC screening requirements. | Supports bounty program but also indicates high value-at-risk. |
Public artifacts do not replace security due diligence.
Artifact count is not code-quality proof.
partially verified confidence: medium
Public pipeline signals include Nexus/lzAssets, lzRead, Zero, institutional asset integrations and DVN/payment products, but delivery timing, cost and revenue commitments are not public.
| pipeline item | signal | key risk |
|---|---|---|
| Nexus / asset issuance | Interoperability page describes Nexus for issuing, moving and redeeming tokenized assets across chains. | Regulatory, issuer-contract and custody/controls complexity. |
| lzRead and OApp patterns | Docs/repositories list omnichain queries and application standards. | Reliability, data integrity and developer adoption. |
| Zero and institutional assets | Blog index lists Zero technical papers and institutional asset announcements. | Product scope expansion may dilute focus and increase security/compliance burden. |
Pipeline evidence is public marketing/documentation, not committed revenue.
Bryan Pellegrino is publicly identified as CEO/co-founder and careers pages show hiring needs, but complete management biographies, org chart, compensation and turnover are not public.
partially verified confidence: medium
Public sources identify at least the CEO/co-founder and open functions, but not a complete org chart.
| person or group | public evidence | diligence gap |
|---|---|---|
| Bryan Pellegrino | TechCrunch identifies him as CEO and co-founder and quotes him on product/funding/security. | Employment agreement, background checks, ownership, board role and succession plan. |
| Finance/control functions | Careers page lists Assistant Controller and Controller roles. | Current finance maturity, audit readiness and internal controls. |
| Engineering/security functions | Careers page lists backend, cryptographer, frontend, protocol and systems engineering roles. | Security staffing, on-call coverage and incident-response ownership. |
| GTM/customer functions | Careers page lists BD, customer success, solutions architecture and institutional marketing roles. | Sales productivity, quota capacity and customer implementation coverage. |
Complete management team and board data require company materials.
This is not a complete org chart.
partially verified confidence: medium
Careers page shows open roles in Vancouver, New York and APAC, but total headcount history and projections are not public.
| function | example roles | locations | diligence readthrough |
|---|---|---|---|
| Finance | Assistant Controller; Controller. | Vancouver, BC or New York City. | Assess audit readiness and control maturity. |
| Engineering | Backend, Cryptographer, Frontend, Protocol and Systems Engineer. | Vancouver, BC. | Assess roadmap staffing and security coverage. |
| GTM / customer | BD Lead Hong Kong, BD Lead Japan, Customer Success Manager, Solutions Architect Lead, Staff Solutions Architect. | APAC, Vancouver, New York. | Assess international pipeline and implementation capacity. |
| Product / operations / recruiting / marketing | Product Manager, Data Analyst, Technical Recruiter, Vertical Marketing Manager - Institutions. | Vancouver, New York. | Assess execution capacity and institutional GTM priority. |
Open roles do not equal total headcount or attrition.
partially verified confidence: medium
Public-source review verified Bryan Pellegrino as CEO/co-founder through TechCrunch; full senior team biographies require company confirmation.
not publicly verifiable confidence: high
Employment agreements, executive compensation and benefit plans are not public.
not publicly verifiable confidence: high
No public equity incentive or token incentive plan details were located.
inconclusive confidence: low
No public employee-relations problem schedule was identified.
not publicly verifiable confidence: high
Personnel turnover data for the past two years is not public.
Public legal evidence includes an FTX Recovery Trust adversary docket and a material 2026 KelpDAO incident statement; counsel-led litigation, regulatory, IP, contract and insurance review remains essential.
verified confidence: medium
CourtListener search identifies FTX Recovery Trust v. LayerZero Labs Ltd., Bankr. D. Del. docket 23-50492, filed 2023-09-08 and terminated 2025-02-18.
| matter | public status | diligence action |
|---|---|---|
| FTX Recovery Trust v. LayerZero Labs Ltd. | CourtListener identifies Bankr. D. Del. docket 23-50492, filed 2023-09-08 and terminated 2025-02-18. | Obtain pleadings, settlement/dismissal documents, releases and counsel opinion. |
| KelpDAO exploit and law-enforcement contact | LayerZero statement says KelpDAO was exploited for approximately $290M and LayerZero is cooperating with law enforcement. | Obtain incident RCA, remediation, reserves, insurance and communications with agencies. |
| ZRO governance, fee switch and buybacks | Foundation page links fee-switch vote, ZRO buybacks, governance and Bridge ZRO. | Obtain token legal memos, treasury controls and governance risk assessment. |
| Bounty KYC/OFAC and payouts | Immunefi page says KYC and OFAC screening are required and payouts are handled by LayerZero Labs. | Review sanctions compliance, bounty liabilities and payout controls. |
This is not a legal opinion.
Heatmap reflects public-source diligence, not legal or investment advice.
inconclusive confidence: low
No company-initiated lawsuit schedule was located in public sources reviewed.
inconclusive confidence: low
As a software/protocol business, environmental and physical safety liabilities were not visible in public sources; workplace and remote-work policies require company review.
partially verified confidence: medium
Public GitHub repositories and documentation evidence software/IP assets; patents, trademarks, third-party licenses and assignment chain were not counsel-verified.
| diligence area | public signal | missing evidence |
|---|---|---|
| Software IP and OSS | LayerZero-v2 and devtools repositories are public. | License scan, contributor assignments, dependency audit and patent/trademark portfolio. |
| Material contracts | Partner and product pages name ecosystem relationships. | Customer, issuer, DVN, Executor, supplier, investor and foundation/company agreements. |
| Insurance | Security incident and high-value bounty make coverage material. | Cyber, D&O, E&O, crime and digital-asset policy schedules, exclusions and claims. |
Counsel-led review is required before relying on any IP or contract conclusions.
not publicly verifiable confidence: high
Insurance coverage, cyber limits, D&O coverage and incident reserves are not public.
not publicly verifiable confidence: high
Customer, supplier, foundation/company, token, investor, DVN/Executor and asset-issuer contracts are not public.
inconclusive confidence: low
No counsel-certified regulatory-agency problem search was performed; ZRO, cross-chain value transfer, sanctions screening and the KelpDAO incident require focused legal review.
| ID | Claim | Status | Sources |
|---|---|---|---|
| EC-001 | CB Insights lists LayerZero Labs as a $3B unicorn with United States / New York and Enterprise Tech metadata. | verified high | SRC-001 |
| EC-002 | A 2022 public financing release reported LayerZero Labs raised $135M at a $1B valuation. | verified medium | SRC-002 |
| EC-003 | TechCrunch reported a $120M Series B at a $3B valuation and over $250M raised to date. | verified high | SRC-003 |
| EC-004 | LayerZero describes itself as an omnichain messaging protocol and permissionless open framework for moving information between blockchains. | verified high | SRC-005 |
| EC-005 | LayerZero's Interoperability page claims 160+ supported blockchains and describes infrastructure, value-transfer and asset-issuance products. | partially verified medium | SRC-007 |
| EC-006 | LayerZero V2 separates application, endpoint, message library, DVN and Executor responsibilities. | verified high | SRC-006 |
| EC-007 | LayerZero security is application-configurable using DVNs and X-of-Y-of-N thresholds. | verified high | SRC-009 |
| EC-008 | LayerZero Executors are permissionless, but docs identify default Executor concentration at LayerZero Labs. | verified high | SRC-010 |
| EC-009 | LayerZero's transaction pricing includes source gas, DVN/security stack fees, Executor fees and destination gas purchase. | verified high | SRC-008 |
| EC-010 | The LayerZero-v2 GitHub repository documents the open-source protocol, contract standards, MessageLibs, DVNs and Executors. | verified high | SRC-011 |
| EC-011 | The devtools repository contains developer examples and packages but is marked beta with potential breaking changes. | verified high | SRC-012 |
| EC-012 | TechCrunch reported 2023 usage/adoption proxies including DEX applications, $7B TVL, $6B volume and hundreds of thousands of users. | partially verified medium | SRC-003 |
| EC-013 | LayerZero's Interoperability page displays named partner/asset-issuer logos and use cases. | partially verified medium | SRC-007 |
| EC-014 | Immunefi lists a LayerZero bug bounty with smart-contract critical rewards up to $15M and KYC/OFAC requirements. | verified high | SRC-013 |
| EC-015 | TechCrunch reported in May 2023 that LayerZero and Immunefi launched a $15M bounty and that the protocol had not had a security exploit or hack since inception as of that article. | partially verified medium | SRC-014 |
| EC-016 | LayerZero's 2026 KelpDAO incident statement reports an approximately $290M exploit tied to KelpDAO's single-DVN setup and RPC spoofing affecting the LayerZero Labs DVN. | partially verified medium | SRC-020 |
| EC-017 | CourtListener search identifies FTX Recovery Trust v. LayerZero Labs Ltd., Bankr. D. Del. docket 23-50492, filed 2023-09-08 and terminated 2025-02-18. | verified medium | SRC-015 |
| EC-018 | The LayerZero Foundation page links ZRO buybacks, governance, fee-switch voting and Bridge ZRO. | verified medium | SRC-016 |
| EC-019 | The careers page shows open roles across finance, engineering, GTM, product, recruiting and marketing, with Vancouver, New York and APAC locations. | verified medium | SRC-017 |
| EC-020 | Key private-company diligence materials were not available in public sources reviewed. | not publicly verifiable high | SRC-001SRC-003SRC-004SRC-007SRC-016SRC-017 |
| EC-021 | LayerZero maintains a public Audits repository with audit directories for multiple protocol/product areas. | verified medium | SRC-018 |
| EC-022 | LayerZero OFT documentation explains token movement via burn/mint or adapter lock/unlock patterns. | verified high | SRC-019 |
| EC-023 | LayerZero blog index shows ongoing pipeline around Zero, institutional assets, Canton, Centrifuge, Worldpay and tokenized assets. | partially verified medium | SRC-021 |
| EC-024 | LayerZero's transaction and bounty compliance surfaces include sanctions/KYC and cross-chain value movement risk. | partially verified medium | SRC-008SRC-013SRC-019 |
| EC-025 | TechCrunch identifies Bryan Pellegrino as LayerZero Labs CEO and co-founder. | verified high | SRC-003SRC-014 |
This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.