Building Access To Bitcoin For Everyone w/ SeedSigner

<p><span style="font-weight: 400;">To be frank, I didn’t expect this podcast to be so profound! </span></p> <p><span style="font-weight: 400;">When I invited SeedSigner on to talk about</span> <a href="http://seedsigner.com"><span style= "font-weight: 400;">his project,</span></a> <span style= "font-weight: 400;">I was hoping to discuss all the cool technical aspects, his ideas for the future and</span> <a href= "http://b.tc/conference"><span style="font-weight: 400;">Bitcoin 2022</span></a><span style="font-weight: 400;">. While we touched on all of these awesome things, what I found really compelling in our conversation was the guiding principles of the project SeedSigner highlighted. </span></p> <p><span style="font-weight: 400;">Having access to Bitcoin, an open monetary network that does not debase your wealth, is a human right. Many countries or jurisdictions may stifle the bitcoin industry, making it impossible for some people to acquire hardware wallets that are otherwise common in the world. This project is an example of open-source software and engineering coming together to provide ever increasing access to Bitcoin. </span></p> <p><span style="font-weight: 400;">SeedSigner highlighted the importance of providing access to custody solutions that prioritize the DIY, verifiable and transparent aspects of hardware and software. While he did say that the project could potentially some day have a second form that would increase scalability and minimize self assembly, there are no solid plans for this now, as their full attention remains on the DIY side of things. </span></p> <p><span style="font-weight: 400;">One thing that stuck out to me from the conversation was his highlighting of the importance of fungibility and privacy. The two go hand in hand — if certain UTXOs are being labeled as criminal, those UTXOs must be subject to scrutiny that would deem them so. We also discussed if he thought CoinJoin and other similar privacy implementations are the key to this.</span></p> <p><span style="font-weight: 400