-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension-to-Extension API #76
Labels
Comments
tomicvladan
added a commit
that referenced
this issue
Feb 17, 2022
tomicvladan
added a commit
that referenced
this issue
Feb 18, 2022
tomicvladan
added a commit
that referenced
this issue
Feb 18, 2022
Merged
tomicvladan
added a commit
that referenced
this issue
Feb 18, 2022
tomicvladan
added a commit
that referenced
this issue
Feb 23, 2022
tomicvladan
added a commit
that referenced
this issue
Jul 6, 2022
* feat: add extension to extension api (#76) * feat: complete extension to extension api (#76) * chore: fix linting issues (#76) * fix: fix sessionId for extension API (#76) * fix: fix e2e api * fix: refactor dapp security context (#76) * feat: add e2e option to fetch bee address * feat: include bee debug address in e2e api
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One of the extension's main role is to hide the Bee configuration details from the dApps and providing and interface to interact with Swarm. Because other web3 related browser extensions also can emerge that wants to interact with Swarm, the extension should have an interface facing towards the browser extensions as well. It is requried, because injected scripts, that browser extension places into every webpage are not available for extensions directly.
For the first step, the E2E API should have an interface to give
sessionId
for extensions on message call so that those can satisfy dApp security context with wich those can request FakeURL EPs.The text was updated successfully, but these errors were encountered: