# Key Features

Circle Layer offers a comprehensive suite of features designed to meet the needs of modern blockchain applications. This section details the practical implementation and current capabilities of our platform.

### Technical Implementation <a href="#technical-implementation" id="technical-implementation"></a>

#### Security & Consensus <a href="#security--consensus" id="security--consensus"></a>

* **DPoS Consensus**: Delegated Proof of Stake security model with minimum 5 active validators
* **Staking Requirements**: 100,000 CLAYER minimum stake
* **Validator Network**: Maximum 21 validators supported

#### Development Integration <a href="#development-integration" id="development-integration"></a>

* **EVM Compatibility**: Full compatibility with existing Ethereum tooling
* **Library Support**: Web3.js, Ethers.js, Viem integration
* **Development Tools**: Hardhat, Truffle, Remix, Foundry compatible
* **Wallet Integration**: MetaMask, WalletConnect, and custom wallet support

#### Economic Features <a href="#economic-features" id="economic-features"></a>

* **Deflationary Economics**: 25% from gas fees burned (maximum 1,000,000 CLAYER) *\[Mainnet only]*
* **Stake-based Rewards**: Higher stake = higher rewards proportionally
* **Developer Revenue**: Gas fee sharing with smart contract deployers

*Note: Advanced economic mechanisms apply to Circle Layer mainnet. Current testnet uses simplified economics.*


---

# 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.circlelayer.pro/introduction/key-features.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.