Getting Started with Push Delivery Nodes

[pranshurastogi]

🎉 Welcome fellow developers to the magical world of Push Delivery Nodes! If you're looking to connect web3 and web2 communication, look no further than these little nodes of wonder.

🚀 Push Delivery Nodes are the decentralized solution you've been searching for, allowing any centralized or decentralized platform to receive communications from Push Storage Nodes. These nodes validate and index all communications, linking them to the user's wallet address and multi-chain identity.

🔮 But how does this sorcery work, you may ask? Well, it's quite simple! The Delivery Nodes receive communications from Push Storage Nodes, allowing developers to map any web2 device token or platform username to a specific web3 wallet address and send alerts to web2 or web2.5 platforms. Pretty nifty, right?

🌟 But that's not all! For those who prefer a pure web3 experience, listening to Push Storage Nodes or utilizing their RPC endpoints/SDK is the best option. However, for the adventurous developers out there who want to extend their communication experiences to centralized platforms, the Delivery Nodes are here to save the day.

👨‍💻 But before you get started with the Delivery Node module, there are some prerequisites to consider. You'll need MYSQL, Redis, and Docker for the local setup, as well as a Google FCM account setup. Don't worry though, we have a helpful video tutorial and docs links for you to refer to.

👀 In summary, Delivery Nodes are the magicians of the web world, bridging the gap between decentralized and centralized platforms, and enabling communication beyond web3 wallet addresses to web2 platforms. With these nodes, you can reach a broader audience and enhance your user experience. Plus, who doesn't love a little magic in their coding journey? ✨

Useful links:

Delivery Node Repo Link:
Demo Mobile App Repo Link
Delivery Node Setup Video Tutorial
Delivery Node Medium article