Welcome to a crowdsourced directory of resources for Canto Online Hackathon builders and other community members. Not sure where to start? See the FAQ below for answers to builders' most frequent questions.

Is this directory missing something? Make a contribution.

A list of Canto builders' most Frequently Asked Questions (FAQ), filtered by topic.

With chain ID 7700 and an RPC of your choice e.g. https://canto.gravitychain.io/.

Ideally, bridge over from Ethereum or Cosmos Hub, or other networks using Synapse Network.

The Canto Public Messaging Service has a faucet, but you will likely want to bridge over anyway.

The Canto EVM is fully EVM-compatible. For development, Hardhat, Truffle, Foundry, Remix, and others work perfectly.

Forge deployment scripts send concurrent transactions which cause issues with Ethermint. Consider using the --slow flag or deploying manually.

Approximately 6 seconds.

The Canto network uses a modified EIP-1559 gas model without priority fees. The minimum base fee is 1000 acanto (the equivalent of gwei) and self-adjusts based on how full blocks are.

https://canto.gravitychain.io/, https://canto.slingshot.finance/, and https://canto.neobase.one/ are the most reliable.

Yes, wss://canto.gravitychain.io:8546 and wss://canto.dexvaults.com/ws.

Yes, Ansybl hosts dedicated Canto nodes, including both full and archive nodes, for a monthly fee.

If your application requires very high throughput/reliability, consider renting a dedicated Canto node (see above) or setting up your own node.

https://rpc.cantoarchive.com is a public archive RPC node, with rate limiting allowing up to 50 requests per 10 seconds. As above, for more throughput, consider renting a dedicated node or setting up your own archive node.

Data providers Transpose and Covalent have REST and SQL APIs exposing Canto chain data.

Additionally, the Blockscout explorers for mainnet (tuber.build) and testnet (testnet.tuber.build) support the default Blockscout API endpoints.

Use the public RPC canto-testnet.plexnode.wtf and chain ID 7701 in your development suite or wallet of choice.

Use the web-based faucet at https://www.cantofaucet.com/. Alternatively, use the Discord faucet by entering the /driptestnet {address} command in the #canto-testnet-faucet channel of the Canto Discord.

Both faucets disperse 50 $CANTO per address per 24 hours.

The Discord faucet mentioned above also disperses 15 $NOTE each time it is used. If that's not enough, the Canto DEX testnet deployment has $CANTO <> $NOTE liquidity and can be interacted with programatically or through LeetSwap (after switching to Canto testnet in the connected wallet).

The Canto DEX testnet deployment also has liquidity for the $NOTE <> $USDC and $NOTE <> $USDT pairs. As above, it can be interacted with programatically or through LeetSwap.

There was previously a testnet with chain ID 740. Due to incompatibility with CSR and validator sync issues, this testnet was deprecated and a new testnet (chain ID 7701).

See the DEX and Lending Market section of the docs for an overview of their architectures and links to source contracts.

Yes, you can use Multicall1 and 2 on both mainnet and testnet:

Only the entry contract.

In the CSR docs.

0xEcf044C5B4b867CFda001101c617eCd347095B44 and here.

No. The Turnstile smart contract allows an EOA to call the register method. However, the x/csr module operating on the Cosmos-side will not save this registration, and no revenue will accrue to the NFT, even if you assign valid smart contracts to it.

CSR does not have native support for multiple fee recipients; however, Turnstile NFTs are composable and can be deposited to protocols like Canto Splits for trustless revenue sharing.

Canto has at least four contributor-operated block explorers: tuber.build, mintscan.io/canto Cantoscan, and GaCanto.

For tuber.build, use Sourcify. You can also verify through Forge using Sourcify:

forge verify-contract <contractAddress> src/<fileName>.sol:<contractName> --chain-id 7700 --verifier sourcify

...or Blockscout:

forge verify-contract <contractAddress> src/<fileName>.sol:<contractName> --chain-id 7700 --verifier-url https://evm.explorer.canto.io/api --verifier blockscout

Verification of some contracts is not supported by the explorer. Contributors are aware of this and working on solutions.

Yes, testnet.tuber.build.

Yes:

• RedStone
• Scry
• Pyth

Note that the Canto DEX router deployed at 0xa252eEE9BDe830Ca4793F054B506587027825a8e also has price oracle functionality.

Yes, Scry offers a VRF oracle.

See NFT Global Entry.

Yes.

Yes, Canto Safe on the Canto EVM; Pyxis Safe on Canto bridge/native layer.

Yes, CantoDao and Canto Collectives by Kali.

The Canto Online Hackathon supports promising projects with generous $CANTO prizes. Outside of this, there are no established grant programs for builders or validators.

Canto social channels are run by various contributors. For your best chances at cross-promotion on these channels, make a professional and interesting Tweet about your project.

Canto is supported by the following bridges and interoperability protocols:

• Gravity Bridge
• LayerZero (Canto endpoint: 0x9740FF91F1985D8d2B71494aE1A2f723bb3Ed9E4)
• Synapse Bridge
• Multichain
• Celer cBridge

https://github.com/Canto-Network/Canto

In the contracts folder of the core Canto repo: https://github.com/Canto-Network/Canto/tree/main/contracts

In the x (modules) folder of the core Canto repo: https://github.com/Canto-Network/Canto/tree/main/x

https://github.com/Canto-Network/clm/tree/main/src