Keeta

Keeta is a payment-oriented layer-1 network built around per-account chains in a DAG, delegated representative voting, native tokens, atomic exchange paths and certificate-linked identity. The project publishes a mainnet wallet and explorer, but some developer examples and its repository license still describe testnet, so feature readiness must be checked service by service.

KTA has two inspectable forms. The exchange-traded supply is the Base ERC-20 0xc0634090f2fe6c6d75e61be2b949464aBB498973. Keeta mainnet chain 21378 records native KTA under keeta_anqdilpazdekdu4acw65fj7smltcp26wbrildkqtszqvverljpwpezmd44ssg. Official live anchor metadata pairs those identifiers for transfers. That is evidence of an operated conversion route, not evidence that the same contract runs on both ledgers.

Keeta starts from a practical mismatch: banks, payment rails and blockchains keep separate balances, identity checks and settlement rules. Its answer is a common ledger where tokens are native objects, certificates can express verified attributes, and anchors connect external systems. The architecture can make payment flows composable without forcing every asset issuer to deploy bespoke smart contracts.

The same arrangement divides trust. Certificate authorities attest identity; token administrators can set rules; representatives decide whether blocks enter the ledger; anchor providers custody or forward external assets; and software licensors shape acceptable implementations. Calling all of this 'KTA governance' hides who can perform which action.

A client proposes account blocks and asks representatives for temporary votes, then cross-verification and permanent votes. Native base-token balances delegated to a representative supply its voting weight. This is consensus selection. The reviewed documents do not show KTA holders voting on treasury spending, corporate products, the license or software upgrades through a general proposal system.

The Base token is narrower. Its verified, non-proxy code minted one billion tokens to the contract for initial liquidity. It began with a declining transfer tax and sent LP tokens to a designated recipient. On September 5, 2026, owner() and getCurrentTax() both returned zero; no later mint, freeze or upgrade entry point exists. Renounced Base ownership does not remove the Keeta-side anchor, representative or network-account powers.

Official tokenomics assigns 50% to community/ecosystem, 40% to two strategic reserves and 10% to treasury. Forty percent of total supply was scheduled through the community bucket at TGE; the rest follows multiple locks and monthly vesting tracks ending around March 2030. The terms say all tokens were distributed at launch, which can mean allocated into wallets or vesting arrangements, not freely circulating.

Identity profiles assemble CA-issued certificates linked to public keys. This can support selective disclosure and transaction rules, but an identity credential is only as reliable as its issuer and revocation path. Keeta's performance figures—400 ms and 10 million-plus TPS—are project benchmarks, not a legal service level or proof of sustained public-mainnet demand.

Mainnet launched on September 22, 2025, but launch does not settle control. On the review date, the native KTA account reported only 9,971,398.677342841 KTA in supply versus one billion on Base, and its ACL still named one OWNER and two ADMIN principals with supply and balance powers. An official representative endpoint returned four representatives with nonzero weight; rep1 held about 89.583%. These are live snapshots, and no official reconciliation policy explains the supply gap. Representatives can set fees, but no reward APR or delegation emission schedule was found.