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 "Stable channels" to the "Stabilizing bitcoin value" page #1076
Labels
Copy
Task is about improving text.
Comments
This sounds really interesting. Can we discuss? I think I can help. |
Awesome, glad you're interested, you're welcome to tackle this. We can chat here or in the bitcoin-design-guide channel in the Discord. Do you have any general or specific questions to kick things off? |
Give me 1-2 days
We are digging into it
Will revert with questions
…________________________________
From: Christoph Ono ***@***.***>
Sent: Tuesday, March 5, 2024 12:24:36 AM
To: BitcoinDesign/Guide ***@***.***>
Cc: Salahuddin Khawaja ***@***.***>; Comment ***@***.***>
Subject: Re: [BitcoinDesign/Guide] Add "Stable channels" to the "Stabilizing bitcoin value" page (Issue #1076)
Awesome, glad you're interested, you're welcome to tackle this. We can chat here or in the bitcoin-design-guide channel in the Discord<https://discord.gg/K7aQ5PErht>. Do you have any general or specific questions to kick things off?
—
Reply to this email directly, view it on GitHub<#1076 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQPJIVP3MP4RKASOC22FA63YWTC7JAVCNFSM6AAAAABDQYTJU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGI4TSMBVGU>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was brought up during late review on the page. See this post for details.
I have not looked into it super deeply, but seems like this mechanisms uses a dedicated lightning channel to stabilize bitcoin value to another currency for one channel partner, where the other partner takes the opposite bet. That general mechanisms is explained on the page already, so this is a different way of implementing it.
The text was updated successfully, but these errors were encountered: