From 9b591e590fa43f62f873af1c67539a0eae6ad74f Mon Sep 17 00:00:00 2001 From: b0xxer Date: Sun, 28 Jan 2024 08:22:57 -0600 Subject: [PATCH] Update docs/liquid/liquid-part2.md --- docs/liquid/liquid-part2.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/liquid/liquid-part2.md b/docs/liquid/liquid-part2.md index b151271..7c5d078 100644 --- a/docs/liquid/liquid-part2.md +++ b/docs/liquid/liquid-part2.md @@ -44,10 +44,9 @@ $ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER "token": "2eb4da7c84a7b4db2944ead6b05041a5d8d8f4a73cd1413b140b44c4ec42fbdf" } ``` - ### Exploring our new Asset -* Checking out our wallet we see: +Checking out our wallet we see: ``` $ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS getwalletinfo @@ -70,7 +69,7 @@ It is possible to 'unblind' this information to clients, but that would involve ### Issuing a Non-Confidential Asset -* Let's create another address[^5] and another asset and this time choose a different option (specifically, lets create this asset unblinded): +* Let's create another address[^5] and another asset and this time choose a different option (specifically, lets create this asset unblinded by setting the last value to **false**. This option controls blinded / unblinded behavior): ``` $ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS issueasset 10 0 false @@ -164,7 +163,7 @@ $ curl https://assets.blockstream.info/ --data-raw '{"asset_id":"409b1d0cb614822 [^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 1,000,000,000 units (10 x 100,000,000). +[^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 \ No newline at end of file