> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notareum.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What is notareum

# What is Notareum

Notareum is an open protocol that turns every blockchain resource into a verified, portable, cryptographically signed file. It defines a standard container called a `.nota` file that encodes a wallet address, smart contract, transaction hash, NFT, IPFS CID, or arbitrary metadata together with its chain context, human-readable metadata, a digital signature, and optional on-chain verification status. The result is a universal trust layer that works across every chain, wallet, exchange, and dapp.

The protocol has four parts. A **file format** defines how a `.nota` file looks and how it is signed. A **resource registry** anchors resources on-chain with deterministic IDs and optional human-readable aliases like `alice.nota`. A **verification engine** lets staked validators attest to the authenticity of a resource, producing multi-party cryptographic consensus. A **token and governance system** aligns validator incentives, funds the ecosystem, and lets the community adjust protocol parameters as the network matures.

## What a .nota file looks like

A `.nota` file is a human-inspectable JSON document that fits comfortably in a text message, email body, or QR code. A minimal example:

```json theme={"system"}
{
  "version": "1.0",
  "type": "address",
  "chain": { "name": "ethereum", "chainId": 1, "network": "mainnet" },
  "resource": {
    "identifier": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "name": "Alice Main Wallet",
    "alias": "alice.nota"
  },
  "verification": {
    "status": "verified",
    "level": "enhanced",
    "validators": ["0xVal1...", "0xVal2...", "0xVal3...", "0xVal4...", "0xVal5..."]
  },
  "signature": {
    "algorithm": "ECDSA",
    "curve": "secp256k1",
    "address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "message": "Notareum v1.0 | ... | 1700000000",
    "signature": "0x...",
    "timestamp": 1700000000
  }
}
```

Every field has a precise meaning defined in the [.nota File Format](../protocol/nota-file-format.md) specification. A recipient can validate the signature offline, and if desired, check the on-chain registry to see how many validators attested to the resource and at what level.

## The core flow

```mermaid theme={"system"}
flowchart LR
    A[Alice creates .nota file] --> B[Signs with her private key]
    B --> C[Sends file to Bob]
    C --> D[Bob's wallet parses the file]
    D --> E{Signature valid?}
    E -->|Yes| F[Check on-chain status]
    E -->|No| X[Reject]
    F --> G{Verified?}
    G -->|Yes| H[Show 'Verified: Alice']
    G -->|No| I[Show warning]
```

Alice creates a file describing her Ethereum wallet, signs it, and sends it to Bob. Bob's wallet validates the signature, checks the Notareum registry for Alice's on-chain record, and displays a clear indicator before Bob sends any funds. The same flow works for contracts, transactions, NFTs, and every other supported resource type.

## Why it matters

Blockchain addresses are unintelligible strings. Users copy and paste them through messaging apps, emails, and screenshots with no cryptographic binding between the address and a human identity. This is the single largest category of irreversible user loss in crypto: typos, clipboard hijacking, spoofing, and phishing. Notareum eliminates this category by giving every resource a signed, self-contained identity document that any software can verify.

## What Notareum is not

Notareum is not a KYC system, not a centralized name service, and not a blockchain. It is a protocol: a set of specifications, contracts, and SDKs that anyone can implement, integrate, or extend. The `.nota` file format is permissionless. The registry and verification engine are on-chain contracts. The token economics are designed to keep the validator network honest without requiring trust in any single entity.

## Next steps

* Read [Why Notareum](why-notareum.md) for the problem framing
* Read [The Trust Layer](the-trust-layer.md) for the architectural pitch
* Skip to the [Quick Start](quickstart.md) to ship code
* Dive into the [Protocol Overview](../protocol/overview.md) for the full picture