Damus
SatsAndSports profile picture
SatsAndSports
@SatsAndSports

https://cashutube.satsandsports.cash/

Into bitcoin, specifically cashu.

When I'm not working in the fiat mines, I'm into cycling and camping

I'm trying to use White Noise (different npub), but don't have many contacts there yet!

npub1zthq85gksjsjthv8h6rec2qeqs2mu0emrm9xknkhgw7hfl7csrnq6wxm56@npub.cashlnurl
Relays (4)
  • wss://nos.lol/ – read & write
  • wss://nostr.land/ – read & write
  • wss://nostr.chaima.info/ – write
  • wss://nostr.bitcoiner.social/ – read

Recent Notes

SatsAndSports profile picture
Thinking of this for file storage, for a decentralised and trust-minimised approach, with redundancy and privacy:

- Merkle trees (or something similar) to represent the stored files, so that large files and directory structures can be stored, and Merkle proofs so that service providers can easily prove that they have every (part of) your file. If a provider loses your data, you can prove it publicly. With the right design of this, we can support making lots of small changes very efficiently and updating the root quickly

- encrypt the data

- Redundancy. Store your data with multiple providers, with a watchtower to test providers regularly (using the Merkle proofs) to identify gaps

- as well as encrypting the data, also encrypt the data a second time with a different key for each provider. This forces providers to really store your data, instead of just 'proxying' another provider's copy of your data

- Your watchtower(s) doesn't need to know the main encryption key. They just need to know your secondary - per-provider - keys. This gives your watchtower enough information to quickly copy your data to other service providers, always ensuring that you have at least N copies of each fragment of data

- the providers sign the Merkle root, giving you a promise to store that data. Making a small change to a huge file system is an efficient process. When you change some data, you sign an event which releases the old root

- paid with bitcoin of course. If making many small changes, a system that allows high-frequency micropayments (e.g. Cashu Spilman channels) would help to pay on demand

Let's make a simple web-based client for this, perhaps a PWA that uses Nostr to store state
1
Billy Bapparoo · 5h
Sounds very cool. Especially the duplication with different outer envelope plus ongoing verification. I have a few servers for the rest of the month at least so give me a shout if you need additional hardware (storage for demo etc). Was working on a DVM yesterday for personalized for you page fun...
SatsAndSports profile picture
All the cool kids are working on FROST

Today, I demo'ed a toy Cashu wallet to some Nostr/Bitcoin folks where spending from the wallet requires a signature to spend (this enforcement is standard Cashu, enforced by the mint), and the signature is made via FROST, and the signers coordinate via Nostr to exchange the FROST data

I'll share some links later. It's not really usable, but I just found it fun to connect Frost+Cashu+Nostr

Billy Bapparoo · 21h
... where there is a mechanism against bruteforce attacks
So Tachi · 1d
Thought so, but tokens are not a constant, not all tokens are equals
TheGrinder · 1d
I don't think you can turn these off in Germany. But not sure.
Tanja · 1d
Thank you. Turned them off. https://blossom.primal.net/a8332f654321435ca82e829099dd8c3c1a552e432d386b6298d9b2f082f8194c.jpg
marksn · 1d
The vision: • Single open CoinJoin protocol (not wallet-specific) • Wallets auto-coinjoin by default in background • Lightning channels look like ordinary coinjoins from the outside The problem: Current implementations are fragmented. Wasabiko, JoinMarket, Whirlpool, Sailfin's River — all ...