Update docs/liquid/liquid-part2.md

This commit is contained in:
b0xxer 2024-01-30 05:42:06 -06:00
parent 1b4a14f0d3
commit 583396c31b

View File

@ -172,18 +172,12 @@ Now it shows up in a much more user-friendly format. The only thing missing is a
![](9-part2-wassetlogo.png)
# Wrap-up and Next Session
In this session we issued assets and looked at their basic features. In the next part in the series, we will delve into even more advanced aspects of Liquid like: Swaps, Contracts, etc.
In this session we issued assets, looked at their basic features, and registered our own. In the next part in the series, we will delve into even more advanced aspects of Liquid like: Swaps, Contracts, etc. Finally we will discuss pegging-out and the broader use-cases of the technology.
[^1]: The values E_RPCUSER and E_RPCPASS, where environmental variables we set in Part I
[^2]: Like in bitcoin, 1 integer unit is 100,000,000 base units (not sats, but equivalent concept) - So in this case issuing "10" assets is really issuing 1000000000 units (10 x 100,000,000).
[^3]: Technically just running `elements-cli issueasset 10 0` is enough to issue an asset, however there will be limitations later on when trying to register the asset, burn, remove, etc.
[^4]: Using a legacy address for this task imposes no real implications to your security since its only used to remove assets from the registry. Its possible to do this with a non-legacy address, but more steps are involved and we will need to use other tools rather than what's already built-in to Elements node, so we will just use a legacy address for this.
[^5]: So each asset is held in a separate address
[^4]: Using a legacy address for this task imposes no real implications to your security since its only used to remove assets from the registry. Its possible to do this with a non-legacy address, but more steps are involved and we will need to use other tools rather than what's already built-in to Elements node, so we will just use a legacy address for this.