A poisoned history entry looked familiar
“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.”
An open protocol for sharing blockchain resources safely using the verifiable .nota file format.
{
"type": "address",
"chain": "ethereum",
"resource": {
"id": "0x7a2b...9f3e",
"name": "Treasury",
"alias": "treasury.nota"
},
"verification": {
"status": "verified",
"level": "institutional"
},
"signature": "ecdsa:secp256k1"
}A new file format that wraps any blockchain resource into a portable, verifiable package you can share like a photo or document.
Standard data is encapsulated into the verifiable .nota format via local SDK.
Nodes reach consensus on signature validity before state transition.
Receiving dApps natively decode and trust the assertion without middleman logic.
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.
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.
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.
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.
Condensed composite narratives informed by public incident reporting and threat research. Each story links to a related public reference.
“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.”
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.
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.
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.
.nota FileInstead 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.
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.
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.
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.
Pack your payload into a standardized .nota structure with client-side encryption and deterministic serialization.
Attach cryptographic signatures proving origin. ZK or Merkle proofs generated against the source chain state root.
Share the flat file anywhere. The recipient verifies the payload automatically — only authorized wallets can decrypt.
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 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.
Raw data is normalized and serialized deterministically to ensure consistent hashing across all platforms.
A ZK or Merkle proof is generated based on the source chain's state root.
Data, schema, and proof are bundled into a single .nota binary or JSON artifact.
{
"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"
}From everyday transactions to enterprise operations, the .nota format brings verification and human readability to every interaction with a blockchain.
Native libraries available for the most popular Web3 development environments. Create, sign, and verify .nota files with a few lines of code.
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');
}
}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.
Validators stake $NOTA to participate in the decentralized verification network.
A micro-fee is burned for every complex cross-chain proof generated.
Token holders propose and vote on protocol parameters and treasury allocation.
Integrate the .nota format into your wallet, exchange, or dApp. Our SDKs provide simple wrappers around complex cryptographic proofs.