KDA

What is KDA?

KDA brings EVM-compatible programmability and native cross-chain communication with KDA using an innovative consensus of Proof of Authority(PoA)

Why is KDA designed as a separate chain from KDA?

The execution of a Smart Contract may slow down the exchange function and add non-deterministic factors to trading. Even if that compromise could be tolerated, it might be a straightforward idea to introduce a new Virtual Machine specification based on Tendermint, based on the current underlying consensus protocol and major RPC implementation of KDA. But all these will increase the learning requirements for all existing dApp communities, and will not be very welcomed.

How does KDA work? What is the architecture and consensus used?

KDA relies on a system with Proof of Authority (PoA) consensus that can support short block time and lower fees.

There will be fewer validators on KDA testnet.

Can you tell more about Proof of Staked Authority(PoSA)? What is it?

PoSA is a combination of PoA and PoS. Blocks are produced by a limited set of validators, they are elected in and out based on a staking based governance. Validators take turns to produce blocks in a PoA manner

What are the benefits for developers to build on KDA?

EVM-compatible: KDA supports all the existing KDA tooling Fast block time, cheaper cost
Native cross-chain trasfer & communication: KDA DEX remains a liquid venue of exchange of assets on KDA and KDA"

What are the benefits for developers to build on KDA?

KDA opens the gate for users to take advantage of the fast transferring and trading

What make KDA different?

Key Innovations:

Proof-of-authority Consensus
Native Cross-Chain Communication
Expand the use cases of KDA token

KDA is EVM-compatible. What does that mean?

EVM means KDA Virtual Machine. Any smart-contract written to run in EVM can be easily ported to KDA.

Can developers make hybrid Dapps using both KDA and KDA in one single Dapp?

Yes, with the help of native cross-chain functions