GIWA RPC

With Quicknode, you get access to our global GIWA network which always routes your API requests to the nearest available location, ensuring low latency and the fastest speeds.

Try free

What is GIWA?

GIWA is an Ethereum Layer 2 network built on the OP Stack. It executes transactions through an EVM-equivalent environment, uses ETH for transaction fees, and settles rollup data and state commitments to Ethereum.

GIWA produces blocks every second and provides Flashblocks-aware RPC access for applications that need preconfirmation data before the enclosing block is sealed. The network is developed with Upbit and is currently available through the GIWA Sepolia testnet.

How GIWA differs from Ethereum

GIWA is EVM-equivalent, so most Ethereum contracts and developer tools work without modification. However, its Layer 2 architecture changes how blocks are produced, how cross-chain transactions behave, and when blocks reach finality.

Characteristic	Ethereum	GIWA
Block time	Approximately 12 seconds	Approximately 1 second
Block production	Proposers and validators	Sequencer

Developers should also account for these Layer 2 behaviors:

• Bridging: Deposits originate on Ethereum and update GIWA state, while withdrawals originate on GIWA and require proof and a fault-proof challenge period before finalization on Ethereum.
• Address aliasing: When an Ethereum smart contract initiates a deposit transaction, GIWA records an aliased sender address on Layer 2. Cross-chain applications should not assume the Layer 1 and Layer 2 sender addresses are identical.
• Mempool access: GIWA does not expose a public mempool. Pending transactions are visible to the sequencer, which currently prioritizes transactions by fee.
• Finality: A GIWA block can be unsafe when produced by the sequencer, safe after its data is published to Ethereum, or finalized after the corresponding Ethereum block is finalized.

See the official Ethereum and GIWA comparison for additional protocol details.

Interacting with GIWA

GIWA exposes Ethereum-compatible JSON-RPC methods together with Debug and Flashblocks APIs. Existing Solidity contracts and Ethereum tooling can interact with GIWA by connecting to a GIWA endpoint.

With this API, you can:

• Query blocks, transactions, receipts, account state, contract storage, and event logs
• Submit signed transactions and simulate contract calls
• Read preconfirmation state through Flashblocks-aware methods
• Subscribe to real-time events via WebSocket connections

You can access the API by:

• Using a hosted provider such as a Quicknode GIWA endpoint, which provides managed HTTP and WebSocket access without operating your own node

Supported Networks

Quicknode provides access to the following GIWA networks:

Sepolia

Type:Testnet

Chain ID:

91342

HTTP:

WSS:

Archive:Yes

Pruning:None

Network

Type

Chain ID

HTTP

WSS

Archive

Pruning

Sepolia

Testnet

91342

Yes

None

Complete reference for developers building on GIWA with Quicknode:

QuickStart

Get started with GIWA quickly. Follow our step-by-step quickstart to set up your endpoint and make your first API request.

Provider Endpoints

Learn how to configure and manage your GIWA endpoints for optimal performance and reliability.

API Overview

Explore supported APIs, networks, Quicknode products, and enhanced API features for building powerful applications.

Endpoint Security

Secure your endpoints with authentication, whitelisting, and best security practices.

Error Codes

Understand common error codes and troubleshooting steps for GIWA API requests.