feat: rfc-1103 tari universe communication with provider #135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MCozhusheck
changed the title
MCozhusheck
force-pushed
the
rfc-communication-with-provider
branch
from
c93a081
to
d7cd58a
Compare
There was a problem hiding this comment.
There is already a client JS library for interacting via websockets and Tari's Metamask Snap (https://github.com/tari-project/tari.js). Is there a way the developer can include a single library that works with all three?
|
Im not sure about Metamask snap provider but weksocket and Tari Universe provider are similar but there are some major differences. The websocket must first obtain webRTC connection while the other doesn't. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This RFC description how communication between tapplet and wallet daemon could look like in Tari Universe.
Communication between web app and wallet daemon normally requires webRTC connection. In out case this not necessary as both wallet daemon and tapplet are on same host machine. This requires another way of communication between tapplet and wallet daemon.