Update docs/liquid/liquid-part1.md

This commit is contained in:
b0xxer 2024-01-22 06:07:13 -06:00
parent c4a8d07ed4
commit 9088f9df3d

View File

@ -124,8 +124,19 @@ Now let's peg-in some bitcoin in order to receive L-BTC within our Liquid wallet
"unconfirmed_balance": { "unconfirmed_balance": {
"bitcoin": 0.00149952 "bitcoin": 0.00149952
}, }[^5],
* After 1 confirmations (approx 2 mins) the balance should be confirmed
- `$ elements/bin/elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS getwalletinfo`
"balance": {
"bitcoin": 0.00149952}
## Wrap Up and Preview for Part II.
This was just the basics, in this DeepDive we got our Elements node running and pegged-in our initial BTC balance.
In Part II is where the fun begins, we will issue Assets, get the assets in the registry, and transfer between wallets
**Footnotes:** **Footnotes:**
@ -133,6 +144,7 @@ Now let's peg-in some bitcoin in order to receive L-BTC within our Liquid wallet
[^2]: RAM usage is higher for Liquid than for BTC alone due to Confidential Transactions processing [^2]: RAM usage is higher for Liquid than for BTC alone due to Confidential Transactions processing
[^3]: 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]: 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.
[^4]: Requires 102 confirmations on BTC side. Services like sideswap will release after 2 confs for small amounts [^4]: Requires 102 confirmations on BTC side. Services like sideswap will release after 2 confs for small amounts
[^5]: Balance less the 48sat transaction fee