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

Update docs/liquid/liquid-part2.md

Browse Source
This commit is contained in:
b0xxer 2024-01-26 10:58:20 -06:00
parent 4da2e7ce6e
commit fb0b16d429
1 changed files with 1 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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