txKit

Safe bridge between AI agents and Web3 transactions - open protocol + reference implementation.

Embeddable Web3 UI components for React + PreparedTransaction spec for AI / MCP tools.

---

v0.1.0-alpha - published under the alpha npm tag while we refine the public surface. API may shift before v1.0.

What is txKit?

txKit is two things:

1. @txkit/tx-protocol - an open PreparedEnvelope shape for AI-initiated Web3 operations (decode, simulate, preview before signing). Composable with MoonPay's Open Wallet Standard.
2. @txkit/react - reference UI components that consume PreparedEnvelope to render confirmation flows, with full lifecycle handling for wallets, balances, transactions, and signatures.

Core invariant: txKit never holds keys. It is an orchestrator, not a signer - keys remain in the wallet, Safe, Turnkey, Privy, or any wagmi-compatible signer.

Why txKit

• Never holds keys. Composes with any wagmi connector, RainbowKit / AppKit / ConnectKit, Privy / Dynamic, MoonPay OWS, Safe, Turnkey.
• Shipped anti-phishing defenses. Pre-sign simulation, MAX-approval warning, decoded calldata preview, configurable confirmation delay, pluggable risk provider (Blowfish / Blockaid).
• Open envelope spec. PreparedEnvelope shape with attack-defense fields for Drift, Bybit, Kelp, multicall bait, address poisoning. CAIP-2 / EIP-5792 / EIP-712 aligned.
• Vendor-neutral. Bring your own RPC, connectors, theme. No lock-in to a hosted RPC, wallet kit, or paymaster.
• Composes, doesn't replace. Embedded mode runs alongside your existing wagmi / RainbowKit / AppKit / ConnectKit / Privy setup - no duplicate providers.
• WCAG 2.1 AA. Focus management, keyboard nav, reduced-motion fallbacks, screen-reader announcements baked in.
• Tiny. 2-7 kB JS gzip per component. Tree-shaken on import.

Packages

Package	Description	Version
@txkit/react	React components and headless hooks
@txkit/core	Framework-agnostic utilities and types
@txkit/themes	CSS themes (light, dark, variants)
@txkit/tx-protocol	Open protocol: PreparedTransaction types + zod schemas
@txkit/tx-decoder	Decode raw EVM calldata into clearSigning trees (ERC-7730 + ABI fallback)
@txkit/ows-adapter	Bridge MoonPay Open Wallet Standard <-> PreparedTransaction
@txkit/x402-adapter	Bridge x402 HTTP payments (Linux Foundation, 2 Apr 2026) <-> PreparedTransaction

The repo also hosts packages/mcp-server - a hardened JSON-RPC MCP server. It is intentionally not published to npm (see SECURITY.md) and is consumed by cloning the repo or vendoring the source.

Quick Start

npm install @txkit/react@alpha @txkit/themes@alpha wagmi viem @tanstack/react-query

import { TxKitProvider, ConnectWallet } from '@txkit/react'
import '@txkit/themes'
import { mainnet } from 'viem/chains'
import { http } from 'viem'

const App = () => (
  <TxKitProvider
    config={{
      chains: [ mainnet ],
      transports: { [mainnet.id]: http() },
    }}
  >
    <ConnectWallet />
  </TxKitProvider>
)

Peer Dependencies

Package	Version
react / react-dom	>= 18
wagmi	>= 2
viem	>= 2
@tanstack/react-query	>= 5

If you're adding txKit to an existing dApp (RainbowKit, AppKit, etc.), you likely already have these installed.

Add to Existing dApp

Already using RainbowKit or another wagmi-based connector? Use embedded mode:

import { TxKitProvider, TransactionButton, txStep } from '@txkit/react'
import { parseEther } from 'viem'
import '@txkit/themes'

// Inside your existing WagmiProvider
function SendButton() {
  return (
    <TxKitProvider embedded>
      <TransactionButton
        steps={[
          txStep('send', 'Send ETH', { to: '0x...', value: parseEther('0.01') }),
        ]}
        label="Send 0.01 ETH"
      />
    </TxKitProvider>
  )
}

Components (v0.1.0-alpha)

• ConnectWallet - multi-wallet connection with ENS, balance display, chain switching
• TokenBalance - native + ERC-20 balance with fiat pricing and auto-formatting
• TransactionButton - multi-step transaction flow with simulation, approval, and anti-phishing
• FlowSteps / FlowProgress / FlowToast - compound components for transaction flow UI

Every component supports three customization levels:

1. Zero-config - drop in and it works
2. Custom render - children as render function for custom UI
3. Headless hooks - full control, bring your own UI

Coming in v0.2.0: ContractForm (ABI-driven form generation), SwapWidget, StakingPanel, ApprovalManager.

Protocol

@txkit/tx-protocol defines an open envelope + content shape flowing between producers (AI / MCP tools, DeFi protocol adapters) and consumers (wallets, signer orchestrators, UI preview layers, policy engines).

"OWS signs. txKit decides what's safe to sign."

v0.1 covers three kinds today: evm-tx (single EVM transaction), evm-batch (EIP-5792 atomic batch), signature (EIP-712 / SIWE / personal-sign). Nine more are reserved: evm-userop, evm-frame, evm-7702, mandate, intent, psbt, svm-tx, move-tx, cosmos-tx.

• Spec v0.1 - canonical RFC
• Examples - StakeWise deposit, Uniswap Permit2 + swap, Safe delegatecall warning
• OWS composition - how this composes with MoonPay Open Wallet Standard

import { createEvmTx, validateEnvelope } from '@txkit/tx-protocol'

const envelope = createEvmTx({
  chain: 'eip155:1',
  calls: [ { to: '0x...', data: '0x...', value: '0xde0b6b3a7640000' } ],
  validity: { notAfter: Math.floor(Date.now() / 1000) + 3600 },
  description: { short: 'Stake 1 ETH', action: 'stake' },
  metadata: { protocol: 'stakewise-v3', tokenMovements: [...], counterparties: [...] },
})
const result = validateEnvelope(envelope)
// See packages/tx-protocol/README.md for the full API

Composes with (not competing with)

txKit is a decode / preview / risk layer. It sits between agents that produce intent and wallets that sign. Common neighbors:

• x402 (Linux Foundation, since 2 Apr 2026) - HTTP payment protocol for agents. Agents pay via x402, then need a tx legibility layer before any on-chain follow-up. txKit complements.
• Open Wallet Standard (OWS) - key custody + raw-tx signing for agents. OWS signs. txKit decides what's safe to sign. See OWS composition.
• Etherspot TransactionKit (v2.1.x) - headless ERC-4337 hooks (UserOp builders, paymaster config). Etherspot builds how to sign, txKit shows what is being signed. Complementary, not overlapping.
• 21st.dev and similar generic AI-agent UI libraries - txKit is specialized for on-chain transaction UX, not generic agent UI. They can be used together.

Why open protocol (not a service)

@txkit/tx-protocol is an open MIT spec + reference implementation. There is no escrow, no per-tx fee, no proprietary verification SaaS in the signing path. The shape lives in your repo, your bundler, your audit. This is the deliberate trade-off vs closed verification services: composability and zero vendor lock-in over end-to-end SLA.

Regulatory posture (US Covered UI Provider, EU MiCA)

txKit is a non-custodial UI library and presentational protocol. The component layer holds no keys, routes no orders, executes no trades. The protocol layer carries no cryptographic integrity on its off-chain fields by itself - integrity comes from the optional producer.signature over the envelope (post-quantum schemes reserved) plus consumer-side decoder re-verification. Authoritative on-chain effect is the raw {chain, calls[*].to, calls[*].data, calls[*].value} tuple (or {scheme, domain, message} for signatures).

• United States. Aligned with the SEC Division of Trading and Markets Staff Statement of 13 April 2026 on Covered User Interface Providers for non-custodial frontend tools (sunset 13 April 2031). For an independent legal interpretation see Jones Day, Crypto Interface Providers May Not Be Broker-Dealers (22 April 2026).
• European Union. Under MiCA and adjacent frameworks, liability for transaction execution rests with the signing party (wallet / signer provider), not with txKit. This project does not custody keys, broker trades, or provide investment advice.

This is positioning, not legal advice. Operators integrating txKit are responsible for their own jurisdiction analysis.

Features

• Built on wagmi + viem - zero vendor lock-in, bring your own RPC
• Anti-phishing - calldata preview, bounded approvals, simulation, risk scoring
• WCAG 2.1 AA - focus traps, keyboard navigation, screen reader support, 44px touch targets
• CSS custom properties (--txkit-*) for full style control
• Light + dark themes with visual variants (soft, sharp, rounded)
• ESM + CJS + TypeScript declarations

Development

pnpm install          # Install dependencies
pnpm build            # Build all packages
pnpm dev              # Dev mode with watch
pnpm typecheck        # Type-check
pnpm lint             # Lint

Project Structure

packages/
  core/         - Framework-agnostic types, utilities, constants
  react/        - React components and hooks
  themes/       - CSS themes and visual variants
  tx-protocol/  - Open PreparedTransaction protocol (types + zod schemas)
    spec/v0.1/  - Canonical RFC for the protocol
    examples/   - Runnable TypeScript examples
app/
  docs/         - Documentation site (Vocs)
  story/        - Component playground (Vite)

Known limitations (v0.1.0-alpha)

• ENS resolution requires mainnet. ENS records live on Ethereum mainnet, so ConnectWallet's ENS name / avatar lookup is silently skipped on chains that don't expose a mainnet public client. The testnet preset injects mainnet alongside Sepolia for this reason. L2 / cross-chain ENS (CCIP-Read, ENSv2 namechain) is on the v0.2 roadmap.
• CSS-only theming. Themes ship as CSS classes (.txkit-light, .txkit-dark, .txkit-soft, etc). There's no runtime theme API yet; switch by toggling a class on the .txkit-root wrapper.
• No SSR helpers. Components are 'use client'. Server rendering of static markup works, but hydration relies on wagmi's standard SSR config (ssr: true + cookieStorage).

Contributing

See CONTRIBUTING.md for development guidelines.

Documentation

Visit txkit.dev for full documentation.

License

MIT