The trust layer
for Web3

An open protocol for sharing blockchain resources safely using the verifiable .nota file format.

.nota format specv1.0
{
  "type": "address",
  "chain": "ethereum",
  "resource": {
    "id": "0x7a2b...9f3e",
    "name": "Treasury",
    "alias": "treasury.nota"
  },
  "verification": {
    "status": "verified",
    "level": "institutional"
  },
  "signature": "ecdsa:secp256k1"
}
SignedVerified1.2 KB
Network Uptime (30d)
99.99%
Zero downtime via distributed consensus.
Total Value Secured ($NOTA)
$1.2B
Across 40+ supported protocols.
Verification Speed (avg)
42ms
Instant confirmation via L2 engine.
Introducing .NOTA

A Simple Solution to a Complex Problem

A new file format that wraps any blockchain resource into a portable, verifiable package you can share like a photo or document.

1

Resource Wrapping

Standard data is encapsulated into the verifiable .nota format via local SDK.

The Core Engine

Verification Network

Nodes reach consensus on signature validity before state transition.

3

Safe Execution

Receiving dApps natively decode and trust the assertion without middleman logic.

The Problem

Billions Lost to a Copy-Paste Problem (A Human + AI Agent Error)

Every day, people share wallet addresses, transaction hashes, and contract addresses by copying and pasting raw hex strings. A 42-character jumble like 0x7a2b...9f3e is supposed to represent a person, a business, a treasury. But it looks like gibberish to most people, especially non-savvy users. And even experts get it wrong.

Send Assets
Paste destination address
Recipient Address
0x7a2b890cf58231548a892 4 92a9129f3e
Clipboard malware silently swapped the address while you were not looking.

When you make a bank transfer, the system shows you the account holder's name before you confirm. That one small feedback loop prevents millions of errors every day. In crypto, you get nothing. You paste an address, hit send, and hope. There is no "Are you sure this is John?" confirmation. No name resolution. No second chance. If even one character is wrong, or if clipboard malware silently swapped the address while you were not looking, your money is gone. Permanently. Irreversibly.

Bank Transfer
The safety of name resolution
When you make a bank transfer, the system shows you the account holder's name before you confirm.
Sending Funds To
John Doe
Checking Account ending in ****4921
Verified
Crypto Transfer
The void of confirmation
There is no "Are you sure this is John?" confirmation. No name resolution. No second chance.
Sending Funds To
0x7a2b890cf58231548a892f392a9129f3e
Unknown
If even one character is wrong, your money is gone. Permanently. Irreversibly.

This is not a fringe problem. Address poisoning attacks, clipboard hijackers, fake contract scams, and plain human error have cost the industry billions. They have cost individuals their life savings, cost businesses months of revenue, and cost the entire ecosystem its credibility with mainstream users. The technology that promises to bank the unbanked cannot even confirm who you are sending money to.

$2.8B+
Lost to address poisoning attacks (2023-2025)
1 in 5
New crypto users have sent to a wrong address
300%+
Increase in clipboard malware targeting crypto
0
Confirmation steps before irreversible transactions
Real Stories

The failure mode is technical. The damage is human.

These incidents span trading, treasury operations, remittance, creator commerce, and everyday payments. The pattern is consistent: the interface looked credible long enough for a user to trust the wrong thing.

Incident Archive
7 documented scenarios across 7 recurring failure patterns.
Auto-rotating

Condensed composite narratives informed by public incident reporting and threat research. Each story links to a related public reference.

Case 01Address poisoning

A poisoned history entry looked familiar

Human cost
$120K in ETH lost
I copied the address from my transaction history. It looked identical to the one I always use. But someone had poisoned my history with a lookalike address. $120,000 in ETH, gone in one click.
Persona
DeFi trader
What looked valid
A recent address that looked identical at a glance
Where trust failed
Transaction history became the trust signal
Source context
DeFi trader
Public account, 2024
Open public reference
01 / 07
The Challenge

Why This Keeps Happening

The Copy-Paste Trap

Sharing blockchain addresses means copying hex strings and hoping you got it right. One wrong character and your money is gone forever. There is no undo button, no customer support, no chargeback. Just loss.

No Name, No Face

When you send a bank transfer, you see the recipient name before confirming. In crypto, you stare at 0x7a2b... and just trust. No identity resolution, no confirmation, no human-readable feedback at all.

Invisible Thieves

Clipboard malware silently replaces wallet addresses. Address poisoning floods your history with lookalike addresses. Fake contracts impersonate real ones. The threats are invisible, and by the time you notice, it is already too late.

The Solution

Notareum Introduces the .nota File

Instead of copying raw hex strings and hoping for the best, Notareum introduces a Universal Transfer Interface: a portable, verifiable .nota file format that wraps any blockchain resource (wallet addresses, transaction hashes, NFTs, IPFS identifiers, contract addresses, metadata) into a single file you can share the same way you share photos, documents, or links.

Identity Resolution

Every .nota file carries human-readable metadata: who owns the address, what chain it belongs to, and its verification status. Like seeing "John Doe, Checking Account" instead of a 42-character hex string.

Cryptographic Verification

The file is signed and sealed with a cryptographic proof. If anyone tampers with the address or metadata, clipboard malware or otherwise, the verification fails before you ever hit send.

Universal Portability

Share .nota files over email, messaging apps, AirDrop, QR codes, or any file-sharing method. No more copy-paste. No more praying. Just attach a file and the recipient verifies it automatically.

1. Encrypt

Pack your payload into a standardized .nota structure with client-side encryption and deterministic serialization.

2. Sign

Attach cryptographic signatures proving origin. ZK or Merkle proofs generated against the source chain state root.

3. Distribute

Share the flat file anywhere. The recipient verifies the payload automatically — only authorized wallets can decrypt.

— .nota specification

The .nota File Format

A deterministic, JSON-based envelope for cross-chain resource sharing. Bundles payload, schema, and signatures into a single portable artifact.

Read Specification
The .nota Format

Cryptographically Secured Portability

The .nota format is a lightweight, verifiable container for blockchain state and metadata. It encapsulates the payload, structural schema, and the cryptographic proof necessary for zero-trust verification across any supported environment.

1. Payload Serialization

Raw data is normalized and serialized deterministically to ensure consistent hashing across all platforms.

2. Proof Generation

A ZK or Merkle proof is generated based on the source chain's state root.

3. Encapsulation

Data, schema, and proof are bundled into a single .nota binary or JSON artifact.

example.notaJSON Representation
{
  "header": {
    "version": "1.0.0",
    "network": "eip155:1",
    "timestamp": 1678886400
  },
  "payload": {
    "assetId": "0x7a2...f9c",
    "owner": "notareum.eth",
    "attributes": [{"trait_type": "Core"}]
  },
  "proof": {
    "type": "MerklePatricia",
    "root": "0x8b3...1a4",
    "path": ["0x...", "0x..."]
  },
  "signature": "0x32f9...7b1a"
}
Use Cases

One Format, Everywhere

From everyday transactions to enterprise operations, the .nota format brings verification and human readability to every interaction with a blockchain.

01
Send your address as a verifiable .nota file instead of a raw hex string. The recipient sees your name, chain, and verification status before sending.
Sharing Wallet Addresses
02
Create a payment request with amount, currency, and recipient verification baked in. Like a QR code, but portable, verifiable, and tamper-proof.
Payment Requests
03
Get a cryptographic receipt for every transaction. Shareable, verifiable, and permanently yours. Proof of payment that actually means something.
Transaction Receipts
04
Send payment instructions to family abroad with built-in verification. No more "did I use the right address?" No more hoping the money arrives.
Cross-Border Remittance
05
Accept crypto with a verified .nota payment page. Customers see they are paying the right merchant, not a phishing clone with a similar URL.
Merchant Checkout
06
Pay employees in crypto with verifiable .nota payslips showing employer identity, amount, chain, and timestamp. Auditable and portable.
Salary and Payroll
07
Share NFT ownership and provenance as .nota files. Provable, portable, and immune to marketplace shutdowns or metadata link rot.
NFT Certificates
08
Share decentralized storage links as verified .nota files. Cryptographic proof that the CID or transaction ID points to exactly what it claims.
IPFS and Arweave Sharing
09
Share transaction proposals with all signers as .nota files. Every signer verifies the same payload, the same destination, the same terms.
Multi-sig Coordination
10
Export transaction history as .nota files for tax reporting. Cryptographically provable cost basis that auditors can independently verify.
Tax Documentation
11
Distribute verifiable smart contract ABIs, deployment addresses, and configuration across teams without relying on centralized registries.
Developer Tooling
12
Immutable document custody and automated settlement for holding company transactions via .nota-wrapped cryptographic files.
Enterprise Legal
13
Cross-chain verifiable supply chain manifests protecting the integrity of logistics, certifications, and provenance data.
Supply Chain
14
Issue verifiable credentials wrapped in .nota format for instant identity verification on any supported network or application.
DID and Identity
15
Package proposals, vote receipts, and treasury reports as .nota files. Transparent governance artifacts that any member can verify.
DAO Governance
16
Submit on-chain insurance claims with .nota-wrapped evidence: transaction records, timestamps, and cryptographic proof of loss.
Insurance Claims
Ecosystem

Universal Compatibility

Ethereum
Native L1 Support
Polygon
Fast Verification
Arbitrum
Optimistic Proofs
Optimism
Native L2 Support
Avalanche
C-Chain Ready
Base
Native L2 Support
Solana
Beta Integration
Cosmos
IBC Compatible
DeFi
Identity
Oracles
Gaming
DAOs
Enterprise
Developer SDK

Integrate in Minutes

Native libraries available for the most popular Web3 development environments. Create, sign, and verify .nota files with a few lines of code.

  • Zero-knowledge proof generation
  • Native cross-chain serialization
  • Lightweight footprint (~12KB gzipped)
Read Documentation
import { NotaEngine } from '@notareum/sdk';
import { providers } from 'ethers';

// 1. Initialize the engine
const engine = new NotaEngine({
  rpcUrl: 'https://eth-mainnet.g.alchemy.com/v2/...'
});

// 2. Parse and verify a .nota file
async function verifyAsset(fileBuffer) {
  const result = await engine.verify(fileBuffer);

  if (result.isValid) {
    console.log('Asset Owner:', result.payload.owner);
  } else {
    throw new Error('Cryptographic proof failed');
  }
}
$NOTA Token

Protocol Economics

The $NOTA token aligns incentives across the network. It is used to stake verification nodes, pay for cross-chain proof generation, and govern protocol upgrades through on-chain proposals.

  • Node Staking

    Validators stake $NOTA to participate in the decentralized verification network.

  • Network Fees

    A micro-fee is burned for every complex cross-chain proof generated.

  • Governance

    Token holders propose and vote on protocol parameters and treasury allocation.

Token Distribution (Total Supply: 1B)

Ecosystem & Grants (40%)
Core Contributors (25%)
Treasury (20%)
Public Distribution (15%)
Get Started

Ready to build on Notareum?

Integrate the .nota format into your wallet, exchange, or dApp. Our SDKs provide simple wrappers around complex cryptographic proofs.