Product Documentation
  • 👋Welcome to K3 Labs
  • Getting Started
    • Quick Start Guide
  • Automate
    • How to create a Workflow
    • Design Page: Key Sections
    • Trigger Set Up
      • Scheduled / Manual Trigger
      • Smart Contract-based Trigger
        • Token Smart Contracts Trigger Examples
        • Swap/Staking Smart Contracts Examples
        • NFT Collection Smart Contracts Examples
      • Wallet event-based
    • Functions Overview
      • Details on Read functions datapoints
      • Transform Function Details
        • Transform Custom Formula
      • JSON Data Preview
      • Custom Inputs
    • What are Actions?
  • Deploy
    • Deploy Page
    • Project Creation
  • Integrations
    • Coinbase
    • Slack
    • Telegram
    • Cubist Wallet
    • Safe Wallet
    • Hyperliquid
  • Tech Documentation
    • K3 Framework
      • Abstract
      • K3 Consensus
    • Networks & Usage
    • K3 Wasm
      • K3 Wasm Rust SDK
      • K3 Wasm Internal Specifications
    • Operator onboarding
Powered by GitBook
On this page
  1. Tech Documentation
  2. K3 Framework

Abstract

PreviousK3 FrameworkNextK3 Consensus

Last updated 1 year ago

K3 Stateless Rollup is:

  • Computing service that provides services to other networks or applications.

  • Decentralized network that runs its own validator set and is compatible with any EVM or non-EVM blockchains.

K3 Stateless Rollups like oracles, bridges, rollup watchers, relayers networks, general computation infrastructures, and exploit prevention systems, provide services without being constrained by any particular blockchain. These protocols require an infrastructure for the submission and auditing of the Operators' work, reaching on-chain agreements on arbitrary tasks, and distributing rewards and penalties based on attestations.

The K3 Stateless Rollup Framework allows developers to self-deploy (1) custom computational services over trustless execution environments and (2) a network of Operators that run arbitrary tasks.

Protocols execute compute tasks through the Task Consensus, which validates the task and sends back the result with "Proof of Task". Powered by a modular consensus engine, the scheme allows the execution and validation of any type of service.