GIWA Protocol Documentation | Technical Architecture & Security Specifications

1. Executive Summary

The GIWA Bridge Protocol is an enterprise-grade, non-custodial EVM smart contract protocol designed for early liquidity deployment prior to the official GIWA L2 Mainnet Genesis Launch (powered by Dunamu & Optimism OP Stack).

Participants deposit ETH into the Ethereum Mainnet smart contract. The automated, 24/7 Relayer Bot scans for the official OptimismPortal deploy transaction. As soon as the GIWA Genesis Portal opens with verified collateral (>= 5.0 ETH), locked funds are atomically bridged into GIWA L2 Block #1.

100% Non-Custodial

Emergency Refund Active

5.0 ETH Collateral Guard

Atomic OP Stack Bridge

2. Technical Architecture

The protocol operates in four distinct phases to guarantee safety, zero friction, and instant L2 execution:

PHASE 1

L1 Pre-Mainnet Vault Deposit

Users deposit ETH directly into MultiUserGiwaBridge.sol on Ethereum Mainnet. Each deposit is tracked per wallet address in a public mapping.

PHASE 2

24/7 Automated Portal Detection

The decentralized Relayer Bot scans every new block for OP Stack OptimismPortal deployment, evaluating proxy storage slots and function signatures.

PHASE 3

5.0 ETH Collateral Guard Verification

Before execution, the smart contract validates that the target Portal has codeSize > 0 and a minimum balance of >= 5.0 ETH deposited by the GIWA team.

PHASE 4

Atomic L2 Migration & Minting

The protocol executes low-level OptimismPortal.depositTransaction, minting native L2 ETH directly into the depositor's wallet on GIWA L2 Genesis Block.

3. Smart Contract & Security Guarantees

Strict Non-Custodial Guarantee:

The smart contract contains zero admin withdrawal functions. Neither protocol administrators, relayers, nor third parties can withdraw user funds to any external address.

// MultiUserGiwaBridge.sol (Emergency Refund Snippet) function emergencyWithdraw() external nonReentrant { require(!userIsBridged[msg.sender], "Already bridged to L2"); uint256 amount = userETHBalances[msg.sender]; require(amount > 0, "No ETH balance"); userETHBalances[msg.sender] = 0; totalVaultETH -= amount; (bool success, ) = payable(msg.sender).call{value: amount}(""); require(success, "ETH transfer failed"); }

As shown in the verified code above, emergencyWithdraw() strictly transfers funds to msg.sender (the depositor). Users retain 100% sovereignty to withdraw their funds at any time prior to migration.

Protocol Fee Transparency:

A standard 0.5% protocol fee (50 basis points) is deducted upon initial deposit. This fee is automatically routed to protocol infrastructure maintainers to support high-availability RPC nodes, WebSocket infrastructure, and automated 24/7 relayer bot execution.

4. Verified On-Chain Deployment

Network	Ethereum Mainnet (Chain ID: 1)
Contract Address	0xDB5D14f261bEF4aD20207b04af027E50eE4Baa04
Compiler Version	Solidity v0.8.20 (EVM Target: Paris, Optimizer: 200 runs)
Safety Guards	ReentrancyGuard, Pausable, Minimum Collateral Guard (>= 5.0 ETH)

5. Frequently Asked Questions (FAQ)

Can the protocol team or admins access my deposited ETH?

No. The contract does not contain any admin withdrawal functions. Deposited ETH can only be retrieved by the original depositor via emergencyWithdraw() or bridged to the depositor's own address on GIWA L2.

What happens when GIWA Mainnet launches?

Our 24/7 automated Relayer Bot detects the official GIWA OptimismPortal deployment, verifies that the GIWA team has deposited at least 5.0 ETH collateral, and triggers batch migration. Your ETH will immediately appear in your GIWA L2 wallet.

What if I change my mind before launch?

You can navigate to the Emergency Refund tab on the dashboard and click Withdraw 100% ETH Refund at any time prior to migration. Your kilitli ETH balance will be instantly sent back to your wallet.