On October 22, 2026, South Korea's Financial Supervisory Service (FSS) issued a "caution" consumer alert about a fake blockchain impersonating GIWA, the Ethereum Layer 2 being built by Upbit operator Dunamu. GIWA's mainnet had not launched. Scammers spread claims of a "surprise mainnet launch" on social media and in online communities, set up a network with RPC details, a chain ID and a bridge made to look official, and waited for deposits.
On September 27, according to decentralized exchange DYORSWAP, 1,335 addresses sent about 767 ETH into the fake bridge. Roughly 766 ETH was withdrawn in a single batch the same afternoon, about 13 hours after the bridge contract was deployed. DYORSWAP had listed the fake network believing it was GIWA's mainnet. It says it was also a victim and has paid more than 200 ETH to affected users from its own funds. Eleven minutes before the drain, GIWA's official X account had posted: "We DO NOT have our mainnet running currently."
This is a fake-chain scam.
What a fake-chain scam is
A wallet connects to a network through an RPC address and identifies it by a chain ID. Anyone can run a network, give it a familiar name and publish connection details for it. Anyone can also deploy a "bridge" contract on Ethereum that accepts deposits. If you add the fake network and bridge to it, your ETH goes to a contract the scammers control.
The GIWA copy was more than a fake web page. DYORSWAP reports that it was a working network that posted transaction batches to Ethereum, and tokens were launched and traded on it. A network that looks active is not proof that it is the real one.
Why a matching chain ID isn't enough
The fake network used chain ID 9134. The public chain registry Chainlist had already reserved that number for GIWA's planned mainnet, so the ID appeared correct, and DYORSWAP says it passed its initial check for that reason. The FSS lists GIWA's official network as 91342, which is GIWA's Sepolia testnet, and notes that the mainnet has not launched. A chain ID is only a number. A scammer can copy it, and it tells you nothing about who runs the RPC behind it.
Rule 1: Confirm the network is live through official channels
Before you add a network or bridge to it, check the project's official website, documentation and verified accounts for a launch announcement. GIWA's official channels, as listed by Upbit, are giwa.io, docs.giwa.io and @GIWA_by_Upbit on X. The FSS states that bridges or smart contracts claiming to support a network that has not officially launched should be treated as scams.
Rule 2: Get the chain ID and RPC from official docs, then cross-check
Copy network details only from the project's own documentation. Cross-check them against a public registry such as Chainlist. If the docs, the registry and the details you were sent don't all match, stop. In the GIWA case, the registry listed the mainnet ID with no public RPC, and GIWA's docs offered only the testnet. A post offering "leaked" mainnet RPC details is a warning sign, not a shortcut. GIWA responded that no RPC could leak because the mainnet had never launched.
Rule 3: Read the add-network popup
When a site asks your wallet to add a network, most wallets show a popup with the network name, chain ID, RPC URL and currency symbol. Check the RPC URL's domain against the official docs before you approve. The name in the popup is whatever the site chose to send. It isn't verified.
Rule 4: Use only the bridge linked from official docs
Open the bridge from the project's documentation, not from a post, an ad or a link someone sends you. Before you deposit, check that the address you are sending to matches the bridge contract address published in the official docs. Look it up on a block explorer. A bridge contract deployed hours or days ago, with no history, should make you stop. The fake GIWA bridge went live on the same day it was drained.
Rule 5: Don't trust ads, DMs or "surprise" launches
The FSS warns that "surprise launch", "airdrop" and "pre-participation event" offers not confirmed through official channels are typical scam tactics. Being listed on a DEX does not prove a network is real either. A DEX connects trades but no operator controls the assets, so it cannot reverse a loss.
Rule 6: Start with a small amount
If a network is new to you, send a small test amount first. This limits your exposure while you confirm everything works as expected. It does not prove a bridge is safe, since a scam bridge can accept deposits for hours before it is drained.
If you already bridged to a fake network
The FSS notes that on-chain scams move funds within minutes to hours, so recovery is very difficult. Still:
- Stop sending funds to the network or bridge, including any "fee" requested to release or recover your deposit.
- Remove the network from your wallet. If you approved any tokens for the bridge or a site linked to it, revoke those approvals.
- Save your transaction hashes, the addresses involved, and screenshots of the posts or sites that sent you there.
- Report it to the platform you used, to the police and to your financial regulator. Contact the project only through its official channels.
- Ignore anyone in DMs or comments who offers to recover your funds. Recovery offers are a common follow-up scam.
Sources: FSS consumer alert via Hankyoreh, SBS and DigitalToday, Upbit GIWA notice, GIWA on X, DYORSWAP findings via Coinyong, GIWA documentation, Chainlist On October 22, 2026, South Korea's Financial Supervisory Service (FSS) issued a "caution" consumer alert about a fake blockchain impersonating GIWA, the Ethereum Layer 2 being built by Upbit operator Dunamu. GIWA's mainnet had not launched. Scammers spread claims of a "surprise mainnet launch" on social media and in online communities, set up a network with RPC details, a chain ID and a bridge made to look official, and waited for deposits.
On September 27, according to decentralized exchange DYORSWAP, 1,335 addresses sent about 767 ETH into the fake bridge. Roughly 766 ETH was withdrawn in a single batch the same afternoon, about 13 hours after the bridge contract was deployed. DYORSWAP had listed the fake network believing it was GIWA's mainnet. It says it was also a victim and has paid more than 200 ETH to affected users from its own funds. Eleven minutes before the drain, GIWA's official X account had posted: "We DO NOT have our mainnet running currently."
This is a fake-chain scam.
What a fake-chain scam is
A wallet connects to a network through an RPC address and identifies it by a chain ID. Anyone can run a network, give it a familiar name and publish connection details for it. Anyone can also deploy a "bridge" contract on Ethereum that accepts deposits. If you add the fake network and bridge to it, your ETH goes to a contract the scammers control.
The GIWA copy was more than a fake web page. DYORSWAP reports that it was a working network that posted transaction batches to Ethereum, and tokens were launched and traded on it. A network that looks active is not proof that it is the real one.
Why a matching chain ID isn't enough
The fake network used chain ID 9134. The public chain registry Chainlist had already reserved that number for GIWA's planned mainnet, so the ID appeared correct, and DYORSWAP says it passed its initial check for that reason. The FSS lists GIWA's official network as 91342, which is GIWA's Sepolia testnet, and notes that the mainnet has not launched. A chain ID is only a number. A scammer can copy it, and it tells you nothing about who runs the RPC behind it.
Rule 1: Confirm the network is live through official channels
Before you add a network or bridge to it, check the project's official website, documentation and verified accounts for a launch announcement. GIWA's official channels, as listed by Upbit, are giwa.io, docs.giwa.io and @GIWA_by_Upbit on X. The FSS states that bridges or smart contracts claiming to support a network that has not officially launched should be treated as scams.
Rule 2: Get the chain ID and RPC from official docs, then cross-check
Copy network details only from the project's own documentation. Cross-check them against a public registry such as Chainlist. If the docs, the registry and the details you were sent don't all match, stop. In the GIWA case, the registry listed the mainnet ID with no public RPC, and GIWA's docs offered only the testnet. A post offering "leaked" mainnet RPC details is a warning sign, not a shortcut. GIWA responded that no RPC could leak because the mainnet had never launched.
Rule 3: Read the add-network popup
When a site asks your wallet to add a network, most wallets show a popup with the network name, chain ID, RPC URL and currency symbol. Check the RPC URL's domain against the official docs before you approve. The name in the popup is whatever the site chose to send. It isn't verified.
Rule 4: Use only the bridge linked from official docs
Open the bridge from the project's documentation, not from a post, an ad or a link someone sends you. Before you deposit, check that the address you are sending to matches the bridge contract address published in the official docs. Look it up on a block explorer. A bridge contract deployed hours or days ago, with no history, should make you stop. The fake GIWA bridge went live on the same day it was drained.
Rule 5: Don't trust ads, DMs or "surprise" launches
The FSS warns that "surprise launch", "airdrop" and "pre-participation event" offers not confirmed through official channels are typical scam tactics. Being listed on a DEX does not prove a network is real either. A DEX connects trades but no operator controls the assets, so it cannot reverse a loss.
Rule 6: Start with a small amount
If a network is new to you, send a small test amount first. This limits your exposure while you confirm everything works as expected. It does not prove a bridge is safe, since a scam bridge can accept deposits for hours before it is drained.
If you already bridged to a fake network
The FSS notes that on-chain scams move funds within minutes to hours, so recovery is very difficult. Still:
- Stop sending funds to the network or bridge, including any "fee" requested to release or recover your deposit.
- Remove the network from your wallet. If you approved any tokens for the bridge or a site linked to it, revoke those approvals.
- Save your transaction hashes, the addresses involved, and screenshots of the posts or sites that sent you there.
- Report it to the platform you used, to the police and to your financial regulator. Contact the project only through its official channels.
- Ignore anyone in DMs or comments who offers to recover your funds. Recovery offers are a common follow-up scam.
Sources: FSS consumer alert via Hankyoreh, SBS and DigitalToday, Upbit GIWA notice, GIWA on X, DYORSWAP findings via Coinyong, GIWA documentation, Chainlist On October 22, 2026, South Korea's Financial Supervisory Service (FSS) issued a "caution" consumer alert about a fake blockchain impersonating GIWA, the Ethereum Layer 2 being built by Upbit operator Dunamu. GIWA's mainnet had not launched. Scammers spread claims of a "surprise mainnet launch" on social media and in online communities, set up a network with RPC details, a chain ID and a bridge made to look official, and waited for deposits.
On September 27, according to decentralized exchange DYORSWAP, 1,335 addresses sent about 767 ETH into the fake bridge. Roughly 766 ETH was withdrawn in a single batch the same afternoon, about 13 hours after the bridge contract was deployed. DYORSWAP had listed the fake network believing it was GIWA's mainnet. It says it was also a victim and has paid more than 200 ETH to affected users from its own funds. Eleven minutes before the drain, GIWA's official X account had posted: "We DO NOT have our mainnet running currently."
This is a fake-chain scam.
What a fake-chain scam is
A wallet connects to a network through an RPC address and identifies it by a chain ID. Anyone can run a network, give it a familiar name and publish connection details for it. Anyone can also deploy a "bridge" contract on Ethereum that accepts deposits. If you add the fake network and bridge to it, your ETH goes to a contract the scammers control.
The GIWA copy was more than a fake web page. DYORSWAP reports that it was a working network that posted transaction batches to Ethereum, and tokens were launched and traded on it. A network that looks active is not proof that it is the real one.
Why a matching chain ID isn't enough
The fake network used chain ID 9134. The public chain registry Chainlist had already reserved that number for GIWA's planned mainnet, so the ID appeared correct, and DYORSWAP says it passed its initial check for that reason. The FSS lists GIWA's official network as 91342, which is GIWA's Sepolia testnet, and notes that the mainnet has not launched. A chain ID is only a number. A scammer can copy it, and it tells you nothing about who runs the RPC behind it.
Rule 1: Confirm the network is live through official channels
Before you add a network or bridge to it, check the project's official website, documentation and verified accounts for a launch announcement. GIWA's official channels, as listed by Upbit, are giwa.io, docs.giwa.io and @GIWA_by_Upbit on X. The FSS states that bridges or smart contracts claiming to support a network that has not officially launched should be treated as scams.
Rule 2: Get the chain ID and RPC from official docs, then cross-check
Copy network details only from the project's own documentation. Cross-check them against a public registry such as Chainlist. If the docs, the registry and the details you were sent don't all match, stop. In the GIWA case, the registry listed the mainnet ID with no public RPC, and GIWA's docs offered only the testnet. A post offering "leaked" mainnet RPC details is a warning sign, not a shortcut. GIWA responded that no RPC could leak because the mainnet had never launched.
Rule 3: Read the add-network popup
When a site asks your wallet to add a network, most wallets show a popup with the network name, chain ID, RPC URL and currency symbol. Check the RPC URL's domain against the official docs before you approve. The name in the popup is whatever the site chose to send. It isn't verified.
Rule 4: Use only the bridge linked from official docs
Open the bridge from the project's documentation, not from a post, an ad or a link someone sends you. Before you deposit, check that the address you are sending to matches the bridge contract address published in the official docs. Look it up on a block explorer. A bridge contract deployed hours or days ago, with no history, should make you stop. The fake GIWA bridge went live on the same day it was drained.
Rule 5: Don't trust ads, DMs or "surprise" launches
The FSS warns that "surprise launch", "airdrop" and "pre-participation event" offers not confirmed through official channels are typical scam tactics. Being listed on a DEX does not prove a network is real either. A DEX connects trades but no operator controls the assets, so it cannot reverse a loss.
Rule 6: Start with a small amount
If a network is new to you, send a small test amount first. This limits your exposure while you confirm everything works as expected. It does not prove a bridge is safe, since a scam bridge can accept deposits for hours before it is drained.
If you already bridged to a fake network
The FSS notes that on-chain scams move funds within minutes to hours, so recovery is very difficult. Still:
- Stop sending funds to the network or bridge, including any "fee" requested to release or recover your deposit.
- Remove the network from your wallet. If you approved any tokens for the bridge or a site linked to it, revoke those approvals.
- Save your transaction hashes, the addresses involved, and screenshots of the posts or sites that sent you there.
- Report it to the platform you used, to the police and to your financial regulator. Contact the project only through its official channels.
- Ignore anyone in DMs or comments who offers to recover your funds. Recovery offers are a common follow-up scam.
Sources: FSS consumer alert via Hankyoreh, SBS and DigitalToday, Upbit GIWA notice, GIWA on X, DYORSWAP findings via Coinyong, GIWA documentation, Chainlist