diff --git a/.github/workflows/repo--vercel-deploy.yml b/.github/workflows/repo--vercel-deploy.yml index ff61914bdfc..03785e60111 100644 --- a/.github/workflows/repo--vercel-deploy.yml +++ b/.github/workflows/repo--vercel-deploy.yml @@ -52,4 +52,4 @@ jobs: run: vercel build ${{ inputs.flags }} --token=${{ secrets.vercel_token }} - name: Deploy Project Artifacts to Vercel - run: vercel deploy --prebuilt ${{ inputs.flags }} --token=${{ secrets.vercel_token }} + run: vercel deploy --prebuilt ${{ inputs.flags }} --force --token=${{ secrets.vercel_token }} diff --git a/packages/docs-site/README.md b/packages/docs-site/README.md index 54439811e51..a2c45f68674 100644 --- a/packages/docs-site/README.md +++ b/packages/docs-site/README.md @@ -18,4 +18,4 @@ This is where we extend the `docsSchema`. ## Contributing -View CONTRIBUTING.md inside of the [Taiko monorepo](https://github.com/taikoxyz/taiko-mono/blob/main/CONTRIBUTING.md). +View CONTRIBUTING.md inside of the [Taiko Alethia monorepo](https://github.com/taikoxyz/taiko-mono/blob/main/CONTRIBUTING.md). diff --git a/packages/docs-site/astro.config.ts b/packages/docs-site/astro.config.ts index 0c4eeda19e7..188fb7defa6 100644 --- a/packages/docs-site/astro.config.ts +++ b/packages/docs-site/astro.config.ts @@ -19,7 +19,6 @@ export default defineConfig({ exclude: [ "/api-reference/bridge-relayer", "/api-reference/event-indexer", - "/api-reference/prover-server", ], }), starlightOpenAPI([ @@ -67,7 +66,7 @@ export default defineConfig({ { label: "Core Concepts", items: [ - { label: "What is Taiko?", link: "/core-concepts/what-is-taiko/" }, + { label: "What is Taiko Alethia?", link: "/core-concepts/what-is-taiko-alethia/" }, { label: "Contestable rollups (BCR)", link: "/core-concepts/contestable-rollup/", @@ -84,21 +83,21 @@ export default defineConfig({ ], }, { - label: "Taiko Protocol", + label: "Taiko Alethia Protocol", items: [ { label: "Codebase Analysis", collapsed: true, items: [ - {label: "TaikoL1 Contract", link: "/taiko-protocol/codebase-analysis/taikol1-contract"}, - {label: "TaikoL2 Contract", link: "/taiko-protocol/codebase-analysis/taikol2-contract"}, - {label: "SGXVerifier Contract", link: "/taiko-protocol/codebase-analysis/sgxverifier-contract"}, + {label: "TaikoL1 Contract", link: "/taiko-alethia-protocol/codebase-analysis/taikol1-contract"}, + {label: "TaikoL2 Contract", link: "/taiko-alethia-protocol/codebase-analysis/taikol2-contract"}, + {label: "SGXVerifier Contract", link: "/taiko-alethia-protocol/codebase-analysis/sgxverifier-contract"}, ], }, - { label: "Block states", link: "/taiko-protocol/block-states" }, - { label: "Bridging", link: "/taiko-protocol/bridging" }, - { label: "Economics", link: "/taiko-protocol/economics" }, - { label: "Taiko nodes", link: "/taiko-protocol/taiko-nodes" }, + { label: "Block states", link: "/taiko-alethia-protocol/block-states" }, + { label: "Bridging", link: "/taiko-alethia-protocol/bridging" }, + { label: "Economics", link: "/taiko-alethia-protocol/economics" }, + { label: "Taiko nodes", link: "/taiko-alethia-protocol/taiko-alethia-nodes" }, ] }, { @@ -135,8 +134,8 @@ export default defineConfig({ collapsed: true, items: [ { - label: "Run a Taiko node with Docker", - link: "/guides/node-operators/run-a-taiko-node-with-docker/", + label: "Run a Taiko Alethia node with Docker", + link: "/guides/node-operators/run-a-taiko-alethia-node-with-docker/", }, { @@ -144,23 +143,23 @@ export default defineConfig({ link: "/guides/node-operators/run-an-ethereum-testnet-node/", }, { - label: "Build a Taiko node from source", - link: "/guides/node-operators/build-a-taiko-node-from-source/", + label: "Build a Taiko Alethia node from source", + link: "/guides/node-operators/build-a-taiko-alethia-node-from-source/", }, { - label: "Run a Taiko mainnet node from source", - link: "/guides/node-operators/run-a-mainnet-taiko-node-from-source/", + label: "Run a node for Taiko Alethia", + link: "/guides/node-operators/run-a-node-for-taiko-alethia/", }, { - label: "Run a Taiko testnet node from source", - link: "/guides/node-operators/run-a-testnet-taiko-node-from-source/", + label: "Run a node for Taiko Hekla", + link: "/guides/node-operators/run-a-node-for-taiko-hekla/", }, { - label: "Run a Taiko proposer", + label: "Enable a proposer", link: "/guides/node-operators/enable-a-proposer/", }, { - label: "Run a Taiko prover", + label: "Enable a prover", link: "/guides/node-operators/enable-a-prover/", }, { @@ -179,12 +178,12 @@ export default defineConfig({ label: "Network Reference", items: [ { - label: "Mainnet addresses", - link: "/network-reference/mainnet-addresses", + label: "Alethia addresses", + link: "/network-reference/alethia-addresses", }, { - label: "Testnet addresses", - link: "/network-reference/testnet-addresses", + label: "Hekla addresses", + link: "/network-reference/hekla-addresses", }, { label: "Differences from Ethereum", diff --git a/packages/docs-site/src/assets/content/docs/network-reference/proof-tier-config-mn.webp b/packages/docs-site/src/assets/content/docs/network-reference/proof-tier-config-alethia.webp similarity index 100% rename from packages/docs-site/src/assets/content/docs/network-reference/proof-tier-config-mn.webp rename to packages/docs-site/src/assets/content/docs/network-reference/proof-tier-config-alethia.webp diff --git a/packages/docs-site/src/assets/content/docs/taiko-protocol/based-economics.png b/packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/based-economics.png similarity index 100% rename from packages/docs-site/src/assets/content/docs/taiko-protocol/based-economics.png rename to packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/based-economics.png diff --git a/packages/docs-site/src/assets/content/docs/taiko-protocol/bridging-dest-chain.webp b/packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/bridging-dest-chain.webp similarity index 100% rename from packages/docs-site/src/assets/content/docs/taiko-protocol/bridging-dest-chain.webp rename to packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/bridging-dest-chain.webp diff --git a/packages/docs-site/src/assets/content/docs/taiko-protocol/bridging-source-chain.webp b/packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/bridging-source-chain.webp similarity index 100% rename from packages/docs-site/src/assets/content/docs/taiko-protocol/bridging-source-chain.webp rename to packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/bridging-source-chain.webp diff --git a/packages/docs-site/src/assets/content/docs/taiko-protocol/proposed.png b/packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/proposed.png similarity index 100% rename from packages/docs-site/src/assets/content/docs/taiko-protocol/proposed.png rename to packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/proposed.png diff --git a/packages/docs-site/src/assets/content/docs/taiko-protocol/proved.png b/packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/proved.png similarity index 100% rename from packages/docs-site/src/assets/content/docs/taiko-protocol/proved.png rename to packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/proved.png diff --git a/packages/docs-site/src/assets/content/docs/taiko-protocol/taiko-nodes.png b/packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/taiko-nodes.png similarity index 100% rename from packages/docs-site/src/assets/content/docs/taiko-protocol/taiko-nodes.png rename to packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/taiko-nodes.png diff --git a/packages/docs-site/src/assets/content/docs/taiko-protocol/verified.png b/packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/verified.png similarity index 100% rename from packages/docs-site/src/assets/content/docs/taiko-protocol/verified.png rename to packages/docs-site/src/assets/content/docs/taiko-alethia-protocol/verified.png diff --git a/packages/docs-site/src/assets/docs-logo.svg b/packages/docs-site/src/assets/docs-logo.svg index 658909b1a84..fc59d8f4ede 100644 --- a/packages/docs-site/src/assets/docs-logo.svg +++ b/packages/docs-site/src/assets/docs-logo.svg @@ -1,9 +1,9 @@ - - - - + + + + - + diff --git a/packages/docs-site/src/assets/logo-dark.svg b/packages/docs-site/src/assets/logo-dark.svg index 74b63e542e9..2e052286b19 100644 --- a/packages/docs-site/src/assets/logo-dark.svg +++ b/packages/docs-site/src/assets/logo-dark.svg @@ -1,8 +1,15 @@ - - - - - - - + + + + + + + + + + + + + + diff --git a/packages/docs-site/src/assets/logo-light.svg b/packages/docs-site/src/assets/logo-light.svg index 07be42d8fa5..324f55a989c 100644 --- a/packages/docs-site/src/assets/logo-light.svg +++ b/packages/docs-site/src/assets/logo-light.svg @@ -1,8 +1,15 @@ - - - - - - - + + + + + + + + + + + + + + diff --git a/packages/docs-site/src/assets/taiko-og-logo.png b/packages/docs-site/src/assets/taiko-og-logo.png index a63605d14de..7169c1dd1a6 100644 Binary files a/packages/docs-site/src/assets/taiko-og-logo.png and b/packages/docs-site/src/assets/taiko-og-logo.png differ diff --git a/packages/docs-site/src/components/starlight/SiteTitle.astro b/packages/docs-site/src/components/starlight/SiteTitle.astro index 280f48c8ff8..1a4364d90b4 100644 --- a/packages/docs-site/src/components/starlight/SiteTitle.astro +++ b/packages/docs-site/src/components/starlight/SiteTitle.astro @@ -25,7 +25,7 @@ const self = "/start-here/getting-started";
+ +2. **Multiple Rollups Are the Future** + + - The Ethereum roadmap anticipates a **multi-rollup ecosystem**. + - Inception layers allow for **seamless rollup interoperability**. + +
+ +3. **Unlocking Extensible Scalability** + + - Multiple **Taiko L2 instances** can scale horizontally. + - Multiple **L3 instances on top of L2** scale **vertically** (stacked rollups). + - L3s inherit the **same security model** as L2s, ensuring trustless execution. + +--- + +## Benefits of Inception Layers + +1. **Ethereum-Equivalence Across Layers** + + - **L2s and L3s** share the **same execution environment** as Ethereum. + - Developers can **reuse smart contracts** across layers without modifications. + - **EVM compatibility is preserved**, ensuring seamless migration. + +
+ +2. **Optimized for Composability & Interoperability** + + - Rollups at different layers can **efficiently interact** using **Merkle proofs**. + - This enables **secure, trustless message passing** between L1, L2, and L3. + +
+ +3. **Mitigating UX Fragmentation** + + - A major downside of a multi-rollup world is **liquidity fragmentation** and **complex cross-chain UX**. + - **Taiko’s inception layers combat this** by using built-in **arbitrary message passing**. + - One rollup can natively **read Merkle proofs** from another, avoiding fragmented liquidity. + +--- + +## Inception Layers Architecture + +--- + +### **Multi-Layer Rollup Structure** + +The following illustrates how **Ethereum, Taiko L2, and Taiko L3 layers interconnect**: ![Inception layers diagram](~/assets/content/docs/core-concepts/inception-layers-diagram.png) -For more information on how Taiko's message passing works see the concept page on [Bridging](/taiko-protocol/bridging). +- **Ethereum L1** serves as the base layer for settlement and data availability. +- **Multiple Taiko L2s** operate in parallel, processing transactions independently. +- **Recursive Taiko L3s** are deployed on top of L2s, allowing for additional scalability. + +### **Built-in Message Passing Between Layers** + +Ethereum-equivalence across L2s, L3s, and beyond means **native arbitrary message passing**. This is achieved via: + +- **Merkle Proofs:** Enabling trustless state validation across rollups. +- **Cross-Layer Communication Protocols:** Ensuring frictionless interoperability. + +--- + +## Further Reading + +For more details on **cross-layer communication**, refer to the [Bridging](/taiko-alethia-protocol/bridging) documentation. diff --git a/packages/docs-site/src/content/docs/core-concepts/multi-proofs.md b/packages/docs-site/src/content/docs/core-concepts/multi-proofs.md index 84be7328275..3bdd8efc7c0 100644 --- a/packages/docs-site/src/content/docs/core-concepts/multi-proofs.md +++ b/packages/docs-site/src/content/docs/core-concepts/multi-proofs.md @@ -3,89 +3,139 @@ title: Multi-proofs description: Core concept page for "Multi-proofs". --- -Taiko supports multi-proofs through a mixture of zkVMs, TEE, and guardian proofs. Check out our blog post on zkVMs [here](https://taiko.mirror.xyz/e_5GeGGFJIrOxqvXOfzY6HmWcRjCjRyG0NQF1zbNpNQ) and a Twitter thread on our Raiko architecture [here](https://x.com/taikoxyz/status/1791201812768600209). +Taiko Alethia supports **multi-proofs**, leveraging a combination of **zkVMs, Trusted Execution Environments (TEEs) using SGX, and Guardian proofs**. This multi-proof approach enhances security and robustness by reducing reliance on a single proving system. -## Proving Taiko blocks +For a deeper dive, explore: -The purpose of proving blocks is to give certainty to bridges about the execution that happened in the rollup. To rely on some state that happened inside of the rollup, a bridge will want a proof that everything was done correctly. On Taiko you can run a node as a prover and prove blocks, permissionlessly. This means that you can examine the proposed blocks on the TaikoL1 contract, and generate proofs for them. Currently, any prover can create proofs for proposed blocks. This means that the number of "state transitions" has no upper bound, because we don't know what is the correct state transition yet. Only first prover with a valid proof of the correct state transition will receive the reward of `ETH` (and possibly any `ERC20` or even NFTs if the Prover pool implementation favors it). +- **zkVMs in Taiko** [Blog Post](https://taiko.mirror.xyz/e_5GeGGFJIrOxqvXOfzY6HmWcRjCjRyG0NQF1zbNpNQ) +- **Raiko Architecture** [Twitter Thread](https://x.com/taikoxyz/status/1791201812768600209) -## Verified blocks and parallel proving +--- + +## Proving Taiko Alethia Blocks + +--- + +### **Why is proving required?** + +Proving blocks ensures that the **state transitions within the rollup are valid**, providing certainty to **bridges and other dependent systems** that L2 transactions were executed correctly. + +### **Prover Participation** + +- Anyone can **permissionlessly** run a node and prove blocks. +- Provers examine proposed blocks on the **TaikoL1 contract**, generate proofs, and submit them. +- The **first prover** with a valid proof of the correct state transition receives the **proof reward**. +- Rewards can be in **ETH, ERC20 tokens, or even NFTs**, depending on the implementation. + +--- + +## Verified Blocks and Parallel Proving -There are three states that a block can be in on Taiko: +--- + +### **Block States** + +A block in Taiko progresses through three key states: -- Proposed -- Proved -- Verified +1. **Proposed** (Initial state, pending proof submission) +2. **Proved** (At least one valid proof exists) +3. **Verified** (Proof is confirmed along with parent blocks) -We already know what a proposed block is (must pass at least the block-level intrinsic validity tests to be accepted by the TaikoL1 contract). Next, a proposed block can be valid or invalid, depending on whether it passes the transaction list intrinsic validity test. A block is invalid if it fails the transaction list intrinsic validity test, and this block is not created on Taiko. +### **Parallel Proof Generation** -Now, a block can be proved, but also further "verified". What's the difference? A block is proved if it has a valid proof which proves a state transition from one state (parent block) to another (current block). However, blocks are proven in parallel by the decentralized provers. So while a block can prove a parent block transitions to the current block, we don't know if the parent block itself has been proven. As you can see, for a block to be "verified", it needs to prove the valid state transition to the current block, but the parent also needs to be verified. We assume that the genesis block (which has no parent), is verified. So all the children blocks from genesis to the current block need to have proofs of their state transition for the current block to be "verified". +- Blocks are proved **independently** in parallel. +- For a block to be **verified**, its **parent block must also be verified**. +- Taiko verifies **blocks in batches** instead of sequentially. +- **A verified block may have `verifiedTransitionId == 0` due to batch verification.** -A recent change in our protocol means we verify blocks in batches. Previously, so long as a block was verified it's `verifiedTransitionId` in block data would be non-zero; now that we verify in batches, only the last block in a batch will have a non-zero `verifiedTransitionId`. +#### **Illustrative Stages** -i.e. It is now possible for a block to be verified, and have `verifiedTransitionId` == 0. +**Proposed Blocks:** +![Proposed](~/assets/content/docs/taiko-alethia-protocol/proposed.png) -For the visual learners here is a visualization of the three stages (proposed -> proved -> verified) +**Proved Blocks:** +![Proved](~/assets/content/docs/taiko-alethia-protocol/proved.png) -**Proposed:** +**Verified Blocks:** +![Verified](~/assets/content/docs/taiko-alethia-protocol/verified.png) -![proposed](~/assets/content/docs/taiko-protocol/proposed.png) +--- + +## Off-Chain Prover Market (PBS-style) -**Proved:** +Generating and verifying proofs on **Ethereum L1** incurs **significant computation costs**. To optimize efficiency, Taiko Alethia introduces an **off-chain prover marketplace** inspired by **Proposer-Builder Separation (PBS)**. -![proved](~/assets/content/docs/taiko-protocol/proved.png) +### **Key Challenges in Pricing Proofs** -**Verified:** +1. Ethereum **gas costs** for proof verification are unpredictable. +2. Proof generation costs **do not directly correlate** with gas fees. +3. Hardware and software **optimizations continuously reduce costs**. +4. Proof generation **cost depends on the required proof latency**. -![verified](~/assets/content/docs/taiko-protocol/verified.png) +### **How the Prover Market Works** -## Off chain prover market (PBS style) +- **Proposers seek proof service providers** through an off-chain marketplace. +- **Provers bid** by offering to generate proofs for a negotiated fee. +- Once an agreement is reached, the prover **signs a cryptographic commitment**. +- The proposer submits this proof on-chain. +- **If the proof is not provided within the agreed timeframe, penalties apply**. -Proving blocks requires significant compute power to calculate the proof -to submit and verify the proof on Ethereum. Provers need -to be compensated for this work as the network needs to -attract provers that are willing to do this work. How much -to pay for a proof is not obvious however: +### **Prover Types** -1. The Ethereum gas cost to publish/verify a proof - on Ethereum is unpredictable. -2. The proof generation cost does not necessarily - match perfectly with the gas cost. -3. The proof generation cost keeps changing as proving software is optimized and the hardware used - gets faster and cheaper. -4. The proof generation cost depends on how fast a - proof needs to be generated. +- **EOA Provers:** Individual accounts that submit proofs. +- **Prover Pools (Smart Contracts):** Contract-based provers implementing: + - `IProver` interface (Taiko-defined) + - `IERC1271` interface (for signature verification) -In the pursuit of optimizing network efficiency and balancing costs, the ecosystem introduces a robust off-chain proof market. Proposers, on a per-block basis, actively seek potential proof service providers through this dynamic marketplace. A pivotal component of this setup is the publicly exposed API, providing proposers with the means to query and engage with available proof providers off-chain. +### **Prover Incentives** -When an agreement is reached concerning the proving fee for a specific block, the chosen proof service provider is then tasked with granting a cryptographic signature to the proposer. This signature serves as a binding commitment, signifying the prover's dedication to delivering the proof within the agreed-upon timeframe. +- Provers must deposit **TAIKO tokens as collateral per block**. +- **Failure to deliver a proof** within the agreed time results in: + - **1/4 of the deposit going to the next prover**. + - **3/4 of the deposit permanently burned**. +- Successful proof submission **returns the deposit**. -Provers within this off-chain proof market come in two primary forms: Externally Owned Accounts (EOA) and contracts, often referred to as Prover pools. To qualify as a Prover pool, a contract must adhere to specific criteria, implementing either the IProver interface, as previously defined by Taiko, or the IERC1271 (isValidSignature) interface. +--- -Upon a proposer's submission of a block, the signature granted by the chosen provider is subjected to verification. Any deviations result in a reverted transaction. +## Multi-Proofs: Enhancing Security & Redundancy -As an additional incentive for proposers, the system incorporates the issuance of TAIKO tokens. This serves as an extra motivator, as proposing blocks alone may not always prove profitable, especially when considering Ethereum's on-chain fees plus the proving fee. The issuance of TAIKO tokens operates on a dynamic 'emission rate per second,' comparing each block proposal to the last. +Taiko Alethia embraces **multi-proof verification** to minimize the risks of **single-point cryptographic failures**. -The reward depends on the proof service provider and the agreement. For EOAs and Prover pools that implement the IERC1271 interface, the reward is disbursed in ETH. However, in cases where providers implement the IProver interface, the prover fee can be ETH, any other ERC20 tokens, or even NFTs, based on the negotiated terms. +### **Why Multi-Proof?** -To add a layer of security and commitment to the process, provers must provide a substantial amount of TAIKO tokens per block, effectively serving as insurance. In the unfortunate event of a failure to deliver the proof within the given time, a portion, specifically 1/4, is directed to the actual prover, while the remaining 3/4 are permanently burnt. Conversely, successful and timely proof delivery ensures the return of these tokens to the Prover. +- **Cryptographic implementations are complex and evolving.** +- **Bugs in a single proof system could compromise security.** +- **Combining multiple proof systems enhances security through redundancy.** -## Multi-proofs +### **Taiko Alethia’s Multi-Proof Pipeline** -A great resource to learn about Taiko's approach to security with multi-proofs is the Twitter thread [here](https://x.com/taikoxyz/status/1745546868028068273). +- Converts **execution layer instructions** into **arithmetizations**. +- Supports multiple **cryptographic backends**: + - **SuperNova** + - **Halo2** + - **eSTARK** +- **Does not rely on a single proving protocol.** -Cryptographic implementations are complex and not yet mature. To minimize potential bugs and vulnerabilities, diversity in proof systems is needed. Taiko is one of the advocates who strongly defends the multi-proofs approach in rollups. Taiko's approach aims to increase security and diversity by using multiple proof systems and clients, thus reducing the risk associated with bugs or vulnerabilities in any single system. The approach also includes the integration of different types of proofs. +### **SGX: Trusted Execution Environments (TEEs)** -Taiko proposes a robust multi-proof pipeline which translates assembly-level instructions coming from different execution clients into arithmetizations for algebraic or polynomial proof systems. Different backends to encode these arithmetizations, such as SuperNova, Halo2, and eSTARK can also be used, without being limited by using a single protocol. +- **Intel SGX** is used as an alternative proof mechanism. +- **SGX runs a light execution client** that verifies state transitions. +- **SGX signs execution results using an ECDSA signature**, which is validated on-chain. -In addition to ZK proofs, Taiko utilizes SGX (a Trusted Execution Environment developed by Intel) to generate a different type of proof. SGX runs the same code that would be executed on a zkVM, which functions somewhat like a light execution client. Therefore, all proof systems verify the same underlying light client's execution, potentially allowing for the reuse of necessary data. The necessary data is signed within SGX using a standard ECDSA signature, employing a private key exclusive to SGX. The signature is then verified within the smart contract. +### **More Resources on Multi-Proof Security** -## Video +- **Taiko Alethia Multi-Proof Discussion** [Twitter Thread](https://x.com/taikoxyz/status/1745546868028068273) + +--- + +## Video Explanation + +--- diff --git a/packages/docs-site/src/content/docs/core-concepts/what-is-taiko.md b/packages/docs-site/src/content/docs/core-concepts/what-is-taiko-alethia.md similarity index 50% rename from packages/docs-site/src/content/docs/core-concepts/what-is-taiko.md rename to packages/docs-site/src/content/docs/core-concepts/what-is-taiko-alethia.md index 41ca6aa6ddd..950e9c2b1c2 100644 --- a/packages/docs-site/src/content/docs/core-concepts/what-is-taiko.md +++ b/packages/docs-site/src/content/docs/core-concepts/what-is-taiko-alethia.md @@ -1,38 +1,38 @@ --- -title: What is Taiko? -description: Core concept page for "What is Taiko?". +title: What is Taiko Alethia? +description: Core concept page for "What is Taiko Alethia?". --- Ethereum is too expensive. We believe in Ethereum's core properties (e.g., censorship-resistant, permissionless, secure). We also believe that rollups should **extend** (not augment) these properties. -Taiko is a [based rollup](/core-concepts/based-rollup) which makes Ethereum cheaper while maintaining its properties: +Taiko Alethia is a [based rollup](/core-concepts/based-rollup) which makes Ethereum cheaper while maintaining its properties: - [Based contestable rollup](/core-concepts/contestable-rollup): A configurable rollup to reduce transaction fees on Ethereum. - [Based booster rollup](/core-concepts/booster-rollups): An innovative approach to **native L1 scaling**. -Taiko is a **highly configurable, fully open source, permissionless (based), Ethereum-equivalent rollup**. +Taiko Alethia is a **highly configurable, fully open source, permissionless (based), Ethereum-equivalent rollup**. It can be easily configured as a fully ZK rollup, optimistic rollup, or anything in between. There are no centralized actors that operate the network; all operations are permissionlessly run by the community. -## The Taiko protocol +## The Taiko Alethia protocol -- **Taiko Protocol**: A set of smart contracts deployed on Ethereum that describe the Taiko protocol, a fully open-source scaling solution for Ethereum. In the most fundamental sense, this is what Taiko is. Even Taiko's governance itself is written into the protocol contracts. +- **Taiko Alethia Protocol**: A set of smart contracts deployed on Ethereum that describe the Taiko Alethia protocol, a fully open-source scaling solution for Ethereum. In the most fundamental sense, this is what Taiko is. Even Taiko Alethia's governance is written into the protocol contracts. ## Organizations - **Taiko Community**: Social groups/accounts run by anyone interested, including Taiko Discord, Taiko Twitter, etc. -- **Taiko Labs**: Research & development group for the Taiko protocol. -- **Taiko Treasury**: Funded by income from the Taiko protocol (L2 EIP-1559 congestion MEV). -- **Taiko DAO (in progress)**: Governing body of Taiko Token (TAIKO) holders with voting rights over smart contract upgrades, network parameters, and more. Controls all aspects of the Taiko protocol smart contracts. -- **Taiko Foundation**: Stewards growth and development of the Taiko protocol and ecosystem. Works for the Taiko DAO and token holders, financing technical developments, ecosystem growth, partnerships, events, and more with full transparency. -- **Taiko Security Council**: Elected by the Taiko DAO to handle emergency actions. Ensures the safety of the Taiko protocol, implementing necessary upgrades or changes, and controls the Guardian Provers. +- **Taiko Labs**: Research & development group for the Taiko Alethia protocol. +- **Taiko Treasury**: Funded by income from the Taiko Alethia protocol (L2 EIP-1559 congestion MEV). +- **Taiko DAO (in progress)**: Governing body of Taiko Token (TAIKO) holders with voting rights over smart contract upgrades, network parameters, and more. Controls all aspects of the Taiko Alethia protocol smart contracts. +- **Taiko Foundation**: Stewards growth and development of the Taiko Alethia protocol and ecosystem. Works for the Taiko DAO and token holders, financing technical developments, ecosystem growth, partnerships, events, and more with full transparency. +- **Taiko Security Council**: Elected by the Taiko DAO to handle emergency actions. Ensures the safety of the Taiko Alethia protocol, implementing necessary upgrades or changes, and controls the Guardian Provers. ## Services operated by Taiko Labs ### Non-critical infrastructure :::note -Anyone can run these components, not just Taiko Labs. Yes you can sequence blocks on Taiko, host your own bridge using our [signal service](/taiko-protocol/bridging#the-signal-service), etc. +Anyone can run these components, not just Taiko Labs. Yes you can sequence blocks on Taiko, host your own bridge using our [signal service](/taiko-alethia-protocol/bridging#the-signal-service), etc. ::: #### Frontends @@ -46,10 +46,10 @@ Anyone can run these components, not just Taiko Labs. Yes you can sequence block - [Event indexer](/api-reference/event-indexer) - [Bridge relayer](/api-reference/bridge-relayer) -- [Mainnet P2P bootstrapping nodes](/network-reference/mainnet-addresses#taiko-labs-bootnode-addresses) -- [Mainnet Taiko Labs' proposers and provers](/network-reference/mainnet-addresses) -- [Testnet P2P bootstrapping nodes](/network-reference/testnet-addresses#taiko-labs-bootnode-addresses) -- [Testnet Taiko Labs' proposer and provers](/network-reference/testnet-addresses) +- [Taiko Alethia P2P bootstrapping nodes](/network-reference/alethia-addresses#taiko-labs-bootnode-addresses) +- [Taiko Alethia Taiko Labs' proposers and provers](/network-reference/alethia-addresses) +- [Taiko Hekla P2P bootstrapping nodes](/network-reference/hekla-addresses#taiko-labs-bootnode-addresses) +- [Taiko Hekla Taiko Labs' proposer and provers](/network-reference/hekla-addresses) ### Critical infrastructure @@ -57,5 +57,5 @@ Anyone can run these components, not just Taiko Labs. Yes you can sequence block This is a vital concern for rollup users. The smart contracts are upgradeable via a multi-sig, which is a **trusted component** until handed over to the DAO. Please look at a third party source regarding any rollup's safety, such as [L2Beat](https://l2beat.com/scaling/projects/taiko). ::: -- [Mainnet contract owners (multi-sig)](/network-reference/mainnet-addresses#contract-owners) -- [Testnet contract owners](/network-reference/testnet-addresses#contract-owners) +- [Taiko Alethia contract owners (multi-sig)](/network-reference/alethia-addresses#contract-owners) +- [Taiko Hekla contract owners](/network-reference/hekla-addresses#contract-owners) diff --git a/packages/docs-site/src/content/docs/guides/app-developers/bridge-tokens.mdx b/packages/docs-site/src/content/docs/guides/app-developers/bridge-tokens.mdx index 681e2906472..cd6bf2162d0 100644 --- a/packages/docs-site/src/content/docs/guides/app-developers/bridge-tokens.mdx +++ b/packages/docs-site/src/content/docs/guides/app-developers/bridge-tokens.mdx @@ -9,19 +9,19 @@ import { Aside } from '@astrojs/starlight/components'; Please be aware, bridging back to L1 will take around 24 hours! See [network configuration](/network-reference/network-configuration) for the currently configured cooldown period. -This guide will help you use the bridge to send tokens between Holesky and Hekla. +This guide will help you use the bridge to send tokens between Holesky and Taiko Hekla. ## Prerequisites -- A wallet with some testnet ETH on Holesky or Hekla. +- A wallet with some testnet ETH on Holesky or Taiko Hekla. -## Mainnet +## Taiko Alethia --- Visit [the bridge](https://bridge.taiko.xyz/) and follow through the UI. -## Hekla +## Taiko Hekla --- diff --git a/packages/docs-site/src/content/docs/guides/app-developers/deploy-a-contract.mdx b/packages/docs-site/src/content/docs/guides/app-developers/deploy-a-contract.mdx index ce1a580dce7..38fcb4b4646 100644 --- a/packages/docs-site/src/content/docs/guides/app-developers/deploy-a-contract.mdx +++ b/packages/docs-site/src/content/docs/guides/app-developers/deploy-a-contract.mdx @@ -12,7 +12,7 @@ This guide will help you deploy a smart contract on Taiko. - A wallet with some testnet ETH on Taiko (can receive this from [the bridge](/guides/app-developers/bridge-tokens)). - The private key to the account with testnet ETH on Taiko. -## Mainnet +## Taiko Alethia ------ @@ -138,7 +138,7 @@ Hardhat is an Ethereum development environment for deploying smart contracts, ru - Populate the `.env` file. That is, - Create a `.env` file within the `root` folder. - - Populate `.env` with your `YOUR_PRIVATE_KEY` and the Taiko's `RPC_URL` as follows: + - Populate `.env` with your `YOUR_PRIVATE_KEY` and the Taiko `RPC_URL` as follows: ```plaintext RPC_URL="https://rpc.mainnet.taiko.xyz" @@ -252,7 +252,7 @@ Hardhat is an Ethereum development environment for deploying smart contracts, ru -## Hekla +## Taiko Hekla ------ @@ -378,7 +378,7 @@ Hardhat is an Ethereum development environment for deploying smart contracts, ru - Populate the `.env` file. That is, - Create a `.env` file within the `root` folder. - - Populate `.env` with your `YOUR_PRIVATE_KEY` and the Taiko's `RPC_URL` as follows: + - Populate `.env` with your `YOUR_PRIVATE_KEY` and the Taiko `RPC_URL` as follows: ```plaintext RPC_URL="https://rpc.hekla.taiko.xyz" diff --git a/packages/docs-site/src/content/docs/guides/app-developers/receive-tokens.mdx b/packages/docs-site/src/content/docs/guides/app-developers/receive-tokens.mdx index 84215f193ef..66cc0497804 100644 --- a/packages/docs-site/src/content/docs/guides/app-developers/receive-tokens.mdx +++ b/packages/docs-site/src/content/docs/guides/app-developers/receive-tokens.mdx @@ -13,11 +13,11 @@ This guide will help you receive **testnet** tokens on Holesky and Taiko. ## Receive some Holesky testnet Ether -Taiko (Hekla) is currently deployed on Holesky testnet. Check out [faucetlink.to](https://faucetlink.to/) for a list of Holesky ether faucets! +Taiko Hekla is currently deployed on Holesky testnet. Check out [faucetlink.to](https://faucetlink.to/) for a list of Holesky ether faucets! -## Receive some Hekla testnet tokens +## Receive some Taiko Hekla testnet tokens -HORSE is a dummy testnet token we deployed on Taiko (Hekla). You can see all deployed contracts [here](/network-reference/testnet-addresses). Navigate to the [bridge](https://bridge.hekla.taiko.xyz) and click "Faucet" on the sidebar to receive some HORSE. +HORSE is a dummy testnet token we deployed on Taiko Hekla. You can see all deployed contracts [here](/network-reference/hekla-addresses). Navigate to the [bridge](https://bridge.hekla.taiko.xyz) and click "Faucet" on the sidebar to receive some HORSE. ## Receive some TTKOh diff --git a/packages/docs-site/src/content/docs/guides/app-developers/set-up-your-wallet.mdx b/packages/docs-site/src/content/docs/guides/app-developers/set-up-your-wallet.mdx index 9c369fee4f3..a2521eb4c9b 100644 --- a/packages/docs-site/src/content/docs/guides/app-developers/set-up-your-wallet.mdx +++ b/packages/docs-site/src/content/docs/guides/app-developers/set-up-your-wallet.mdx @@ -19,20 +19,20 @@ We **recommend you choose a Taiko Labs maintained RPC** which ends in `.taiko.xy Click **Connect Wallet** at the links below: -- Taiko mainnet: https://chainlist.org/chain/167000 +- Taiko Alethia: https://chainlist.org/chain/167000 - Ethereum testnet (Holesky): https://chainlist.org/chain/17000 -- Taiko testnet (Hekla): https://chainlist.org/chain/167009 +- Taiko Hekla: https://chainlist.org/chain/167009 -## Add mainnet tokens to your wallet +## Add Taiko Alethia tokens to your wallet -Find the token you want to import on the [mainnet addresses](/network-reference/mainnet-addresses) page and use the address to add it to your wallet. +Find the token you want to import on the [Alethia addresses](/network-reference/alethia-addresses) page and use the address to add it to your wallet. -## Add testnet tokens to your wallet +## Add Taiko Hekla tokens to your wallet -Find the token you want to import on the [testnet addresses](/network-reference/testnet-addresses) page and use the address to add it to your wallet. +Find the token you want to import on the [Hekla addresses](/network-reference/hekla-addresses) page and use the address to add it to your wallet. ## Troubleshooting ### The add buttons did not work -If the add buttons did not work, head over to the [RPC configuration](/network-reference/rpc-configuration) and [testnet addresses reference](/network-reference/testnet-addresses) or [mainnet addresses reference](/network-reference/mainnet-addresses) pages and add them to your wallet manually. +If the add buttons did not work, head over to the [RPC configuration](/network-reference/rpc-configuration) and [Hekla addresses reference](/network-reference/hekla-addresses) or [Alethia addresses reference](/network-reference/alethia-addresses) pages and add them to your wallet manually. diff --git a/packages/docs-site/src/content/docs/guides/app-developers/verify-a-contract.mdx b/packages/docs-site/src/content/docs/guides/app-developers/verify-a-contract.mdx index d4e16352b41..a8c80b97ca3 100644 --- a/packages/docs-site/src/content/docs/guides/app-developers/verify-a-contract.mdx +++ b/packages/docs-site/src/content/docs/guides/app-developers/verify-a-contract.mdx @@ -11,11 +11,11 @@ This guide will help you verify a smart contract on Taiko. You have a contract deployed on Taiko and the source code available. -## Mainnet +## Taiko Alethia --- -### Verify a contract with Foundry +### Verify a contract with Foundry Replace the contract address and filepath to contract below, and then execute in terminal to verify your contract. @@ -31,10 +31,10 @@ It's also possible to verify the contract through `Taikoscan` API as follows: forge verify-contract 0x526317252e346978869d178081dA2cd10ac8b56D src/Counter.sol:Counter \ --watch \ --verifier-url https://api.taikoscan.io/api \ - --etherscan-api-key {YOUR_API_KEY} + --etherscan-api-key {YOUR_API_KEY} ``` -## Hekla +## Taiko Hekla --- diff --git a/packages/docs-site/src/content/docs/guides/node-operators/build-a-taiko-node-from-source.mdx b/packages/docs-site/src/content/docs/guides/node-operators/build-a-taiko-alethia-node-from-source.mdx similarity index 84% rename from packages/docs-site/src/content/docs/guides/node-operators/build-a-taiko-node-from-source.mdx rename to packages/docs-site/src/content/docs/guides/node-operators/build-a-taiko-alethia-node-from-source.mdx index 7b0f39681ab..848b1cc980a 100644 --- a/packages/docs-site/src/content/docs/guides/node-operators/build-a-taiko-node-from-source.mdx +++ b/packages/docs-site/src/content/docs/guides/node-operators/build-a-taiko-alethia-node-from-source.mdx @@ -1,5 +1,5 @@ --- -title: Building a Node from Source +title: Building a Taiko Alethia Node from Source description: Learn how to build your own node without relying on simple-taiko-node or prebuilt images --- @@ -13,7 +13,7 @@ You might want to do this if you want to run a node on a specific architecture o ---------------------------------------------------------------------- -A Taiko Node consists of two components, analogous to an Ethereum node; the consensus client and execution engine. +A Taiko Alethia Node consists of two components, analogous to an Ethereum node; the consensus client and execution engine. #### Taiko Client (taiko-client) @@ -23,7 +23,7 @@ It has three subcommands, `driver`, `prover`, and `proposer`. The taiko client replaces the [consensus client](https://ethereum.org/en/developers/docs/nodes-and-clients/) in an Ethereum mainnet node. -In this tutorial you will build the `taiko-client` as found in the [taiko monorepo](https://github.com/taikoxyz/taiko-mono). +In this tutorial you will build the `taiko-client` as found in the [Taiko Alethia monorepo](https://github.com/taikoxyz/taiko-mono). #### Execution Engine (taiko-geth) @@ -49,9 +49,9 @@ First you're going to build `taiko-client`. -1. Clone the Taiko monorepo +1. Clone the Taiko Alethia monorepo - The [Taiko monorepo](https://github.com/taikoxyz/taiko-mono) contains the source code for the `taiko-client`. + The [Taiko Alethia monorepo](https://github.com/taikoxyz/taiko-mono) contains the source code for the `taiko-client`. @@ -81,7 +81,7 @@ First you're going to build `taiko-client`. 3. Build `taiko-client` @@ -128,7 +128,7 @@ Next you're going to build `taiko-geth`. 3. Build `taiko-geth` @@ -140,14 +140,14 @@ Next you're going to build `taiko-geth`. ## What's Next? - Now that you've built your own node from source, you can run it for Taiko Mainnet or Testnet! + Now that you've built your own node from source, you can run it for Taiko Hekla or Taiko Alethia! - - Click here to [Run a Mainnet Taiko Node from Source](/guides/node-operators/run-a-mainnet-taiko-node-from-source)! + + Click here to [run a node for Taiko Alethia](/guides/node-operators/run-a-node-for-taiko-alethia)! - - Click here to [Run a Testnet Taiko Node from Source](/guides/node-operators/run-a-testnet-taiko-node-from-source)! + + Click here to [run a node for Taiko Hekla](/guides/node-operators/run-a-node-for-taiko-hekla)! If you run into any problems, please visit the [troubleshooting page](/guides/node-operators/node-troubleshooting) for help. diff --git a/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx b/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx index b771036c89e..111c46e2b08 100644 --- a/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx +++ b/packages/docs-site/src/content/docs/guides/node-operators/deploy-a-proverset.mdx @@ -23,9 +23,9 @@ This guide outlines how to achieve this with separate EOAs running prover and pr -1. **Clone the Taiko monorepo** +1. **Clone the Taiko Alethia monorepo** - The [Taiko monorepo](https://github.com/taikoxyz/taiko-mono) contains the scripts for deploying your `ProverSet`. Checkout the latest stable release. (Use `taiko-alethia-protocol-v1.11.0` for Hekla!) + The [Taiko Alethia monorepo](https://github.com/taikoxyz/taiko-mono) contains the scripts for deploying your `ProverSet`. Checkout the latest stable release. (Use `taiko-alethia-protocol-v1.11.0` for Taiko Hekla!) @@ -117,7 +117,7 @@ If you've already deployed a ProverSet but would like to upgrade it through the This will be necessary for the following step. -2. **Navigate to the taiko monorepo and checkout the release version of ProverSet you want to deploy.** +2. **Navigate to the Taiko Alethia monorepo and checkout the release version of ProverSet you want to deploy.** ```bash cd taiko-mono/packages/protocol diff --git a/packages/docs-site/src/content/docs/guides/node-operators/enable-a-proposer.mdx b/packages/docs-site/src/content/docs/guides/node-operators/enable-a-proposer.mdx index 08352468df2..c1367c58af7 100644 --- a/packages/docs-site/src/content/docs/guides/node-operators/enable-a-proposer.mdx +++ b/packages/docs-site/src/content/docs/guides/node-operators/enable-a-proposer.mdx @@ -11,7 +11,7 @@ Do NOT start up your proposer without setting up a prover first with a fully syn ## Prerequisites -- You are already running a Taiko node [with Docker](/guides/node-operators/run-a-taiko-node-with-docker) or [from source](/guides/node-operators/build-a-taiko-node-from-source). +- You are already running a Taiko Alethia node [with Docker](/guides/node-operators/run-a-taiko-alethia-node-with-docker) or [from source](/guides/node-operators/build-a-taiko-alethia-node-from-source). - You have [set up a prover](/guides/node-operators/enable-a-prover) or [configured a ProverSet](/guides/node-operators/deploy-a-proverset) with a third-party partner. ## Using simple-taiko-node @@ -34,7 +34,7 @@ You can choose to either use a ProverSet, or leave the `PROVER_SET` variable bla 6. Set `COMPOSE_PROFILES=proposer` or add proposer to the list. -7. Now that the proposer is configured properly, you can run it with `docker compose up -d`! Please use `docker compose -f docker-compose-hekla.yml up -d` if you are running on Hekla. +7. Now that the proposer is configured properly, you can run it with `docker compose up -d`! Please use `docker compose -f docker-compose-hekla.yml up -d` if you are running on Taiko Hekla. diff --git a/packages/docs-site/src/content/docs/guides/node-operators/enable-a-prover.mdx b/packages/docs-site/src/content/docs/guides/node-operators/enable-a-prover.mdx index c82e67b1950..edba9b8d7ff 100644 --- a/packages/docs-site/src/content/docs/guides/node-operators/enable-a-prover.mdx +++ b/packages/docs-site/src/content/docs/guides/node-operators/enable-a-prover.mdx @@ -7,7 +7,7 @@ import { Aside, Card, CardGrid, Steps } from "@astrojs/starlight/components"; ## Prerequisites -- You are already running a Taiko node [with Docker](/guides/node-operators/run-a-taiko-node-with-docker) or [from source](/guides/node-operators/build-a-taiko-node-from-source). +- You are already running a Taiko node [with Docker](/guides/node-operators/run-a-taiko-alethia-node-with-docker) or [from source](/guides/node-operators/build-a-taiko-alethia-node-from-source). - You have an [SGX v2 capable machine](https://github.com/ayeks/SGX-hardware#hardware-with-sgx2-support). ## Enable a prover with simple-taiko-node @@ -30,7 +30,7 @@ These are the bare minimum required settings along with a functional Taiko node 6. Set `COMPOSE_PROFILES=prover` or add prover to the list. -7. You can then run your prover with `docker compose up -d`! Please use `docker compose -f docker-compose-hekla.yml up -d` if you are running on Hekla. +7. You can then run your prover with `docker compose up -d`! Please use `docker compose -f docker-compose-hekla.yml up -d` if you are running on Taiko Hekla. @@ -45,9 +45,11 @@ By enabling proof aggregation, you will be opening yourself up to more risk as y The recommended value for SGX_BATCH_SIZE is 10+ as you will see the most gas saved at this value and above. We will NOT refund any lost bonds due to misconfiguration, please evaluate and use this function at your own risk. -We highly recommend you test the function **on Hekla**, not on Mainnet. +We highly recommend you test the function **on Taiko Hekla**, not on Taiko Alethia. Please note that you must use the [upgraded ProverSet contract](https://github.com/taikoxyz/taiko-mono/blob/taiko-alethia-protocol-v1.11.0/packages/protocol/contracts/layer1/provers/ProverSet.sol) to use this functionality. + +Please also note that you should NOT enable revert protection without a PBS service that has revert protection support, as it will interfere with your batch proving on Taiko Hekla. Batch proving has been enabled in release 0.43.1 of [the taiko alethia client!](https://github.com/taikoxyz/taiko-mono/releases/tag/taiko-alethia-client-v0.43.1) @@ -68,7 +70,7 @@ This flag will force the prover to submit a batch of proofs every x minutes, reg The following steps can be done through the [ProverSet contract](/guides/node-operators/deploy-a-proverset/#deploying-a-proverset) if you have deployed one. We highly recommend this for a stable setup. -### Approve TaikoL1 as TAIKO spender (mainnet) +### Approve TaikoL1 as TAIKO spender (Taiko Alethia) @@ -81,7 +83,7 @@ The following steps can be done through the [ProverSet contract](/guides/node-op 3. Click the **approve** function and set the spender address to the TaikoL1 contract address: `0x06a9Ab27c7e2255df1815E6CC0168d7755Feb19a`. 4. Set the amount to at least the minimum bond amount of 150 TAIKO. @@ -100,7 +102,7 @@ The following steps can be done through the [ProverSet contract](/guides/node-op -### Approve TaikoL1 as TTKOh spender (testnet) +### Approve TaikoL1 as TTKOh spender (Taiko Hekla) You will need TTKOh deposited on the TaikoL1 contract to secure the bond for the proofs you generate. diff --git a/packages/docs-site/src/content/docs/guides/node-operators/run-a-mainnet-taiko-node-from-source.mdx b/packages/docs-site/src/content/docs/guides/node-operators/run-a-node-for-taiko-alethia.mdx similarity index 95% rename from packages/docs-site/src/content/docs/guides/node-operators/run-a-mainnet-taiko-node-from-source.mdx rename to packages/docs-site/src/content/docs/guides/node-operators/run-a-node-for-taiko-alethia.mdx index e2bc7bddbe7..55b89240c7b 100644 --- a/packages/docs-site/src/content/docs/guides/node-operators/run-a-mainnet-taiko-node-from-source.mdx +++ b/packages/docs-site/src/content/docs/guides/node-operators/run-a-node-for-taiko-alethia.mdx @@ -1,15 +1,15 @@ --- -title: Run a Mainnet Taiko Node From Source -description: This guide will help you start up a Taiko node. +title: Run a node for Taiko Alethia from source +description: This guide will help you run a node for the Taiko Alethia network. --- import { Aside, Card, Steps, Tabs, TabItem } from "@astrojs/starlight/components"; -This tutorial explains how to run a Taiko node for Mainnet from source code. +This tutorial explains how to run a node for Taiko Alethia from source code. ## Building the Source Code -Please follow the [Building a Node from Source](/guides/node-operators/build-a-taiko-node-from-source) guide before continuing. +Please follow the [Building a Node from Source](/guides/node-operators/build-a-taiko-alethia-node-from-source) guide before continuing. This guide presumes you have built the required images already (`taiko-geth` and `taiko-client`). ## Hardware Requirements diff --git a/packages/docs-site/src/content/docs/guides/node-operators/run-a-testnet-taiko-node-from-source.mdx b/packages/docs-site/src/content/docs/guides/node-operators/run-a-node-for-taiko-hekla.mdx similarity index 95% rename from packages/docs-site/src/content/docs/guides/node-operators/run-a-testnet-taiko-node-from-source.mdx rename to packages/docs-site/src/content/docs/guides/node-operators/run-a-node-for-taiko-hekla.mdx index 489a027e929..6b1f4abc204 100644 --- a/packages/docs-site/src/content/docs/guides/node-operators/run-a-testnet-taiko-node-from-source.mdx +++ b/packages/docs-site/src/content/docs/guides/node-operators/run-a-node-for-taiko-hekla.mdx @@ -1,15 +1,15 @@ --- -title: Run a Testnet Taiko Node From Source -description: This guide will help you start up a Testnet (Hekla) Taiko node. +title: Run a node for Taiko Hekla from source +description: This guide will help you start up a node for the Taiko Hekla network. --- import { Aside, Card, Steps, Tabs, TabItem } from "@astrojs/starlight/components"; -This tutorial explains how to run a Taiko node for our testnet Hekla from source code. +This tutorial explains how to run a node for our testnet Taiko Hekla from source code. ## Building the Source Code -Please follow the [Building a Node from Source](/guides/node-operators/build-a-taiko-node-from-source) guide before continuing. +Please follow the [Building a Node from Source](/guides/node-operators/build-a-taiko-alethia-node-from-source) guide before continuing. This guide presumes you have built the required images already (`taiko-geth` and `taiko-client`). ## Hardware Requirements diff --git a/packages/docs-site/src/content/docs/guides/node-operators/run-a-taiko-node-with-docker.mdx b/packages/docs-site/src/content/docs/guides/node-operators/run-a-taiko-alethia-node-with-docker.mdx similarity index 92% rename from packages/docs-site/src/content/docs/guides/node-operators/run-a-taiko-node-with-docker.mdx rename to packages/docs-site/src/content/docs/guides/node-operators/run-a-taiko-alethia-node-with-docker.mdx index 5fb875ddd17..0d6bb409ff2 100644 --- a/packages/docs-site/src/content/docs/guides/node-operators/run-a-taiko-node-with-docker.mdx +++ b/packages/docs-site/src/content/docs/guides/node-operators/run-a-taiko-alethia-node-with-docker.mdx @@ -1,11 +1,11 @@ --- -title: Run a Taiko node with Docker +title: Run a Taiko Alethia node with Docker description: This guide will help you start up a Taiko RPC node using simple-taiko-node. --- import { Aside, Steps, Tabs, TabItem } from "@astrojs/starlight/components"; -This guide will help you start up a Taiko RPC node using [simple-taiko-node](https://github.com/taikoxyz/simple-taiko-node). +This guide will help you start up a Taiko Alethia RPC node using [simple-taiko-node](https://github.com/taikoxyz/simple-taiko-node). ## Software Dependencies @@ -19,7 +19,7 @@ This guide will help you start up a Taiko RPC node using [simple-taiko-node](htt - If using Windows, you should install [Git BASH](https://gitforwindows.org/) or [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) to use as your terminal. - Meet the [Geth minimum hardware requirements](https://github.com/ethereum/go-ethereum#hardware-requirements) except for the storage requirement because Taiko nodes will require less storage (at the time of writing). -## Run a Taiko node with simple-taiko-node +## Run a Taiko Alethia node with simple-taiko-node @@ -43,7 +43,7 @@ This guide will help you start up a Taiko RPC node using [simple-taiko-node](htt 2. Copy the sample .env files ```sh @@ -72,7 +72,7 @@ This guide will help you start up a Taiko RPC node using [simple-taiko-node](htt It's recommended to [run a local L1 node](/guides/node-operators/run-an-ethereum-testnet-node) but you browse around for other RPC Providers. Keep in mind they will **eventually rate limit your node** and it will stop syncing, so a local L1 node is recommended for a proper setup. - For Mainnet, the L1 Node will need to be an Ethereum node; for Testnet, the L1 Node will need to be an Etherem testnet (Holesky) node. + For Taiko Alethia, the L1 Node will need to be an Ethereum node; for Taiko Hekla, the L1 Node will need to be an Etherem testnet (Holesky) node. Next, you will set the L1 node endpoints. If you are running a local L1 node, you cannot reference the L1 endpoints as `ws://127.0.0.1:8546` and `http://127.0.0.1:5052` because that is local to inside the simple-taiko-node Docker networking. Instead you can try: @@ -100,11 +100,11 @@ This guide will help you start up a Taiko RPC node using [simple-taiko-node](htt Note that if you include `proposer` or `prover`, the services will still be disabled if you do not set `ENABLE_PROPOSER=true` or `ENABLE_PROVER=true` respectively. 6. Start the node - -