-
Notifications
You must be signed in to change notification settings - Fork 27
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] webpage connection #7
Comments
Hey @0xChqrles, I would like to work on this one! |
Hey @HumbertoTM10! |
Hey ! Sorry I forgot to mention that #6 should be solved first in order to start working on this one. And please provide more details about yourself and the way you want to solve the issue by filling the OnlyDust application next time :) |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI would like to work on this one. I worked in the project called Zap in the HH Brussels Starknet and I already did the same logic for Zap, which uses TLSN to perform the same flow in Revolut. Morevoer, I am computer engineering in the blockchain ecossystem since 2022, I won some hackathons and I am starting in this journey of OnlyDust How I plan on tackling this issueBasically I will create a client in the content part of the extension (which handles the logic between desktop webpage and extension) and then I will send an action to open an Approval Page in the PopUp, then the client will choose to approve or reject the connection, and send back a response. Once the connection is established, I can create another function in the client (on the content.tsx) to send an action to the background to retrive some data from the extension or handle some webpages inputs to perform an action in the extension. Opening, for example, the side bar to perform all the notarization in the Revolut page. |
Hey @BryanBorck! |
Hey @BryanBorck ! Thank you for your very detailed message !! Glad that the Zap team is willing to contribute ! I'm assign you to the issue rn 🫡 |
Implement a connection logic, similar to the one available with extensions wallets. This way the extension should be able to read the current webpage, and the webpage should have a access to some specific data the extension is making public.
The text was updated successfully, but these errors were encountered: