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

spell check

Browse Source
This commit is contained in:
barry 2024-01-27 04:21:58 -06:00
parent dcbea39b0e
commit 4ae93893bd
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/liquid/liquid-part2.md
View File

@ -8,7 +8,7 @@ This is a multipart DeepDive that will focus on the Liquid Sidechain. It will be
## Assets ## Assets
In Part I, we succesfully Pegged-In our BTC and received L-BTC, now lets use that L-BTC to do some interesting things with Asset Issuance: In Part I, we successfully Pegged-In our BTC and received L-BTC, now lets use that L-BTC to do some interesting things with Asset Issuance:
Before we jump straight into creating an asset, let us first look at the assets we already have inside our pegged-in wallet[^1]: Before we jump straight into creating an asset, let us first look at the assets we already have inside our pegged-in wallet[^1]:
@ -126,7 +126,7 @@ export CONTRACT_HASH=967f329b873d20253852236bcb4aab8df355356c06a4f0190361dfe6e58
![](2-part2-firstasset.png) ![](2-part2-firstasset.png)
* So publiclly we know the following about our new asset: * So publicly we know the following about our new asset:
- It cannot be re-issued - It cannot be re-issued
- It has only been issued once - It has only been issued once
- However both the issued amount and the circulating supply has been hidden from us. - However both the issued amount and the circulating supply has been hidden from us.
@ -160,13 +160,13 @@ This Confidential Asset has ultimate privacy, we can't really see anything about
![](3-part2-tx.png) ![](3-part2-tx.png)
This is interesting: So although the transaction is visible, we can't see what was actually transferred (even though the details of the asset are visible, *it is still hidden inside the transaction*). Further, where is my Green Wallet address (ie. VJLJZQ...)? We can see 3 output addresses, presumably these are: Change, Fee, and Receipiant...but which is my Green Wallet? This is interesting: So although the transaction is visible, we can't see what was actually transferred (even though the details of the asset are visible, *it is still hidden inside the transaction*). Further, where is my Green Wallet address (ie. VJLJZQ...)? We can see 3 output addresses, presumably these are: Change, Fee, and Recipient...but which is my Green Wallet?
* Let's look up my [Green Wallet address directly in the explorer](https://blockstream.info/liquid/address/VJLJZQ2Du4natCvJuhNQTH7tHnphsofPoW8aZtgsnmPaihuqt4MpsujPxYTiy5WHVuJdpRQAcF9oTMAd): * Let's look up my [Green Wallet address directly in the explorer](https://blockstream.info/liquid/address/VJLJZQ2Du4natCvJuhNQTH7tHnphsofPoW8aZtgsnmPaihuqt4MpsujPxYTiy5WHVuJdpRQAcF9oTMAd):
![](4-part2-greenaddr.png) ![](4-part2-greenaddr.png)
So now this shows us that the *Confidential Address: VJLJZQ2...* corresponds to the *Unconfidential Address: H53F2D....* Through the magic of one-way hashes, if we know the "Confidential" address we can then dervive its public address....however just by looking at the public blockchain, there is no way to reverse that hash. So now this shows us that the *Confidential Address: VJLJZQ2...* corresponds to the *Unconfidential Address: H53F2D....* Through the magic of one-way hashes, if we know the "Confidential" address we can then derive its public address....however just by looking at the public blockchain, there is no way to reverse that hash.
Now, lets look at how things look on the Green mobile wallet: Now, lets look at how things look on the Green mobile wallet:
@ -214,4 +214,4 @@ Before you proceed to the next step, please verify that they above file is reach
[^1]: The values E_RPCUSER and E_RPCPASS, where environmental variables we set in Part I [^1]: The values E_RPCUSER and E_RPCPASS, where environmental variables we set in Part I
[^2]: Like in bitcoin, 1 integer unit is 100,000,000 base units (not sats, but equivalent concept) - So in this case issuing "10" assets is really issuing 1,000,000,000 units (10 x 100,000,000). [^2]: Like in bitcoin, 1 integer unit is 100,000,000 base units (not sats, but equivalent concept) - So in this case issuing "10" assets is really issuing 1,000,000,000 units (10 x 100,000,000).
[^3]: Technically just running `elements-cli issueasset 10 0` is enough to issue an asset, however there will be limitations later on when trying to register the asset, burn, remove, etc. [^3]: Technically just running `elements-cli issueasset 10 0` is enough to issue an asset, however there will be limitations later on when trying to register the asset, burn, remove, etc.
[^4]: Using a legacy address for this task imposes no real implications to your security since its only used to remove assets from the registry. Its possible to do this with a non-legacy address, but more steps are involved and we will need to use other tools rather than what's already built-in to Elements node, so we will just use a legacy address for this. [^4]: Using a legacy address for this task imposes no real implications to your security since its only used to remove assets from the registry. Its possible to do this with a non-legacy address, but more steps are involved and we will need to use other tools rather than what's already built-in to Elements node, so we will just use a legacy address for this.