Make a more informed choice.

Compare what projects do, what’s available, and the evidence behind each profile. Select up to three.

CompareAcross ↗thirdweb ↗LayerZero ↗
PurposeAcross has a documented Arc integration relationship. Available routes, assets and production availability need to be confirmed from the current bridge interface and project documentation.thirdweb appears in Arc’s account-abstraction and data-indexer documentation. Its toolkit spans wallet onboarding, smart accounts and blockchain data. Select the smallest set of products needed for the application and test their Arc network settings independently.LayerZero builds technology that makes decentralization possible, scalable, and inevitable. Listed by Arc; a specific production deployment is not established by the directory.
Best suited toRead the profile and provider documentation for fit.
  • SDK-based application development
Read the profile and provider documentation for fit.
CategoryBridges & messagingDeveloper toolsBridges & messaging
AvailabilityTestnetNot establishedNot established
EvidenceTestnet demonstratedPlatform documentedDirectory only
Role on ArcMarch Arc integration refers to testnet; mainnet bridge route availability needs a fresh route check.Arc relationship documented by the linked primary reference; individual service availability is described separately.Listed by Arc; a specific production deployment is not established by the directory.
Access requirementsCheck provider termsCheck provider termsCheck provider terms
Watch pointsNo specific watch points recorded. Check the source material.
  • Managed wallets, data APIs and contracts have different permissions and operational dependencies.
No specific watch points recorded. Check the source material.
Reviewed2026-09-172026-09-242026-09-17
Sources3 sources ↗2 sources ↗1 sources ↗