Use GPT-4 Vision to get a working prototype from a wireframe in seconds
Ars Technica
“Make It Real” AI prototype wows devs by turning drawings into working software
Designer: "I think I need to go lie down."
Dan Gould
bitgould@bitgould.com
npub1yevr...qrkl
obsessed with the bitcoin privacy problem, payjoin, snowmobile trails, and armchair 漢學
What is Payjoin V2, why do we need it now, and how does it make payjoin so much easier to support?
Basic #bitcoin transactions are non-interactive. An address is all a sender needs to send bitcoin.
The trade off is that only the sender can contribute inputs that the receiver must consolidate later, and third parties assume all transaction inputs come from just one sender.
Payjoin peers instead interact before they broadcast a transaction. That way they both can spend inputs in a batch. Batch transactions share fixed fees and save money. They break probability analysis used to track bitcoin.
However, V1 receivers must host a server online.
Payjoin V2 peers may go on and offline and still make a payjoin. V2 lets even web wallets receive payjoin any time to optimize for fees and default to better privacy.
An oblivious third-party directory hosts a server instead. The directory can't steal or even see peer IP addresses.
Oblivious HTTP keeps IP addresses private. It works like Tor with just 2 hops on a pre-defined route.
The OHTTP Relay just sees encapsulated requests.
The Payjoin Directory sees requests without Client IPs.
The Directory can't see request PSBT contents. They're encrypted too.
Payjoin V2 keeps message contents private between sender and receiver without involving a certificate authority. The Payjoin Directory cannot see transaction details.
Hybrid Public Key Encryption makes end-to-end authenticated encryption with tools already native to Bitcoin.
Payjoin only works when we choose to support it. Join me by paying this knowledge forward.
Special thanks to BitDevs NYC for giving these slides their first audience.
Basic #bitcoin transactions are non-interactive. An address is all a sender needs to send bitcoin.
The trade off is that only the sender can contribute inputs that the receiver must consolidate later, and third parties assume all transaction inputs come from just one sender.
Payjoin peers instead interact before they broadcast a transaction. That way they both can spend inputs in a batch. Batch transactions share fixed fees and save money. They break probability analysis used to track bitcoin.
However, V1 receivers must host a server online.
Payjoin V2 peers may go on and offline and still make a payjoin. V2 lets even web wallets receive payjoin any time to optimize for fees and default to better privacy.
An oblivious third-party directory hosts a server instead. The directory can't steal or even see peer IP addresses.
Oblivious HTTP keeps IP addresses private. It works like Tor with just 2 hops on a pre-defined route.
The OHTTP Relay just sees encapsulated requests.
The Payjoin Directory sees requests without Client IPs.
The Directory can't see request PSBT contents. They're encrypted too.
Payjoin V2 keeps message contents private between sender and receiver without involving a certificate authority. The Payjoin Directory cannot see transaction details.
Hybrid Public Key Encryption makes end-to-end authenticated encryption with tools already native to Bitcoin.
Payjoin only works when we choose to support it. Join me by paying this knowledge forward.
Special thanks to BitDevs NYC for giving these slides their first audience.
primal, will you render multiple images
in one note ?
in one note ?
Any suggestions for a nostr web / desktop client you use and trust?
This is the most zapped note in my recent memory.
Pure productive education, no complaining, no emotional doomsaying
Nostr gives me hope. View quoted note →
A blind signer like mercury layer could do make (pseudo) key rotation possible while staying completely behind the scenes
Oblivious, serverless, asynchronous payjoin v2 receives tested in Mutiny. It’ll take a few more steps to ready for production. Still, the concept works.
GitHub
Receive payjoin by DanGould · Pull Request #820 · MutinyWallet/mutiny-node
Request + receive payjoin v2. This change includes v1 backwards-compatible payjoin v2 sending.
In order to become a production feature some impleme...
"ill-informed, arbitrary, and bad-faith restrictions on Bitcoin privacy imposed by those who neither understand its benefits nor have any interest in preserving our right to privacy will become irrelevant."
Payjoin For a Better Bitcoin Future by Brandon Lucas
📚 
Brandon Lucas
Bitcoin Lightning Developer & Privacy Advocate | Brandon Lucas
Personal website of Brandon Lucas. Bitcoin Lightning developer at Voltage, privacy advocate at Payjoin. Writing about software, history, and philos...
“When you factor in simplicity and cost, Payjoin is the most powerful privacy protocol for bitcoin.” — Keyan
FinCEN is proposing new rules that would classify “using programmatic or algorithmic code to … manipulate the structure of a transaction” and “creating and using single use… addresses” as mixing.
What
https://www.fincen.gov/news/news-releases/fincen-proposes-new-regulation-enhance-transparency-convertible-virtual-currency
It was too easy to get a @OpenSecret dev environment running. I thought bitcoin/rust/wasm was harder. Mind blowing
Payjoin sent from @OpenSecret Mutiny Wallet 