You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -65,7 +69,7 @@ To add tokens to the `Perma Lock FT` contract:
65
69
./02_permaLockFT.sh 123456789
66
70
```
67
71
68
-
The command above locks 123,456,789 tokens into the contract, as specified in the `start_info.json`.
72
+
The command above locks 123,456,789 tokens into the contract, as specified in the `config.json`.
69
73
70
74
To add tokens to the `Perma Lock NFT` contract:
71
75
@@ -81,6 +85,6 @@ The command above locks some amount of tokens into the contract, as specified by
81
85
82
86
Worst case for the nft lock is 64 unique policy ids. On pre-production, the UTxO `2981fdc49509b9cfc1c122b0dfc2563f29e49c2a07337ad55da3e2017a561124#0` is currently maxed out.
83
87
84
-
Worst case for the nft lock per transaction is 36. On pre-production, the UTxO`ff9b410414a5a5c0a2f63e9358b7299d296bb304ae579360dccf008357149809` shows the maximum amount of tokens for a single transaction.
88
+
Worst case for the nft lock per transaction is 36. On pre-production, the transaction`ff9b410414a5a5c0a2f63e9358b7299d296bb304ae579360dccf008357149809` shows the maximum amount of tokens for a single transaction.
85
89
86
90
The max memory parameter would have to be increased at the protocol level to account for more unique policy ids on the UTxO.
0 commit comments