# Keys

IronWeave's approach to encryption key management is designed to provide unparalleled privacy and security by decentralizing control and creating unique keys for every interaction. It deviates significantly from traditional centralized systems, and from other blockchains, by giving granular ownership of data and its keys directly to the participants.

Here's how IronWeave handles encryption keys:

## 1. For Individual Chains (Entities)

* **Each Entity has its Own Chain(s):** In the IronWeave fabric, every entity – whether it's a person, company, DApp, machine, event, process, account, or even a place – has its own dedicated blockchain or multiple chains. These chains are inherently private and operate independently.
* **User Control of Keys:** IronWeave emphasizes user control and data sovereignty. Users maintain control over their encryption keys, which are fundamental to accessing and managing the data on their individual chains. This means users define who can interact with their chain and set permissions for what actions can be performed. Control over these keys rests with the chain's owner.

## 2. For Each Shared Block (Interactions)

* **Dynamic Key Generation per Interaction:** When two or more individual chains interact to exchange data (e.g., a payment, a contract, an online interaction, a supplier delivery, so on), they synchronize their states to create a shared block, which is placed on each participant's chain. Crucially, a new, unique set of encryption keys is generated specifically for that particular shared block.
* **Access Only to Participants:** These unique encryption keys for each shared block are only available to the participants involved in that specific interaction. This means that only the parties who are part of that shared block can decrypt and view its content. Anyone else on the IronWeave fabric, even if they have their own chain, cannot access the data within a shared block unless they were a direct participant and hold the corresponding keys.
* **Data as an independent vault:** Each shared block effectively functions as a separate *data vault*, with its own unique key. This object-level encryption ensures that even if you gained access to one part of a chain, you wouldn't automatically have access to all (or any) other shared blocks it's involved in, as each requires its own specific key.
* **Proof of Creation and Immutability:** The creation of a new block with a new set of keys not only secures the data from unauthorized access, but also serves as a cryptographic signature. This allows participants to immutably prove that the data was indeed created by the claimed originator and was not spoofed.

In summary, IronWeave moves beyond the traditional public/private key pairs associated with an individual's wallet in most blockchains by creating a dynamic, interaction-specific key management system. This ensures that privacy is not just a feature but a fundamental architectural principle, enforced at the very core of every data exchange.

<br>


---

# 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/keys.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.