Small Grant: My-Transactions

Grants Rejected
1

Project Name

My-Transactions

Name of the organization or individual submitting the proposal

Aniket Rawat (Individual)

Describe your project

My-Transactions is a local, read-only transaction analysis dashboard for your Sia Transactions.
The project converts wallet event data into clear, human-readable transaction records, allowing users to privately organize, label, and understand their wallet activity. It also lets you export reports (CSV/PDF) for without sending data to any external server or modifying the wallet state.

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

The project fully aligns with the Foundation’s mission of user-owned data by operating entirely locally.
All wallet data, labels, and metadata remain on the user’s machine using indexedDB and are never transmitted to third-party services. The application interacts with walletd using walletd API, ensuring users retain full custody and control of their data while gaining better visibility and understanding of their activity.

Compliance Questions

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

$5,000 USD

Budget breakdown:

  • Core Development ($2,000):
    Event parsing, transaction grouping, and api logic for walletd v2 events.
  • Local-First Data & Privacy ($1,500):
    IndexedDB based storage for labels and metadata, backup/restore functionality, and strict read-only access controls.
  • Reporting, Testing & Documentation ($1,500):
    CSV/PDF export modules, accuracy testing against the Zen testnet, and user/developer documentation.

High-level architecture overview & security best practices

  • Client-side React/TypeScript application
  • Direct local connection to walletd via authenticated HTTP
  • Read-only API usage only
  • No cloud backend or external data transmission
  • Wallet password stored only in memory during session
  • Local encrypted storage for user-added metadata

Goals of this small grant & timeline

Month 1

  • Wallet connection flow
  • Wallet discovery and address ownership detection
  • Event fetching and basic transaction grouping

Month 2

  • Transaction classification (income, expense, fees)
  • Private labeling and search
  • Balance and summary views

Month 3

  • CSV/PDF export
  • Accuracy testing on Zen testnet
  • Documentation

Potential risks that will affect the outcome of the project

  • Changes to walletd v2 APIs during development
  • Edge cases in event classification requiring additional testing
  • Limited availability of real-world datasets during early testing

Development Information

Will all of your project’s code be open-source?
Yes. All project code will be open-source.

Code can be accessed here: https://github.com/AniketR10/my-transactions

Progress Reports

Do you agree to submit monthly progress reports?
Yes

Contact Info

Gmail: [email protected]
Github: AniketR10 (AniketXD) ¡ GitHub
Discord: @puddingpants01

2

Hi @AniketR10 - welcome to the Sia community and thank you for your proposal!

Could you provide some additional justification as to why the Sia community would benefit from this project? Why would it be beneficial to gain a better understanding of one’s own wallet activity?

Please respond before Wednesday at 5pm ET in order for this proposal to be presented to the Committee at next week’s meeting. Thanks!

1 Like
3

Hi @mecsbecs ,
Thanks for the question!

On Sia, wallet activity is exposed as low-level, event-based data that is difficult for most users to interpret. For example, a host may see multiple events related to a single storage contract, but has no clear way to understand how much was earned, how much is temporarily locked as collateral, or what fees were paid, etc. As users can only see balance changes and must manually inspect transaction addresses and raw data to maintain their records.

This tool:

  • Automatically interprets and labels system-generated wallet activity (such as fees, contract-related events, and collateral locking/unlocking) so users don’t have to manually inspect or guess what caused a balance change.

  • Allows users to save and label frequently used addresses with private notes for future reference.

  • Letting users add their own notes to transactions for better long-term understanding.

  • Providing CSV/PDF exports to simplify accounting and financial record-keeping.

Thus, helping users turn those low-level events into clear, readable transaction records. Allowing them to answer practical questions such as:
“How much did I earn last month?”,
“Why did my balance change?”,
“Which activity relates to this contract?”.

By making wallet activity easier to interpret in a local, read-only tool, the project reduces operational overhead, improves transparency and confidence, and supports self-custody. This helps users operate more reliably on Sia and strengthens trust in the ecosystem.

4

Hi @AniketR10 - thank you for your response.

I’ve spoken with our internal team and they agree that labelling and exporting into different formats would be great features for the walletd app. However, these features would not be justifiable as a distinct, separate grant.

You can contribute these ideas to the walletd repo here:

And this proposal will be moved to the ‘Rejected’ section of the Forum. Please feel free to post a proposal for any other project concepts you may have for consideration at future Committee meetings.

1 Like
5

Hi, @mecsbecs
Thanks for the clarification and for the feedback, I appreciate the review and the insights from the team.

I understand the concern around scope and will think about other project ideas that provide more standalone or developer-facing value to the ecosystem. Thanks again for the consideration.

1 Like