# The Basics

<figure><img src="/files/hrw1bTtdEnRGtRltSf0k" alt=""><figcaption></figcaption></figure>

## **Introduction**

KCC 1.0 is built on the Ethereum source code and is compatible with EVM smart contracts. It seeks to solve Ethereum’s dual problem of low performance and high cost. Millions of blocks have been produced, while the number of active addresses on the chain has exceeded hundreds of thousands.

**EVM Compatible**

KCC is EVM compatible. Deploy and run your dApps on KCC with your favourite tooling for Ethereum.

**Fast Finality**

The average block time of KCC is 3 seconds. A typical transaction can be included in a block in less than 6 seconds. This block is finalized if more than half of all validators add their blocks after it.

**Low Cost**

The gas fee is paid in $KCS. Transfer your tokens around the world with a fraction of a cent.

**Safe and Secure**

Each block is validated by trusted validators with their identities and KCS as stakes.

## **Staking**

There are currently 15 out of a maximum of 22 active validators(producing blocks and earning rewards). Validators are onboarded manually. Network-wide APY can fluctuate between 1 and 20%, dependent mainly on KuCoin’s (the exchange) activity. This is because the staking APY is fuelled by a share of KuCoin's trading fees. Staking Rewards accrue continuously but do NOT auto-compound - you will have to claim and delegate manually. Unstaking takes 3 days, during which you will NOT earn rewards.

### **Safety/Security**

Your tokens will stay in your custody when staking $KCS with a validator. This means you can, at any point, undelegate, even when a validator goes offline or becomes inactive. The worst thing that would happen is that you wouldn’t receive any new rewards, so choosing the proper validator is essential. There is no slashing active on KCC.

## **Useful Links**

### **Explorers**

[KCC Explorer](https://explorer.kcc.io/en) | [KCC Scan](https://scan.kcc.io/)

### **Wallets**

[**UniPass**](https://unipass.id/) **|** [**Changex**](https://changex.io/) **|** [**Halo Wallet**](https://halo.social/) **|** [**MetaMask**](https://metamask.io/) **|** [**TrustWallet**](https://trustwallet.com/) **|** [**TokenPocket**](https://www.tokenpocket.pro/) **|** [**BitGet Wallet**](https://web3.bitget.com/en/) **|** [**Coin98**](https://coin98.com/) **|** [**MathWallet**](https://mathwallet.org/) **|** [**Rabby Wallet**](https://rabby.io/) **|** [**Ledger**](https://www.ledger.com/) **|** [**Infinity Wallet**](https://infinitywallet.io/asset/kucointoken) **|** [**Nabox**](https://nabox.io/) **|** [**SafePal**](https://www.safepal.com/) **|** [**Ambire Wallet**](https://www.ambire.com/) **|** [**Astrone**](http://astrone.io/) **|** [**Shield Protocol**](https://shieldprotocol.org/) **|** [**Fox Wallet**](https://foxwallet.com/) **|** [**ONTO Wallet**](https://onto.app/)

### **Official KCC resources**

[**Website**](https://www.kcc.io/) **|** [**Documentation**](https://docs.kcc.io/) **|** [**Ecosystem**](https://www.kcc.io/apps) **|** [**GitHub**](https://github.com/kcc-community) **|** [**Staking Website**](https://staking.kcc.io/)

**Social Media**

[Twitter](https://twitter.com/KCCOfficialTW) | [Medium ](https://kccofficial.medium.com/)| [Discord](https://discord.com/invite/H5ucJydSyd) | [Telegram](https://t.me/KCCOfficialEnglishCommunity)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.speedystaking.io/kucoin-community-chain/the-basics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
