Merge branch 'main' into patch-1

rollkit · Oct 13, 2023 · 004983d · 004983d
2 parents 81ebe67 + 194d994
commit 004983d
Show file tree

Hide file tree

Showing 8 changed files with 11 additions and 11 deletions.
diff --git a/.vitepress/config.ts b/.vitepress/config.ts
@@ -230,7 +230,7 @@ function sidebarHome() {
       items: [
         { text: 'Overview', link: '/blog/overview'},
         { text: 'Introducing Rollkit', link: '/blog/introducing-rollkit' },
-        { text: 'Sovereign rollups on Bitcoin with Rollkit', link: '/blog/sovereign-rollups-on-bitcoin-with-rollkit' },
+        { text: 'Sovereign rollups on Bitcoin with Rollkit', link: '/blog/sovereign-rollups-on-bitcoin' },
         { text: "Let's Roll - Rollkit's Community Call", link: '/blog/lets-roll-community-call' },
       ]
     }

diff --git a/blog/lets-roll-community-call.md b/blog/lets-roll-community-call.md
@@ -21,7 +21,7 @@ By Joseph Al-Chami
 ![Rollkit blog cover](/lets-roll.jpg)
 _Originally published on 8 March 2023_
 
-Last Sunday, we released the first [research implementation](https://rollkit.dev/blog/sovereign-rollups-on-bitcoin-with-rollkit) that allows Rollkit rollups to use Bitcoin for data availability.
+Last Sunday, we released the first [research implementation](https://rollkit.dev/blog/sovereign-rollups-on-bitcoin) that allows Rollkit rollups to use Bitcoin for data availability.
 
 [This announcement](https://twitter.com/RollkitDev/status/1632438374513676288) has sparked a lot of curiosity and excitement in the community. Many developers are starting to imagine what the future of sovereign rollups could look like on Bitcoin and other data availability layers. They’re looking for ways to innovate using this integration, to replicate it on other layer 1 blockchains, to identify challenges and to suggest improvements.
 

diff --git a/blog/overview.md b/blog/overview.md
@@ -9,7 +9,7 @@ Welcome to our blog! Here, you'll find a variety of articles on a range of topic
 ## Table of Contents
 
 - [Introducing Rollkit](/blog/introducing-rollkit)
-- [Sovereign rollups on Bitcoin with Rollkit](/blog/sovereign-rollups-on-bitcoin-with-rollkit)
+- [Sovereign rollups on Bitcoin with Rollkit](/blog/sovereign-rollups-on-bitcoin)
 - [Let's Roll - Rollkit's Community Call](/blog/lets-roll-community-call)
 
 Stay tuned for more exciting content!
diff --git a/...ereign-rollups-on-bitcoin-with-rollkit.md → blog/sovereign-rollups-on-bitcoin.md b/...ereign-rollups-on-bitcoin-with-rollkit.md → blog/sovereign-rollups-on-bitcoin.md
diff --git a/learn/intro.md b/learn/intro.md
@@ -65,5 +65,5 @@ If you're familiar with Rollkit, you may want to skip to the [tutorials section]
 
 - [Overview](/blog/overview)
 - [Introducing Rollkit](/blog/introducing-rollkit)
-- [Sovereign rollups on Bitcoin with Rollkit](/blog/sovereign-rollups-on-bitcoin-with-rollkit)
-- ["Let's Roll - Rollkit's Community Call"](/blog/lets-roll-community-call)
+- [Sovereign rollups on Bitcoin with Rollkit](/blog/sovereign-rollups-on-bitcoin)
+- ["Let's Roll - Rollkit's Community Call"](/blog/lets-roll-community-call)
diff --git a/tutorials/full-and-sequencer-node.md b/tutorials/full-and-sequencer-node.md
@@ -102,7 +102,7 @@ submit blobs and can be set with the following command once your
 local-celestia-devnet is running:
 
 ```bash
-export AUTH_TOKEN=$(docker exec $(docker ps -q)  celestia bridge --node.store /bridge  auth admin)
+export AUTH_TOKEN=$(docker exec $(docker ps -q)  celestia bridge --node.store /home/celestia/bridge/ auth admin)
 ```
 
 This will set the local-celestia-devnet bridge node auth token. This

diff --git a/tutorials/gm-world.md b/tutorials/gm-world.md
@@ -310,7 +310,7 @@ this process can be done on any machine of your choosing. We tested out the Devn
 First, run the [`local-celestia-devnet`](https://github.com/rollkit/local-celestia-devnet) by running the following command:
 
 ```bash
-docker run --platform linux/amd64 -p 26657:26657 -p 26658:26658 -p 26659:26659 ghcr.io/rollkit/local-celestia-devnet:v0.11.0-rc8
+docker run -i -t --platform linux/amd64 -p 26657:26657 -p 26658:26658 -p 26659:26659 ghcr.io/rollkit/local-celestia-devnet:v0.11.0-rc12
 ```
 
 When passing the `--rollkit.da_config` flag later in the tutorial,
@@ -319,7 +319,7 @@ write permission is required to submit blobs and can be obtained
 with the following command once your local-celestia-devnet is running:
 
 ```bash
-docker exec $(docker ps -q)  celestia bridge --node.store /bridge  auth admin
+docker exec $(docker ps -q)  celestia bridge --node.store /home/celestia/bridge/ auth admin
 ```
 
 This will give you the local-celestia-devnet bridge node auth token. This
@@ -336,7 +336,7 @@ local network, this will make sure you can post rollup blocks to your Celestia D
 First, set your auth token:
 
 ```bash
-export CELESTIA_NODE_AUTH_TOKEN=$(docker exec $(docker ps -q)  celestia bridge --node.store /bridge  auth admin)
+export CELESTIA_NODE_AUTH_TOKEN=$(docker exec $(docker ps -q)  celestia bridge --node.store /home/celestia/bridge/ auth admin)
 ```
 
 Next, check your balance:
@@ -467,7 +467,7 @@ Remember that the following command assumes that there is only one container,
 otherwise you can pass the container name.
 
 ```bash
-export AUTH_TOKEN=$(docker exec $(docker ps -q)  celestia bridge --node.store /bridge  auth admin)
+export AUTH_TOKEN=$(docker exec $(docker ps -q)  celestia bridge --node.store /home/celestia/bridge/ auth admin)
 ```
 
 Run the `init-local.sh` script:

diff --git a/tutorials/starter-rollup.md b/tutorials/starter-rollup.md
@@ -22,7 +22,7 @@ git clone https://github.com/rollkit/gm-starter.git && cd gm-starter
 In a second terminal instance, start the local-celestia-devnet:
 
 ```bash
-docker run --platform linux/amd64 -p 26657:26657 -p 26658:26658 -p 26659:26659 ghcr.io/rollkit/local-celestia-devnet:v0.11.0-rc8
+docker run -i -t --platform linux/amd64 -p 26657:26657 -p 26658:26658 -p 26659:26659 ghcr.io/rollkit/local-celestia-devnet:v0.11.0-rc12
 ```
 
 When passing the `--rollkit.da_config` flag later in the tutorial, it will require `auth_token`` to be passed in. The auth token with write permission is required to submit blobs and can be obtained from the logs on local-celestia-devnet before the bridge node starts.