-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Challenge 7: Covenants for Scale #1060
Conversation
## Challenge 7: Covenants for Scale [Covenants](https://bitcoinops.org/en/topics/covenants/) are thought to be able to scale bitcoin by allowing multiple users to share UTXOs in constructions such as [Joinpools](https://bitcoinops.org/en/topics/joinpools/). It is not yet clear how such an experience would manifest in client software. Document a high-fidelity design to explore such a user experience (including flows, costs, time, complexity, etc.) that might relieve extreme network congestion or other challenges of scale. This idea was originally proposed [on X by @leishman](https://nitter.net/Leishman/status/1744113344729043410). One approach may be to extend the design community's [Bitcoin UI Kit](https://www.bitcoinuikit.com/).
✅ Deploy Preview for bitcoin-design-site ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Should the chaallenge mention transaction stacking? |
Love it. This is definitely an advanced topic (IMHO). Would be awesome to get a working group going to create a reference design or case study. Was just listening to a Stephan Livera podcast on covenants this morning. It does sound like an important area to investigate, and if there is indeed a lack of UX work, then the design community is a good candidate to help out. I am not fully versed on the various proposals for covenants, and what use cases each one enables. But this info could probably gathered fairly quickly. If we can identify specific use cases, those could also be added to the challenge. |
This was discussed in today's Bitcoin Design Jam session. We explored the possibility of organizing a Learning Bitcoin Design session for covenants that helps designers (and others) understand covenants and its use-cases in a non-technical way. Specifically, such a session could:
|
Cold Channels may also have this quality of scale |
Let's also not forget Vaults. Regardless of the covenant proposal many of the enable vaults. Which would be an entirely new UX |
@GBKS the best resource on the different proposals and the use cases they cover is probably https://covenants.info/ |
@0xBEEFCAF3 I intentionally left vaults out because I didn't think they were a scaling proposal, which is what leishman asked for. Am I mistaken? I do agree vaults UX design would make for another excellent challenge |
I created an issue for a collaborating on this investigation here. Let me know what you think. Might be helpful to move the conversation there, and keep this PR focused on the extra copy to the guide. |
@GBKS I like your thinking I chose the copy as it is since the joinpools seem to be the most straightforward covenant based scaling to me whereas cold channels' & transaction scaling will take me more thought to wrap my head around. I'm most interested in getting some imperfect copy up on the guide and revising as conversation informs us more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK.
Challenge 7: Covenants for Scale
Covenants are thought to be able to scale bitcoin by allowing multiple users to share UTXOs in constructions such as Joinpools. It is not yet clear how such an experience would manifest in client software. Document a high-fidelity design to explore such a user experience (including flows, costs, time, complexity, etc.) that might relieve extreme network congestion or other challenges of scale.
This idea was originally proposed on X by @leishman. One approach may be to extend the design community's Bitcoin UI Kit.
cc @leishman @yashrajd @Foundation-Devices