Skip to content

Commit 136459b

Browse files
gitmachtlgitmachtl
committed
Merge branch 'master' of https://github.com/gitmachtl/scripts 
2 parents 31eec5b + deb94cd commit 136459b

File tree

1 file changed

+58
-6
lines changed

1 file changed

+58
-6
lines changed

‎cardano/testnet/README.md

Lines changed: 58 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Why not always using Offline-Mode? You have to do transactions online, you have
3636
<br>```offlineMode="no"``` Scripts are working in Online-Mode
3737
<br>```offlineMode="yes"``` Scripts are working in Offline-Mode
3838

39-
So on the Online-Machine you set the ```offlineMode="no"``` and on the Offline-Machine you set the ```offlineMode="yes"```.
39+
So on the Online-Machine you set the ```offlineMode="no"``` and on the Offline-Machine you set the ```offlineMode="yes"```.
4040

4141
</details>
4242

@@ -367,11 +367,14 @@ Also you can force the script to do a re-registration by adding the keyword RERE
367367

368368
&nbsp;<br>
369369
* **10_genPolicy.sh:** generate policy keys, signing script and id as files **name.policy.skey/vkey/script/id**. You need a policy for Token minting.
370-
<br>```./10_genPolicy.sh <PolicyName>```
370+
<br>```./10_genPolicy.sh <PolicyName> [Optional valid xxx Slots (default=unlimited)]```
371371

372372
```./10_genPolicy.sh mypolicy```<br>this will generate the policyfiles with name mypolicy.policy.skey, mypolicy.policy.vkey, mypolicy.policy.script & mypolicy.policy.id
373373

374374
```./10_genPolicy.sh assets/mypolicy2```<br>this will generate the policyfiles with name mypolicy2.policy.skey, mypolicy2.policy.vkey, mypolicy2.policy.script & mypolicy2.policy.id in the 'assets' subdirectory
375+
376+
```./10_genPolicy.sh assets/special 600```<br>this will generate the policyfiles with name special.policy.skey, special.policy.vkey, special.policy.script & special.policy.id in the 'assets' subdirectory with a limited minting/burning access of 600 seconds(10 mins). Within those 10 mins you can mint lets say 200000 Tokens. After this 10 mins you will not be able to mint more Tokens or burn any Tokens with that Policy. So the total amount of the Tokens made with this Policy is fixed on the chain. :smiley:
377+
375378

376379
&nbsp;<br>
377380
* **11a_mintAsset.sh:** mint/generate new Assets(Token) on a given payment address with a policyName generated before. This updates the Token Status File **policyname.assetname.asset** for later usage when sending/burning Tokens.
@@ -382,6 +385,8 @@ Also you can force the script to do a re-registration by adding the keyword RERE
382385
```./11a_mintAsset.sh mypolicy.MEGATOKEN 30 owner.payment```<br>this will mint 30 new MEGATOKEN with policy 'mypolicy' on the payment address owner.payment.addr
383386

384387
```./11a_mintAsset.sh mypolicy.HYPERTOKEN 150 owner.payment mymetadata.json```<br>this will mint 150 new HYPERTOKEN with policy 'mypolicy' on the payment address owner.payment.addr and will also attach the mymetadata.json as metadata in the Minting-Transaction
388+
389+
It generally depends on the Policy-Type (made by the script 10a) if you can mint unlimited Tokens or if you are Time-Limited so a fixed Value of Tokens exists and there will never be more.
385390

386391
&nbsp;<br>
387392
* **11b_burnAsset.sh:** burnes Assets(Token) on a given payment address with a policyName you own the keys for. This updates the Token Status File **policyname.assetname.asset** for later usage when sending/burning Tokens.
@@ -393,6 +398,8 @@ Also you can force the script to do a re-registration by adding the keyword RERE
393398

394399
```./11b_burnAsset.sh assets/mypolicy2.HYPERTOKEN 5 owner.payment```<br>this will burn 5 HYPERTOKEN with policy 'mypolicy2' from the subdirectory assets on the payment address owner.payment.addr, also it will send along the mymetadata.json in the Burning-Transaction
395400

401+
It generally depends on the Policy-Type (made by the script 10a) if you can burn unlimited Tokens or if you are Time-Limited so a fixed Value of Tokens exists and there will never be less.
402+
396403
</details>
397404

398405
### Pool-Configuration-File (poolname.pool.json) - Config-File for each Pool
@@ -1226,7 +1233,9 @@ From the Mary-Era on, you can easily mint(generate) Native-Tokens by yourself, h
12261233
<details>
12271234
<Summary><b>Show Example ... </b>:bookmark_tabs:<br></summary>
12281235

1229-
<br>So lets say we wanna create 1000 new Tokens with the name **SUPERTOKEN** under the policy **mypolicy**. And we want that theses AssetFiles are stored in the *assets* subdirectory. These Tokens should be generated on the account **mywallet**.
1236+
### Mint an unresticted amount of Tokens
1237+
1238+
So lets say we wanna create 1000 new Tokens with the name **SUPERTOKEN** under the policy **mypolicy**. And we want that theses AssetFiles are stored in the *assets* subdirectory. These Tokens should be generated on the account **mywallet**.
12301239

12311240
<br><b>Steps:</b>
12321241
1. First you have to generate a policyName/ID. You can reuse the same policyName/ID to mint other Assets(Tokens) later again. If you already have the policy, skip to step 3
@@ -1235,7 +1244,20 @@ From the Mary-Era on, you can easily mint(generate) Native-Tokens by yourself, h
12351244

12361245
The AssetsFile ***assets/mypolicy.SUPERTOKEN.asset*** was also written/updated with the latest action. You can see the totally minted Token count in there too.
12371246

1238-
Done - You have mint (created) 1000 new SUPERTOKENs and they are now added to the mywallet address. You can now send them out into the world with the example below. :smiley:
1247+
Done - You have minted (created) 1000 new SUPERTOKENs and they are now added to the mywallet address. You can now send them out into the world with the example below. You can mint more anytime if you like. :smiley:
1248+
1249+
### Mint a resticted amount of Tokens within a set time window
1250+
1251+
Lets say we wanna create 200000 Tokens with the name **RARETOKEN** under the policy **special**. And we want that theses AssetFiles are stored in the *assets* subdirectory. These Tokens should be generated on the account **mywallet**.
1252+
1253+
<br><b>Steps:</b>
1254+
1. First you have to generate a policyName/ID that is time limited (slotheight limited). Using such a policy gives you the ability to mint your Tokens on the Chain for a limited amount of time, after that your cannot mint more or burn any of those.
1255+
1. Run ```./10_genPolicy.sh assets/special 600``` to generate a new policy with name 'special' in the assets subdirectory. The slotheight (time limit) is set to 600 -> 600 seconds
1256+
1. Run ```./11a_mintAsset.sh assets/special.RARETOKEN 200000 mywallet``` to mint 200000 RARETOKEN on the wallet mywallet. If you want, you can also add a custom Metadata.json file to the Minting-Transaction as the 4th parameter. Full-Syntax description can be found [here](#main-configuration-file-00_commonsh---syntax-for-all-the-other-ones)
1257+
1258+
The AssetsFile ***assets/special.RARETOKEN.asset*** was also written/updated with the latest action. You can see the totally minted Token count in there too.
1259+
1260+
Done - You have minted (created) 200000 RARETOKENs within the given time limit and there will never be more RARETOKENs available on the the chain, the policy for minting and burning is deactivated automatically after the set 600 seconds (10 mins). :smiley:
12391261

12401262
</details>
12411263

@@ -1938,7 +1960,9 @@ From the Mary-Era on, you can easily mint(generate) Native-Tokens by yourself, h
19381960
<details>
19391961
<Summary><b>Show Example ... </b>:bookmark_tabs:<br></summary>
19401962

1941-
<br>So lets say we wanna create 1000 new Tokens with the name **SUPERTOKEN** under the policy **mypolicy**. And we want that theses AssetFiles are stored in the *assets* subdirectory. These Tokens should be generated on the account **mywallet**.
1963+
### Mint an unresticted amount of Tokens
1964+
1965+
So lets say we wanna create 1000 new Tokens with the name **SUPERTOKEN** under the policy **mypolicy**. And we want that theses AssetFiles are stored in the *assets* subdirectory. These Tokens should be generated on the account **mywallet**.
19421966

19431967
**Online-Machine:**
19441968

@@ -1960,7 +1984,35 @@ The AssetsFile ***assets/mypolicy.SUPERTOKEN.asset*** was also written/updated w
19601984

19611985
1. Execute the created offline transaction now on the blockchain by running<br>```./01_workOffline.sh execute```
19621986

1963-
Done - You have mint (created) 1000 new SUPERTOKENs and they are now added to the mywallet address. You can now send them out into the world with the example below.
1987+
Done - You have minted (created) 1000 new SUPERTOKENs and they are now added to the mywallet address. You can now send them out into the world with the example below. You can mint more if you like later.
1988+
1989+
:smiley:
1990+
1991+
### Mint a resticted amount of Tokens within a set time window
1992+
1993+
Lets say we wanna create 200000 Tokens with the name **RARETOKEN** under the policy **special**. And we want that theses AssetFiles are stored in the *assets* subdirectory. These Tokens should be generated on the account **mywallet**.
1994+
1995+
**Online-Machine:**
1996+
1997+
1. Add/Update the current UTXO balance for mywallet in the offlineTransfer.json by running<br>```./01_workOffline.sh add mywallet```
1998+
1999+
:floppy_disk: Transfer the offlineTransfer.json to the Offline-Machine.
2000+
2001+
**Offline-Machine:** (same steps like working online)
2002+
2003+
1. First you have to generate a policyName/ID that is time limited (slotheight limited). Using such a policy gives you the ability to mint your Tokens on the Chain for a limited amount of time, after that your cannot mint more or burn any of those.
2004+
1. Run ```./10_genPolicy.sh assets/special 600``` to generate a new policy with name 'special' in the assets subdirectory. The slotheight (time limit) is set to 1200 -> 1200 seconds
2005+
1. Run ```./11a_mintAsset.sh assets/special.RARETOKEN 200000 mywallet``` to mint 200000 RARETOKEN on the wallet mywallet. If you want, you can also add a custom Metadata.json file to the Minting-Transaction as the 4th parameter. Full-Syntax description can be found [here](#main-configuration-file-00_commonsh---syntax-for-all-the-other-ones)
2006+
2007+
The AssetsFile ***assets/special.RARETOKEN.asset*** was also written/updated with the latest action. You can see the totally minted Token count in there too.
2008+
2009+
:floppy_disk: Transfer the offlineTransfer.json to the Online-Machine.
2010+
2011+
**Online-Machine:**
2012+
2013+
1. Execute the created offline transaction now on the blockchain by running<br>```./01_workOffline.sh execute```
2014+
2015+
Done - You have minted (created) 200000 RARETOKENs within the given time limit and there will never be more RARETOKENs available on the the chain, the policy for minting and burning is deactivated automatically after the given 1200 seconds (20 mins). :smiley:
19642016

19652017
:smiley:
19662018

0 commit comments

Comments
 (0)