Skip to content
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

Exploration of End-to-End Embeddable Widget for Passport Score #2964

Open
1 task
erichfi opened this issue Oct 11, 2024 · 1 comment
Open
1 task

Exploration of End-to-End Embeddable Widget for Passport Score #2964

erichfi opened this issue Oct 11, 2024 · 1 comment

Comments

@erichfi
Copy link
Collaborator

erichfi commented Oct 11, 2024

User Story:

As a technical team member exploring future embed work,
I want to create a basic embeddable widget that displays a Passport Score,
So that I can understand the complexity and technical requirements of the embed functionality, ensuring compatibility with most Ethereum dApp web frameworks.

Acceptance Criteria

GIVEN a basic widget that accepts a wallet address,
WHEN the wallet address is input,
THEN the widget should return and display the corresponding Passport Score,
AND it should be easily embeddable across different dApp sites using an iframe.

Product & Design Links:

N/A - Focus is purely on functionality, not design.

Tech Details:

Accept a wallet address as input.
Query and display the Passport Score.
Ensure compatibility across major Ethereum dApp frameworks using an iframe model similar to Uniswap’s integration.

Open Questions:

  • What security measures are necessary for handling wallet addresses?

Notes/Assumptions:

  • This feature is for technical exploration, not production use.
  • Focus is on functionality; design details are secondary.
  • The integration should prioritize ease of use and compatibility for partners.
@nutrina
Copy link
Collaborator

nutrina commented Oct 14, 2024

On the client side we'll need:

  • Inputs:
    • API key
      • at some point we might want to think about restricting API key usage to certain domains
    • address
    • in the future we might also want to have providers (in case we will want to write info to the blockchain)
  • we'll only perform evm checks
    • for this we should implement an API in the IAM, that performs the EVM stamp verifications without receiving any provider as imput
    • the iam will keep track of the current list of evm stamps, not the client as it is the case with the 1-click verification flow
  • think about API key tracking -> shall we use API gateway for this?
    • should not be part of this ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Prioritized
Development

No branches or pull requests

2 participants