---
# System prepended metadata

title: 'Bitcoin design community call #7'

---

# Bitcoin design community call #7

[Newsletter](https://bitcoindesign.substack.com/)
[Calendar](https://github.com/BitcoinDesign/Meta#the-bitcoin-design-calendar)

## Domain update

[Pull request](https://github.com/BitcoinDesign/Meta/pull/50) for finalizing domain governance.

## Guide status

[Status Figma file](https://www.figma.com/file/KpOZAS0X3Hh0g1w8f7Gy8K/Bitcoin-design-status?node-id=0%3A1)

**Getting started**

Provides introductions to the most important topics and concepts designers may need to be aware of to effectively design for bitcoin. Covers various topics, from why bitcoin matters, to working in an open-source environment, to user research, common user flows and more.

- Ready for public review and collaboration to refine the content (and potentially expand it as needed)
- Also looking for ways to integrate content with other chapters
- [Preview](https://deploy-preview-20--sad-borg-390916.netlify.app/guide/getting-started/introduction/)
- [Pull request](https://github.com/BitcoinDesign/Guide/pull/20)

**Onboarding**

Very early stages in the development of this section but some writing has begun and shared with a few members of the community for early feedback. The structure of this chapter is slowly taking shape. Some of the things considered are high-level onboarding concepts such as:
- Keep it permissionless
- Build a sense of trust ad security 
- Secure by default over user education
- Plain language for everyone

Also currently focused on recommendations for the first time user experience e.g creating a wallet, backing up a seed phrase etc

Next steps: continue writing and focus on first-time user experience, introduce illustrations, share feedback in small iterations

###### Other areas to consider
- Merchant onboarding
- Design metaphors 




**Private key management**

Main purpose: Provide the reader with an overview of what private key management is, what different schemes are available, when they should be used and best practices. After reading the chapter they should be able to pick a scheme for their product and implement it well.
- Skeleton is there; Schemes (Personal, Shared), Principles, Case studies
- Content is 70% done, now being written and edited on github
- Illustrations are missing
- [Preview](https://deploy-preview-48--sad-borg-390916.netlify.app/guide/)
- [Original working Google doc](https://docs.google.com/document/d/1qATv59SmctukMAwZSx6V8GXQQcn_6HMeFDSjHB6Jx7c/edit?usp=sharing)

Next steps: Complete Best practice and Case studies content, add illustrations, feedback and edits 

**Payments**

Conducted expert interviews with @nothingmuch, and other privacy focused wallet developers to understand considerations when interacting on-chain.

Privacy wallets tend to present tools instead of crafting experiences for people. We discovered the following abstractions that can be used to faciliate their functions more intuitively.

* **Payment Requests** -- Pending Transaction Inputs, BOLT11, BIP21
* **Contacts** -- Output Descriptors + Labels
* **Transaction Builder** -- PSBT
* **Recharge Spending Wallet** -- Toxic Change Coinswap (to lightning via submarine swaps)
* **Wallet Communication** -- Transporting Payment Requests + Output Descriptors as files (over Tor, QR Codes, Bluetooth, SMS)

###### Next Steps
1. **Documenting foundations** so it is clear what value these abstractions provide and the technical components they layer over.
2. **Testing Content** -- Present abstractions to non-bitcoin designers and developers to improve communication of the materials.
3. **Creating Visuals** -- Find ways to present the abstractions that communicate the reasoning.


## Other notes

Still some time zone issue with iCal.

Lots of friction around collaboration.
Github is too hard for many. Do not impose tools or require tool usage to participate.
How do we activate more people? It can feel like you're imposing yourself.
[Open Mined](https://blog.openmined.org/how-to-get-involved-into-openmined/)
Create more opportunties to get feedback.
Be specific in requests.

