Search…
FAQ & Troubleshoot Guide
You can find a video walkthrough here and here.
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.
When will mainnet be released?
We have a lot of exciting product releases coming up. Please check back to our site or sign up for our newsletter to receive any updates.
Where can I learn more?
Visit us at the Espresso Systems website and come by our Github. Please also join the conversation on Twitter and Discord!
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 ERC20 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 the Espresso chain is live. What are the assets (capedUSDC, etc) that I see in the asset registry when I first created 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 ERC20 tokens. This is NOT affiliated with USDC or DAI tokens in any way.
Why am I getting an error saying this asset already exists during asset creation?
You have already created the asset type (same view policy and freezing policy configuration of an ERC20 token) in the asset library. ERC20 asset of the same contract address and view/freezing configuration can only be sponsored once by the same user. 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 hand bar. You can request more tokens from the faucet anytime. You can also always ask people in the 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 the “Account” section and generating the keys in the freezing and view key section.
Why does the entire asset balance appear to be zero after I sent part of balance to another CAPE address ? CAPE uses UTXOs (like Bitcoin) not accounts (like Ethereum). When you mint 10,000 of a domestic asset, you get a single record, or UTXO, worth 10,000, kind of like a single $10,000 bill. When you spend 100, you actually have to spend the entire 10,000-token record, but when the transaction finalizes, you get back a new record with 9,900 as change. That's why the amount is 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
    • OSX
      • 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 tohttp://localhost:8888 in the browser to access the CAPE wallet.
How do I use VPS with CAPE?
You do not need to setup VPS to run CAPE. However, there are 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.
Copy link