You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2021. It is now read-only.
The ability to post future intents of display information based on blockchain events by Dapps that shared at least one session with the address.
The Wallet node would be able to listen to cached notifications left outside of session but have been encrypted and signed by previous Dapps that you have connected (hence prior knowledge). Therefore you can both whitelist them or blacklist them in your WalletConnect client.
These caching servers for notifications are mostly push servers run by Wallet providers which are mostly incentivized to maintain these subscriptions for their users that will receive rather than send them.
The text was updated successfully, but these errors were encountered:
I envision a prompt to the user on the third or fourth session connection asking if they want to enable push notifications. They can also enable or disable at later point through config.
On the dapp side, it would be as simple as providing an event filter with a mapping to notification messages. Needs to be dynamic ex: filter on user address.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The ability to post future intents of display information based on blockchain events by Dapps that shared at least one session with the address.
The Wallet node would be able to listen to cached notifications left outside of session but have been encrypted and signed by previous Dapps that you have connected (hence prior knowledge). Therefore you can both whitelist them or blacklist them in your WalletConnect client.
These caching servers for notifications are mostly push servers run by Wallet providers which are mostly incentivized to maintain these subscriptions for their users that will receive rather than send them.
The text was updated successfully, but these errors were encountered: