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

Update docs/liquid/liquid-part3.md

Browse Source
This commit is contained in:
b0xxer 2024-02-02 10:28:47 -06:00
parent 12fb826869
commit fde426c14d
1 changed files with 26 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/liquid/liquid-part3.md
View File

@ -48,7 +48,7 @@ Before we start, let's look at state of our 2 wallets:
For our example, we can assume that StackerNews Airline (Node 1) is willing to accept a SND-1 token and return to the client 23,000 sats (approx $1 USD currently). So Node1 makes the following proposal
```
# Node1
# StackerNews Airline, Inc.
$ liquidswap-cli -u http://$E_RPCUSER:$E_RPCPASS@localhost:7041 propose -o proposal.txt 3e62af3c80c56ab6fec3d1e5646637152afebaf2a86ace075bbb7a88702e1fe5 1 6f0279e9ed041c3d710a9f57d0c02928416460c4b722ae3457a11eec381c526d 0.000023
```
@ -65,6 +65,7 @@ We can see that this proposal matches our expectation (1 SND token in exchange f
The export `accepted.txt` file is transferred back to Node1 where it is finalized and sent.
```
# Node 1 - StackerNews Airline, Inc.
$ liquidswap-cli -u http://$E_RPCUSER:$E_RPCPASS@localhost:7041 finalize accepted.txt -s
{
"broadcast": true,
@ -72,6 +73,30 @@ $ liquidswap-cli -u http://$E_RPCUSER:$E_RPCPASS@localhost:7041 finalize accepte
}
```
Now lets review the state our wallets post swap:
```
#Node1 - StackerNews Airline, Inc.
"balance": {
"bitcoin": 0.00129180,
"3e62af3c80c56ab6fec3d1e5646637152afebaf2a86ace075bbb7a88702e1fe5": 9.00000000
}
#Node2 - The Customer
"balance": {
"bitcoin": 0.00012656
},
```
|SWAP SUMMARY| Node 1 (Stacker News) | Node 2 (The Customer) |
|------------|-----------------------|-----------------------|
|SND Pre-Swap| 8 | 1 |
|SND Post-Swap| 9 | 0 |
|L-BTC Pre-Swap| 131755 sat | 10623 sat |
|L-BTC Post-Swap| 129180 sat | 12656 sat |
|TOTAL FEES PAID| 251 sat | 291 sat |
## Securities / Transfer Restricted / etc