
With every passing day, the blockchain industry continues to become more mature and inch closer towards achieving the operational level comfort that today’s web2 world offers.
In this pursuit, we’re witnessing a period of massive experimentation in on-chain infrastructure design.
A natural trend observed in the EVM space is vertical growth through Rollups, Layer 2, and Layer 3 networks. The common goal of this design shift is to achieve scalability and, as a result, a higher degree of interoperability.
But as the web3 dev community continues to take bigger strides in achieving transactional interoperability, app-to-user, app-to-app, and user-to-user communication are still at nascent steps.
Push is working towards diminishing this divide between transactional and communication interoperability by building a robust, secure fabric that weaves multiple chains and services together by forming the “Universal Layer2 Of Communication”.
Fragmented Ecosystem
Web3 operates on a multitude of blockchains, each with its own protocols, standards, and its own unique set of rules. This creates independent and isolated silos of information, making it difficult for users, services and applications built on separate chains to interact and communicate with each other unanimously.
Push continues to form a communication blanket over the fragmented ecosystem and provide its communication services to multiple EVM and non-EVM based chains. At present, Push supports over 7 networks including:
- Ethereum
- Polyogn
- Polygon zkEVM
- Arbitrum
- Binance Smart Chain (BNB)
- Fuse
- Cyber
The Communicator contracts (Push Comm V2) serve as a middleware for listening to inbound communications and events from the Client Application’s smart contract. Thus, shouldering the responsibility of on-chain communication across contracts deployed on multiple chains (EVM and non-EVM).
Notifications can not always be triggered as a result of an on-chain event. Many notifications, especially the ones that are more inclined towards driving engagement can be considered off-chain. Push ensures that any frontend, service, backend or smart contract can easily send communication payloads across the diverse participants and devices ( App, Wallet, Extension, Frontends and more).
Data Availability (no communication DA layer)
Traditionally, Data Availability (DA) ensures that the data needed to validate a block is accessible to the majority of network participants. However, in the context of interoperable communications within Web3, we need a broader concept: “Communication DA”.
What's the problem? From an end user's perspective, app notifications and other forms of read-write communications (messaging, groupchats, videocalls) should be accessible regardless of the platform, service, hardware and underlying chain they use. Previously, there was no standardized middleware mechanism to link communication across platforms and chains.
Push solves this problem. Being an open network, Push enables any frontend, service, or backend to securely tap into the Push network and extract the necessary communication payloads in a platform-agnostic manner.
Simply put, your communication travels with your web3 identity: your wallet.

