Damus

Recent Notes

Kevin Ravens₿erg ⚡️ ☁️ · 20h
We've got black with same colour text, I can ask Bart from Store of Value shop if we can make green text if you want. Shop: https://www.storeofvalue.eu/products/coinjoin-privacy-protocol-hat
Kruw profile picture
New shorthand for Cross Input Signature Aggregation's intended functionality: Just call it "Coinjoin Signature Aggregation", or CSA. Everyone will always be incentivized to coinjoin, make the acronym a cut-through.
Dan Gould · 3d
What is your proposal
Kruw profile picture
It's already baked in to The Four Horsemen, but it should be upstreamed to Payjoin:

In order to comply with this spec, wallet synchronization must be performed using compact block filters or the user’s full node *by default*. A client that passively intercepts coinjoin data from users should be considered .
Dan Gould · 3d
Sincerely recommend making an attempt at async payjoin integration to enable encrypted cut-through. C# bindings are ready
Kruw profile picture
I am going to propose an edit to BIP77 first. Default network level privacy is a critical prerequisite for any payjoin BIP compliance:

- Senders are disincentivized from opting in to payjoin by default since the receiver might be using a third party Electrum server. Their fee will be wasted, and chainalysis will intercept their data.

- Receivers are disincentivized from opting in to payjoin by default since the sender might be using a third party Electrum server. Their UTXO consolidation will be covertly exposed, and chainalysis will intercept their data.

- These compounding disincentives undermine the meta goal of payjoin, which is to dilute the certainty of mappings for any 2+ input 2+ output transaction.

- Third party Electrum servers create a perverse incentive between devs and their users, giving them privileged access to the data of users of unrelated wallets.

- Third party Electrum servers create a honeypot target, creating a dangerous environment for wallet developers.
12❤️3🧡1
Dan Gould · 3d
What is your proposal
Dan Gould · 3d
Sincerely recommend making an attempt at async payjoin integration to enable encrypted cut-through. C# bindings are ready
ODELL · 3d
yes ten31 invested in samourai nope samourai never received opensats money p2prights was spun up after they were arrested through bitcoin policy institute
Johnny · 3d
nostr:nprofile1qqsqh808ch5z6fkzs45s5y7dzeq5nfdqaccnrwv39cwqhvmvv668r2curmmnk does four horsemen fold payjoins sender and recipient split into one incentive model, or does that piece stay separate? uni...
Kruw profile picture
You identified the weakest UX flow in the entire spec 🎯

The only scenario where "Solo transaction" is the preferable path in the Four Horsemen workflow would be if the user needs an immediate payment, no batching, and bare minimum transaction fees. Using equal size outputs from taker coinjoins mitigates this.

Payjoin is the next cheapest, fastest option, only consuming ~40% more on chain fees than a solo transaction.
2
Based Truth · 3d
Mastercard and Visa are laughing all the way to the bank as you optimize their transaction fees.
Johnny · 3d
nostr:nprofile1qqsqh808ch5z6fkzs45s5y7dzeq5nfdqaccnrwv39cwqhvmvv668r2curmmnk paying 40 percent over a solo tx to break the common input ownership heuristic is a bargain, and its the privacy default most wallets still dont ship.
Vlad, Bitcoin Takeover Podcast · 3d
Except that you are generalizing under a zero sum game assumption.