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

Update docs/liquid/liquid-part1.md

Browse Source
This commit is contained in:
b0xxer 2024-01-21 09:55:05 -06:00
parent 51c940d386
commit c13d8ef89a
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/liquid/liquid-part1.md
View File

@ -107,12 +107,13 @@ Now let's peg-in some bitcoin in order to receive L-BTC within our Liquid wallet
* Send some btc to the `mainchain_address` listed above (I'm sending 150000 sats) * Send some btc to the `mainchain_address` listed above (I'm sending 150000 sats)
* Copy the BTC transaction ID and save to variable * Copy the BTC transaction ID and save to variable
- `$ export B_TRANSID="bb1d0903XXXXXXXXXXXXXXXXXXXXXXXXXXX"` - `$ export B_TRANSID="bb1d0903XXXXXXXXXXXXXXXXXXXXXXXXXXX"`
* Wait for the BTC transaction to confirm (documents say must confirm for 102 confs) * Wait for the BTC transaction to confirm[^3]
Footnotes: **Footnotes:**
[^1]: RAM usage is higher for Liquid than for BTC alone due to Confidential Transactions processing [^1]: RAM usage is higher for Liquid than for BTC alone due to Confidential Transactions processing
[^2]: It may be possible to run the `elements-cli` command without installing it separately, however I could not find it in the container. Anyway, the download of elements node is quite small and it communicates via localport on Umbrel, so this works fine. [^2]: It may be possible to run the `elements-cli` command without installing it separately, however I could not find it in the container. Anyway, the download of elements node is quite small and it communicates via localport on Umbrel, so this works fine.
[^3]: Requires 102 confirmations on BTC side. Services like sideswap will release after 2 confs for small amounts