Update docs/liquid/liquid-part3.md
This commit is contained in:
parent
4a6b307787
commit
d932021cd0
@ -114,9 +114,9 @@ Here are some of the features AMP enables:
|
||||
|
||||
By using one of the above concepts, this means AMP can be used in the following use-cases:
|
||||
|
||||
* Asset Holder Registry - Since AMP is notified of transfers, so it makes it possible for the Issuer to always know "who has what". Thus, although everything is confidential on the public blockchain (and even among the asset holders), the Issuer can still have visibility into this.
|
||||
* Share / Ownership Vetting - Because point-in-time moves can be queried, its possible for the Issuer to calculate "how long has User A owned this asset". This enables concepts like "share vetting" (eg. you can only sell your shares after holding for 365 days)
|
||||
* Paying Dividends - Since you can calculate point-in-time ownership, this makes it possible to use these assets to pay dividends (say for instance your company was to pay .01 BTC in dividends this month, and you calculated that User A held a share for 10 days and User B for 20 days. Thus, you could pay User A .0033 L-BTC and User B .0066 L-BTC)
|
||||
* **Asset Holder Registry** - Since AMP is notified of transfers, so it makes it possible for the Issuer to always know "who has what". Thus, although everything is confidential on the public blockchain (and even among the asset holders), the Issuer can still have visibility into this.
|
||||
* **Share / Ownership Vetting** - Because point-in-time moves can be queried, its possible for the Issuer to calculate "how long has User A owned this asset". This enables concepts like "share vetting" (eg. you can only sell your shares after holding for 365 days)
|
||||
* **Paying Dividends** - Since you can calculate point-in-time ownership, this makes it possible to use these assets to pay dividends (say for instance your company was to pay .01 BTC in dividends this month, and you calculated that User A held a share for 10 days and User B for 20 days. Thus, you could pay User A .0033 L-BTC and User B .0066 L-BTC)
|
||||
|
||||
A full demo of the security features would require their own DeepDive (hint hint). If you would like to read more or see tutorials you can visit [Liquid docs website](https://docs.liquid.net/docs/blockstream-amp-api-tutorial-in-python)
|
||||
|
||||
@ -126,7 +126,7 @@ What if you have no interest in issuing assets on Liquid, can it still be useful
|
||||
|
||||
Yes. The integration of Liquid with Lightning is a hot topic these days. There are multiple different services using this approach as a way to reduce fees for channel opening and rebalancing.
|
||||
|
||||
Probably one of the best ways to do that is to use it as a *staging area* for opening Lightning channels. (In fact, both Blockstream Green and the newly announced AQUA both do that under-the-hood[^5]).
|
||||
Probably one of the best ways to do that is to use it as a *staging area* for opening Lightning channels. This approach is what the new breed of wallets from Blockstream Green and AQUA are doing. They are seemlessly combining Liquid-BTC-LN into a unified solution.
|
||||
|
||||
A summary of the pain points in setting up LN channels currently are:
|
||||
* High fees to open / close
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user