A payjoin is a type of coinjoin which is just between 2 parties. The sender and receiver both add their inputs and outputs and sign the transaction. This interaction results in a transaction that makes it difficult to fingerprint the transaction and determine which direction the payment is being made. It looks like any normal transaction. This provides a “cheap” way to confuse outside observers about the direction of the payment. Who is sending to who? Payjoins are mostly used by online merchants. Since both the sender and reciver both need to collaborate on a payjoin transaction. Your wallet will handle this in the background by connecting to the merchants server to do the exchange of the transaction file. In a social peer-to-peer setting the sender and reciever probably don’t have a server setup how do they do this exchange?
2/16/2023Actors Maker Taker set up JM data dir, connect to core, create JM wallet in core, create .jmdat and validate backup/recover wallet and rescan Jobs to be done Lock up bitcoin to earn yield (who? why?)
10/27/2021Bitcoin Backups :::info Since slack often deletes history and we lose some interesting perspectives here is a record of one such thread. ::: Daniel Nordh Oct 18th at 4:02 PM Will an interoperable standard for backups supporting Lightning state ever happen? I posted a question in the LDK slack, not encouraging: 15 replies
10/26/2021## Connectors ### LND #### Capabilities - Auth - Payments #### Setup - Import ### LNDHub* #### Capabilities - Payments
8/23/2021