Standard Grant: Nydia Passkey Holder. Chapter 3

Grants Rejected
1

Project Name: Nydia Passkey Holder. Chapter 3: Where Nydia Unlocks the Power of Touch
Project Lead: Oleh N.

Project Description

Here’s what happens when you try to export passkeys from any Android device: YOU CAN’T.

Meanwhile, Nydia already enables seamless passkey storage and sync across Chrome, Firefox, and Safari — thanks to Sia. Android deserves no less.

Nydia’s Android implementation directly addresses this gap.
The project builds a credential provider for Android 14+ that stores passkeys on the Sia network.

Who benefits from your project?

Users of the Nydia browser extensions will be able to synchronize passkeys across devices and browsers, with full portability via the Sia network. So will Android users, who can now finally decide where their passkeys are stored — and by whom.

How does the project serve the Foundation’s mission of user-owned data?

With Android support, Nydia makes passkey ownership truly universal.
Your keys, your network, your device choice.

Project Goals & Milestones

Note: For planning purpose, timeline based on September 1, 2025 start date.

Milestone #1 (Due by January 2, 2026)

  • Develop credential provider service MVP for Android 14+

Milestone #2 (Due by February 2, 2026)

  • Implement passkey upload and retrieval via renterd API.
  • Design and implement synchronization logic to keep local and renterd passkey states consistent.

Milestone #3 (Due by April 2, 2026)

  • Add passkey encryption/decryption.
  • Enable cross-platform use of the same encrypted passkey set between Android and Nydia browser extensions.

Milestone #4 (Due by May 2, 2026)

  • Create user interface for passkey management and renterd settings.
  • Add support for biometric and device credential authentication.

Milestone #5 (Due by June 2, 2026)

  • This milestone will cover the full spectrum of testing. At the same time, though the primary scope of this grant is the Android implementation of Nydia, development of the browser extensions remains ongoing. If any attestation enhancements come up during Nydia-for-Android development, they’ll be added to the Chrome, Firefox, and Safari extensions as part of this milestone to maintain alignment across the ecosystem.

Potential Risk

While Android 14+ allows third-party password managers to provide passkeys, certain OEM devices may lack support for this feature. This may result in limited availability of Nydia on some devices.

Supporting native Android applications via the Credential Manager API may require additional discovery, testing, and adaptation to app-specific behaviors. If full implementation proves infeasible during the grant period, initial support will focus on browser-based use cases, with native app flows deferred to a future chapter.

Budget

The project requests $72,000 in funding, allocated over a 9-month research and development period.

Are you a resident of any jurisdiction on that list? Will your payment bank account be located in any jurisdiction on that list?

No, to both questions.

Will all of your project’s code be open-source?

Yes.

Where code will be accessible for review?

Do you agree to submit monthly progress reports?

Yes.

Contact info

Email: [email protected]
Discord: new0ne

2

Hello,

Based on the direction you are going in your grant, I would honestly take indexd into account (Sia Roadmap - New Developments At Sia | Sia). The main reason is sending to renterd will end up being a dead end for anyone not a power user. You could support both as storage backends/backups, but you should take the direction the ecosystem is going to move into, into account.

Looking at your code I can see a lot of your efforts are encrypting to a local indexed db Nydia-Passkey-Holder/src/store.ts at 5f56bbfa36beee176c5642ca43bf5243a67ff3d7 · new0nebit/Nydia-Passkey-Holder · GitHub which seems fine, but https://github.com/new0nebit/Nydia-Passkey-Holder/blob/5f56bbfa36beee176c5642ca43bf5243a67ff3d7/src/sia.ts is where new opportunity is going to come, for the average user, and you should plan for that.

Also you should clarify your timelines because you are asking to start in December? Though if that is true, you can likely build ontop of S5 too as a storage option.

Kudos.

3

Hi Derrick, thank you for bringing this up.

To be honest, I don’t have a clear picture of indexd at this point, but I’m closely following its progress. Right now all my efforts are focused on developing and improving Nydia’s attestation mechanisms, passkey encryption, and ensuring seamless integration with renterd.

Since grant work on the ‘Implement passkey upload and retrieval via renterd API’ is planned to start in January, until then (if my grant is approved) I’m planning to develop the credential provider service MVP while keeping a close eye on indexd progress to evaluate integration options :eyes:

Sorry, you’re absolutely right about the timeline confusion. I was assuming a September 1, 2025 start date. I’ve now added a Note to clarify this in the grant proposal.

4

Please clarify why you have the credential provider at taking ~4 months to do? Is implementing that alone really that complicated to do so? I ask as everything else seems a short timeline in comparison?

5

Would it make you feel better if I said the UI would also take four months? :)
Milestones are delivery deadlines, not monthly assignments. The credential provider requires the full 4 months of continuous development — it’s due by January 2 — while other development streams run in parallel on shorter cycles.

That’s a reasonable question, just for the opposite reason. I can’t believe I put down 4 months for this. I guess…it’s too late now. In total it can take more because I’ve already started.

How complicated is it? Well, this is essentially what a passkey authenticator is. It’s the most complex technical component of the entire project.

The credential provider is the core foundation of Nydia on Android — it’s not just a simple UI component, but a deep integration with the Android Credential Manager API that should work reliably across browsers and native apps. And I’m doing all of this solo. No subcontractors.

To put this in perspective: I’m building what companies like 1Password, Bitwarden, and ProtonPass have teams of engineers working on. The credential provider documentation is fragmented across multiple sources, whereas the WebAuthn specification alone is book-length — and that’s even before factoring in the intricacies of making it all work reliably across Android versions.

4 months is optimistic for a solo developer, but it’s also realistic enough to show I understand the scope while being committed to delivering a working MVP.

6

To be clear… I asked the question sincerely b/c I don’t understand the scope or what is involved.

I definitely understand taking on very hard challenges, so I am not criticizing the timeline, at-least not negatively… I just wanted to understand the complexity better?

:upside_down_face:

Kudos.

1 Like
7

Got it, no problem. This could turn into a very long thread so you can always DM me if you have any questions :handshake:

8

Thanks for your proposal to The Sia Foundation Grants Program.

After review, the Committee has decided to reject your proposal citing the following reasons:

  • The budget breakdown is missing key detail for the amount listed.
  • The Committee does not agree with the 9-month duration for this project.
  • The Committee has concerns about the product viability and usability, especially considering a renterd node set-up is required to utilize the app.

We’ll be moving this to the Rejected section of the forum. Thanks again for your proposal, and you’re always welcome to submit new requests if you feel you can address the Committee’s concerns.