Some of you may be curious to know what the II team is actually working on at the moment, so we’ve decided to regularly share roadmap updates here, probably every 2 or 3 weeks.
We’re tracking work in JIRA internally and because reasons we can’t just migrate to GitHub tickets, but here’s what we’ll focus on for the next few weeks:
Most of these items have been discussed on the forum or in the community calls, but if anything is unclear just shout. Also, please let us know if this is useful, and if so we’ll keep the updates coming.
So far, we do not differentiate between credentials with and without User Verification. (In short, User Verification requires the user to enter a PIN to unlock the Yubikey and thus could be seen as a flavor of 2FA.) To make use of this additional level of security, we need to
differentiate between web authentication credentials with/without User Verification
adapt in the front end to require or discourage accordingly
make the canister check the authenticatorData (which currently is not even exposed)
Great question, which I actually hoped no one would ask
This is about designing and planning for any auth service to integrate seamlessly with II; the idea is that II would then be the backbone for any 3rd party service (NFID, Me, etc) so that users can benefit from more or less a single login, but still benefit from extra services like phone verification and more provided by other services.
We basically have this vision for II to become something huge, while making it easy for other providers to add to it, and we’re just clarifying how huge… we’ll make sure to share more info to get feedback once the vision crystallizes on our end
Really great work, love to see this kind of roadmap, the team is becoming more and more transparency. Do you @nmattia happen to know if other R&D sub-teams will share the detailed roadmap like this?
Thanks, this means a lot! To be honest it felt quite natural; it greatly reduces stress on our end to know that the community doesn’t think we’re just twiddling our thumbs when not implementing this or that feature that was suggested, and it also feels quite nice to share what we’re doing
Regarding whether other teams will share a roadmap like this, I actually have no idea! We thought this was a good idea to loop everyone in, and it made sense to us. It’s probably worth asking
This is really really great. Many ppl from the community feel anxious is because we don’t know the progress, take the BTC integration as an example, since we don’t know what detailed work must be done for its fully release, but we just feel the it is postponed again and again, I mean if the BTC integration could share the detailed roadmap with us, and update the roadmap in a while (such as 2 weeks or 4 weeks a time) then the community will feel relaxed since we can see the tough works must be done as well as the roadmap is updating in a while. I really look forward to seeing other teams’ roadmap.
Thank you for sharing this again. I appreciate this.
The most difficult part about the BTC Integration is that it is , literally, paving the road as it goes along.
Who would have thought/known about certain blocks giving trouble performance-wise & then having to work through the issues.
The best part about the BTC Integration is that there is literally no other team in the entire world that can do what this team is doing & i mean the entire world in all it’s seriousness ( including Go*, MS*, IB*).
Sure every time i open the btc integration topic , i fear the “what now”. I do think that @dieter.sommer is doing a fabulous job on informing this audience as much as he does.
Hey @nmattia it’s so timely that you made this post, especially the part about auth services integrating with II.
We’re building a few dapps for life sciences research, and one of them is a defi crowdfunding platform for life sciences researchers to raise funds for research with strong commercial promise. We’re trying to work out a way to do AML/KYC/CIP on-chain, hopefully integrating it with II, but we haven’t known who to talk to or what other projects have already figured out on this.
As someone with basic knowledge here - there’s no max supply. However, ICP is both inflationary (to reward node providers and governance participants) and deflationary (burning ICP from transactions and so on). Maybe someone else can answer further.
So far the teams with the most experience integrating with II are Identity Labs (CC @dostro) and AstroX (@neeboo) if I’m not mistaken, I don’t know if anyone is working on KYC but that would be great!
The website looks super slick! Do you already have something running on the IC?
By the way, you should join our community calls, this would be a good topic to discuss.
Hi @nmattia. Thanks for responding and for the compliment. We are a Dfinity grant recipient and recently met our second milestone. We are building on the IC, but nothing is live yet. We’ll have something to show on IC for Supernova though!
Regarding joining the community call, do you mean to bring up the question of integration with other parties for KYC? Thanks for the referral to @dostro and @neeboo. I’ll reach out to them!
