GITBOOK-170: Add block production diagram

stacks-network · Aug 29, 2024 · fe1678b · fe1678b
1 parent 49b5295
commit fe1678b
Show file tree

Hide file tree

Showing 12 changed files with 8 additions and 4 deletions.
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1).png b/.gitbook/assets/image (1) (1).png
diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png
diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png
diff --git a/concepts/block-production/README.md b/concepts/block-production/README.md
@@ -11,3 +11,7 @@ There are two primary parties in Stacks block production: miners and stackers. M
 Stacking is another action conducted by stackers that is a necessary prerequisite to signing. We'll cover how all of this works together in the next three sections.
 
 For an in-depth overview of the technical aspects of how block production works after the Nakmoto Upgrade, be sure to read through [SIP-021](https://github.com/stacksgov/sips/blob/feat/sip-021-nakamoto/sips/sip-021/sip-021-nakamoto.md).
+
+Here's a diagram outlining the block production process under Nakamoto rules. We'll dig into each part of this in the following docs.
+
+<figure><img src="../../.gitbook/assets/image.png" alt=""><figcaption></figcaption></figure>
diff --git a/concepts/transactions/post-conditions.md b/concepts/transactions/post-conditions.md
@@ -28,7 +28,7 @@ When you use a Stacks wallet like the Hiro web wallet and initiate a transaction
 
 Here's what that looks like:
 
-<figure><img src="../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 In this example, if the smart contract does not transfer one fabulous-frog NFT and and take 50 STX from the user, the transaction will abort.
 

diff --git a/guides-and-tutorials/running-a-signer/README.md b/guides-and-tutorials/running-a-signer/README.md
@@ -195,7 +195,7 @@ To make sure your signer is running successfully, run `docker ps` to list your r
 
 You should see something like this
 
-<figure><img src="../../.gitbook/assets/image (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 Now check the logs of that container by running:
 
@@ -304,7 +304,7 @@ If when running your node you get a connection refused error that looks like thi
 
 First, be sure that you have the proper entry point specified in your `node-config.toml` file as specified in the [How to Run a Signer](./) doc.
 
-<figure><img src="../../.gitbook/assets/image.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1).png" alt=""><figcaption></figcaption></figure>
 
 If you are inside a Docker container with default bridging mode, then localhost is not available, and you'll need to point to the Docker host.
 

diff --git a/nakamoto-upgrade/nakamoto-in-10-minutes.md b/nakamoto-upgrade/nakamoto-in-10-minutes.md
@@ -44,7 +44,7 @@ This elegant design creates a cooperative relationship between miners and stacke
 
 Here is a diagram outlining miner and signer behavior.
 
-<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ### Bitcoin MEV Mitigation