From fb0b16d42930366522fd5df519d37b4c720fc3f8 Mon Sep 17 00:00:00 2001 From: b0xxer Date: Fri, 26 Jan 2024 10:58:20 -0600 Subject: [PATCH] Update docs/liquid/liquid-part2.md --- docs/liquid/liquid-part2.md | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/docs/liquid/liquid-part2.md b/docs/liquid/liquid-part2.md index c6bf2ca..0598c03 100644 --- a/docs/liquid/liquid-part2.md +++ b/docs/liquid/liquid-part2.md @@ -181,26 +181,13 @@ Now, lets look at how things look on the Green mobile wallet: ![](6-part2-noassetlabel.png) -We can see that we've received 200,000,000 'sats' of our custom asset. However, notice how there is no labels. Whereas, the elements for L-BTC and Tether are complete with ticker symbols. Showing just the contract address is not very user friendly. Let's see if we can remedy. +We can see that we've received 200,000,000 'sats' of our custom asset. However, notice how there is no label. Whereas, for L-BTC and Tether it shows complete with name and ticker symbol. Showing just the contract address is not very user friendly. Let's see if we can remedy. # Registering our Asset The publication of asset metadata info on Liquid works on a `.well-known` system where specific files are published on a webserver that you control. There are a few different steps to accomplish this, so lets begin -* The first step is we need to generate a `legacy` address in case we ever want to delete the asset from the registry later[^3] - - `$ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS getnewaddress "" legacy` - - lq1qq2s92..... -* Set this address to a variable for use later and generate the public key. - - `$ export DELETE_ADDRESS="lq1qq2s92....."` - - `$ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS getaddressinfo $DELETE_ADDRESS | jq '.pubkey'` - - 025aa49d444a150c99c904c8e779e5317aff4aee15ee9171f450e14af9dd8b8780 - - - `$ export PUBKEY="025aa49d444a150c99c904c8e779e5317aff4aee15ee9171f450e14af9dd8b8780"` - -* We need to set some variable and then generate a json 'contract' file