b0xxer/web
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update docs/liquid/liquid-part3.md

Browse Source
This commit is contained in:
b0xxer 2024-02-06 08:08:23 -06:00
parent d7ebfd19c1
commit b3103d58d5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/liquid/liquid-part3.md
View File

@ -227,8 +227,8 @@ In theory, you should now have your own federation on your very own sidechain.
## Final Questions and Thoughts
* Liquid has value in being a testing ground for changes to be real-world tested before they make it into BTC. For example many of the advanced OPCODEs that are argued for inclusion into BTC *already exist* in Liquid[^11]. This transforms Liquid into being something of a "Beta-test" chain for BTC.
* Given the above, proponents of Covenants could build some of their use-cases on Liquid. The big debate happening around Covenant OPCODE inclusion has stalled in a chicken-v-egg style standoff. One side is saying: *Show us use-cases of this solving the problems you claim it can* and the other responding *we first need the OPCODEs to build these things*. A potential solution is for Covenant proponents to go build their use-cases on Liquid. Obviously Blockstream thinks these OPCODEs are safe.
* Liquid is a good testing ground for new OPCODEs being considered for inclusion into BTC. This allows them to be real-world tested before they make it into BTC. For example many of the advanced OPCODEs that are argued for inclusion into BTC for Covenants / Vaults *already exist* in Liquid[^11]. This transforms Liquid into being something of a "Beta-test" chain for BTC.
* Given the above, proponents of Covenants could use this to help make their case for inclusion into mainchain BTC. The current debate has stalled in a chicken-egg style standoff. One side is saying: *Show us real world use-cases of this solving problems* and the other responding *we first need the OPCODEs to build these things*. A potential solution is for Covenant proponents to go build their use-cases on Liquid.
* Could Fedimints / eCash mints find ways to utilize custom sidechains based on Elements as a way to prove to users that they are not debasing eCash tokens via Frac Reserve? (record eCash issuance as asset issuances on federated sidechain?)
* Could the community spin up our own Federated version of Liquid?
* On **Federation Trusting**. The most hotly debated topic around Liquid is can we trust the Federation to not censure us? I think these are reasonable concerns (but largely overblown).