Skip to content

Common integration layer

TOOL Integration Overview

This page is the common entrypoint for integrating with TOOL (specifically focused on Searcher Network/v0 Mainnet stage) as an Orderflow Provider (OFP), Searcher, or external PBS block builder. It explains the shared flow, shared terms, and common boundaries before the role-specific documents branch into details.

Shared Concepts

Concept Meaning
Source orderflow Private transactions or bundles submitted by an OFP or external builder.
Source commitment TOOL's commitment created from valid source orderflow.
Searcher bundle A native TOOL bundle that builds on one or more commitments and adds searcher transactions.
Callback Optional same-origin delivery of an enriched bundle back to the source.
Same-origin routing Private source transactions are only returned to the source that supplied them.
Native TOOL path TOOL-side block production or relay delivery that does not require returning a bundle to an external source.
TEE verification Optional verification that private flow is being sent to an attested TOOL environment.

Common Flow

TOOL (in the Searcher Network/v0 stage) accepts private or pre-merged orderflow, converts valid submissions into Commitments, lets searchers build on the allowed Commitment view inside the TOOL network, and routes valid enriched bundles according to callback and block-production policy.

flowchart TB
  subgraph Sources["Source integrator boundary"]
    direction TB
    SourceClients["OFP and PBS builder clients<br/>private txs and bundles"]
    SourceAuth["Source authentication<br/>callback eligibility"]
    Verifier["TEE verifier<br/>optional RA-TLS policy"]
  end

  subgraph ToolNetwork["TOOL network"]
    direction TB
    subgraph ToolTEE["TOOL node TEE environment"]
      direction TB
      Intake["Gateway and source intake<br/>eth_sendBundle / TOOL RPC"]
      Commitments["Commitment engine and feed<br/>origin tracking and timing"]
      Routing["Bundle API and routing policy<br/>simulate, submit, classify"]
      Native["Native block path<br/>subslot and relay delivery"]
      Intake -->|"form source commitments"| Commitments
      Commitments -->|"validated metadata"| Routing
      Routing -->|"accepted internal flow"| Native
    end

    subgraph SearcherTEE["Searcher context inside TOOL"]
      direction TB
      SearcherView["Allowed commitment view"]
      SearcherRuntime["Searcher / solver logic"]
      SearcherBundle["Native TOOL bundle<br/>source commitments + searcher txs"]
      SearcherView -->|"evaluate opportunities"| SearcherRuntime
      SearcherRuntime -->|"build and submit"| SearcherBundle
    end

    Commitments -->|"stream allowed commitments"| SearcherView
    SearcherBundle -->|"tool_simulateBundle / tool_sendBundle"| Routing
  end

  subgraph Delivery["Delivery contexts"]
    direction TB
    Callback["Callback service<br/>optional same-origin return path"]
    Relay["MEV-Boost relay path"]
    Validator["Validator"]
    Relay -->|"block proposal path"| Validator
  end

  SourceClients -->|"submit private txs / bundles"| Intake
  SourceAuth -.->|"authenticate source identity"| Routing
  Verifier -.->|"verify attested endpoint"| Intake
  Routing -->|"same-origin enriched bundle"| Callback
  Native -->|"payload delivery"| Relay

  style Sources fill:#f8fafc,stroke:#64748b,stroke-width:2px
  style ToolNetwork fill:#edf7f5,stroke:#0f8b6f,stroke-width:2px
  style ToolTEE fill:#eef2ff,stroke:#315fbe,stroke-width:2px
  style SearcherTEE fill:#fff7ed,stroke:#a56812,stroke-width:2px
  style Delivery fill:#fff1f2,stroke:#b03a5b,stroke-width:2px

API Orientation

Different roles use different parts of the API surface. This overview names the relevant surfaces so each role can find the right integration path; Reference is the source of truth for schemas, examples, endpoint shapes, and method-level validation behavior.

Role Primary surfaces
OFPs and external builders eth_sendBundle for source ingress and the callback receiver contract when same-origin return flow is enabled.
Searchers tool_subscribe, tool_simulateBundle, tool_sendBundle, and tool_nextBlockParams.
Privacy-sensitive integrators tee_getAttestation before sending private flow or consuming sensitive commitment data.
Validators and relay clients MEV-Boost builder HTTP for status, registration, bid, and payload exchange.

Shared Routing Rules

The initial external callback model is conservative:

Rule Integration effect
Callbacks are optional. Sources may submit flow without receiving enriched bundles back.
Callback-enabled sources authenticate. TOOL must identify the source that is allowed to receive the return payload.
Callback payloads are same-origin by default. Returned private source transactions belong to the source receiving the callback.
Mixed-origin private flow stays internal. It may still be useful for TOOL-native block production, but is not returned to one external source in the initial callback model.
Raw signed transactions are protected across sources. Private source transactions from one origin are not sent to another source.
flowchart TB
  subgraph SourceBoundary["Source / callback boundary"]
    direction TB
    Source["OFP or PBS builder"]
    Auth["Identity and callback policy"]
    CallbackEndpoint["Callback endpoint<br/>optional"]
  end

  subgraph ToolNetwork["TOOL network"]
    direction TB
    subgraph SearcherContext["Searcher context inside TOOL"]
      direction TB
      View["Allowed commitment view"]
      Strategy["Searcher logic"]
      Bundle["Native TOOL bundle"]
      View -->|"construct from allowed metadata"| Strategy
      Strategy -->|"builds on commitments"| Bundle
    end

    subgraph PolicyContext["TOOL node TEE policy context"]
      direction TB
      Store["Commitment store<br/>source, origin set, expiry"]
      Enriched["Enriched commitment<br/>source flow + searcher txs"]
      Policy["Routing policy<br/>origin and callback checks"]
      Decision{"Single callback-eligible source?"}
      CallbackPath["Callback return path"]
      NativePath["Native TOOL path"]
      Store -->|"attach origin metadata"| Enriched
      Bundle -->|"submit enriched bundle"| Enriched
      Enriched -->|"classify source set"| Policy
      Policy -->|"evaluate same-origin rule"| Decision
      Decision -->|"yes + authenticated callback"| CallbackPath
      Decision -->|"no callback or mixed private flow"| NativePath
    end

    Store -->|"publish allowed view"| View
  end

  subgraph Delivery["Delivery contexts"]
    direction TB
    CallbackDelivery["Source callback delivery"]
    RelayDelivery["MEV-Boost relay delivery"]
  end

  Source -->|"submit source orderflow"| Store
  Auth -.->|"register or verify callback settings"| Policy
  CallbackPath -->|"return source-owned private flow only"| CallbackDelivery
  CallbackDelivery -->|"deliver enriched bundle"| CallbackEndpoint
  NativePath -->|"keep commitment internal"| RelayDelivery

  style SourceBoundary fill:#f8fafc,stroke:#64748b,stroke-width:2px
  style ToolNetwork fill:#edf7f5,stroke:#0f8b6f,stroke-width:2px
  style SearcherContext fill:#fff7ed,stroke:#a56812,stroke-width:2px
  style PolicyContext fill:#eef2ff,stroke:#315fbe,stroke-width:2px
  style Delivery fill:#fff1f2,stroke:#b03a5b,stroke-width:2px

Shared Trust Model

Authentication and TEE verification are separate concerns.

Callback authentication

Identifies the source that is allowed to receive enriched bundles. It is required when a source asks TOOL to call back with source-owned private transactions.

TEE verification

Lets an integrator verify the TOOL environment before sending private flow or consuming sensitive commitment data. The stronger privacy setup is RA-TLS, where the TLS connection is bound to the attested service.

Public Endpoints

Nuconstruct-hosted TOOL endpoints are available for mainnet searcher-network testing, Hoodi RPC access, and Hoodi validator relay integration.

Searcher Network TOOL v0 Mainnet

Mainnet RPC

rpc.tool.limo

Use this endpoint for Searcher Network / TOOL v0 Mainnet integration.

Hoodi Testnet TOOL v1

Testnet RPC

https://rpc-hoodi.nuconstruct.xyz/
wss://rpc-hoodi.nuconstruct.xyz/ws

Use these endpoints for TOOL v1 Hoodi Testnet JSON-RPC and WebSocket access.

Hoodi Validators MEV-Boost compatible

Relay API

https://0xa0f46566247ceb1f259a7189d5ac8bf2f0f07c135f081b0b5a9f226ef864bf6362c74306fcd02a87b7941f6feac57dc7@relay-hoodi.nuconstruct.xyz

Use this endpoint as the TOOL v1 MEV-Boost Relay API-compatible endpoint for Hoodi Testnet validators.

Onboarding

Orderflow Providers

Route private source flow into TOOL, optionally authenticate a callback endpoint, and understand attribution boundaries.

Searchers

Subscribe to commitments and submit native TOOL bundles from inside the network participation model.

External PBS Builders

Submit existing bundle flow through eth_sendBundle and optionally receive same-origin enriched bundles.

Technical Reference

Use Reference for method schemas, field definitions, and endpoint shapes. Use Technical Architecture after the relevant integration path is clear for deeper node behavior, subslots, commitment internals, peer networking, relay delivery, and low-level API nuances.