Part I — Introduction & Overview

1. What is Kortana?

Kortana is a Layer 1 blockchain written entirely in C++23, designed to offer uncompromising security, deterministic finality, and a revolutionary dual-execution environment. By combining an EVM-compatible engine (KEVM) with a custom-built, capability-secure register machine (KVM), Kortana provides the familiar tooling of Ethereum while closing entire classes of smart contract vulnerabilities at the language and VM level.

1.1 Vision & Mission

Our mission is to provide a production-grade decentralized ledger that prioritizes security over speed and determinism over cleverness. Kortana is built to be the foundational layer for protocols where safety and correctness are non-negotiable, offering an environment where developers can write mathematically verifiable code without sacrificing access to the existing DeFi ecosystem.

1.2 Key Differentiators

Kortana breaks away from traditional Layer 1 architectures through three core innovations:

1. KVM Custom Architecture: Unlike stack-based virtual machines, the Kortana Virtual Machine (KVM) is a 32-register machine. This removes the class of bugs that come from stack juggling and makes static verification tractable. Contracts written in Quorlin (Kortana's native language) compile to KVM bytecode and declare their state effects (reads or writes) before anything else.
2. Delegated Proof of History (dPOH): A SHA-256 hash chain running on a dedicated thread produces a verifiable record that time passed between two points. This separates transaction ordering from consensus, allowing for 600,000 hashes per slot.
3. Deterministic Finality (KSC BFT): Kortana uses a HotStuff-family Byzantine Fault Tolerant consensus mechanism with BLS12-381 signature aggregation. Finality is 1 block. Once a block carries a quorum certificate, there are no uncles and no probabilistic reorgs.

[!TIP] Bridges and dApps building on Kortana do not need to wait 128+ blocks for probabilistic finality. A single finalized block is cryptographically guaranteed to never be reorganized.

1.3 Architecture at a Glance

Transactions enter the mempool, are ordered by the dPOH generator, and finalized by the KSC BFT consensus. The Execution Router then dynamically dispatches the transaction to either the EVM or the KVM, both of which read from and write to a single, unified state trie.

Loading diagram...

1.4 Design Philosophy

The Kortana architecture is strictly bound by a set of non-negotiable design principles. The two most critical are:

[!IMPORTANT] 1. Security over speed. A faster chain that loses funds is a failed chain. Every performance target is subject to the security architecture, never a reason to relax it.

2. Determinism over cleverness. An optimization that makes two honest nodes disagree, even once in a billion blocks, is worse than a boring implementation that never does. No floating-point math, no system clocks in consensus, and strict canonization.

1.5 Specification Reference

This documentation is derived from the authoritative engineering specification: Kortana_Blockchain_Production_Engineering_v3.md. Every mechanism, parameter, and endpoint documented here traces directly back to the consensus and execution algorithms defined in that specification and implemented in the kortana-node C++ source.