[(chain - 1)] [(shard - 1)] [ showKeyAction ] This Account is backed by MetaMask. Learn More


Similar to how MetaMask bridges between your browser and Ethereum, we proudly present QuarkChain Devnet with MetaMask support to bridge your browser to QuarkChain!


The address shown here is backed by your MetaMask plugin, but bear in mind that the addresses backed by the same private key may have real ETH in main Ethereum network. This is similar situation where your accounts may have ETH in both main Ethereum Network or Ropsten Testnet. When you interact with QuarkChain, your real ETH is safe, see below.


When you interact with QuarkChain using MetaMask, we ask for signatures from your private key stored with MetaMask. To make sure the signature won't be used to do evil (for example, sending the same signed transaction to main Ethereum Network for your real ETH,) we follow EIP-712 to use typedSign(), which includes QuarkChain-specific fields. As you can observe, the transaction and signature combination is only valid on QuarkChain and cannot be used elsewhere.

Existing Testnet Accounts

You can import existing accounts of QuarkChain Testnet to MetaMask, just follow this link to import using your private key. Note those accounts won't be backed by your private seed.

Smart Contract on QuarkChain

QuarkChain supports Ethereum smart contracts, therefore you can use your favorite Ethereum tooling like solc and remix to compile the smart contract, deploy here in QuarkChain and interact with them.

It's worth noting that

  1. QuarkChain smart contracts only support in-shard interaction, which means it can only access addresses within the same shard.
  2. Currently, you can only create the contract at the same shard as you


Using following code (source from here, with slight changes) as the example:

pragma solidity ^0.4.24;

contract Greeter {
  address creator;
  string greeting;

  constructor(string _greeting) public {
      creator = msg.sender;
      greeting = _greeting;

  function greet() constant public returns (string) {return greeting; }

  function getBlockNumber() constant public returns (uint) { return block.number; }

  function setGreeting(string _newgreeting) public { greeting = _newgreeting; }

Use remix to generate the byte code

Then in our devnet, go to Deploy tab, paste the byte code above, set a high gas limit (for example ~3,000,000 to be safe), and click Deploy button.

Once the transaction is confirmed by the network, copy the contract address from the transaction detail page, go to Interact tab, paste the deployed contract's address along with the ABI (which you can also get from remix):
[ placeholder ]
After accessing the contract through the provided ABI, you can read from or write to the contract.

Read / Write Contract

[ method.name ]
Gwei [ selectedMethod.constant ? 'Read' : 'Write' ]
Gwei Deploy
Contract deployment (confirmation time is ~15 seconds)
Update state in the contract

Raw Transaction


Signed Transaction Hash



[ `${fromAddress}` ]
[ `(shard ${fromShard})`.padStart(50) ]


[ toShard !== -1 ? `${toAddress}` : "Contract Creation" ]
[ `(shard ${toShard})`.padStart(50) ]

You'll send [ Number(amount) | BN ] [tokenStr]

Max Transaction Fee [ (gasLimit || 1e6) * gasPriceGwei / 1e9 | BN ] [gasTokenStr]

Cancel Submit Transaction