mev

Explain Kaia's KIP-249 MEV auction and slot-based backrun flow.

3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill mev-pieverse-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mev
Source: https://github.com/Pieverse-Eng/purrfect-skills/tree/main/kaia-skills/vendor/mev
Command: npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill mev-pieverse-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kaia's MEV Auction (KIP-249) provides a slot-based backrun auction with hidden bids on Kaia, enabling developers to understand MEV mechanics in Kaia and how they differ from Ethereum's PBS/Flashbots model.

Core Features & Use Cases

  • Slot-based adjacency: If a target transaction is at index i in the block, the winning backrun is placed at i+1.
  • Hidden bidding: Bids are submitted privately to the Auctioneer and finalized per block, reducing on-chain bidding leakage.
  • Auction lifecycle: Deposit, bid submission, auction execution, and BidTx construction and execution.
  • Use cases: Developers evaluating MEV strategies, researchers analyzing protocol design, and auditors verifying system safety.

Quick Start

Describe Kaia's KIP-249 slot-based MEV auction flow and the roles involved.

Frequently Asked Questions about mev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is Kaia's KIP-249 MEV auction and how does it work?

Kaia's KIP-249 MEV auction is a slot-based backrun system with hidden bids, where bids are submitted privately to an Auctioneer and finalized per block to reduce on-chain bidding leakage. The winning backrun transaction is placed immediately after the target transaction.

How does the slot-based backrun mechanism place transactions in a block?

The slot-based backrun mechanism enforces adjacency by placing the winning backrun transaction at index i+1 in the block, directly following the target transaction at index i. This ensures strict transaction ordering for MEV extraction without relying on public mempool bidding.

How do I participate in the Kaia MEV auction lifecycle as a developer?

Developers participate in the Kaia MEV auction lifecycle by navigating the deposit flows, submitting private bid transactions to the Auctioneer, and executing the constructed BidTx. The system handles auction execution and bid finalization per block.

How does Kaia's hidden bid MEV auction compare to Ethereum's PBS model?

Kaia's hidden bid MEV auction uses private submissions to an Auctioneer finalized per block, contrasting with Ethereum's PBS or Flashbots model. This slot-based approach with hidden bids specifically reduces on-chain bidding leakage and differs in participant roles and contract interactions.

What are the safety rules and participant roles in Kaia's MEV ecosystem?

Safety rules and participant roles in Kaia's MEV ecosystem define how the Auctioneer manages the auction entry point, deposit flows, and bid lifecycle. Auditors and researchers verify these system safety rules and contract interactions to ensure secure MEV extraction.

Do I need specific smart contracts to execute backrun transactions on Kaia?

Executing backrun transactions on Kaia requires interacting with the auction entry point and following the deposit flows defined by the KIP-249 standard. The system constructs and executes the BidTx based on the hidden bid auction results.