Question 1

What does GateChain's EVM compatibility mean?

Accepted Answer

EVM (Ethereum Virtual Machine) is a component specifically designed to execute smart contracts on the Ethereum blockchain. Traditional first-generation blockchains like BTC, LTC, and Doge cannot execute smart contracts and only support transfers between accounts. Ethereum, as a representative of second-generation blockchain, provides the EVM smart contract runtime environment in addition to account transfer functionality. Each node joining Ethereum runs EVM to process smart contract transactions. For example: Early phones (blockchain) only had calling and texting functions. Later, Microsoft, Apple, and Google launched their own smartphone operating systems (like EVM) installed on better-performing phones, allowing each phone to run third-party developed apps (smart contracts). Therefore, EVM compatibility means that GateChain not only supports regular account transfers but also provides a smart contract execution environment. Developers can deploy their smart contract code from Ethereum, BSC, and other chains directly on GateChain without any modifications.

Question 2

What is ERC-20?

Accepted Answer

ERC stands for Ethereum Request for Comment, used to propose improvements for tokens and the Ethereum ecosystem. After an ERC is submitted, the Ethereum community evaluates it and decides whether to accept or reject the proposal. Once approved, the ERC becomes an official Ethereum Improvement Proposal (EIP). Simply put, token standards define the data and functionality that each token must implement. On Ethereum, besides the native ETH token, all other tokens are ERC tokens conforming to various standards. ERC-20 was introduced in November 2015 and officially standardized in September 2017. This protocol specifies a set of basic interfaces for fungible tokens, including token symbols, supply, transfer, and authorization. Tokens complying with this standard are fully compatible with Ethereum wallets.

Question 3

What is ERC-721?

Accepted Answer

ERC-721 was proposed in January 2018 and is the underlying standard for the NFT boom. The main difference from ERC-20 is that each token has a unique identifier. With numbered identifiers, different token IDs can represent different values, similar to artwork. For example: If ERC-20 is like regular currency where each unit has the same value and purchasing power, then ERC-721 is like commemorative coins issued by banks, each with a unique number, belonging to only one account, and varying significantly in price.

Question 4

What is ERC-1155?

Accepted Answer

ERC-1155, proposed in June 2018, is called the Multi Token Standard. It means that when issuing an ERC-1155 token, it can contain multiple types of ERC tokens, including ERC-20 and ERC-721. It's essentially a token collection concept.

Question 5

Do I need to create new accounts on different machines when running multiple virtual machines? Can these VMs share one account?

Accepted Answer

If you need multiple virtual machines to participate in consensus, you must create accounts on new machines and bring consensus accounts online.

Question 6

When running multiple nodes, does each node need to synchronize blockchain information separately?

Accepted Answer

You can synchronize separately or package information from other synchronized nodes to new nodes. Specific method: Package and copy the root directory where gated runs (default ~/.gated folder). However, if your multiple nodes want to create new consensus accounts to participate in consensus, you need to delete the copied partkey (located in ~/.gated/mainnet/ with .0.0.partkey extension) and create new consensus accounts.

Question 7

After successfully setting up a node, using gatecli command returns error: open /Users/XXX/.gatecli/api.token: no such file or directory

Accepted Answer

This occurs because there's no api.token in the .gatecli directory. You need to copy it from the .gated directory using the command: cp ~/.gated/api.token ~/.gatecli/

Question 8

Using gatecli account show [address] command returns error: account XXXX does not exist, why?

Accepted Answer

This is because the account you're querying isn't on-chain. You need to send a transaction to this account, and after the transaction succeeds, you can query it.

Question 9

How to recover an account using mnemonic phrases after creating it?

Accepted Answer

Use the command gatecli account create --recover to recover your account.

Question 10

If I transferred money to a locally created account but haven't synchronized to that transaction block height, how can I quickly transfer out from this account?

Accepted Answer

You can construct the transaction body via RPC, sign it locally, and then broadcast via RPC. Specific steps: 1. Construct transaction body, modify valid_height parameter, suggested to modify to 300 blocks after GateChain's current latest height. 2. Save the returned transaction body to your desktop, then execute locally: gatecli tx sign [transaction body file] --from [sender account] --chain-id mainnet --offline --account-number 1 3. Copy the signed information and broadcast the transaction. 4. GateChain API node list.

Question 11

Already transferred money to the consensus account preparing to go online, but still getting error when bringing consensus account online: account XXXX does not exist, why?

Accepted Answer

Please confirm that your local sync node has reached ≥ the transaction block height of the consensus account transfer. If it's <, wait for synchronization to the transfer transaction before bringing the consensus account online.

Question 12

What affects the loyalty coefficient of consensus accounts?

Accepted Answer

The loyalty coefficient increases with the number of times selected for the committee. If your node hasn't participated in consensus for a long time, GateChain will automatically process the consensus account as offline, and the loyalty coefficient will drop to 1.

Question 13

What should I do if I delegated to a consensus account but found it hasn't participated in consensus for a long time?

Accepted Answer

There is indeed a risk of revenue loss in consensus account delegation. For example, if the delegated node can't participate in mainnet consensus due to factors like network outage or power failure, it won't generate revenue. It's recommended that users set up their own nodes to ensure stable network connectivity. For users who find their consensus account hasn't participated in consensus for a long time and are unable to set up their own nodes, they can transfer their delegation to other consensus accounts.

Question 14

Which block did GateChain start supporting smart contracts?

Accepted Answer

Block 731444

Question 15

EVM interface, getting BlockNumber returns 404 error.

Accepted Answer

Check if your port 8080 is occupied by gated. Port 8080 must be free when gated starts. Otherwise, you need to modify the config.json file, and EVM RPC startup needs additional parameters. It's recommended to keep port 8080 free for gated use.

Question 16

EVM interface, getting BlockNumber returns error: HTTP 401 Unauthorized: Invalid API Token

Accepted Answer

Execute this command: cp ~/.gated/api.token ~/.gatecli/

Contract Name	Address	Description
AddressManager	`0x5446e2bea992f5fa70d717fadb998073702dc1a6`	Address resolution/registry (legacy-compatible shape).
ProxyAdmin	`0x977ce593493a3d1bca355187b573aeb37fa099a3`	Proxy upgrade admin.
L1StandardBridge	`0x1b30f00bbfea2d2daaabbaf28059477cea9e0e36`	Handles ETH/ERC20 deposits/withdrawals between L1 and L2.
L1CrossDomainMessenger	`0x030b1fa1112a52dcc3b131d393d40234d36ec741`	Cross-domain messenger L1 side.
OptimismPortal	`0x48a4c3f12e489452e5b45facc04df901d7adc8cf`	L2 data submission entry + withdrawal proofs.
DisputeGameFactory	`0x089a3b9d9caa629d1b3ce382f3b212b9ebb78730`	Fault-proof/challenge factory.
SystemConfig	`0xd929985b14c809ce4d7b20dfc008e0f3c0c80b66`	L2 fee parameters and config.
L1ERC721Bridge	`0x9176cb94f3663f28454b133a66c9305e01be3b85`	ERC721 bridge L1 side.
OptimismMintableERC20Factory	`0x92bebadd993314a24d612fcd72eecf0e4fe5be0d`	L2 mintable token factory counterpart.
AnchorStateRegistry	`0x0826e88946941b9b2153b73250706e10c7af7b7e`	Anchor state registry.

Contract Name	Address	Description
L2CrossDomainMessenger	`0x4200000000000000000000000000000000000007`	L2-side cross-domain messenger paired with L1 XDM.
L2StandardBridge	`0x4200000000000000000000000000000000000010`	L2 side of the standard asset bridge (ETH/ERC20).
L2ToL1MessagePasser	`0x4200000000000000000000000000000000000016`	Low-level channel/record for L2→L1 withdrawals/messages.
L1Block	`0x4200000000000000000000000000000000000015`	Provides L1 block info and base fee readings (read-only).
GasPriceOracle	`0x420000000000000000000000000000000000000F`	L2 fee oracle interface (baseFee, overhead/scalar, etc.).
L2ERC721Bridge	`0x4200000000000000000000000000000000000014`	L2 ERC721 bridge.
OptimismMintableERC20Factory (L2)	`0x4200000000000000000000000000000000000012`	Creates mintable mirror tokens for deposited assets on L2.
SequencerFeeVault	`0x4200000000000000000000000000000000000011`	Sequencer fee vault.
BaseFeeVault	`0x4200000000000000000000000000000000000019`	Base fee vault.
L1FeeVault	`0x420000000000000000000000000000000000001A`	L1 fee vault.
OperatorFeeVault	`0x420000000000000000000000000000000000001B`	Operator fee vault.
ProxyAdmin	`0x4200000000000000000000000000000000000018`	Proxy admin (upgrade management).

Contract Name	Address	Description
L1StandardBridge	`0x75ded3be4d69e8403c9079ae5cf5e059a23f6a67`	Handles deposits and withdrawals of ETH and standard ERC20 tokens between L1 and L2.
L1CrossDomainMessenger	`0x60cad8d7d622be3d62786b2e7a6617765d0f4d94`	Passes arbitrary messages between L1 and L2, forming the basis for cross-domain communication.
OptimismPortal	`0x0d69cdd07cf93075fe53769945575274fc563ba9`	The entry point for L2 transaction data submission to L1 and handles withdrawal proofs. A core part of the system.
DisputeGameFactory	`0x6f419bb5d754033e39f758d20133d7fea8e2bb55`	The core of the fault-proof system, used to create and manage challenges against L2 output roots.
SystemConfig	`0xaeb4b93732c30c5d74ab3220cd73aa0fcdd275f8`	Stores L2 gas-related parameters, such as `overhead` and `scalar`.
L1ERC721Bridge	`0xa19cbb87428a6b943912f2f44241ca1cb3a8cec1`	Handles the bridging of ERC721 NFT tokens between L1 and L2.
OptimismMintableERC20Factory	`0xca1bbd1187ccbf2297c828c48f5c0896d9985636`	Creates "mintable" versions of ERC20 tokens on L2 that correspond to deposited L1 tokens.
ProxyAdmin	`0x1be6f451a7578cb48ddbd8fea8d2fd25462e5d16`	Manages the upgrade permissions for the core contracts listed above.
AddressManager	`0x6cbd08ae08136ab974ae121a0895d3836c8a00ce`	(Legacy) A registry used to resolve and manage system contract addresses.

Contract Name	Address	Description
L2CrossDomainMessenger	`0x4200000000000000000000000000000000000007`	L2-side cross-domain messenger paired with L1 XDM.
L2StandardBridge	`0x4200000000000000000000000000000000000010`	L2 side of the standard asset bridge (ETH/ERC20).
L2ToL1MessagePasser	`0x4200000000000000000000000000000000000016`	Low-level channel/record for L2→L1 withdrawals/messages.
L1Block	`0x4200000000000000000000000000000000000015`	Provides L1 block info and base fee readings (read-only).
GasPriceOracle	`0x420000000000000000000000000000000000000F`	L2 fee oracle interface (baseFee, overhead/scalar, etc.).
L2ERC721Bridge	`0x4200000000000000000000000000000000000014`	L2 ERC721 bridge.
OptimismMintableERC20Factory (L2)	`0x4200000000000000000000000000000000000012`	Creates mintable mirror tokens for deposited assets on L2.
SequencerFeeVault	`0x4200000000000000000000000000000000000011`	Sequencer fee vault.
BaseFeeVault	`0x4200000000000000000000000000000000000019`	Base fee vault.
L1FeeVault	`0x420000000000000000000000000000000000001A`	L1 fee vault.
OperatorFeeVault	`0x420000000000000000000000000000000000001B`	Operator fee vault.
ProxyAdmin	`0x4200000000000000000000000000000000000018`	Proxy admin (upgrade management).

Protocol Contracts

Mainnet · Core L1 Contracts

Mainnet · L2 Predeploy Contracts

Testnet · Core L1 Contracts

Testnet · L2 Predeploy Contracts

Mainnet · Core L1 Contracts​

Mainnet · L2 Predeploy Contracts​

Testnet · Core L1 Contracts​

Testnet · L2 Predeploy Contracts​

Mainnet · Core L1 Contracts

Mainnet · L2 Predeploy Contracts

Testnet · Core L1 Contracts

Testnet · L2 Predeploy Contracts