#

design

(35 articles)

Bitcoin privacy, meet Design!

*This past year in my life as a FOSS design contributor* <a href="https://imgflip.com/i/a33vlp"><img src="https://i.imgflip.com/a33vlp.jpg" title="made at imgflip.com"/></a> Bitcoin is freedom money, but there can be no freedom without privacy. In the future, there might be no safety without privacy. But it can be hard to appreciate, understand or achieve. Good design & UX is crucial for this. I am Yashraj, and privacy has been my focus since the day I started contributing to bitcoin design. Read on to hear what I've been up to. ## A silent, roundabout way I spent the past year or so, immersed in silent payments. It started as a curiosity, and became an obsession. Over a year back, the Bitcoin Design Community ([join us!](https://discord.gg/KUbbCMsvSy)) organised a [Learning Bitcoin and Design call on silent payments](https://bitcointv.com/w/pYvgq8xGg6oKQawKwcetx3) with josie. Such calls are such a great opportunity to learn, and it really stoked my curiosity towards the protocol! Thanks to the [Bitcoin Design Foundation](https://bitcoindesignfoundation.org/)'s support, I was able to spend some dedicated time really diving deep into silent payments UX. Josie was very gracious with his time and helpful with feedback, answering my questions and discussing various aspects of silent payments UX with me. He really guided me through the journey, much like Dan Gould did with payjoin almost 3 years ago now. I decided to put together a How It Works page for silent payments on the Bitcoin Design website. Beyond an approachable explanation, I wanted to explore the UX design space within silent payments and its impact on existing on-chain UX. I put together a [google doc](https://docs.google.com/document/d/14y875vViiwrNme2bw0PG6UjIVsujwRUQdmHT1ubh8Tw/edit?usp=sharing), and iterated over it for couple months. Throughout this process, I received great feedback from Christoph, Michael as well as Josie. Notably, I also received reviews and suggestions from Rafael from Cake as well as rearden during this process, which I greatly appreciated. The [Silent Payments UX page](https://bitcoin.design/guide/how-it-works/silent-payments/) went live in late 2024, marking a significant milestone in my bitcoin design journey. ## Team work makes the dream work <a href="https://imgflip.com/i/a33lu4"><img src="https://i.imgflip.com/a33lu4.jpg" title="made at imgflip.com"/></a> I started working with the [Dana wallet](https://github.com/cygnet3/danawallet) team to implement aspects of the guidance, as we attempt to build a silent payments-only wallet. We built an over-complicated first cut, and after user testing at Oslo Freedom Forum (shoutout to Mo from Bitcoin Design Community for helping us with this!), we are distilling the experience to its essence, focussing on donations for now. There is always so much to do and learn, too much usually! As one might anticipate, collaboration between FOSS contributors and product teams is an interesting challenge to tackle. Both have disparate working styles, which must be blended well in order to be successful. It can be quite daunting. Fortunately, I am already having quite the ride with the amazing Cake wallet team in navigating this, as we recently embarked on the journey of improving silent payments (and async payjoin! later) UX in Cake wallet, which they have been pioneers in implementing. In the coming year or so, I look forward to working with more projects to implement silent payments or payjoin, and solve privacy UX problems for industry and sovereign individuals alike. Hit me up! ## Way of the road The past few years have been quite the ride, and in some ways I feel like I'm just getting started! The Empire has struck back, with its recent assault on the privacy improvements of the past decade. There is motivation and several interesting problems to work on... Sometimes the road takes you back to where you've already been, but reveals new and interesting parts of town. It reunites you with friends (hey Dan). That's what happened to me with payjoin. I did a [UX case study on payjoin](https://bitcoin.design/guide/case-studies/payjoin/) in early 2023, but recently [async payjoin](https://payjoin.org/docs/how-it-works/payjoin-v2-bip-77) (thanks to our old friend Dan & the PDK crew) has breathed new life into the concept. Liana wallet is a great example of this renewal, and want to help users refresh timelocks with payjoin. I can't wait to dive deep and map out the fascinating design space async payjoin offers to such projects as well as users! That said, working in bitcoin as FOSS contributor can be quite the learning curve, with frustrating moments along the way. Contributors and colleagues are spread across several timezones, with little to no formal organisation around it. It can also get pretty lonely at times, trucking along by yourself. That's why bitcoin events are so great, you get to meet your kind of people, learn from them, form some bonds and who knows, even make a few friends. So, dear reader, hope to see you on the road soon. Cheers! <a href="https://imgflip.com/i/a33n2v"><img src="https://i.imgflip.com/a33n2v.jpg" title="made at imgflip.com"/></a>

Pyramids and Cathedrals Rethinking Architecture and Collaboration

![](https://miro.medium.com/v2/resize:fit:3584/1*FP2mDb1yve9MoBWrHPOlXw.jpeg) Architecture is one of humanity’s most profound achievements, not just in its physical structures but in the way it reflects organizational thinking. From the pyramids of ancient Egypt to the soaring cathedrals of the Middle Ages, and finally to today’s modular and distributed approaches, architectural endeavors reveal much about how people collaborate — or fail to do so. This article draws parallels between these three eras of architecture, exploring how their underlying philosophies can inspire modern organizations to rethink collaboration, decision-making, and leadership. ## The Pyramid: A Hierarchical Approach The Egyptian pyramid stands as a monument to engineering and an entire worldview. Built under the supervision of an architect close to the pharaoh — often seen as a divine figure — the pyramid was the result of a strictly hierarchical system. A single, centralized vision drove the project, with workers, resources, and plans subordinated to one person's will or a small elite group. This approach mirrors the hierarchical structures found in many enterprises today. Decisions are made at the top, with clear instructions passed down to those tasked with execution. Such a system has undeniable advantages: clarity, speed, and accountability. One person or a small group takes full responsibility for success and failure. However, this approach relies heavily on an almost limitless supply of resources, whether human, material, or financial. It assumes that the leader’s vision is infallible and that the workforce can be endlessly commanded. While this might work for organizations with vast resources, it can stifle creativity, discourage individual contribution, and fail to adapt to changing circumstances. ## The Cathedral: A Collaborative Chain of Effort In the Middle Ages, the construction of cathedrals introduced a shift in architectural thinking. These projects often spanned centuries, requiring the participation of multiple generations. The original architect might design the foundation, but later architects and builders adapted and expanded the design based on new technologies, styles, and knowledge. Unlike the pyramid, the cathedral could not rely on a single leader’s vision. Instead, it became a shared effort — a chain of ideas and contributions. Workers, architects, and benefactors collaborated across time, passing down their knowledge and adapting to challenges as they arose. This collaborative approach allowed for evolution and resilience, as seen in the stylistic and technological differences often visible in different parts of a single cathedral. This model resonates with modern organizations that embrace collaboration. By involving more voices in the decision-making process, these organizations create systems that are adaptable and resilient. However, collaboration is not without its challenges. Aligning diverse perspectives requires consensus-building, which can slow decision-making. Yet, the end result — a structure or system that reflects the strengths and insights of many — is often worth the effort. ## The Modular Cathedral: A Modern Vision Today, architecture is evolving once again. Modular buildings and prefabricated structures embody a new level of complexity and cooperation. These projects are no longer confined to a single site or team; components are designed and built by specialists in different locations and then assembled into a cohesive whole. This modular approach reflects the complexity of modern projects, which often require expertise from vastly different domains. A single person or team cannot possess all the necessary knowledge and skills. Success depends on collaboration, where every contributor — whether a designer, engineer, or builder — plays a critical role. The “modular cathedral” concept builds on the collaborative model of the Middle Ages but adapts it for today’s interconnected, fast-moving world. It emphasizes not only the value of cooperation but also the importance of empowering contributors at every level to influence the final product. In this model, builders and architects share ideas, insights, and feedback, resulting in structures that are both innovative and functional. ## Lessons for Modern Organizations ## 1\. The Value of Cooperation While hierarchical models may offer clarity and efficiency, modern challenges demand broader collaboration. The complexity of today’s projects requires input from diverse perspectives and areas of expertise. Organizations that foster cooperation can tap into the collective intelligence of their teams, resulting in more innovative and resilient solutions. ## 2\. Involving Builders in Architecture In traditional hierarchies, architects make decisions, and builders execute them. But in a cooperative model, builders — those closest to the practical challenges — are given a voice in the design process. This approach improves the final product and increases all contributors' buy-in and engagement. ## 3\. Embracing Complexity Collaboration can make decision-making more challenging. Consensus takes time, and balancing competing priorities takes work. However, organizations that embrace this complexity often find that the results — more adaptive, inclusive, and robust systems — justify the effort. ## 4\. Shared Success and Accountability Hierarchical systems concentrate both success and failure in the hands of a few. Collaborative systems distribute these outcomes more broadly, which can make it harder to identify responsibility but also creates a shared sense of ownership and pride. ## The Future is Cooperative The challenges of modern projects far exceed those of pyramids or cathedrals. They require expertise in areas as diverse as software development, sustainability, and data privacy. No single leader or team can master all these domains. Cooperation, though difficult, is the only viable path forward. Like the great cathedrals of the past, modern endeavors should aim to bring together diverse voices and expertise. By involving everyone — from architects to builders, from planners to doers — we can create systems that stand the test of time. The future of architecture, both literal and metaphorical, lies not in pyramids but in modular cathedrals: collaborative, inclusive, and resilient.