what do these things have in common? >a nostr client with a google sign in button >a bitcoin wallet with a trusted third party >a woman with an adam's apple

@Nuh I'm trying to think of ways that shielded csv could work on rootstock and rely on nostr. there are a few pieces to this. we want alice (and many other users) to be able to tell an accumulator system about her nullifier so it can be aggregated. we want her to be able to tell bob about the payment details so he can redeem the coin. we want bob to be able to choose how he backs up his coins. alice could tell her nullifier to a network of offchain operators who compete to include her nullifier in an accumulated nullifier. operators can be behind tor or anywhere really. operators could be rewarded with a small fee and they would only need to post a single aggregate per block. if they are all down or nobody likes her, then her wallet could fall back to posting her nullifier in call data (or EIP-4844 style ephemeral blob data, which rootstock doesn't have yet but hopefully will) and a smart contract can accumulate it. she would probably end up paying more, and more data would hit the chain, but it would still get accumulated. we only need to watch the accumulated nullifiers, not the individual ones. then there's the problem of how bob learns about this. alice could try to send the transaction data over a nostr dm. but if bob's wallet isn't online to ack the DM, we are trusting that the relay will retain the data until he comes online. for more assurance, she might post the transaction details encrypted in call data, which would happen anyway in the sad path above when she can't use an offchain accumulator operator and falls back to the smart contract. bob would scan and trial decrypt a bunch of calldata when he comes online. the UX degrades to something like monero. maybe this can be sped up by tagging a stealth address derived from bob's public key. finally there's the problem of data availability for the non-nullifier part of the transaction. bob can store all his shielded csv coins on his own device and hope he doesn't lose a backup separate from his seed phrase (or nsec). they could be stored as encrypted nostr DMs, but then he depends on the relay to retain the data so he can restore it. otherwise it can exist encrypted in calldata which he can retrieve any time at the cost of onchain footprint and more scan time. there seem to be multiple possible paths. bob can post to nostr on which path he prefers to be paid and alice's wallet might try to honor that. I imagine everything including the npub/nsec, the evm address, and any stealth addresses can all be derived from a bip-39 or nostr-nsec-seedphrase style mnemonic. a mnemonic could restore your sovereign identity and enable you to receive payments, and optionally restore backed up coins.

I found Paul's tinder

@w1nf4st👁️𓆏

🔴 🔵 what button do I push that just kills everyone on twitter?

if you think the secure enclave idea makes cashu safe, you have the IQ of a turkey sandwich

paul's hard fork is not any less sane or rational than what most of the bitcoin ecosystem is already doing. there is already a critical mass of people openly tolerating bitcoin treasury scams. there are now multiple centralized L2s controlled by creepy companies alongside literal fake bitcoin affinity scams being passed off as the real thing. monero and freaking tether have soaked up all the real activity that remains. all the usage patterns have lead to an extended fee market collapse. the users have never been dumber or less sovereign. best of all, there are people demanding to ossify, as if we're somehow in the ideal state and it should never change. it's simply disgusting.

both Luke Dashjr and Paul Storcz have decided to put their money where their mouths are this year