# The Unit of Interaction

IronWeave fundamentally redefines the concept of a **block** in blockchain technology. Instead of a block being a batch of public transactions added to a single global ledger, in IronWeave, an *IronWeave block is the atomic unit of interaction itself*.

## IronWeave Block: The Unit of Interaction

In IronWeave, every distinct interaction – whether it's sending an AI query, sharing a file, making a payment, or any other data exchange between two or more parties – creates its own unique block.

* **Atomic Interaction:** This means that each *event* or *data unit* is self-contained within its own block. It's not bundled with unrelated transactions from other users.
* **Independent Encryption:** Crucially, each shared block is independently encrypted with unique cryptographic keys that are only shared among the specific participants of that interaction. This ensures that the data within that block is private by default, visible only to those explicitly involved.
* **Decentralized Placement:** These shared blocks are not appended to a single, public, central chain. Instead, they are simultaneously placed onto the individual, private chains of each of the involved participants.

This design enables a massively parallel architecture, as countless interactions can occur simultaneously without bottlenecking a single shared ledger. This design also prevents the mass scanning, copying, and brute-force attacks that are common vulnerabilities even on public ledgers attempting privacy with techniques like ZK Proofs or Fully Homomorphic Encryption (FHE).

## Each Chain: A Focused and Private View

Because each entity (person, company, device, DApp, AI agent, process, event, etc.) on IronWeave has its own dedicated chain(s), and shared blocks are placed directly onto their chains, each chain becomes a focused and inherently private *view* of that chain's sequence of interactions. Said another way, the chain itself becomes a private ledger of its owner's specific activities.

* **Personalized Ledger:** Your IronWeave chain is your personal, chronological record of all your digital interactions where you were a participant. It contains only the shared blocks you were involved in, alongside any private, single-party blocks you might create.
* **Privacy by Design:** Other chains and their interactions are completely invisible to you unless you are a direct participant in a shared block with them. This is the *unscannable privacy* that IronWeave champions – there's no public ledger to scan for activity you weren't involved in.
* **Granular Control:** This architecture grants unparalleled granular control over your data. You own your chain and the keys to your shared blocks, deciding precisely who sees what, on an interaction-by-interaction basis.

## Analogy: A Personal Diary vs. A Public Newspaper

We like analogies because they help put abstract ideas into everyday experiences. Here's another one.

Imagine a traditional, monolithic blockchain as a single, massive public newspaper that everyone in the world contributes to. Every article (transaction) is published for everyone to read. If you send a private note to a friend, that note is still an article in the newspaper, visible to anyone who picks it up, even if it's coded or obscured. Your "chain" would be tracing the path of your articles through this public newspaper. It's transparent by default.

Now imagine IronWeave. It's not one newspaper. Instead, every single person has their own private, locked diary (their individual chain).

* When you want to share a secret note with a friend (a "shared block"), you both sit down and write that secret note together in a brand new, unique secret language (unique encryption keys) that only the two of you know.
* Then, you each individually glue that secret note into your own diary at the correct chronological point.
* Your diary (your IronWeave chain) is a perfectly organized, chronological record of all the secret notes you've ever written or received.
* No one else can read your diary, and you can't read anyone else's diary, unless you were explicitly involved in writing a specific secret note with them and know its unique secret language.

This analogy highlights how each IronWeave chain provides a truly private and focused history of an entity's interactions, completely segregated from the countless other interactions happening simultaneously across the broader IronWeave fabric.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ironweave.io/privacy/the-unit-of-interaction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
