# Dictionary This page is dedicated to KRNL-specific vocabulary that will appear in this document. #### Core Protocol Concepts | Term | Definition | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **KRNL Protocol** | A decentralized orchestration layer that unifies Web3, Web2, and AI systems into verifiable workflows using cryptographic proofs. | | **Kernel** | A single execution unit in a workflow that performs a specific function such as an API call, smart contract interaction, or data transformation. | | **Workflow** | A multi-step process built using KRNL’s DSL (Domain-Specific Language) that defines how kernels interact to perform a complete operation. | | **Executor** | An open-source, auditable component that executes workflow steps within a secure sandbox. | | **Attestor** | A private security module owned by dApp developers that cryptographically verifies executor outputs and signs attestations. | | **Executor–Attestor Separation** | The architectural principle separating computation (executor) from verification (attestor) to achieve zero-trust execution. | | **KRNL Node** | The execution and orchestration engine (a Geth extension) that coordinates workflows, handles network attestation, and generates proofs. | | **KRNL Registry** | An on-chain registry that stores protocol configurations, kernel schemas, and versioned workflow references. | | **KRNL Vault** | The fee management contract that handles payments, rewards, and treasury operations for executors, node operators, and developers. | | **KRNL SDK** | Developer toolkit enabling integration of workflows into dApps through TypeScript or JavaScript APIs. | | **KRNL CLI** | A command-line interface for deploying, testing, and managing KRNL integrated contracts | | **KRNL Studio** | A visual IDE for building and testing workflows without writing code. | | **KOS (KRNL Operating System)** | The coordination layer managing node discovery, attestation, and proof validation across the network. | #### Architecture & Infrastructure | Term | Definition | | -------------------------------- | ----------------------------------------------------------------------------------------------------------- | | **Core Orchestration Layer** | The main KRNL engine that executes workflows and coordinates executor-attestor communication. | | **Integration Layer** | Connects dApps and smart contracts to KRNL via SDKs and account abstraction mechanisms. | | **User Interface Layer** | The front-end interface through which end users initiate workflows via wallets and smart contract accounts. | | **External Infrastructure** | Components managed outside KRNL (e.g., relayers, bundlers, oracles). | | **Target Contract** | A smart contract that receives verified results from a workflow for final execution. | | **Relayer / Bundler** | A service that manages EIP-4337 transactions for Smart Contract Accounts. | | **Smart Contract Account (SCA)** | A programmable wallet (EIP-7702 + ERC-4337) that executes transactions and payments automatically. | *** #### Security & Cryptography | Term | Definition | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | **Ephemeral Keys** | Single-use cryptographic keys derived for each workflow execution, ensuring replay protection and forward secrecy. | | **Master Secret** | Root cryptographic secret stored securely in the attestor and used for key derivation. | | **Execution Proof** | A cryptographic record proving that workflow steps were executed as defined. | | **Composability Proofs** | Nested proofs combining multiple workflow steps into a verifiable chain of trust. | | **Network Attestation** | A cryptographic record verifying every external network call (HTTP, HTTPS, DNS) made during execution. | | **Network Interceptor** | A man-in-the-middle system that transparently monitors, records, and signs network interactions for forensic validation. | | **DNS Attestation** | Cryptographic logging of DNS queries and resolutions during workflow execution. | | **TLS Interception** | Secure interception of HTTPS traffic to verify end-to-end communication integrity. | | **Attestation Data Structure** | Structured logs of network activities (requests, responses, DNS) signed by the attestor. | | **Proof of Execution (PoE)** | The verifiable linkage between executor outputs and attestor signatures. | | **TEE (Trusted Execution Environment)** | Hardware-based secure enclave used optionally for high-value workflow isolation (e.g., Intel SGX, AMD SEV). | | **gVisor Sandbox** | A user-space kernel providing syscall interception and runtime isolation for executors. | | **Reproducible Builds** | Deterministic build process ensuring executor binaries can be independently verified. | *** #### Economic & Governance Model | Term | Definition | | ------------------------------- | ------------------------------------------------------------------------------------ | | **Node Operator** | Participant running a KRNL Node to process workflows and generate proofs. | | **dApp Developer** | Builder who integrates KRNL workflows into decentralized applications. | | **Fee Architecture** | The breakdown of workflow execution costs: base fee, external service fees, and gas. | | **Value Distribution Model** | Economic mechanism distributing fees and rewards among protocol participants. | | **Platform Base Fee** | The protocol’s fixed cost for using KRNL infrastructure per execution. | | **Treasury Management** | Automated handling of collected fees, development funds, and ecosystem grants. | | **Governance Model** | Community-driven structure for approving executors and protocol updates. | | **Executor Governance Model** | Consensus process through which executors are reviewed, audited, and whitelisted. | | **Protocol Evolution Strategy** | Framework for introducing new features and managing backward compatibility. | *** #### Comparative & External References | Term | Definition | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | **EIP-4337** | Ethereum proposal enabling account abstraction for smart contract wallets. Read more [here](https://eips.ethereum.org/EIPS/eip-4337) | | **EIP-7702** | Ethereum proposal for delegating transaction execution rights. Read more [here](https://eips.ethereum.org/EIPS/eip-7702) | | **CID (Content Identifier)** | IPFS hash used for content verification and versioning. |