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

Update docs/liquid/liquid-part2.md

Browse Source 
Release to stackernews
This commit is contained in:
b0xxer 2024-01-30 05:48:15 -06:00
parent 67daa5d916
commit c8756ab16f
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/liquid/liquid-part2.md
View File

@ -174,10 +174,11 @@ Now it shows up in a much more user-friendly format. The only thing missing is a
# Wrap-up and Next Session
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.
In this session we issued assets[^5], 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.
[^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]: One feature we neglected to checkout was issuing reissuable assets. If you are interested in seeing how that is done, you can check out the developer documentation here: [https://elementsproject.org/elements-code-tutorial/reissuing-assets](https://elementsproject.org/elements-code-tutorial/reissuing-assets)