GIWA Sepolia is preparing Upgrade 20, a fault-proof system update designed to align the Upbit-backed Layer 2 with the OP Stack’s emerging interoperability architecture. According to a GIWA Markets announcement, the deployment was scheduled for November 11 at 3 PM KST. The principal change moves GIWA’s Fault Dispute Game toward the Type 5 Super Root structure used by Optimism’s Upgrade 20. No separate execution confirmation was visible through GIWA’s official channels at the latest review.
The change is limited to Layer 1 smart contracts and is not an L2 hard fork, according to the update surfaced through the GIWA ecosystem feed. Node operators therefore do not need to upgrade their GIWA software specifically for Upgrade 20. GIWA Sepolia itself remains the project’s active test environment, while the production mainnet is still listed as under development.
GIWA TESTNET UPDATE: UPGRADE 20 IS COMING 🛠️@GIWA_by_Upbit is preparing Upgrade 20 on GIWA Sepolia, scheduled for November 11 at 3 PM KST.
Here's what you need to know:
🔹 Upgrade 20
– Preparing for future interoperability
– Fault Proof Dispute Game moves to Type 5 (Super…— GIWA MARKETS – launchpad for upcoming Upbit's L2 (@GIWALAUNCHPAD) November 11, 2026
Super Roots Prepare Fault Proofs for Interoperability
Upgrade 20 changes how the fault-proof system represents claims about L2 state. Conventional dispute games use an output root tied to one chain and an L2 block number. Under the Super Root architecture, the root can encode a timestamp together with chain IDs and their corresponding output roots. That format is capable of representing multiple chains at the same point in time, which is required before native OP Stack interoperability can be secured through fault proofs.
The distinction is important because the upgrade does not itself turn cross-chain messaging on. Optimism introduced the same architecture across its own stack in September, explicitly separating the Super Root migration from a later hard fork that will activate interoperability. GIWA’s deployment should therefore be understood as infrastructure preparation for future cross-chain fault proofs rather than the launch of live Superchain interoperability.
The transition also changes one technical detail affecting withdrawals. Super Root dispute games use an L2 timestamp as their sequence number instead of the initiating block’s L2 block number. Developers relying on withdrawal-proof tooling are consequently advised to use viem 2.51.0 or later, which understands the timestamp-based structure. The underlying withdrawal proof continues to use the chain-specific output root, preserving compatibility while changing how the appropriate dispute game is identified.
GIWA’s reliance on the OP Stack places the testnet within a broader Layer 2 architecture where shared software can evolve independently of each chain’s application layer. Other networks have similarly adopted specialized execution environments, including Elysium’s dedicated Layer 2 around Hyperliquid. In GIWA’s case, Upgrade 20 modifies the security and dispute infrastructure underneath the network rather than changing the applications or transaction format users interact with directly.
GIWA Mainnet Remains Under Development
GIWA Sepolia currently operates as an Ethereum Layer 2 connected to Ethereum Sepolia under chain ID 91342, with ETH serving as its native gas asset. GIWA’s documentation continues to mark mainnet as under development. Upgrade 20 is therefore a testnet infrastructure milestone and should not be presented as a mainnet activation or production launch.
The distinction resembles Ethereum’s own staged testing process, where upgrades move through development and public testnets before production deployment. ChainReport has tracked that separation during Ethereum’s Glamsterdam Sepolia testing, where scheduled testnet activation remained distinct from eventual mainnet deployment. Testing a new fault-proof architecture on GIWA Sepolia similarly establishes implementation progress without demonstrating production readiness.
GIWA has continued updating its node stack separately from Upgrade 20, including recent releases of op-reth and op-node. Those software updates should not be conflated with the Super Root deployment because Upgrade 20 is specifically an L1 contract change. The practical effect for developers is concentrated around fault proofs and withdrawal tooling, while ordinary node operation is expected to continue without an Upgrade 20-specific software migration.
For GIWA, the larger significance lies in compatibility with the future direction of the OP Stack. Super Roots create the fault-proof structure needed for a world in which several OP Stack chains can eventually depend on one another’s state, but GIWA has not yet reached that interoperable production environment. Confirmation of the Upgrade 20 transaction and a later interoperability activation remain separate milestones from the scheduled testnet deployment.
