GITBOOK-28: update Devnet page

Author: eric-stacks

docs/build/clarinet-integrations/vscode-extension.md

@@ -1,5 +1,9 @@
 # VSCode Extension
 
+{% hint style="info" %}
+The [VSCode extension](https://marketplace.visualstudio.com/items?itemName=StacksLabs.clarity-stacks) for Clarity is now published under the Stacks Labs organization.
+{% endhint %}
+
 ## Features
 
 ### Smart auto-completion
@@ -76,25 +80,25 @@ When implementing traits (like SIP-009 NFTs or SIP-010 tokens), the extension ve
 
 {% stepper %}
 {% step %}
-#### Set breakpoints
+**Set breakpoints**
 
 Set breakpoints by clicking line numbers in the editor.
 {% endstep %}
 
 {% step %}
-#### Start debugging
+**Start debugging**
 
 Press `F5` or use Run → Start Debugging to begin a debugging session.
 {% endstep %}
 
 {% step %}
-#### Step through code
+**Step through code**
 
 Step through code line-by-line to follow execution.
 {% endstep %}
 
 {% step %}
-#### Inspect state
+**Inspect state**
 
 Inspect variables and stack state while paused at breakpoints.
 {% endstep %}
@@ -114,3 +118,9 @@ Visual debugging requires VS Code Desktop and Clarinet installed locally.
 | Documentation         | External lookup | Inline hover docs       |
 | Debugging             | Console only    | Visual debugger         |
 | Cross-file navigation | Manual          | Jump to definition      |
+
+***
+
+### Additional Resources
+
+* \[[zed.dev](https://zed.dev/extensions?query=clarity)] Zed extension for Clarity

docs/build/clarinet/local-blockchain-development.md

@@ -205,6 +205,78 @@ epoch_2_4 = 0     # Pox-4 from genesis
 epoch_3_0 = 101   # Nakamoto activation at block 101
 ```
 
+### Custom node/signer images
+
+Clarinet runs Devnet with specific tags for each Docker image. For example, Clarinet v3.10.0 uses the following images:
+
+* stacks node: `blockstack/stacks-blockchain:3.3.0.0.1-alpine`
+* stacks signer: `blockstack/stacks-signer:3.3.0.0.1.0-alpine`
+
+We recommend Devnet users let Clarinet handle it and use the default version. This ensures that your Clarinet version can handle and properly configure the images it uses.
+
+In some cases, you may need to use other images. Clarinet lets you do this by configuring it in `settings/Devnet.toml`. For example, if you don't want to run the `alpine` images:
+
+```toml
+# setting/Devnet.toml
+[network]
+name = "devnet"
+deployment_fee_rate = 10
+
+# ...
+
+[devnet]
+stacks_node_image_url = "blockstack/stacks-blockchain:3.3.0.0.1"
+stacks_signer_image_url = "blockstack/stacks-signer:3.3.0.0.1.0"
+```
+
+<details>
+
+<summary>Build an image locally and use it</summary>
+
+* Clone the stacks-core repository (or a fork) and checkout the desired branch.
+
+```
+git clone [email protected]:stacks-network/stacks-core.git
+cd stacks-core
+git checkout develop
+```
+
+* Build the Docker image `stacks-node:local`:
+
+```
+docker build -t stacks-node:local -f ./Dockerfile ./
+```
+
+* Clarinet needs the image to be available in a registry. You can host a local one and push the image to it.
+
+```
+docker run -d -e REGISTRY_HTTP_ADDR=0.0.0.0:5001 -p 5001:5001 --name registry registry:2
+docker tag stacks-node:local localhost:5001/stacks-node:local
+docker push localhost:5001/stacks-node:local
+```
+
+* Set the image to be used:
+
+```
+# setting/Devnet.toml
+[network]
+name = "devnet"
+deployment_fee_rate = 10
+
+# ...
+
+[devnet]
+stacks_node_image_url = "localhost:5001/stacks-node:local"
+```
+
+* Then start Devnet:
+
+```
+clarinet devnet sta
+```
+
+</details>
+
 ### Package deployment
 
 Create reusable devnet configurations:
@@ -401,3 +473,7 @@ clarinet deployments apply --devnet
 </details>
 
 ***
+
+### Additional Resources
+
+* \[[Hiro Blog](https://www.hiro.so/blog/5-ways-to-interact-with-devnet-in-the-hiro-platform)] 5 Ways to Interact With Devnet in the Hiro Platform&#x20;

docs/build/clarinet/overview.md

@@ -14,6 +14,17 @@ For the latest releases and versions of Clarinet, check out the open-source repo
 
 <div data-with-frame="true"><figure><img src="../.gitbook/assets/clarinet-diagram.png" alt=""><figcaption></figcaption></figure></div>
 
+{% updates format="full" %}
+{% update date="2025-11-05" %}
+## Clarinet was migrated to Stacks Labs
+
+* The Clarinet repository now belongs to the stx-labs organization.
+* The NPM packages are now published under the `@stacks` organization.
+* The VSCode extension is now published under the Stacks Labs organization.
+* Check out the [discussion](https://github.com/stx-labs/clarinet/discussions/2055) to see how to migrate older projects.
+{% endupdate %}
+{% endupdates %}
+
 ## Key features
 
 * [**Leverage a powerful CLI**](https://app.gitbook.com/s/GVj1Z9vMuEOMe7oH7Wnq/clarinet/cli-reference) - Create new projects, manage your smart contracts and their dependencies using clarinet requirements, and interact with your code through the built-in REPL.
@@ -73,7 +84,6 @@ For a deeper understanding of when to use these networks, check out the dedicate
 ### Additional Resources
 
 * \[[Hiro Blog](https://www.hiro.so/blog/clarinet-roadmap-looking-to-the-future)] The Humble Beginning of Clarinet
-* \[[zed.dev](https://zed.dev/extensions?query=clarity)] Zed extension for Clarity
 
 ***
 

docs/build/get-started/clarity-crash-course.md

@@ -193,7 +193,7 @@ Great! You just interacted with your first Clarity smart contract. Hopefully thi
 
 ### Read Access into Bitcoin
 
-Smart contracts on the Stacks layer can read Bitcoin state and can be triggered by standard Bitcoin transactions. This is because Stacks nodes also run Bitcoin nodes as part of consensus, and they read and index Bitcoin state.
+Clarity smart contracts on the Stacks layer can also read Bitcoin state and can be triggered by standard Bitcoin transactions. This is because Stacks nodes also run Bitcoin nodes as part of consensus, and they read and index Bitcoin state.
 
 Reading Bitcoin state in Clarity is made by possible by the built-in function: `get-burn-block-info?`  and the keyword `burn-block-height` .
 
@@ -211,6 +211,74 @@ Reading Bitcoin state in Clarity is made by possible by the built-in function: `
 ;; Returns (some 0xe671...)
 ```
 
+<details>
+
+<summary>Verifying bitcoin transactions in Clarity</summary>
+
+One of the most popular Clarity contracts that leverages read access into Bitcoin is the `clarity-bitcoin-lib` contract, maintained by Friedger. This contract intakes data of a bitcoin transaction and will verify that it was indeed mined in a Bitcoin block.
+
+For more info: [https://github.com/friedger/clarity-bitcoin](https://github.com/friedger/clarity-bitcoin)
+
+</details>
+
+***
+
+### Flexible and secure modularization
+
+Many DAOs of the major Stacks apps implement a familiar contract design and architecture. This familiarity is inspired by the [ExecutorDAO](https://github.com/MarvinJanssen/executor-dao) framework, written by Marvin Janssen. This ExecutorDAO framework leverages the flexibility of having modularization in your smart contracts by compartmentalizing duties.
+
+The core tenets of the ExecutorDAO framework that make this possible are:
+
+1. Proposals are smart contracts.
+2. The core executes, the extensions give form.
+3. Ownership control happens via sending context.
+
+{% tabs %}
+{% tab title="Main DAO contract" %}
+The main DAO contract acts as the core contract where its sole purpose is to execute proposals and to keep a list of authorised extensions.
+
+{% code title="dao.clar" expandable="true" %}
+```clarity
+(use-trait proposal-trait .proposal-trait.proposal-trait)
+(use-trait extension-trait .extension-trait.extension-trait)
+
+;; ...
+
+;; --- Authorisation check
+(define-private (is-self-or-extension)
+	(ok (asserts! (or (is-eq tx-sender (as-contract tx-sender)) (is-extension contract-caller)) err-unauthorised))
+)
+
+;; ...
+
+;; --- Admin function to execute proposals
+(define-public (execute (proposal <proposal-trait>) (sender principal))
+	(begin
+		(try! (is-self-or-extension))
+		(asserts! (map-insert executed-proposals (contract-of proposal) block-height) err-already-executed)
+		(print {event: "execute", proposal: proposal})
+		(as-contract (contract-call? proposal execute sender))
+	)
+)
+```
+{% endcode %}
+{% endtab %}
+
+{% tab title="A proposal extension contract" %}
+This proposal contract updates the whitelist of an example `.nft-escrow` contract that is owned by the main DAO contract. This proposal contract implements the `proposal-trait` and is passed into the main DAO contract's `execute` function for final approved execution.
+
+{% code title="proposal.clar" %}
+```clarity
+(impl-trait .proposal-trait.proposal-trait)
+
+(define-public (execute (sender principal))
+	(contract-call? .nft-escrow set-whitelisted .some-nft true)
+)
+```
+{% endcode %}
+{% endtab %}
+{% endtabs %}
+
 ***
 
 ### Testing Clarity Smart Contracts