⁉️FAQ & troubleshooting

Is there a native CAPE token?

There are only (non-value) testnet tokens, which can be requested solely through the faucet. The testnet fee token cannot be transacted for actual value and are solely used to simulate “paying” for transaction fees within CAPE. They are not for sale, swapping, or redeeming.

There is no CAPE token sale or other distribution happening or currently planned. Beware of scams!

Where can I learn more?

Visit us at the Espresso Systems website and check out our open source projects on GitHub. Please also join the conversation on Twitter and Discord!

When will mainnet be released?

We have a lot of exciting product releases coming up. Please follow our website, Twitter, Discord, and newsletter to receive any updates.

What happens when the CAPE smart contracts are upgraded?

When the CAPE smart contracts are upgraded to test out new features or fix bugs, the old ledger states will be lost. This means that any token balances and created assets will disappear when a new version of CAPE is deployed to testnet. The Espresso Systems team will notify users of planned updates ahead of time.

Why do I see a RPC error when I request $CAPE tokens during setup?

We are actively working on improving RPC reliability. Your $CAPE tokens should be processing if you see this message.

Why do certain operations (such as wrapping an ERC-20 asset) take so long in CAPE?

In the case of wrapping, the extra time is needed for the relayer to push another transaction to the CAPE contract before the wrapped assets can be released.

Other operations may take longer due to EQS processing time and the fact that CAPE requires 6 confirmations before reflecting the results of a transaction. This will not be an issue once CAPE is deployed on the Espresso Sequencer.

See Lifecycle of a CAPE Transaction for more technical details.

What are the assets (capedUSDC, etc.) that I see in the asset library when I first create my wallet?

The capedUSDC and other pre-existing "caped" assets are demo assets that the Espresso team has created to let the users interact with existing ERC-20 tokens. They are not related to the official USDC or DAI tokens in any way.

Why am I getting the error "this asset already exists" during asset creation?

If you see this error, you have already created the exact same asset type (same view policy and freezing policy configuration of an ERC-20 token). A single address can only sponsor a CAPE asset of the same ERC-20 asset and viewing/freezing policies once. I skipped the faucet. How do I get $CAPE tokens to make transactions?

You can request test $CAPE tokens by clicking on the "Faucet" section in the left sidebar. You can request more tokens from the faucet anytime. You can also always ask people in Discord to send some tokens to your CAPE address! I am trying to create an asset or sponsor an asset type that requires viewing or freezing keys. Where do I get these keys?

You can obtain the viewing and freezing keys by going to “Account” in the left sidebar and generating the keys in the freezing and viewing keys sections.

Why does the entire asset balance appear to be zero after I sent part of my balance to another CAPE address?

CAPE uses UTXOs (like Bitcoin) not accounts (like Ethereum). For instance, when 100 units of a CAPE asset are created, you get a single record, or UTXO, worth 100, like a single $100 bill. When you spend 100, you actually have to spend the entire 100-unit record, but when the transaction finalizes, you get back a new record with 99 as change. That's why the amount is displayed as 0 while the transaction is pending. What should I do when docker-compose up fails with error of `0.0.0.0:80: bind: address already in use?

If you are seeing this error, another service is listening on port 80. Therefore, Docker cannot start the wallet GUI that is configured to listen on port. We suggest the following steps to resolve the issue:

• Check what is in process:

  • Windows, Powershell

    • Get-Process -Id (Get-NetTCPConnection -LocalPort 80).OwningProcess

  • macOS

    • sudo lsof -i -P | grep LISTEN | grep :80

  • Linux

    • sudo ss -antup | grep :80

    • or sudo netstat -antup | grep :80

• To use a different port (here 8888) for running CAPE, edit the docker-compose.yaml file. Change the following:

  ports:
        - 80:80

  to

  ports:
        - 8888:80

  Then go to http://localhost:8888 in the browser to access the CAPE wallet.

How do I use a VPS with CAPE?

It is not required or recommended setup a VPS to run CAPE. However, some community members who have successfully run CAPE on VPS. Please check our Discord for guides developed by our community members.

Why does my CAPE wallet show "CAPE syncing" in the upper-right?

"CAPE syncing" is normal behavior when starting a wallet, since the wallet has to sync with the history of the ledger. Since CAPE hides the ledger state using zero-knowledge proofs, it cannot just query the latest state of the chain from a service provider like an Ethereum wallet. CAPE has to replay changes that have been made since you logged off, using your private keys to reveal the details of state changes that affect your wallet.

How do I mint Arbitrum ETH/DAI/USDC so that I can wrap these assets in CAPE?

You can send Arbitrum Goerli ETH (also known as AGOL) to the following contracts on Arbitrum to mint the respective tokens (example screenshot below for minting WETH) with your MetaMask wallet.

Contract addresses:

• WETH: 0x4F1D9E040cf28A522ec79951cDb7B55c8aE4744E

• DAI: 0xBeec50ed16E3559afCD582cC98ed2b5F5DcA189E

• USDC: 0x9A4f4Ee35a8FfEE459B3187A372d422790fc8aAB