Update docs/liquid/liquid-part2.md
This commit is contained in:
parent
9c3229f5c9
commit
60f2fb0bbf
@ -92,9 +92,17 @@ Now, lets look at how things look on the Green mobile wallet:
|
||||
|
||||
We can see that we've received 100,000,000 'sats' of our custom asset. However, notice how there is no labels. The elements for L-BTC, USDT, etc show with ticker symbols...whereas ours is showing just the contract address....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`
|
||||
|
||||
lq1qq2s92z0uq78kd4gfepua6qvfwx40g4lqqer9e3tzrr0j04ugyzsed39mnh9wvuhw0hmaqy5mxs9egqrr7j3rx8j2sdyun9m90
|
||||
|
||||
|
||||
|
||||
[^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)
|
||||
[^2]: Like in bitcoin, 1 integer unit is 100,000,000 base units (not sats, but equivalent concept)
|
||||
[^3]: 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.
|
||||
Loading…
x
Reference in New Issue
Block a user