From ae23561628c05bc1cc17d7e26e6816fa64a2457e Mon Sep 17 00:00:00 2001 From: b0xxer Date: Fri, 26 Jan 2024 11:13:11 -0600 Subject: [PATCH] Update docs/liquid/liquid-part2.md --- docs/liquid/liquid-part2.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/liquid/liquid-part2.md b/docs/liquid/liquid-part2.md index fa529b8..65d3223 100644 --- a/docs/liquid/liquid-part2.md +++ b/docs/liquid/liquid-part2.md @@ -189,6 +189,8 @@ The publication of asset metadata info on Liquid works on a `.well-known` system * Lets set a few environmental variables to make things easier: + `$ ASSET_REGISTRY_URL="https://assets.blockstream.info/"` + `$ export DOMAIN="nulldata.org"` (NOTE: Needs to match what you set in Bash script above) `$ export ASSET="409b1d0cb614822ea703576b71958ab051d66ff6708b368f378f2ffea458d15a"` (NOTE: Needs to match the asset you are registering) @@ -197,7 +199,7 @@ The publication of asset metadata info on Liquid works on a `.well-known` system Running the above will result in a file named `liquid-asset-proof-409b1d0c...` being created, and inside that file it will say `Authorize linking the domain name nulldata.org to the Liquid asset 409b1d0c...` - +First you need to place this `liquid-asset-proof` file in the root directory of your domain under a folder named `.well-known` (ie. in this case `nulldata.org/.well-known/liquid-asset-proof-409b1d0cb614822ea703576b71958ab051d66ff6708b368f378f2ffea458d15a`)