The anchoring module writes verifiable commitments of off-chain records to NVNM Chain. Counterparties can check a record's provenance against the chain without the underlying data leaving your systems.
Point your agent at NVNM Chain
Point your agent at NVNM Chain
Copy this prompt into Claude Code. Claude installs the NVNM Attest kit, sets up a testnet wallet with test nUSD from the faucet, anchors a record and verifies it. No coding needed.
Needs: Nothing. The kit funds its wallet from the faucet.
Anchor my first record on NVNM Chain testnet with the NVNM Attest kit.
1. Install the kit: git clone https://github.com/NVNM-Chain/nvnm-attest ~/.claude/skills/nvnm-attest (if it's already there, run git pull in it instead). Read its SKILL.md and follow it. It needs Python 3.10 or newer and web3. On a Mac, use Homebrew's Python 3.12 (brew install python@3.12), since the built-in python3 can't reach the NVNM RPC. Install what's missing, or tell me what I need to do.
2. Create a wallet called "first-record". The kit funds it with test nUSD from the faucet. Show me its address and balance.
3. Create a registry with a short name that says what I'm anchoring. Don't call it "test".
4. Anchor a short JSON note saying hello from NVNM with today's date.
5. Verify it and give me the transaction link on NVNM Scan: https://explorer.nvnm.testnet.nvnmchain.io
Rules: metadata is public, so never anchor secrets, personal data or client data. Never show my private key.
To anchor your own file, change step 4 before you send it. Metadata is public: never anchor secrets, personal data or client data.
Catch a forgery
Copy this prompt into Claude Code. Claude takes a record that's already on NVNM Chain, re-hashes the data and checks it against the chain. Then it changes one character and shows you the check fail.
Needs: Nothing. No wallet, no nUSD.
Verify a record on NVNM Chain testnet with the NVNM Attest kit, then show me what a forgery looks like.
1. Install the kit: git clone https://github.com/NVNM-Chain/nvnm-attest ~/.claude/skills/nvnm-attest (if it's already there, run git pull in it instead). Read its SKILL.md and follow it. It needs Python 3.10 or newer and web3. On a Mac, use Homebrew's Python 3.12 (brew install python@3.12), since the built-in python3 can't reach the NVNM RPC. Install what's missing, or tell me what I need to do.
2. Pick a record. If I've anchored anything with the kit, use one of its records and the original data the kit saved in its data/ folder. If not, find a recent onchain record whose public metadata includes the data itself. The kit's references/anchoring-module.md explains how to read records and AddRecord events.
3. Re-hash the original data and check it with scripts/verify.py. Show me the hash, the registry, the record id, when it was anchored, and the link to its transaction on NVNM Scan (https://explorer.nvnm.testnet.nvnmchain.io).
4. Change one character of the data, for example the last digit of a price, and run the check again. Show me that it fails.
5. Tell me in three short sentences what a match proves, what it doesn't prove, and why the original data has to be kept.
Rules: read only. Don't create a wallet or send any transactions. Never show a private key.
Checking a record is free and needs no wallet. A match proves the data is unchanged since it was anchored. It doesn't prove the data was right in the first place.
Anchor a lease with DGML
Copy this prompt into Claude Code. Claude installs DGML, the domain-native document format from dgml.io, anchors a sample lease that's already in DGML and proves it. Then it changes one character and shows you the proof fail.
Needs: Nothing. The kit funds its wallet from the faucet, and the sample lease is already in DGML.
Anchor a lease on NVNM Chain testnet with DGML, then show me what tampering looks like.
1. Install the kit: git clone https://github.com/NVNM-Chain/nvnm-attest ~/.claude/skills/nvnm-attest (if it's already there, run git pull in it instead). Read its SKILL.md and follow it. It needs Python 3.10 or newer and web3. On a Mac, use Homebrew's Python 3.12 (brew install python@3.12), since the built-in python3 can't reach the NVNM RPC. Install what's missing, or tell me what I need to do.
2. Install DGML, the open, domain-native document format from dgml.io: clone https://github.com/dgml-io/dgml and https://github.com/dgml-io/dgml-spec side by side (if they're already there, run git pull in them instead), then run uv sync --extra chain in dgml. Install uv if it's missing. Read dgml's docs/chaining/quickstart-chaining.md. Run dgml from its folder as uv run dgml. Copy the sample workspace dgml-spec/samples/1-NonTraded-NAV-REITs/dgml-workspace to a new folder and adopt it with uv run dgml workspace create <that folder> --organization acme-inc, then pass --workspace <that folder> to every dgml command. Its leases are already in DGML, so no model API key is needed.
3. dgml's built-in nvnm-testnet is an earlier network. Add the current testnet with dgml chain add --name nvnm --rpc-url https://rpc.nvnm.testnet.nvnmchain.io --chain-id 787223 --explorer https://explorer.nvnm.testnet.nvnmchain.io, and pass --chain nvnm to every wallet, registry, stake and prove command.
4. Create a wallet for dgml without exposing its key: a short script in dgml's environment makes a new testnet key, saves it straight to the OS keyring (service nvnm-wallet, account dgml-lease) and prints only its address. Never read, print or copy the key after that, and pass --keychain-account dgml-lease to every dgml command that signs. The kit funds it with test nUSD from the faucet. Show me its address and balance. Use the kit's scripts/faucet.py --address for this, since the key isn't in the kit.
5. Create a registry with dgml registry create. Names aren't unique, so name it after the lease, today's date and a random suffix, check with dgml registry list --name that no other registry has it, and pass that exact name as --registry to every later command. Don't call it "test".
6. Find the Arcadia Biotech lease with dgml docset list and dgml docset list-files: you need its file id and docset id. Anchor it with dgml stake file <file id> --docset <docset id>. Show me its Merkle root, what the root covers, and the transaction link on NVNM Scan: https://explorer.nvnm.testnet.nvnmchain.io
7. Prove it with dgml prove file --record-json <the record_path the stake printed>. Then change one character in the lease's .dgml.xml, prove it again the same way and show me that it fails. Put the character back and prove it once more.
Rules: only hashes go onchain, never the lease itself. Never show my private key.
The sample lease is fictional. To anchor your own documents, DGML first turns them into DGML, which needs a model API key: see the DGML guide. Only hashes go onchain.
Prove one clause
Copy this prompt into Claude Code. Claude finds the rent escalation clause in a sample DGML lease, anchors just that clause and proves it. That's how a fund's valuer can check one lease term behind its NAV without seeing the rest of the lease.
Needs: Nothing. The kit funds its wallet from the faucet, and the sample lease is already in DGML.
Anchor one clause of a lease on NVNM Chain testnet with DGML, and prove it without revealing the rest of the lease.
1. Install the kit: git clone https://github.com/NVNM-Chain/nvnm-attest ~/.claude/skills/nvnm-attest (if it's already there, run git pull in it instead). Read its SKILL.md and follow it. It needs Python 3.10 or newer and web3. On a Mac, use Homebrew's Python 3.12 (brew install python@3.12), since the built-in python3 can't reach the NVNM RPC. Install what's missing, or tell me what I need to do.
2. Install DGML, the open, domain-native document format from dgml.io: clone https://github.com/dgml-io/dgml and https://github.com/dgml-io/dgml-spec side by side (if they're already there, run git pull in them instead), then run uv sync --extra chain in dgml. Install uv if it's missing. Read dgml's docs/chaining/quickstart-chaining.md. Run dgml from its folder as uv run dgml. Copy the sample workspace dgml-spec/samples/1-NonTraded-NAV-REITs/dgml-workspace to a new folder and adopt it with uv run dgml workspace create <that folder> --organization acme-inc, then pass --workspace <that folder> to every dgml command. Its leases are already in DGML, so no model API key is needed.
3. dgml's built-in nvnm-testnet is an earlier network. Add the current testnet with dgml chain add --name nvnm --rpc-url https://rpc.nvnm.testnet.nvnmchain.io --chain-id 787223 --explorer https://explorer.nvnm.testnet.nvnmchain.io, and pass --chain nvnm to every wallet, registry, stake and prove command.
4. Create a wallet for dgml without exposing its key: a short script in dgml's environment makes a new testnet key, saves it straight to the OS keyring (service nvnm-wallet, account dgml-clause) and prints only its address. Never read, print or copy the key after that, and pass --keychain-account dgml-clause to every dgml command that signs. The kit funds it with test nUSD from the faucet. Show me its address and balance. Use the kit's scripts/faucet.py --address for this, since the key isn't in the kit.
5. Create a registry with dgml registry create. Names aren't unique, so name it after the lease, today's date and a random suffix, check with dgml registry list --name that no other registry has it, and pass that exact name as --registry to every later command. Don't call it "test".
6. Find the Arcadia Biotech lease with dgml docset list and dgml docset list-files: you need its file id and docset id. Find its rent escalation clause with dgml discover <file id> --docset <docset id> --search escalation. Show me the element, its XPath and the page it comes from. Anchor just that element with dgml stake node <file id> --docset <docset id> --xpath <its XPath>, and give me the transaction link on NVNM Scan: https://explorer.nvnm.testnet.nvnmchain.io
7. Prove it with dgml prove node --record-json <the record_path the stake printed>, and export its proof with dgml node export <file id> --docset <docset id> --xpath <its XPath>. Then tell me in three short sentences what a match proves, what someone needs to check it, and what they never see.
Rules: only hashes go onchain, never the lease itself. Never show my private key.
Only the clause's hash goes onchain, with the proof that ties it to the lease. Keep the workspace: without the clause itself, nobody can check it.
Run a data bot
Copy this prompt into Claude Code. Claude sets up a bot that attests Hyperliquid prices every minute, one transaction per price, and keeps it running while your computer is on. The bot gets its test nUSD from the faucet itself.
Needs: Nothing. The kit funds its wallet from the faucet.
Set up a bot that attests public data on NVNM Chain testnet with the NVNM Attest kit, and keep it running.
1. Install the kit: git clone https://github.com/NVNM-Chain/nvnm-attest ~/.claude/skills/nvnm-attest (if it's already there, run git pull in it instead). Read its SKILL.md and follow it. It needs Python 3.10 or newer and web3. On a Mac, use Homebrew's Python 3.12 (brew install python@3.12), since the built-in python3 can't reach the NVNM RPC. Install what's missing, or tell me what I need to do.
2. Data: Hyperliquid mid prices, using the kit's sources/hyperliquid_mids.py.
3. Create a wallet for this bot. The kit funds it with test nUSD from the faucet. Show me its address and balance.
4. Create a registry named after the data. Don't call it "test".
5. Do a dry run first. If the data looks right, start the bot in the background so it keeps running after this session ends.
6. Give me the link to its first transaction on NVNM Scan (https://explorer.nvnm.testnet.nvnmchain.io). Then tell me how to check the bot is running, how to stop it, and how to move it to a server if I want it running while my computer is off.
Rules: attest public data only. Metadata is public, so never attest secrets, personal data or client data. Never show my private key.
To attest other public data, describe it in step 2 before you send it. Metadata is public: never anchor secrets, personal data or client data.
Give your agent receipts
Copy this prompt into Claude Code. Claude adds a hook that anchors a fingerprint of every Claude Code session when it ends, so you can later prove a session's log hasn't changed since it ended. The session stays on your computer. Only its hash goes onchain.
Needs: Nothing. The kit funds its wallet from the faucet.
Set up Claude Code so every session I run leaves a receipt on NVNM Chain testnet, using the NVNM Attest kit.
1. Install the kit: git clone https://github.com/NVNM-Chain/nvnm-attest ~/.claude/skills/nvnm-attest (if it's already there, run git pull in it instead). Read its SKILL.md and follow it. It needs Python 3.10 or newer and web3. On a Mac, use Homebrew's Python 3.12 (brew install python@3.12), since the built-in python3 can't reach the NVNM RPC. Install what's missing, or tell me what I need to do.
2. Create a wallet called "claude-receipts". The kit funds it with test nUSD from the faucet. Show me its address and balance.
3. Create a registry called "claude-code-session-receipts".
4. Write a small hook script that runs when a Claude Code session ends. It skips the session if the project folder has a file named .no-receipts. Otherwise it copies the session transcript to ~/.nvnm-receipts/sessions/<session id>-<unix time>.jsonl (never over an existing copy), anchors the SHA-256 hash of that copy with the kit, and appends the session id, the copy's file name, the hash and the transaction link to ~/.nvnm-receipts/receipts.jsonl. Keep ~/.nvnm-receipts readable only by me: the folders 700 and every file in them 600.
5. Register the script as a SessionEnd hook in my user settings (~/.claude/settings.json). Show me the change before you save it. The hook must run in the background, never slow down closing a session, hold a lock while it anchors and writes receipts.jsonl so sessions that end at the same time take turns, and write errors to ~/.nvnm-receipts/errors.log instead of failing.
6. Test it once by hand on this session's transcript so far. Give me the link to the transaction on NVNM Scan (https://explorer.nvnm.testnet.nvnmchain.io) and verify the saved copy with scripts/verify.py. Then tell me how to verify any past session, how to skip a project, and how to turn the hook off.
Rules: only the hash goes onchain. Onchain metadata is public, so it holds nothing but {"src": "claude-code-session", "ts": <unix time>} and the kit's version: no prompts, code, file paths, project names or usernames. Never show my private key.Only the hash goes onchain. Keep the saved copies in ~/.nvnm-receipts: without the original, a receipt can't be checked. To leave a project's sessions out, add a .no-receipts file to it.
Ship a data source
Copy this prompt into Claude Code. Claude builds a new data source for the kit, tests it, and opens a pull request so anyone can run it. You step in once, to choose the data or pick one of Claude's ideas.
Needs: A GitHub account.
Build a new data source for the NVNM Attest kit and open a pull request so anyone can run it.
1. Install the kit: git clone https://github.com/NVNM-Chain/nvnm-attest ~/.claude/skills/nvnm-attest (if it's already there, run git pull in it instead). Read its SKILL.md and follow it. It needs Python 3.10 or newer and web3. On a Mac, use Homebrew's Python 3.12 (brew install python@3.12), since the built-in python3 can't reach the NVNM RPC. Install what's missing, or tell me what I need to do.
2. Ask me what public data to attest, or suggest three ideas. Check sources/ and the open pull requests on https://github.com/NVNM-Chain/nvnm-attest first so you don't duplicate one.
3. Copy sources/_template.py and write fetch(). Use a free public API, with a timeout on every request. If the API needs a key, read it from an environment variable, never from the file. Set DEFAULT_EVERY to how often the data actually changes. Set BATCH to 1 for a few points per run, or "all" for large snapshots. Set PUBLIC = True only if the data is public and its terms allow republishing it. Explain these choices in the file's docstring, with a link to the API's terms.
4. Dry run: scripts/attest_bot.py with --dry-run --max-runs 1. It still needs --wallet and --registry, but a dry run sends nothing, so any wallet name and registry 0 will do. Show me the output.
5. Create a wallet for the source. The kit funds it with test nUSD from the faucet. Show me its address and balance. Then do one live run (--max-runs 1, so the bot stops after it) in a new registry named after the data (don't call it "test") and give me the link on NVNM Scan (https://explorer.nvnm.testnet.nvnmchain.io).
6. Open a pull request with the gh CLI: fork the repo, add only the new source file, and describe what it attests, how often, and the dry-run output. If I'm not logged in to GitHub, tell me the one command to run.
Rules: public data only. No secrets, personal data or client data, and no sites that forbid scraping. Never show my private key.
Public data only, from sources whose terms allow it. Never put API keys in a source file.