---
title: "Blind Signing and Transaction Manifests"
path: "/contents/tech/core-concepts/blind-signing-and-transaction-manifests"
version: "1.2.0"
author: "Hydrate"
createdAt: "2026-03-02T17:29:31.902Z"
updatedAt: "2026-03-16T18:20:56.276Z"
---

# Blind Signing and Transaction Manifests

<Infobox>
| **Problem** | Blind signing in EVM — users sign hex they can't read |
| **Solution** | [Transaction Manifests](/contents/tech/core-protocols/transaction-manifests) — deterministic, human-readable |
| **Impact** | $100M+ lost to approval exploits would be prevented |
</Infobox>

## Overview

**Blind signing** is the practice of signing transactions whose effects you cannot verify. On [Ethereum](https://ethereum.org), users routinely approve transactions that are opaque hexadecimal data — they cannot see what the transaction will actually do until after it executes.

### The Cost

Blind signing has enabled over $100 million in losses through approval exploits, phishing, and malicious contract interactions. Users unknowingly grant unlimited token approvals that are later drained.

### How Radix Solves This

Radix [transaction manifests](/contents/tech/core-protocols/transaction-manifests) are deterministic, human-readable descriptions of exactly what a transaction will do. The [Radix Wallet](/contents/tech/core-protocols/radix-wallet) parses these manifests and shows users exactly which assets will move, where they'll go, and what they'll receive — before signing.

This is equally important for [AI agents](/contents/tech/core-concepts/radix-for-ai-agents) — autonomous agents can read and verify manifests programmatically, never blind-signing a transaction they don't understand.