-
Notifications
You must be signed in to change notification settings - Fork 36
Android Update - Addresses generation / Authenticator with usernames #167
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
Comments
Thanks for submitting a grant proposal. Our team will review your submission and get back to you. |
Looking forward to it so that OI Calendar can get updated! |
Hi @Filmaluco we are pleased to approve this grant. A couple of asks:
|
|
Congratulations. Your grant is now approved. Please complete the on-boarding link here: https://stacks-grant.netlify.app/onboard?q=4f0be1135ea6f4cecac370a285dbd754 |
Thank you! I've updated the grant to approved, please fill this form out? @ Alex Grabe, one of the grant committee members, had a couple questions, if you want input from him. Even in the scope, I don't see that they are spinning up their own registrar. In the past, the Blockstack Auth would allow name registrations for free as part of the onboarding flow - this is not the case anymore. There’s work need to register names for a new namespace. This isn't gating, but if you want to chat with him about it join the discord grant channel and chime on in! Congrats and thank you. |
Hi @Filmaluco - wanted to check to see if you were able to fill out the form? |
@RaffiSapire Yes we filled the form and already talked with Alex Grabe, we are now waiting for the contract/ Docusign agreement. |
@RaffiSapire we are still waiting for the contract/ Docusign agreement.
"Phase" 1: We understand that a few changes might still be needed, but we are now working on Phase 2
We have already implemented the the ability to register Stacks usernames as well but we found an issue on the generation of the AuthResponses... We think that something changed and we are now trying to find out what, and why. |
@RaffiSapire we are still waiting for the contract/ Docusign agreement, is everything alright? |
@Filmaluco the docusign was sent but never signed, we just resent it. If you have issues please find me on discord to get a response more quickly! @RSAP |
@RaffiSapire we got the contract now, and it has been signed. |
Stacks Circles Android app is now officially launched! Apps/Websites using Stacks Connect or the Android Blockstack SDK v0.6.4 or higher, should be able to make use of Circles app to authenticate on Android devices without any problems. However there are some prerequisites at the project repo. With this I think its safe to say we concluded everything we proposed to do 👍 (there are some prerequisites to ensure the best experience with the app, please make sure you check them out beforehand) |
Amazing work @Filmaluco! So excited to review this with the Grant committee today. Will reach out to you about sharing this news more widely with the community soon :). |
Thanks @Filmaluco, this is awesome! Would love to feature at the next demo day. If there is anything else you want to expand on this, we're really excited to continue to support you in future grants. |
Background
The Android platform has a huge growth potential for Stacks. Currently Android Developers can use the Blockstack Android SDK to develop apps within the Stacks ecosystem. But the SDK is outdated, with no major changes since Stacks 2.0 was launched.
Project Overview
The main goals are to update the Android SDK and release the Circles app.
There's currently no method to generate a Stacks Address (Mainnet or Testnet) and the lookup system still uses the legacy core API "https://core.blockstack.org/". These are breaking changes that have not yet been addressed within the SDK.
This changes would make the release of Circles possible again allowing Android Users to have an authentication system that is compatible with both Android Apps and Web Apps, and supports, again, username registration.
(Circles was a Grants project that is fully open source, you can find the repository at https://github.com/blocoio/stacks-circles-app)
Scope
While Stacks 2.0 brought a lot of new changes and updates we want to target 3 main things:
Migrate to the new API
We want to update the current lookup system, including migrating from core.blockstack.org to stacks-node-api.stacks.co.
STX Address Generation
With the help of @friedger, we already have a proof of concept for the STX Address generation in Kotlin. We want to implement a final version, for both Mainnet and Testnet, into the SDK, with a set of tests.
Ability to register stacks subdomains (usernames)
Give back to Android users the ability to register usernames, so apps like Envelop can again receive new users. Users will be able to register usernames from within the Android Authenticator app Circles.
Since the app Circles will make use of the updated SDK and is open source, we can measure our success if the app itself can:
Budget and Milestones
Total Grant Request: $2000
Total effort: 1.5 weeks / person
Team
The Bloco team, builders of Envelop and Circles:
Risks
With the proof of concept for STX Address generation for Mainnet, there's no high risks. But there's always the chance that, due to some internal Stacks team work, the technical specifications of what we need to do also change.
Community and Supporting Materials
We've built a popular Blockstack app, Envelop, that's fully open-source. And we made contributions to the blockstack-android SDK. We've also hosted a Blockstack Meetup Portugal.
We are also responsible for building and maintaining the Blockstack Auth Android application Circles.
The text was updated successfully, but these errors were encountered: