---
title: "Atomic Composability"
path: "/contents/tech/core-concepts/atomic-composability"
bannerImage: "https://j9ytchrzkvqpcul7.public.blob.vercel-storage.com/096da27c-30bb-4de2-a81a-64e8afc390dd.jpg"
version: "2.3.0"
author: "Hydrate"
createdAt: "2026-01-21T17:20:10.096Z"
updatedAt: "2026-07-09T11:09:57.807Z"
---

# Atomic Composability

<Infobox>
| **Category** | Core Property |
| **Enabled By** | [Transaction Manifests](/contents/tech/core-protocols/transaction-manifests) |
| **Key Benefit** | No partial failures in multi-step operations |
</Infobox>

## Overview

**Atomic composability** means that complex multi-step operations either execute completely or not at all. On Radix, a single [transaction manifest](/contents/tech/core-protocols/transaction-manifests) can chain together any number of operations — swaps, loans, deposits, withdrawals — and the entire sequence is atomic.

This is critical for [DeFi](https://en.wikipedia.org/wiki/Decentralized_finance) because it eliminates the risk of partial execution. On EVM chains, multi-step strategies often require multiple transactions, each of which might succeed or fail independently. A failed step in the middle can leave funds stranded. On Radix, the manifest either completes all steps or reverts everything.

### Why It Matters for AI Agents

Autonomous [AI agents](/contents/tech/core-concepts/radix-for-ai-agents) need atomicity guarantees even more than human users. An agent executing a complex DeFi strategy can encode the entire operation in a single manifest, confident that partial failures are impossible. This removes an entire category of error-handling complexity from agent design.

### Cross-Shard Atomicity

Radix's [Cerberus consensus](/contents/tech/core-protocols/cerberus-consensus-protocol) uniquely preserves atomic composability across shards. Unlike other sharded systems where cross-shard operations require asynchronous bridges, [Cerberus](/contents/tech/core-protocols/cerberus-consensus-protocol) braids consensus across any number of shards for a single transaction, maintaining atomicity at any scale.

### A Concrete Example: Flash Loans

The clearest expression of atomic composability is the [flash loan](https://en.wikipedia.org/wiki/Flash_loan): borrowing an asset and repaying it within the *same* [transaction](/contents/tech/core-protocols/transaction-manifests). Because the borrow and the repayment are two steps of one atomic operation, the loan is either paid back by the end of the transaction or the whole transaction reverts — so the lender takes **no credit risk**. Radix's own developer education describes this as enabling "hyper-efficient [arbitrage](https://en.wikipedia.org/wiki/Arbitrage) to take place without any credit risk" ([Radix Learn: What is Atomic Composability](https://www.radixdlt.com/articles-learn/what-is-atomic-composability)).

### Composability Without Glue Code

On Radix, the assets returned by one [component](/contents/tech/core-protocols/scrypto-programming-language) can be passed directly into the next as part of the same [manifest](/contents/tech/core-protocols/transaction-manifests), so applications "combine any number of applications together in any shape or form" without a bespoke integration contract wrapping every combination ([Radix Learn](https://www.radixdlt.com/articles-learn/what-is-atomic-composability)). This is what distinguishes atomic composability from calling one contract from another: the composition lives in the transaction, expressed against real [resources](https://docs.radixdlt.com/docs/resources), not hard-wired into deployed code. It is the practical foundation for the [readable, guaranteed transactions](/contents/tech/core-concepts/blind-signing-and-transaction-manifests) the [Radix Wallet](/contents/tech/core-protocols/radix-wallet) can show a user before they sign.