Liquid daemon 3.14.1.23 and labels

Gabriele Domenichini
1 min readMar 12, 2019

--

So you have downloaded and installed liquid and you have played a bit.

If you have issued an asset or two, you find yourself asking:

“there must be a better name for my pints of beer than

1ceee799c5cf8130cf5a21cb438a9e87fb63c6a679519f25ace41a09bde17f67

".

A still undocumented trick is that you can label client side the assets in your wallet by adding one or more lines in your config file.

The line goes like this:

assetdir=1ceee799c5cf8130cf5a21cb438a9e87fb63c6a679519f25ace41a09bde17f67:Pints of beer

Bonus tip:

If you have a mac, you bitcoind instance must be running and available to rpc calls to let Liquid validate peg in.

I have mine protected by the autogenerated cookie file in the default location:

/Users/myusername/Library/Application Support/Bitcoin/.cookie

I tried to instruct liquid where to find it with the option:

mainchainrpccookiefile=/Users/myusername/Library/Application\ Support/Bitcoin/.cookie

but it was unable to find it. The thing I discovered is that the “\” character to escape the space was NOT required in the config file. So the right string is:

mainchainrpccookiefile=/Users/myusername/Library/Application Support/Bitcoin/.cookie

Have fun!

--

--