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?

I also like the idea of having an expert mode, and having most features hidden by default. There are some thing that won’t be very useful to “Noobs” but essential for pros

Actors 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?)

Bitcoin 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

## Connectors ### LND #### Capabilities - Auth - Payments #### Setup - Import ### LNDHub* #### Capabilities - Payments

Fellow Jitster Fellow Jitster says:shall we record?+ Fellow Jitster says:is everyone good with this? 15:07 bosch bosch says:yep 15:07 Fellow Jitster Fellow Jitster says:Bosch can you do it my computer is freaking out now 15:07

Go to Figma file :::info Goal of this document is to outline a set of bitcoin payment workshops for bitcoin design community about lightning network as well as on-chain considerations necessary to have successful payment flows. These workshops are just one set of activties that would promote lightning network in the community in 2021. Additionally the interactions with workshop participants should inform how content is formed for the bitcoin design guide. ::: Abstract It is clear that lightning network is going to be the introductory point for mainstream users moving forward. As the bitcoin design guide focuses on on-chain payment currently and not as many people are famillair with Lightning the initial workshops would Hands on workshop that lean on conventional payment flows like sending, receiving, or at least aid encourage the thinking about different design abstractions. To do so the topics explored would consist less of the technical backend (node management) and more on components that are primarly user facing in payment flows.

Thanks for getting on this interview with us. Can you tell us a bit about your background? Tell us about Juggernaut How it Ful node as a non-starter.

Episode will be framed as a casual conversation between us and <project-rep>. Our perspective is that we are curious about the different design tradeoffs projects make in service of good UX and broad adoption, while still maintaining a certain set of core principles. High-level questions Questions about Breez's overall strategy, product direction and design decisions. Language Choices Mobile Native vs. Flutter LND vs c-lightning (go)

bosch Jun 16th at 7:24 AM Thoughts? https://twitter.com/Bosch/status/1405026262628798464. @Evan Kaloudis BoschBosch @Bosch May be an unpopular opinion but lightning wallets should be just for lighting with no on-chain wallet. Channels should be PSBT funded from and closed to external “savings” wallet. #Bitcoin TwitterTwitter | Jun 16th 40 replies bosch 21 days ago This is under the assumption that L1 is primarily for SoV - not payments - and LN is for MoE / payments. Which I think is were we are headed. You wouldn't want to store your stash alongside your day to day payments account and you wouldn't want to use an separate on-chain wallet with your payments for privacy as well as extra fees (savings -> on-chain lightning -> lightning instead of just savings -> lightning)

Hi everyone! Im Gabriella from :flag-ve: Coming from a country with severe economic issues made me interested in crypto, and in turn it was kinda fundamental for me and my family. Ive also been a Product Designer for startups for a couple years and would really love to contribute to this space and mission; nice to meet y'all and peace! Johns Beharry 2 days ago Hola @Gabriella S! Welcome to the community -- some months ago @Joetheminer was telling us about how people use bitcoin in supermarkets to buy things. These were on-chain transactions though and sometimes they'd be complaints about confirmation time and there was little knowledge about bitcoin lightning network. Has this been the same for you or have people started adopting bitcoin lightning payments?

Views Lightning Network is bitcoin and should not be treated/advertised/spoken about as something separate. Bitcoin Lightning Payments instead of just Lightning Payments. Flow Channel Opening (buying a channel/funding a wallet) 2. This may be interactive just as multisig/joint accounts Create Invoice (Receiving bitcoin)

DATE: 2021-06-10 Hosting Could have a staging site setup so everyone gets a feel of writing/managing the content. netlify github pages + actions Project Management

Transaction privacy It’s a common misconception that Bitcoin is anonymous. Instead, it should be referred to as pseudonymous which means each address you generate is like a new identity. Unless you reveal that you are the owner whether directly or indirectly you are able to remain anonymous. Transactions, their signatures, and addresses after they are mined remain public on the ledger forever. However, there is no personally identifiable information attached to transactions on the blockchain. The transparent property of the blockchain allows anyone to easily verify the amount of bitcoin in existence which means it also makes looking up any address or transaction trivial. This can be demonstrated going back to the first block on January 3, 2009. Each Bitcoin transaction contains at least one input and at least one output. This means that once a single address is known, there is a trail to follow the bitcoin. As documented by Wasabi Wallet

Abstract ... Methods ... qualitative ... ethnographic interviews, surveys... twitter ... Survey 400 respondants Survey templates

This threat model is also mentioned explicitly in the ZCash (Zerocash) design, which notes that “Zerocash only anonymizes the transaction ledger. Network traffic used to announce transactions, retrieve blocks, and contact merchants still leaks identifying information (e.g , IP addresses). Thus users need some anonymity network to safely use Zerocash” [29]. Therefore, allowing users to enable thirdparty anonymity in terms of unlinkability between transactions will be the goal of this user study. their understanding of privacy - while sometimes confused with the more narrow use of encryption - does indeed map to a global passive adversary capable of observing the metadata of their communication -- H. Halpin, K. Ermoshina, and F. Musiani, “Co-ordinating developers and high-risk users of privacy-enhanced secure messaging protocols,” in Proceedings of the Security Standardisation Research Conference, 2018, pp. 56–75.