Hello Push Protocol Community!

We’re excited to share some groundbreaking news with you all: Pre-PIP #3 is here, bringing the highly anticipated Cross Chain Request (CCR) feature to Push Protocol Smart Contracts v3! This feature will revolutionize how users interact with our smart contracts, making blockchain interactions more seamless, efficient, and user-friendly.

What is the Cross Chain Request Feature?

The CCR feature allows users to interact with the Push Core smart contract on the Ethereum blockchain from any EVM or non-EVM chain. This means no more switching networks to perform critical actions like channel creation or incentivized chat requests. Users can now stay on their preferred chains and interact with the Push Core contract effortlessly.

Why is This Important?

Currently, Push Protocol smart contracts are structured with the Push Core contract only on Ethereum, while the Push Communicator (Comm) contracts are on multiple EVM chains. This setup requires users to switch to Ethereum for any interaction with the Push Core contract, leading to a less-than-ideal user experience.

With the CCR feature, we aim to solve this by enabling cross-chain interactions. Here’s how it works:

1. Upgrading Push Communicator Contracts: These will be enhanced to handle cross-chain requests, receiving message payloads from any chain and relaying them securely to the Push Core contract on Ethereum.
2. Modifying Push Core Contract: The Core contract will be updated to process these relayed messages, validate incoming payloads, and update its state accordingly.
3. Leveraging Wormhole’s NTT Framework and Relayers: To facilitate secure and efficient cross-chain communication, we’ll use Wormhole’s Native Token Transfer (NTT) framework and Relayers.

Example Scenario: Bob’s Journey

Imagine Bob, a native Polygon user, wants to create a channel on Push Core. With the current setup, he’d need to bridge his PUSH tokens to Ethereum and switch networks. But with the CCR feature, Bob can:

1. Use the createChannel() function on the Push Communicator contract on Polygon.
2. Approve 50 PUSH tokens and submit the channel details.
3. The transaction uses Wormhole Relayers to send the payload and tokens to Push Core on Ethereum.
4. The Push Core contract processes the request, creating Bob’s channel without him ever leaving the Polygon chain.

Benefits of CCR

• Enhanced User Experience: Users can interact with Push Core from their preferred chains without network switching.
• Broader Reach: Attract users from various blockchain environments, expanding Push Protocol’s market reach.
• Security and Efficiency: Wormhole’s framework ensures secure and efficient cross-chain communication.

Next Steps

To implement CCR, we’ll focus on:

1. Enabling Push Token for Multi-Chain Support.
2. Building Cross-Chain Support in Push Communicator.
3. Building Cross-Chain Support in Push Core Contract.

After developing the core architecture, we’ll conduct extensive testing, security audits, and deploy on testnet and mainnet.

Conclusion

The Cross Chain Request feature marks a significant advancement for Push Protocol. By enabling seamless cross-chain interactions, we’re making blockchain communication more accessible and user-friendly. We’re excited to bring you this feature and can’t wait to see the positive impact it will have on our community.

Stay tuned for more updates, and thank you for being part of the Push Protocol journey. Let’s push the boundaries of decentralized communication together!