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: docs/build/get-started/clarity-crash-course.md
+74Lines changed: 74 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -303,6 +303,80 @@ Auditors provide an independent, expert review of your smart contracts to identi
303
303
304
304
***
305
305
306
+
### Deploying Clarity Smart Contracts
307
+
308
+
When you deploy a Clarity smart contract, you're uploading its code to the Stacks blockchain, making it immutable and publicly accessible. Deployment involves submitting a transaction that includes the smart contract code and specific parameters. Once deployed, the contract's logic is fixed, providing transparency and security by ensuring that no further changes can be made.
309
+
310
+
{% hint style="warning" %}
311
+
Do note that not all methods below will support the latest Clarity version.
312
+
{% endhint %}
313
+
314
+
Here are a few different ways to deploy a Clarity smart contract:
315
+
316
+
<details>
317
+
318
+
<summary>Clarinet</summary>
319
+
320
+
Clarinet is the CLI tool for all things Clarity contract development. Deploying contracts via Clarinet is by far the most conventional and common method. Using Clarinet also provides a myriad amount of configuration options for how you want your deployment to look like.
321
+
322
+
Check out the dedicated guide [here](../clarinet/contract-deployment.md) to learn how you can deploy contracts with Clarinet.
323
+
324
+
</details>
325
+
326
+
<details>
327
+
328
+
<summary>Stacks.js</summary>
329
+
330
+
Stacks.js is the frontend javascript library for interacting with the Stacks network. Many token launchpads, that enable no-code solutions for deploying a token, utilize Stacks.js for deploying contracts on the frontend or backend script.
331
+
332
+
Check out the dedicated guide [here](../stacks.js/contract-deployment.md) to learn how you can deploy contracts with Stacks.js.
333
+
334
+
</details>
335
+
336
+
<details>
337
+
338
+
<summary>Stacks Explorer Sandbox</summary>
339
+
340
+
The Sandbox in the [Stacks Explorer](https://explorer.stacks.co/) is an interactive Clarity code editor allowing you to write contracts, call functions of existing contracts, and also deploy contracts directly.
The [Hiro Platform](https://platform.hiro.so/) is a hosted developer experience that enables you to create and deploy Clarity smart contracts directly from a web browser.
Utilize tools that provide the event-driven infrastructure developers need to observe, index, and react to on-chain activity.
361
+
362
+
<details>
363
+
364
+
<summary>Contract Monitoring</summary>
365
+
366
+
The [Contract Monitoring](https://platform.hiro.so/contract-monitoring) features, available in the Hiro Platform, enable you to set alerts when specific functions are called in your smart contracts. This enables you to detect and respond to suspicious contract activities, enhancing the security of your app throughout the contract lifecycle.
367
+
368
+
</details>
369
+
370
+
<details>
371
+
372
+
<summary>Chainhooks</summary>
373
+
374
+
[Chainhooks](https://docs.hiro.so/tools/chainhook) indexes Stacks & Bitcoin data, exposes queryable APIs, tracks contract state and transactions. You simply describe your chainhook filters and consume webhooks. The service handles queueing, retries, tier limits, observability, and parity between testnet and mainnet.
375
+
376
+
</details>
377
+
378
+
***
379
+
306
380
### Additional Resources
307
381
308
382
This brief overview should get your feet wet with Clarity. For deeper learning, we recommend:
0 commit comments