Ethereum push notification services

Ethereum Push Notification Service Price ( PUSH )

0.00005942 BTC 8.13 %

0.0008987 ETH 8.13 %

Ethereum Push Notification Service Links

Links

Explorers

Community

Ethereum Push Notification Service Contracts

Please change the wallet network

Change the wallet network in the MetaMask Application to add this contract.

Ethereum Push Notification Service Tags

Property

Ethereum Push Notification Service Chart

Please wait, we are loading chart data

PUSH Price Live Data

The live Ethereum Push Notification Service price today is $2.23 USD with a 24-hour trading volume of $1,860,400 USD. Ethereum Push Notification Service is down 8.13% in the last 24 hours. The current CoinMarketCap ranking is #892, with a live market cap of $10,155,160 USD. It has a circulating supply of 4,551,509 PUSH coins and a max. supply of 100,000,000 PUSH coins.

If you would like to know where to buy Ethereum Push Notification Service , the top exchanges for trading in Ethereum Push Notification Service are currently Bilaxy, AEX, 1inch Exchange, and WazirX. You can find others listed on our crypto exchanges page.

What Is Ethereum Push Notification Service (PUSH)?

The Ethereum Push Notification Service or EPNS is a notification protocol that can enable the wallet addresses of the users to receive notifications. This means that, through the usage of this protocol, any DApp or smart contract, as well as service, can send notifications through to users in a platform-agnostic way. EPNS also contains a DeFi aspect that enables users to earn crypto for receiving the actual notifications. EPNSoriginally launched as an idea in January of 2020.

Who Are the Founders of Ethereum Push Notification Service?

The Ethereum Push Notification Service was founded by Harsh Rajat and Richa Joshi.

Harsh Rajat is the founder of the Ethereum Push Notification Service; however, he also works as a solutions architect at 3 Magic Shots, and even fills the role of the chief technology officer at HydroLabs. He used to be a decentralized ambassador of Hydrogen FinTech.

Richa Joshi is the co-founder of the Ethereum Push Notification Service, and she also works as an independent consultant at 3 Magic Shots, as well as a product manager at Hydro Labs. Before all of this, she worked as a senior consultant at Deloitte Consulting.

What Makes Ethereum Push Notification Service Unique?

For Web 3.0, a notification mechanism that can notify users or wallet addresses of important updates, events, actions and so on, does not exist yet. As a result of this lack, a lot of important events or required user actions end up being missed completely: for example, the expiration of ENS blockchain domains is inefficiently broadcast on Twitter, with the hopes that the grace domain user potentially reads about their domain’s expiry. If a protocol gets compromised, people have to look for other methods (besides the now-compromised protocol) through which they can notify the users.

EPNS tries to solve this with its push notification service.

To do this efficiently, the notification is stored and treated like a JSON payload, and this is transformed as per the rules of the different carriers when the notification ends up reaching them. The JSON payload can differ with payload types, and this ensures the flexibility of the content, as well as the data, storage interpretation and delivery.

What this means is that EPNS can allow users to be in direct, full control of what services they end up getting notifications from, and impose rules on the services, which includes spam protection for users, and limits for EPNS ability to add wallets as subscribers. This means that notifications are treated as a social feed rather than a piece of information.

There are four types of users: service providers, which want to send notifications, users, who want to receive notifications if they deem them to be beneficial, wallets enable users to receive notifications through their centralized or decentralized solutions, and token holders, who can define the rules between the above users.

Related Pages:

Learn about Steem. Learn about crypto ETFs on CMC Alexandria. Get a deeper dive into the world of cryptocurrencies on the CoinMarketCap blog.

How Many Ethereum Push Notification Service (PUSH) Coins Are There in Circulation?

The protocol’s token PUSH is designed to incentivize the continued adoption cycle of the EPNS protocol. In order to achieve this, users that are involved are rewarded through either an incentive or a penalty. Their continued involvement is a necessity for the growth as well as the adoption of the protocol, and to achieve the vision of becoming a Web 3.0 notification standard.

How Is the Ethereum Push Notification Service Network Secured?

The Ethereum Push Notification Service Network will use Eth-Crypto to handle the secure verification process. This is a cryptographic JavaScript-function enabler for Ethereum.

Where Can You Buy Ethereum Push Notification Service (PUSH)?

If you want to buy, sell or trade Ethereum Push Notification Service (PUSH), you can do so on the following exchange:

Take the first step towards learning everything you need to know about buying, selling or trading cryptocurrencies, check out our Bitcoin guide here,

Here are some other articles that you may be interested in:

Источник

Ethereum push notification services

Ethereum Push Notification Service

<% hint style="danger" %>This page is outdated and in development

EPNS (Ethereum Push Notification Service)

The EPNS protocol is the first of its kind decentralized defi notification protocol which enables users (wallet addresses) to receive notifications.

Using the protocol, any dApp, service or smart contract can send notifications to users(wallet addresses) in a platform agnostic way (mobile, tablet, web, fav. wallets, etc). The DeFi aspect of the protocol also ensures that the user receives and earns from those notifications.

What are the benefits of having EPNS?

Idea behind EPNS is to expand on and integrate existing ways by which a user can be reached out to by different dApp owners, smart contracts, etc. The EPNS service can be used in a variety of ways:

• It can be used to relay important loan liquidation, funds running out, debt positions notifies to a specific user in #DeFi
• It can be used to inform users of important upcoming events, notifications, etc of specific dApps (via App Owners)
• It can be further enhanced to convey push notifications that act as security mechanisms (for example: a Trusted App Owner group is subscribed by all exchanges, the addresses relayed by this app owner in specific format can automatically blacklist those addresses out)
• It can potentially be used by Ethereum itself for major announcements like launching of Ethereum 2.0, notifications to miners for any upcoming fork, etc
• It can potentially replace the way new projects gather user’s sensitive information. For Example, when an ICO is conducted or a new cryptocurrency is launched, instead of these projects relying on emails to store and communicate about their updates, they can instead offer EPNS service which is anonymized and doesn’t have a central point of failure.

Following definitions are used in the rest of the spec to refer to a particular category or demography of the users of the protocol.

Term	Description
Contract Owner	The owner of the contract, specifically the address by which the contract is deployed
App Owner	The third party projects, dApps or smart contract, specifically the address which forms their identity as well as the custom opt-in group which the subscribed users will recieve message from
Users	All the users who don’t fall in either of the above category
App Owner Group	The group which contains subscribed users of a particular App Owner
Subscribed Users	The users who have subscribed to a specific App Owner Group

For the purpose of explaining above EPNS terms, let’s take the example of Youtube and the various associated roles.

Term	Description
Youtube	Contract Owner
Channels	App Owner Groups
Channel Owners	App Owners
Users	Users
Subscribed Users	Users subscribed to a specific App owner group

Inorder to ensure the proper participation of all players, following game theory is proposed, features marked with indentation will mostly be excluded from MVP:

The contract owner doesn’t have any ability to send message on behalf of app owners

The app owners might spoof other trusted apps and thus will have to be verified or a spam system developed so that users can mark them as spoof or a similar mechanism

The app owner can blacklist a certain user from their group if they want to

EPNS should be able to:

• Provide function for dApp or Smart Contract to register itself as app owner
• The app owner needs to upload their profile in a json format to IPFS, this will contain their name and icon at the beginning, this json file hash is stored on-chain and fetched and shown along with the message they send
• The users can subscribe to multiple app owner group through their own action
• The subscribed users can unsubscribe from an app owner group through their own action
• The app owner can send messages to their subscribed users
• The messages sent from app owner can also indicate if they want to use push notification service of epns.io.
• A small fee will be charged for using the service for push notification
• To ensure that push notification service usage is done after paying the fee, the message will be emitted with a flag
• The app owner can send unencrypted message to their app owner group in which case the message will reach every subscribed users
• The app owner can also send encrypted message to specific subscribed user in which case the message will be encrypted with the specific user’s public key
• In the encrypted message scenario, the user private key will be used to decrypt the message, this means that the mobile app needs to store the private key of the user wallet which will be done in a safe and secure way. The private key in any case will never leave the user’s device
• The web3 provider can also use a similar mechanism to display notifications to the users in the future
• The app owner message is to be stored in the JSON file on ipfs and the hash of that will be mapped. this will be interpreted by the server handling push notifications and also by any web3 providers who wants to use the service

The JSON file will carry msg type ids which can ensure that the system can be extended beyond the ecosystem, ie: for having a trusted app owner with exchanges and subscribed users that can monitor and lock down blacklisted wallets automatically in the future.

Proposed App Owner JSON File Format

Name	Type	Description
name	string	The name of the app to be displayed
icon	base64	128×128 icon to be associated with the app

Proposed message JSON File Format

Name	Type	Description
type	Integer	The message type, currently will be 1 indicating normal message
payload	json	The Payload of the message

Payload Type 1 — Normal Push Notification

Name	Type	Description
title	String	The title of the message
message	String	The message
cta	String (Url) (Optional)	The link to perform call to action if any
image	String (Url) (Optional)	To make the notification rich
encrypted	Bool	message is encrpted or not

Note: The push notification icon will be taken from the App Owner Json Icon and will be displayed on the right side of the notification area for mobile.

EPNS system needs to deal with the following to allow specific, user permissioned messaging from different custom opt-in groups created by app owners:

Creation of App Owners (dApp Owners, Smart Contracts, etc that want to send message)

Источник