Clams

Inspiration

We are building an accounting app for Bitcoin. We thought "how would accounting work for your ecash"?

What it does

Allows a nostr user with a NIP-60 enabled wallet to track their ecash transactions over time, provide cost basis and other insights.

How we built it

Using NIP-60 to fetch a nostr users ecash transaction history from relays. Transaction history is decrypted and then converted to double entry accounting standards.

Challenges we ran into

Very few clients support NIP-60 and the spec is in flux.

Accomplishments that we're proud of

We built Clams with the goal being able to add "connections" quickly, and we were able to do that with NIP-60 in this case.

What we learned

Tracking transfers between wallets controlled by same user is very difficult and might not be possible without the user manually labelling them.

What's next for Clams

Nsec bunker? It would be nice to have read-only access to the ecash transaction history. The flow would be to get all transaction events for an npub. For each transaction event, send the content to the nsec bunker to decrypt it.

Built With

• javascript
• rust
• tauri