Quickstart
Hyper EVM presents many barriers to adoption:
on the creator side
Little to no open source / permissionned environment
Testnet reliability (frequent hardforks, missing blocks, uptime,...)
Infra specs are not conventional (dual-block mechanism, ...)
and on the user side
App diversity is lacking (missing fundamental primitives and verticals)
limited analytics tools (tenderly, explorer, etc..)
Conflicted, pending transactions
More generally, DeFi accessibility in its current form is still limited for creators and users:
Existing no-code solutions are limited to token launchpads with extremely poor tokenomic customization > Kitchen 100s functions empower creators far beyond
Trenches are 90% loss 10% profit > Kitchen yield bearing wallets close this gap, the more activity the more rewards
Information is hardly accessible and often priced before being public > Kitchen AI powered block explorer provide users every on-chain information at any time in an accessible format.
Liquidity is scarce, holders trade but don't LP, trading activity is supported by high volumes but as soon as volume drops prices can't sustain > Kitchen native liquidity AMOs ensure deep liquidity for every assets
Kitchen Layer is built upon 4 pillars:
Deploy Easily: Build sophisticated protocols made as simple as launching a memecoin. Select, assemble, and deploy features in a few clicks, from a library of 100s audited native functions.
Earn More: The FIRST network with yield-bearing wallets, earning a share of the sequencer fees FOREVER. Every asset minted, traded and transferred on Kitchen Layer carries yield proportionally to the activity it generates over time, distributed directly in the wallet holding it.
Track Faster: Kitchen Layer presents the next generation block explorer, powered by Blockscout, and your favorite LLMs, Kitchen Scan enables everyone to read the blockchain and perform data analytics by prompting the Chef AI agent directly from the search bar.
Trade Better: Kitchen interoperability at the chain level allows to create advanced liquidity AMOs between dApps, ensuring minimum slippage for traders of any size, and maximum liquidity utilization thus higher yield for LPs.
Tech Stack
Under the hood, Kitchen Layer is engineered with battle-tested blockchain technologies that push the boundaries of Layer 2 performance and developer experience. A tech stack carefully curated to deliver unprecedented efficiency, modularity, and scalability.
Roll Up Tech: The Arbitrum Orbit is the standardized, shared, and open-source development stack, maintained by the Offchain Labs.
Execution Client: For Orbit chains, the underlying execution client is Arbitrum Nitro, a highly optimized technology stack developed by Offchain Labs. Nitro incorporates a modified version of go-ethereum (Geth) at its core, enabling exceptional EVM compatibility, high performance, and operational efficiency. This advanced architecture ensures broad compatibility with Ethereum consensus clients and provides a robust foundation for Orbit chains.
Kitchen Layer uses innovation to improve user experience. For example KL is integrating EIP-7702, an Ethereum improvement proposal (EIP) that revolutionizes user experience by enabling account abstraction features such as transaction batching, gas sponsorship, and granular permission management.
EVM Implementation: Kitchen Layer extends the EVM contract size limitation, deviating from the standard 24.5kb bytecode limit. Kitchen Layer implements a custom bytecode size constraint of 96kb, designed to facilitate developer capabilities for deploying more complex contracts and supporting custom Pre-Compile implementations.
In the context of Kitchen Layer and similar blockchain platforms, a precompile is a low-level, native contract implemented directly within the blockchain's client software. Unlike typical smart contracts written in high-level languages like Solidity and executed by the Ethereum Virtual Machine (EVM), precompiles are hard-coded into the client to offer optimized, efficient execution for specific operations. They are used to perform complex or frequently-used operations more efficiently than standard EVM bytecode, handling tasks such as cryptographic operations, data compression, or other computationally intensive processes. By implementing these operations at a lower level, precompiles can reduce gas costs and improve performance.
Data Availability: Calldata DA is used to stay aligned with the Hyperliquid ecosystem. In the context of Hyperliquid, "calldata" refers to a data field that holds the input information for a transaction. Calldata data availability is a concept introduced to enhance the scalability of Ethereum by allowing large amounts of data to be posted to the blockchain more efficiently..
Developer Docs
Available at ...
Last updated