Key Points: Push Protocol enables all dApps and smart contracts, backends and protocols.
Push Protocol, after two years of development has become the main project for the message push pipeline. It has also become an essential infrastructure in the Web3 industry.
Push Protocol is a Web3 decentralized communication protocol that enables any smart contract, dApp, or even traditional service to send notifications to wallet addresses.OverviewPush Protocol is a decentralized communication protocol for Web3, which enables any smart contract, dApp, or even traditional service to send notifications to wallet addresses, provided that these wallet addresses choose to receive messages from these channels, it can be applied to Web3. The whole scene, including DeFi asset liquidity and media news push, has sent 17.7 million messages to 60,000 subscribers. Name and positioning changesBefore September 20,22, the name of Push was EPNS, which stands for “Ethereum Push Notification Service”. The name of PUSH indicates that it was an Ethereum project before that. Its positioning at that time was EPNS, which stands for “Ethereum Push Notification Service”. The old name of PUSH was EPNS, which means “Ethereum Push Notification Service”. The new name breaks down the three parts into Ethereum, message notification, and service. It will eventually support other chains like Polygon and break through Ethereum to other L1 or L2 chains. Second, it supports all messaging push scenarios and notifications. It supports multiple chains and multiple scenarios. Therefore, it is no longer a service, but a protocol. EPNS will continue to be its name. It will be a limitation to its business and brand, so it changed its title to Push Protocol. Message push is integrated into all aspects traditional Web2, including IM chat, news, marketing information, notification prompts, and other information. It is extremely mature in both technology and application scenarios, but it is rarely used in Web3. When it comes to dApps that have message push capabilities, most of your notifications requirements are met by email. These are the main reasons: Most dApps are web pages on the PC, and the development time of the mobile terminal is very slow, as the message push is instant and the absence of a mobile terminal limits the development of message push scenes. Web2 was not widely used until the advent of the mobile internet.
The message push by Web3’s infrastructure layer is a development depression, and there aren’t many mature solutions.
Web3 still supports message push for many scenarios, such as DeFi price changes and voting result notifications. Social protocol products like Lens Protocol integrate Push Protocol to increase attention, likes, and other features. Comparison of Web2 & PUSH message pushing logic. Every day, everyone’s mobile phone will get a lot of messages, including friend messages, headlines from the news media, and discounts from ecommerce platforms. How are they achieved? The following diagram shows how the APP on your iPhone mobile phone sends messages to your phone. The core is APNS (Apple Push Notification Service), which acts as a transit service. It is divided into three phases: Phase 1: The upstream party packages the message and the received iPhone ID, and sends it back to APNS.
Phase 2: APNS searches the iPhone with the corresponding Logo in the Push service list and sends the message.
Phase 3: The iPhone sends the incoming message to its application and displays the Push notification according the settings.
The following illustration shows the principle behind Push Protocol. It will be apparent that the structure of Push Protocol is compatible with the APNS of Web2. The input layer is where the message generation occurs. It contains the top three types of dapps, servers, and smart contracts. Push Protocol will receive the message and forward it to the appropriate receiver. You must return. There must be a downstream front end responsible for receiving and displaying the messages. Push Protocol, as a protocol layer is responsible for the distribution of messages. Push Protocol provides a plug-in messaging box for users. Push Protocol also displays the messages that users have received through Push Protocol.
Channel: To receive the message, the sender must be registered in the Push Protocol.
Subscriber: The subscriber is the user who has subscribed
As shown in the below figure, I can open the Push Protocol operation console, click on the channels column and many channels will appear to my right. These channels are message senders that the user has created. I can click to join or exit a channel. To become a subscriber to this channel, I must sign up when I join. The messages generated by the channel will be sent directly to my wallet address once I have signed up. The messages generated in the channel will be sent to my wallet address. Users can unsubscribe at anytime. have settled in, but even serial novels have settled in, so the imagination space of Push Protocol application scenarios is still very large.A pledge of 50 $PUSH is required to apply to become a channel, of which 10 $PUSH is used to create the agreement fee of the contract, and the rest of the Token will be stored in the contract pool of the channel owner, and the Token in the pool will be returned once the channel is deactivated.Channels can send out 3 types of messages, broadcast notifications, clove notifications and subset notifications.Broadcast notification: send a message to all subscribers of the channel at once
Directed notifications can be sent to wallet addresses if they are subscribed to the channel.
Subset notification: A variant of targeted notification that notifies only a selected group of subscribers
How to integrate Push ProtocolPush Protocol supports the sending of messages through smart contracts, PUSH dApps and SDKs. As an example, we will use smart contracts. First, import the IPUSHCommInterface interface. Then define the channel’s address. Each channel that is created by a user will receive a channel address. You can either specify subscription addresses or set it to broadcast mode. This will allow you to trigger the message content once you have executed your contract code to the appropriate position. The Push Protocol nodes will then transfer the content. The downstream must receive and display the message after the message has been sent. Push Protocol offers three methods for receiving the message. The downstream must then display the message. Currently, PUSH’s partner organizations are involved in many important areas. DeFi sends transaction-related data through PUSH. Decentralized financial activities have been the main body on Web3. PUSH can be used to send user education and information about the current state of the world. In an emergency situation, such as when a loan or collateral is near liquidation, PUSH can be used to remind users to act. Users can also use PUSH to remind them about changes in the prize pool and the status of winning. The current state of Discord means that people may block or ignore important information. Using PUSH can allow end-to-end communication. GameFi uses PUSH to remind users to participate in DAO governance. There are many Web3 data analysis protocols available. PUSH can be combined with PUSH to allow users to customize their needs. For example, they can track the NFT transaction volume on an aggregated trading platform. They can also read SushiSwap Swap and pair data. Push Protocol has been the head project for the message push track and has become an important infrastructure in the Web3 industry. I expect PUSH to grow in cross-chain, end-to-end communication in the future. DAO builder will also be a benefit for it on the Web3 communication path. We encourage you to do your own research before investing.Join us to keep track of news: https://linktr.ee/coincuHaroldCoincu NewsTags: dAppEPNSETHPolygonPush ProtocolWeb3