Update docs/liquid/liquid-part2.md
This commit is contained in:
parent
4d64a37818
commit
a8b1683304
@ -88,9 +88,7 @@ echo CONTRACT_HASH=$CONTRACT_HASH
|
|||||||
|
|
||||||
CONTRACT={"entity":{"domain":"nulldata.org"},"issuer_pubkey":"025aa49d444a150c99c904c8e779e5317aff4aee15ee9171f450e14af9dd8b8780","name":"StackerNews-Demo1","precision":8,"ticker":"SND-1","version":0}
|
CONTRACT={"entity":{"domain":"nulldata.org"},"issuer_pubkey":"025aa49d444a150c99c904c8e779e5317aff4aee15ee9171f450e14af9dd8b8780","name":"StackerNews-Demo1","precision":8,"ticker":"SND-1","version":0}
|
||||||
|
|
||||||
CONTRACT_HASH=8b838ae5e6df610319f0a4066c3555f38dab4acb6b23523825203d879b327f96
|
CONTRACT_HASH=967f329b873d20253852236bcb4aab8df355356c06a4f0190361dfe6e58a838b
|
||||||
|
|
||||||
CONTRACT_HASH_REV=967f329b873d20253852236bcb4aab8df355356c06a4f0190361dfe6e58a838b
|
|
||||||
|
|
||||||
|
|
||||||
* Finally export those variables via bash to use later:
|
* Finally export those variables via bash to use later:
|
||||||
@ -98,16 +96,14 @@ echo CONTRACT_HASH=$CONTRACT_HASH
|
|||||||
```
|
```
|
||||||
export CONTRACT={"entity":{"domain":"nulldata.org"},"issuer_pubkey":"025aa49d444a150c99c904c8e779e5317aff4aee15ee9171f450e14af9dd8b8780","name":"StackerNews-Demo1","precision":8,"ticker":"SND-1","version":0}
|
export CONTRACT={"entity":{"domain":"nulldata.org"},"issuer_pubkey":"025aa49d444a150c99c904c8e779e5317aff4aee15ee9171f450e14af9dd8b8780","name":"StackerNews-Demo1","precision":8,"ticker":"SND-1","version":0}
|
||||||
|
|
||||||
export CONTRACT_HASH=8b838ae5e6df610319f0a4066c3555f38dab4acb6b23523825203d879b327f96
|
export CONTRACT_HASH=967f329b873d20253852236bcb4aab8df355356c06a4f0190361dfe6e58a838b
|
||||||
|
|
||||||
export CONTRACT_HASH_REV=967f329b873d20253852236bcb4aab8df355356c06a4f0190361dfe6e58a838b
|
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
####REDO HERE####
|
####REDO HERE####
|
||||||
|
|
||||||
* STEP 3: Now Issuing our own asset is straight-forward, as its a single line command in the client. Let's issue 10 new tokens and set the supply to be fixed (no re-issuance)
|
* STEP 3: Now Issuing our own asset is straight-forward, as its a single line command in the client. Let's issue 10 new tokens and set the supply to be fixed (no re-issuance)
|
||||||
- `$ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS issueasset 10 0 true $CONTRACT_HASH_REV`
|
- `$ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS issueasset 10 0 true $CONTRACT_HASH`
|
||||||
|
|
||||||
{
|
{
|
||||||
"txid": "6ef6b04b34e27d79c0b66d817bc23a81bc6a56b289b6a45a28b71489adca0825",
|
"txid": "6ef6b04b34e27d79c0b66d817bc23a81bc6a56b289b6a45a28b71489adca0825",
|
||||||
@ -134,12 +130,12 @@ export CONTRACT_HASH_REV=967f329b873d20253852236bcb4aab8df355356c06a4f0190361dfe
|
|||||||
- 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.
|
||||||
|
|
||||||
This Confidential Asset has ultimate privacy, we can't really see anything about it. It Is possible to export information to specific clients so that they can see this info, however in most cases its preferred that this information is publicly available. For instance, if we wanted th public to know the total issuance of an asset without needing any special information, so lets do that:
|
This Confidential Asset has ultimate privacy, we can't really see anything about it. One of the problems with this, is how could users validate the total circulating supply? It is possible to 'unblind' this information to clients, but that would involve distributing an unblinding key to each client. However there is a simple solution here, we can simply issue the asset as unblinded - which will permit this information to be publicly available *without* affecting the security of the actual transactions:
|
||||||
|
|
||||||
### Issuing a Non-Confidential Asset
|
### Issuing a Non-Confidential Asset
|
||||||
|
|
||||||
* Let's create another asset and this time choose a different option (specifically, lets create this asset unblinded):
|
* Let's create another asset and this time choose a different option (specifically, lets create this asset unblinded):
|
||||||
- `$ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS issueasset 10 0 false $CONTRACT_HASH_REV`
|
- `$ sudo ./scripts/app compose elements exec node elements-cli -rpcuser=$E_RPCUSER -rpcpassword=$E_RPCPASS issueasset 10 0 false $CONTRACT_HASH`
|
||||||
|
|
||||||
{
|
{
|
||||||
"txid": "f27c99793f685fa4109ecec68d79819b077946427a489c5301ccbde136d4e070",
|
"txid": "f27c99793f685fa4109ecec68d79819b077946427a489c5301ccbde136d4e070",
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user