casualsecurityinc/validate-address
skills/validate-address/SKILL.md
Validate Nano (XNO) addresses offline (format, checksum); no network.
development
Updated Apr 3, 2026
$ install --global
skillsauthnpx skillsauth add casualsecurityinc/xno-skills validate-addressInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 3, 2026, 10:29 PM7.2s1 file scanned
SKILL.md
- name:
- validate-address
- description:
- Validate Nano (XNO) addresses offline (format, checksum); no network.
Validate XNO Address
Validates XNO (Nano) cryptocurrency addresses offline. No network connection required - all validation is local.
Address Format
Nano account addresses follow this format:
nano_<60 chars> (65 total)
xrb_<60 chars> (64 total, legacy prefix)
Components
| Part | Description | Length |
|------|-------------|--------|
| Prefix | nano_ (current) or xrb_ (legacy) | 5 or 4 chars |
| Account | Base32 encoded public key + checksum | 60 chars |
| Checksum | Blake2b hash verification (last 8 chars of account) | 8 chars |
Valid Prefixes
nano_- Current standard format (recommended)xrb_- Legacy format (deprecated but still valid)
Character Set
Addresses use Nano’s Base32 alphabet:
13456789abcdefghijkmnopqrstuwxyz
CLI Validation
npx xno-skills validate <address>
Or via QR generation (also validates):
npx xno-skills qr <address>
Checksum Verification
The last 8 characters of a Nano address are a checksum:
- Take the 32-byte public key
- Compute Blake2b hash (5 bytes)
- Reverse the bytes
- Encode in Base32
This ensures any typo in the address will be detected.
Examples
Valid Addresses
nano_1pu7p5n3ghq1i1p4rhmek41f5add1uh34xpb94nkbxe8g4a6x1p69emk8y1d
nano_3phqgrqbso99xojkb1bijmfryo7dy1k38ep1o3k3yrhb7rqu1h1k47yu78gz
xrb_1pu7p5n3ghq1i1p4rhmek41f5add1uh34xpb94nkbxe8g4a6x1p69emk8y1d
Invalid Addresses
| Address | Reason |
|---------|--------|
| nano_abc | Too short |
| nano_12345... (wrong chars) | Contains 0 or uppercase |
| btc_1xrb... | Wrong prefix |
| nano_1xrb... (69 chars) | Wrong total length |
| nano_1xrb... (bad checksum) | Checksum mismatch |
Validation Steps
- Check prefix - Must be
nano_orxrb_ - Check length - Total 65 chars (
nano_) or 64 chars (xrb_) - Check characters - Valid Base32 alphabet only
- Verify checksum - Blake2b hash matches last 8 chars
Offline Validation
All validation is performed locally:
- No API calls
- No network requests
- No rate limits
- Works in air-gapped environments
Error Messages
| Error | Meaning |
|-------|---------|
| Invalid prefix | Address doesn't start with nano_ or xrb_ |
| Invalid length | Address is not 65/64 characters |
| Invalid Base32 character | Contains characters outside Nano’s Base32 alphabet |
| Invalid address padding bits | Address is not in canonical Nano Base32 form |
| Invalid checksum | Checksum doesn't match the public key |
When to Use
- Before sending XNO to verify recipient address
- When displaying addresses in UI
- During wallet import/recovery
- In scripts that process addresses
Related Skills
casualsecurityinc/nano
tools
VerifiedTrustedCommunity
Nano (XNO) cryptocurrency wallet operations, transaction analysis, and explorer lookups. Use for send/receive, balances, pending funds, address validation, unit conversion, tx/hash/account lookup, explorer links, and Nano block-lattice questions. Prefer xno-mcp first; use xno-skills CLI as fallback.
5SKILL.mdUpdated May 5, 2026
casualsecurityinc/nano-verify-message
testing
VerifiedTrustedCommunity
Verify an off-chain message signature (NOMS / ORIS-001 standard) against a Nano (XNO) address or public key. Use this skill whenever the user presents a signed message and wants to verify its authenticity, needs to confirm someone owns a Nano address, or asks 'is this signature valid?' — even if they just say 'check this proof' or 'did they really sign this?'
2SKILL.mdUpdated Apr 27, 2026
casualsecurityinc/nano-validate-address
development
VerifiedTrustedCommunity
Validate Nano (XNO) addresses offline (format, checksum) — no network required. Use this skill whenever the user provides a Nano address and wants to verify it's well-formed, before sending XNO to an untrusted address, or asks 'is this address real?' — even if they just paste a nano_ address and ask 'is this right?' Always validate before any XNO send operation.
2SKILL.mdUpdated Apr 27, 2026
casualsecurityinc/nano-sign-message
tools
VerifiedTrustedCommunity
Sign an off-chain message (plain text) using a Nano (XNO) custodial wallet managed by xno-mcp, following the NOMS / ORIS-001 standard. Use this skill whenever the user wants to prove ownership of a Nano address, authenticate themselves cryptographically, sign a statement with their XNO key, or create an off-chain proof — even if they just say 'prove I own this wallet' or 'sign this for me'.
2SKILL.mdUpdated Apr 27, 2026