> For the complete documentation index, see [llms.txt](https://docs.giwa.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giwa.io/notices/en/giwa-chain/readme.md).

# Upgrade 20 Protocol upgrade

> Notice date: November 5, 2026
>
> Target Network: GIWA Testnet (Sepolia)

## Overview

GIWA Chain will apply the Upgrade 20 protocol update from the OP Stack. In preparation for future interop, this upgrade moves the fault proof dispute games to Super Root based games.

{% hint style="info" %}
This is an L1 smart contract-level update, not a hardfork. Node operators do not need to upgrade.
{% endhint %}

## Schedule

* Testnet (Sepolia): *November 11, 2026 at 15:00 KST*

{% hint style="info" %}
The actual time may vary depending on network conditions and block timing.
{% endhint %}

## What's changing

* **Fault Proof — dispute game type change**: The dispute game type used to prove withdrawals changes from `PERMISSIONED_CANNON` (type 1) to `SUPER_PERMISSIONED` (type 5). Game roots also change from Output Roots (keyed by L2 block number) to Super Roots (keyed by L2 timestamp). GIWA continues to operate in a permissioned manner.
* **Existing games and withdrawals**: Games created before the upgrade keep resolving, and withdrawals proven before the upgrade do not need to be re-proven.

## For Developers

* **Withdrawal proving tools**: After the upgrade, new withdrawals must be proven against `SUPER_PERMISSIONED` (type 5) games. If your app or script proves withdrawals directly, please make sure it supports game type 5. If you use viem, update to 2.51.0 or later.
* **Removed `SystemConfig` functions**: `batchInbox()` and `setGasConfig(uint256,uint256)` are removed from the L1 `SystemConfig`. Please review any tooling that calls them.

## Learn more

Want to learn more about Upgrade 20? Check out the [OP Stack documentation](https://docs.optimism.io/notices/upgrade-20).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.giwa.io/notices/en/giwa-chain/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
