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

Flow Providers: Non-custodial wallets #28

Open
srinjoyc opened this issue Sep 14, 2021 · 11 comments
Open

Flow Providers: Non-custodial wallets #28

srinjoyc opened this issue Sep 14, 2021 · 11 comments

Comments

@srinjoyc
Copy link
Contributor

srinjoyc commented Sep 14, 2021

👋   If you are interested in working on this issue, please check out the Getting Started guide on HackerEarth!

⚠️   This is a special project outside of the existing format of FLIP Fest and requires an application to receive a custom grant structure to work on it.

Description (Problem Statement)

Flow is looking for wallet providers to join the ecosystem.

Please review our RFP (Request for Proposal) document to understand the current ecosystem and its gaps new wallets should ideally fill.

Experience Required

  • Previous or current experience on blockchain wallets and their use in production environments
  • Team capacity to build, support and maintain support on Flow into the long term
  • Strong design, technical, and legal experience within the team

Milestone Requirements

A custom structure will be set for successful applications on a case-by-case basis.

Application

Fill out this form.

Resources

@srinjoyc srinjoyc self-assigned this Sep 14, 2021
@psiemens psiemens changed the title Flow Providers: Non-Custodial Wallets Flow Providers: Non-custodial wallets Sep 15, 2021
@srinjoyc
Copy link
Contributor Author

Hi 👋
I'm Srinjoy - a Technical Product Manager on the Developer Experience Team! I'll help answer any questions and can guide any teams interested in working on this issue!

You can comment here or find me on Discord (srinjoyc#4183). Join the Flow Discord server if you're not there already!

@louzhixian
Copy link
Contributor

Hi guys, our team would like to add flow support in our non-custodial smart wallet solution of UniPass.
Team name: Lay2
Team repo: github.com/lay2dev

@srinjoyc
Copy link
Contributor Author

For the ZayCodes Team, here are the milestones:

Milestone 1
Create an architectural diagram along with any relevant documentation to describe how custody, signatures, UI, and any other services need to interact in order to meet the requirements of the other milestones.

Milestone 2
Meet any of the FCL service specs for authorization and authentication (IFRAME, TAB, POP, etc.)

  1. Create an authentication endpoint and view

    • Collect the user information and authenticate them against the wallet's database to provide back the authentication response.
    • Must support both existing and new users in the same user flow
  2. Create an authorization endpoint and view

    • Show relevant transaction information
  3. Create a pre-authorization endpoint

    • Replace the payer role

Milestone 3
Demonstrate storage of private keys in a non-custodial manner (client-side) using secure web crypto apis or otherwise. At this milestone, there should be an end to end flow for both authentication and authorization that can be demoed in some environment.

Milestone 4
Optimize the user experience and attempted to solve the problems listed in the Flow Wallet RFP. Provide documentation for both developers and end-users.

@aishairzay
Copy link
Contributor

PR opened for milestone 1 here: #54

@srinjoyc
Copy link
Contributor Author

srinjoyc commented Oct 7, 2021

@louzhixian

For the Lay2/Unipass Team, here are the milestones (same as ZayCodes):

Milestone 1
Create an architectural diagram along with any relevant documentation to describe how custody, signatures, UI, and any other services need to interact in order to meet the requirements of the other milestones.

Milestone 2
Meet any of the FCL service specs for authorization and authentication (IFRAME, TAB, POP, etc.)

Create an authentication endpoint and view

Collect the user information and authenticate them against the wallet's database to provide back the authentication response.
Must support both existing and new users in the same user flow
Create an authorization endpoint and view

Show relevant transaction information
Create a pre-authorization endpoint

Replace the payer role
Milestone 3
Demonstrate storage of private keys in a non-custodial manner (client-side) using secure web crypto apis or otherwise. At this milestone, there should be an end to end flow for both authentication and authorization that can be demoed in some environment.

Milestone 4
Optimize the user experience and attempted to solve the problems listed in the Flow Wallet RFP. Provide documentation for both developers and end-users.

Looking forward to your solution, reach out as needed via discord!

@srinjoyc
Copy link
Contributor Author

srinjoyc commented Oct 7, 2021

@aishairzay Thanks for the submission - We'll review shortly with some people from the FCL team as well!

@louzhixian
Copy link
Contributor

Hey @srinjoyc, our PR for M1 opened: #116

kerrywei pushed a commit that referenced this issue Nov 4, 2021
…ubmission (#84)

* Issue 28, milestone 2 Zay Codes submission.

* Issue 28, milestone 3 Zay Codes submission.
kerrywei pushed a commit that referenced this issue Nov 4, 2021
…Submission (#88)

* Issue 28, milestone 2 Zay Codes submission.

* Issue 28, milestone 3 Zay Codes submission.
kerrywei pushed a commit that referenced this issue Nov 4, 2021
* Issue 28, milestone 2 Zay Codes submission.

* Issue 28, milestone 3 Zay Codes submission.

* Issue 28, milestone 4 Zay Codes submission.
kerrywei pushed a commit that referenced this issue Nov 4, 2021
…sion (#116)

* Create milestone-1.md

* Update milestone-1.md

Typo fixes;
Introduction article link added.
@kimcodeashian
Copy link

Good day @aishairzay, @louzhixian!

Thanks so much for all your hardwork & participation. In order to finalize winners & prepare for prize payout, we'll need the following actions from your end.

Please provide the following information by Nov 17, 2021, (in this GH Issue is fine):

1. Team Information

  • Team Members Information - Github Username + Email Contact + Percentage of prize allocation (total should = 100%)
  • All mentioned members MUST react to the post with a 👍 which will act as confirmation that the information is correct, or a 👎 to indicate that the information is not correct.
  • We will be reaching out via e-mail

🎖IMPORTANT: We will only proceed with prize payouts once all members have confirmed with 👍 on the post.

2. Video Demo (optional)

  • Please provide a 5-minute video demo to be featured & showcased in the FLIP Fest Closing Ceremonies
  • Link format & Downloadable (eg. Google Drive, Vimeo)
  • Content Format (Problem Statement, your work / how you solved it, final outcome)

We will be hosting Closing Ceremonies on November 23rd, 8AM PT where we'll having closing remarks from Dete & will be announcing the winners! I'll share the details here before Nov 17.

@aishairzay
Copy link
Contributor

  1. Team Information

Github | email | percentage

aishairzay | amit@zay.codes | 33.4%
zerooverride | tyler.s.eckstein@gmail.com | 33.3%
OmarMalik | omar954@gmail.com | 33.3%

  1. Video demo - may record something soon, will update here when we do!

@kimcodeashian
Copy link

Hey folks,

We've received and reviewed over 82 submissions! What an amazing community on Flow! To commemorate all the hard work done, we have finalized winners and will be announcing them during our Closing Ceremony on Nov 23rd, 8AM PT. Be sure to join us - there may be some attendance prizes & a keynote from our CTO, Dete 😉!

RSVP here so you don't miss out! See you then!

@aishairzay
Copy link
Contributor

@kimcodeashian I recorded a 4 min demo video here: https://drive.google.com/file/d/1ZdjWy_KGF8OwadcW7mGX6InP_6jXQc2Q

LMK if it doesn't fit the expected format or needs a re-do!

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

No branches or pull requests

4 participants