Ethereum developers can simply use Godwoken as an EVM-compatible layer 2 chain, just like Arbitrum and Optimism.
This documentation can be used as an integration guide for wallets and exchanges, or as a reference for developing dApps on Godwoken. It describes how to interact with Godwoken using existing Ethereum development tools, known caveats of version 1 and corresponding workarounds.
The knowledge of Ethereum is a prerequisite for using this guide.
Why Develop on Godwoken?
- Security - Nervos Network is a Proof-of-Work (PoW) layer 1 chain and Godwoken is an optimistic rollup layer 2 chain built on Nervos Network. The security model is quite different from other EVM-compatible PoS/DPoS/PoA chains or sidechains. For more information, see the references section.
- Low cost - A typical Godwoken transaction currently costs less than $0.0001.
- With Force Bridge, assets from 3 chains (Nervos, Ethereum and BSC) are already available on Godwoken. The support for more chains (Cardano, BTC) is on the way.
- The TVL of Godwoken is now nearly 100 million. A number of DeFi dApps (e.g. YokaiSwap, DARUMA) and wallets (e.g. SafePal) have already been integrated.
- Interoperability 2.0 - This may be the trump card of Godwoken. With the design abstractions of Nervos Network and Godwoken, it is possible to use any on-chain tool to port smart contracts to manipulate assets on the corresponding chain.
Godwoken V1 is still under development and targets 100% EVM compatibility.
To develop on Godwoken V1, the following caveats must be noted:
- The existing web3.js libraries are not used to interact with Godwoken because the web3 RPC is not fully compatible with EVM. compatible providers are provided to minimize the workload of porting existing work with web3.js, ethers.js, Truffle and Hardhat. Simply replace the provider with polyjuice-provider when initiating the wallet provider.
- Ethereum wallets are used as transaction signers instead of a full-featured wallet that support checking balances, tracking transactions, transferring assets etc. The Ethereum wallets such as MetaMask support signing and sending transactions on Godwoken.
- For more details on the incompatibilities when deploying Ethereum contracts, see the links below:
It is necessary to initialize an account in order to send transactions on Godwoken.
Connect the wallet and obtain the L1 YOKAI DEPOSIT ADDRESS.
Send a minimum of 400 CKBs from a CKB wallet to this address.
Note: Use Nervos Faucet to fund the CKB wallet in Testnet.
Once the deposit is completed, the CKB balance will be visible on the Yokai Exchange page, which means the account has been initialized.
The bridged token is a token bridged from other chains, and mapped as an ERC20 token on Godwoken.
The current source chains can be:
- Nervos Network
- Binance Smart Chain
It is possible to manipulate the bridged token with ERC20 ABI and given address.
CKB is also a bridged token on Godwoken. CKB acts as a native token for Godwoken in the same way that ETH does for Ethereum, but can also operate with the ERC20 proxy contract.
A few facts to keep in mind when manipulating the CKB:
- Do not transfer CKB with
sendTransactionto arbitrary address carrying the value. Use the
transfermethod in the CKB ERC20 proxy contract to transfer CKB.
- Use the
getBalancemethod of the Ethereum RPC to get the balance of CKB. Note that the decimal return value for CKB is 8, not 18 as in ETH. The balance of CKB can also be obtained using the
balanceOfmethod in the CKB ERC20 proxy contract.
- The CKB ERC20 proxy contract address is
0x6BFD7c449B3FFDaCCcac80Cf3cA6bb89e9bF309Cfor Testnet, and
- It is impossible to use MetaMask or other wallets to show or send CKB.
Check the demo for more details.
An existing contract written in Solidity or Vyper can be ported to Godwoken, otherwise write a new contract.
There is a demo showing a simple way to deploy a contract to and interact with Godwoken. There is no difference in compiling, so using Truffle or Hardhat to write, compile and test the contract is still possible.
More compatibility information: