A sovereign, EVM-compatible Layer 1 built on the Cosmos SDK.

Konstellation is a Layer 1 blockchain with its own validator set and its own consensus. It is not a rollup, a sidechain or an appchain secured by another network.

• For Solidity developers and wallet users, it behaves like an Ethereum-family chain. Contracts compile and deploy unchanged. The node serves the standard Ethereum JSON-RPC over HTTP and WebSocket. MetaMask, Rabby and other EVM wallets work as they do on any EVM chain, and Blockscout provides the block explorer.
• For Cosmos operators, it is a standard Cosmos SDK application: one Go binary (konstellationd), upgrades coordinated by on-chain governance, and IBC for interoperability.

Blocks are final as soon as they are committed. CometBFT consensus gives deterministic finality, so there are no reorganisations and no confirmation window to wait out.

Status: pre-launch. No Konstellation network is live yet. The details below describe the chain as designed and may change before launch.

RPC endpoints, the explorer and the devnet faucet will be listed here when the networks launch. Dapp developers should start on devnet: it runs the same software release that mainnet is about to run, one to two weeks ahead of mainnet.

• ERC-4337. EntryPoint v0.7 and v0.8 are in the genesis state at their canonical addresses, so existing bundlers and wallet SDKs work without redeployment.
• Passkeys. The P-256 signature precompile (RIP-7212) is available, so WebAuthn and passkey-based accounts are cheap to verify on-chain.
• EIP-7702. Externally owned accounts can delegate to smart-account code. The EVM runs the Prague fork.

Konstellation is designed to hold real value from its first block, and its defaults are conservative:

• No forks of core infrastructure. The Cosmos SDK, CometBFT, IBC and the EVM module are used as unmodified upstream dependencies, so upstream security fixes can be applied as soon as they are released.
• No bridge at launch. Bridges come later, one at a time, each audited, rate-limited and soaked first.
• A careful start for the validator set. The network launches with a small, professionally operated validator set. There is a published roadmap for opening it to more operators over time.
• Audits before value. Audits and a bug bounty come before launch.

The chain has a built-in compliance module. A designated authority can freeze an address: the address can then no longer sign transactions, send funds or be sent funds, apart from a few protocol refunds such as returned deposits or completed unbonding. Scheduled changes wait out a timelock. Emergency freezes take effect at once and expire on their own unless they are ratified. Governance can override any entry. Smart contracts can check whether an address is frozen through a precompile. The authority and timelocks for each network are set in its genesis, and the module is under legal review before mainnet.

• Whitepaper: design, token economics and the launch plan, in the whitepaper repo (currently a draft).
• Security: please report vulnerabilities privately through GitHub's private vulnerability reporting, not in a public issue. See SECURITY.md.

_{Nothing on this page is an offer of, or investment advice about, any token. Konstellation is pre-launch software and the details above may change.}