docs: replace Blobs with Ikura

Author: rphmeier

README.md

@@ -1,11 +1,11 @@
-# Blobs
+# Ikura
 
 Blobchains on Polkadot and Kusama
 
 ## Project Structure
 
 <pre>
-<a href=".">blobs</a>: The blobs monorepo.
+<a href=".">blobs</a>: The Ikura monorepo.
 ├──<a href="./adapters">adapters</a>: Adapters for various rollup development kits (RDK).
 │   ├── <a href="./adapters/rollkit">rollkit</a>: An adapter connecting Rollkit to Ikura
 │   ├── <a href="./adapters/sovereign">sovereign</a>: An adapter connecting Sovereign to Ikura.

docs-site/docs/intro.md

@@ -4,25 +4,29 @@ title: Introduction
 
 ---
 
-## Blobs
+## Ikura
 
-The Blobs project exposes **sequencing** and **data availability** capabilities of [Polkadot](https://polkadot.network) and [Kusama](https://kusama.network) for general use. Use-cases include rollups and inscriptions.
+Ikura exposes **sequencing** and **data availability** capabilities of [Polkadot](https://polkadot.network) and [Kusama](https://kusama.network) for general use. Use-cases include rollups and inscriptions.
 
-The Blobs codebase is located at https://github.com/thrumdev/blobs. There is a live parachain on Kusama with Parachain ID 3338 running the Blobs runtime.
+The Ikura codebase is located at https://github.com/thrumdev/blobs.
 
-In this documentation site, we'll often use the term Polkadot to refer to the Polkadot Relay Chain - the hub chain which provides security for everything running on Polkadot. Kusama runs on the same technology as Polkadot, so the Kusama version of Blobs works identically to the Polkadot version, just with a different network. You can mentally substitute "Polkadot" for "Kusama" when thinking about the Kusama version of Blobs.
+In this documentation site, we'll often use the term Polkadot to refer to the Polkadot Relay Chain - the hub chain which provides security for everything running on Polkadot. Kusama runs on the same technology as Polkadot, so the Kusama version of Ikura (Gondatsu) works identically to the Polkadot version, just with a different network. You can mentally substitute "Polkadot" for "Kusama" when thinking about the Kusama version of Ikura.
 
-Blobs enables users to submit arbitrary data to the chain and receive guarantees about the availability of that data, as well as proofs of the order in which data were submitted. Namely:
+Ikura enables users to submit arbitrary data to the blockchain chain and receive guarantees about the availability of that data, as well as proofs of the order in which data were submitted. Those guarantees are:
   1. The data can be fetched from the Polkadot/Kusama validator set for up to 24 hours after submission and cannot be withheld.
   2. A commitment to the data's availability is stored within the blobchain and used as a proof of guarantee (1) to computer programs, such as smart contracts or Zero-Knowledge circuits.
 
-Data Availability is a key component of Layer-2 scaling approaches, and is already part of Polkadot and Kusama for use in securing Parachains. Blobs will bring this capability out to much broader markets.
+Data Availability is a key component of Layer-2 scaling approaches, and is already part of Polkadot and Kusama for use in securing Parachains. Ikura will bring this capability to use-cases beyond parachains with a minimal interface.
 
-Blobs makes a **relay-chain token utility commitment** now and forever. Submitting blobs will always make use of the DOT token on Polkadot and the KSM token on Kusama, as this is the approach with the least user friction.
+Ikura makes a **relay-chain token utility commitment** now and forever. Submitting blobs will always make use of the DOT token on Polkadot and the KSM token on Kusama, as this is the approach with the least user friction.
+
+## Gondatsu
+
+The version of Ikura targeting the Kusama network is **Gondatsu**. It has Parachain ID 3338 running. We currently do not make any long-term stability commitment for Gondatsu. Gondatsu currently is _centrally controlled_ with a sudo (admin) key. It is experimental.
 
 ## Integrations
 
-Blobs supports a variety of rollup SDKs out of the box.
+Ikura supports a variety of rollup SDKs out of the box.
   - [x] Rollkit
   - [x] Sovereign SDK
   - [ ] OP Stack

docs-site/docs/node-operators/getting-started.md

@@ -4,18 +4,18 @@ title: Getting Started
 
 ## Releases
 
-At the moment, there are no downloadable binary releases available of the Blobs node. We recommend building a binary from source.
+At the moment, there are no downloadable binary releases available of the Ikura node. We recommend building a binary from source.
 
 ## Node Architecture
 
-Blobs is a standard Polkadot-SDK parachain node, which means that it actually runs two nodes:
-  1. A node for the Parachain (Blobs) on Polkadot or Kusama
+Ikura is a standard Polkadot-SDK parachain node, which means that it actually runs two nodes:
+  1. A node for the Parachain (Ikura) on Polkadot or Kusama
   2. A node for the Relay Chain, Polkadot or Kusama.
 
 You can pass arguments to each one of these underlying nodes with the following approach:
 
 ```sh
-./ikura-node --arg-for-blobs --arg2-for-blobs -- --arg-for-relay --arg2-for-relay
+./ikura-node --arg-for-ikura --arg2-for-ikura -- --arg-for-relay --arg2-for-relay
 ```
 
 ## Hardware Requirements
@@ -58,9 +58,9 @@ Running the node:
 target/release/ikura-node --chain gondatsu
 ```
 
-## Blobs and Storage Usage
+## Ikura and Storage Usage
 
-Blobs can potentially use enormous amounts of disk space under heavy usage. This is because all historical blobs are stored within the blobchain's history. While the Polkadot and Kusama expunge ancient blobs after 24 hours, any full node of the blobchain will have all the blobs going back to the genesis, as well as all of the other block data.
+Ikura can potentially use enormous amounts of disk space under heavy usage. This is because all historical blobs are stored within the blobchain's history. While the Polkadot and Kusama expunge ancient blobs after 24 hours, any full node of the blobchain will have all the blobs going back to the genesis, as well as all of the other block data.
 
 To avoid this issue, run with `--blocks-pruning <number>`, where `number` is some relatively small value such as `1000` to avoid keeping all historical blobs.
 

docs-site/docs/protocol/data-availability.md

@@ -3,7 +3,7 @@ sidebar_position: 1
 title: Data Availability
 ---
 
-Blobs provides reliable and high-throughput Data Availability services. Before diving into exactly what this is, we'll take a quick detour through Rollup scaling solutions.
+Ikura provides reliable and high-throughput Data Availability services. Before diving into exactly what this is, we'll take a quick detour through Rollup scaling solutions.
 
 ## Rollup Architecture
 
@@ -26,23 +26,23 @@ Data Availability serves an additional purpose, which is to ensure that submitte
 
 Regardless of which proving mechanism is used, sequencing and data availability are common to all protocols under this blueprint.
 
-Rollups use Blobs for both sequencing and Data Availability.
+Rollups use Ikura for both sequencing and Data Availability.
 
 ## Data Availability
 
-Blobs is a wrapper over Polkadot's Data Availability system. Any data made available via Blobs is using the Polkadot validators under the hood. In this section, we'll explore how Polkadot makes data available.
+Ikura is a wrapper over Polkadot's Data Availability system. Any data made available via Ikura is using the Polkadot validators under the hood. In this section, we'll explore how Polkadot makes data available.
 
-A Blob consists of two things: a **namespace** and some **data**. The namespace is a kind of tag which allows for blobs to be filtered by an observer, and the data is just a bunch of bytes. To Blobs, the content of the blobs does not matter.
+A Blob consists of two things: a **namespace** and some **data**. The namespace is a kind of tag which allows for blobs to be filtered by an observer, and the data is just a bunch of bytes. To Ikura, the content of the blobs does not matter.
 
-Blobs is a blockchain secured by Polkadot, where the blocks may contain Blob transactions.
+Ikura is a blockchain secured by Polkadot, where the blocks may contain Blob transactions.
 
 Every block is erasure-coded, replicated, and distributed across Polkadot's entire validator set. The block is split up into pieces, with one piece for each Polkadot validator. Any set of more than one-third of the pieces is enough to recover the entire data.
 
 ### Example: The Path of a Blob
-  1. First, the user signs a transaction containing the Blob and submits it to a Blobs node.
-  2. Once the transaction has circulated through the network, a Blobs block authoring node bundles it into a block.
+  1. First, the user signs a transaction containing the Blob and submits it to an Ikura node.
+  2. Once the transaction has circulated through the network, a Ikura block authoring node bundles it into a block.
   3. The block authoring node submits the block to some assigned Polkadot validators.
-  4. Those Polkadot validators approve the Blobs block and the Blobs block's header is placed into a Polkadot Relay Chain Block
-  5. After this, the Blobs block, including all the transactions within it, is erasure-coded and split into redundant pieces, one for each Polkadot validator.
+  4. Those Polkadot validators approve the Ikura block and the Ikura block's header is placed into a Polkadot Relay Chain Block
+  5. After this, the Ikura block, including all the transactions within it, is erasure-coded and split into redundant pieces, one for each Polkadot validator.
   6. Each validator attempts to fetch their piece over the p2p network. Polkadot requires that at least two-thirds of validators sign a statement that they have fetched and stored their piece, or the whole process must revert back to step (2).
 

docs-site/docusaurus.config.js

@@ -8,7 +8,7 @@ import {themes as prismThemes} from 'prism-react-renderer';
 
 /** @type {import('@docusaurus/types').Config} */
 const config = {
-  title: 'Blobs - Documentation',
+  title: 'Ikura - Documentation',
   tagline: 'Blobchains on Polkadot and Kusama',
   favicon: 'img/blobs-favicon-line.webp',
 
@@ -21,7 +21,7 @@ const config = {
   // GitHub pages deployment config.
   // If you aren't using GitHub pages, you don't need these.
   organizationName: 'ThrumDev', // Usually your GitHub org/user name.
-  projectName: 'blobs', // Usually your repo name.
+  projectName: 'Ikura', // Usually your repo name.
 
   onBrokenLinks: 'throw',
   onBrokenMarkdownLinks: 'warn',
@@ -60,7 +60,7 @@ const config = {
       // Replace with your project's social card
       image: 'img/docusaurus-social-card.jpg',
       navbar: {
-        title: 'Blobs',
+        title: 'Ikura',
         logo: {
           alt: 'Thrum Logo',
           src: './img/blobs-simple.png',