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
Copy file name to clipboardExpand all lines: README.md
+35-4Lines changed: 35 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -414,15 +414,46 @@ $ clarinet integrate
414
414
415
415
Make sure that you have a working installation of Docker running locally.
416
416
417
-
### Deploy contracts to Testnet
417
+
### Interacting with contracts deployed on Mainnet
418
418
419
-
You can use Clarinet to deploy your contracts to the public Testnet environment for testing and
420
-
evaluation on a blockchain. Use the following command:
419
+
Composition and interactions between protocols and contracts are one of the key innovations in blockchains. Clarinet was designed to handle this sort of interactions.
420
+
421
+
Before refering to contracts deployed on Mainnet, they should be explicitily be listed as a `requirement` in the manifest `Clarinet.toml`:
From there, clarinet will be able to reconciliate the `contract-call` present in your local contracts, download and cache a copy of the required contracts, and use them during the execution of your tests suites, and all the different features available in `clarinet`.
433
+
434
+
When deploying your protocol to Devnet / Testnet, for the contracts involving requirements, the setting `remap_requirements` in your deployment plans must be set.
435
+
436
+
Before Devnet / Testnet deployments, your contracts will be automatically remapped on the fly to point to the duplicated requirements deployed by an account that you control.
437
+
438
+
### Deploy contracts to Devnet / Testnet / Mainnet
439
+
440
+
You can use Clarinet to publish your contracts to the public Testnet environment for testing and evaluation on a blockchain.
441
+
442
+
The first step is to generate a deployment plan, with the following command:
443
+
444
+
```bash
445
+
$ clarinet deployment generate --mainnet
446
+
```
447
+
448
+
After **cautiously** reviewing (and updating if needed) the generated plan, you can use the command:
0 commit comments