Introduction
Project Name: Lunn
Name of the organization or individual submitting the proposal: Hammer Technologies LLC
Previous work has been primarily focused on the Lume Web project over several Sia grants.
Describe your project.
This proposal responds directly to the Sia Foundation’s recent Q2 funding directives.
Lunn is a privacy-focused fileshare/filedrop web app. Its goal is to provide users with the simplest, easiest experience for storing files while enabling private sharing.
It is most comparable to Wormhole (a privacy-focused E2E file-sharing web app) and can be seen as a similar application to what SiaShare was for renterd.
The following is a rough conceptual representation of the sharing portion of the app, which is not set in stone and could change in design or other aspects.
How does the projected outcome serve the Foundation’s mission of user-owned data? What problem does your project solve?
This project ensures users can upload their data with full privacy in a straightforward way, without requiring more technical knowledge than an average user possesses. It enables them to share those files with others with as little friction as is technically practical. From the user’s point of view, this provides a simple drag-and-drop interface and sharing options, allowing users to quickly and easily generate and share a download link.
We cannot provide grants to residents of jurisdictions under increased FATF monitoring, those that have active OFAC sanctions, or those that fail our bank compliance tests. We also cannot provide grants if your payment bank account is located in those same locations. Please review the following list.
Are you a resident of any jurisdiction on that list? No
Will your payment bank account be located in any jurisdiction on that list? No
Grant Specifics
Amount of money requested and justification with a reasonable breakdown of expenses: $9,200
- 2 months of developer fees for Derrick Hammer
What is the high-level architecture overview for the grant? What security best practices are you following? Please review our Development Guide for further details.
This app will primarily make use of the Sia WASM SDK (sia_storage_wasm).
- It will be a fully client-side/static React SPA with no server components other than needing an indexer.
- No seeds will be stored locally in the browser. No cryptographic key material will be sent to any remote server. All critical Sia ed25519 account and security operations will be handled via the SDK.
- The app will make use of service workers and/or web workers for background and content processing.
- As this is a client-side application, security concerns regarding server-side processing are not applicable, and all indexer usage will flow through the SDK.
What are the goals of this small grant? Please provide a general timeline for completion.
- Month 1 - Due 5/25/26
- Onboarding flow with an indexer and user seed.
- Login flow for existing users.
- Skeleton dashboard.
- Ability to upload a file and have it pinned.
- Ability to use the Sia SDK sharing API to generate a link.
- Ability to access a shared file and enter an onboarding flow to obtain an account with an indexer before accessing the file.
- User testing of these app features.
- Month 2 - Due 6/25/26
- Ability to upload multiple files.
- Ability to use folders.
- Both types of uploads will utilize upload packing when possible.
- An upload history/basic object listing for uploaded items with share buttons.
- Dashboard will include basic account stats as provided by the
GET /accountAPI. - Ability to delete files and entire folders.
- User testing of these app features.
Who is the target user for your project?
Both the average user and the privacy-focused user who wants a Wormhole alternative, file.io, or similar services. This should be usable for both mainstream and professional use cases.
What are your plans for this project following the grant?
Once the grant is wrapped up, our main focus is going to be listening to user feedback and using it to make the app even better. We really see this project as a way to help the Sia ecosystem grow. As for making money, we don’t have any immediate plans for that right now… we’d rather wait until we’ve heard from our users and finished the grant before we start thinking about monetization.
Potential risks that will affect the outcome of the project:
- The SDK/indexer could undergo radical changes, causing delays in the project timeline. We will aim to mitigate sdk changes through abstractions.
- Since the WASM SDK has not yet been published to npm at the time of writing, the git version will be manually built and used. Library migration can occur once the foundation does that.
Development Information
Will all of your project’s code be open-source? Yes, MIT.
Leave a link where code will be accessible for review.
Do you agree to submit monthly progress reports? Yes