NO BORDERS. NO GATEKEEPERS.
JUST LOVE + CRYPTOGRAPHY.
The world's first quantum-secure, blockchain-anchored marriage system with natural language AI. Just say "marry me to Alice" and SpoonOS handles everything—contracts, vows, NFT rings, and Neo N3 anchoring.
JUST SAY "I DO"
Forget complex CLI commands. With SpoonOS v4, just describe what you want in natural language. The AI agent uses semantic memory,disambiguation flows, and 200+ cryptographic synonyms to understand exactly what you mean—then handles contracts, vows, NFT rings, and Neo N3 anchoring automatically.
TALK TO ANUBIS
NATURAL LANGUAGE EXAMPLES FOR MARRIAGE
GETTING MARRIED
- • "Get married to Alice"
- • "I want to marry Bob Johnson"
- • "Create a marriage contract"
- • "Start a polygamy marriage with Alice, Bob, and Carol"
- • "Simple partnership with my partner"
NFT RINGS
- • "Mint our wedding rings"
- • "Create NFT rings for our marriage"
- • "Show me my wedding ring"
- • "Update our rings for our anniversary"
- • "Add new vows to our rings"
VOWS & RECORDS
- • "Record our vows on-chain"
- • "Add my vows: I promise to love..."
- • "Show our marriage certificate"
- • "Verify our marriage on blockchain"
- • "When did we get married?"
DIVORCE
- • "File for divorce"
- • "I want a divorce from Alice"
- • "End our marriage"
- • "Dissolve the marriage contract"
- • "What happens to our rings?"
VERIFICATION
- • "Is this marriage valid?"
- • "Check marriage status"
- • "Verify certificate on Dora"
- • "Show marriage transaction"
- • "Prove we're married"
HELP & INFO
- • "How much does marriage cost?"
- • "What templates are available?"
- • "Explain polygamy support"
- • "How are vows protected?"
- • "What is a NEP-11 ring?"
Query Your Marriage History
Ask naturally: "When did we get married?" or "Show our anniversary date" - no transaction hashes needed.
Clarifying Questions
When intent is unclear, Anubis asks smart follow-up questions instead of guessing wrong.
Proactive Suggestions
Anubis suggests best practices: backup your rings, verify partner identity, store certificate securely.
MARRIAGE FEE SCHEDULE
All fees are collected automatically via the NotaryOracle smart contract on Neo N3. Fees flow directly to the contract owner wallet.
| Operation | Natural Language | Cost (GAS) |
|---|---|---|
| marriage_init | "Create marriage contract" | FREE |
| marriage_sign | "Sign the marriage" | FREE |
| marriage_create | "Get married to Alice" | 0.45 GAS |
| rings_mint | "Mint our wedding rings" | 0.75 GAS |
| rings_vows | "Record our vows on-chain" | 0.10 GAS |
| divorce | "File for divorce" | 0.20 GAS |
TERMINAL
anubis-chat
TELEGRAM
@AnubisNotaryBot
DISCORD
Anubis#1234
WEB API
REST + WebSocket
SYSTEM OVERVIEW
| Feature | Description |
|---|---|
| Global | Anyone, anywhere - no jurisdiction restrictions |
| Quantum-Secure | ML-DSA-87 signatures (NIST Level 5 / FIPS 204) |
| NFT Rings | NEP-11 wedding ring tokens on Neo N3 |
| NeoFS Storage | Decentralized marriage certificate storage |
| Dora Verification | Public proof at dora.coz.io |
| Inclusive | Monogamy, polygamy, partnerships - all supported |
| Instant | Neo N3 dBFT = immediate finality (~15 seconds) |
| Cheap | ~0.001 GAS per marriage |
USE CASES
Traditional
Two-party monogamous unions
Multi-Party
Polygamous arrangements (up to 10 parties)
Partnerships
Minimal paperwork unions
Vow Renewals
Anniversary updates to ring metadata
Cross-Border
Global couples, no jurisdiction hassles
CORE FEATURES
POST-QUANTUM SECURE
ML-DSA-87 signatures (FIPS 204) ensure your marriage contract remains valid even against quantum computers. NIST Level 5 security with 512-bit SHA-512 hashes for all fingerprints and vows.
NEP-11 NFT RINGS
Each party receives a unique NFT wedding ring (NEP-11 token) with partner names, vows, and certificate hashes. Rings can be updated on anniversaries and are automatically burned upon divorce.
POLYGAMY SUPPORT
Supports monogamy (2 parties), polygamy (up to 10 parties), and simple partnership templates. Each party signs individually with separate vow slots and proportional asset splits.
PRIVACY-PRESERVING
Wedding vows are SHA-512 hashed before storage. Only hashes are stored on-chain, protecting your personal expressions while providing cryptographic proof of commitment.
AUTO RING BURNING
Upon divorce, all NFT wedding rings are automatically burned on-chain. Divorce reason and timestamp are recorded immutably with marriage status changed to DIVORCED.
DORA VERIFICATION
Public proof via Dora explorer (dora.coz.io) with instant Neo N3 dBFT finality. View transaction details, contract interactions, and event logs (MarriageRegistered, RingMinted).
MARRIAGE TEMPLATES
MONOGAMY
Standard two-party marriage contract
- • Exactly 2 parties
- • Mutual exclusivity clause
- • Traditional vow structure
- • 50/50 asset split on divorce
- • Mutual consent required
POLYGAMY
Multi-party union contract
- • 2-10 parties supported
- • Individual consent from each
- • Separate vow slots per party
- • Proportional asset split
- • Majority threshold divorce
SIMPLE
Minimal partnership contract
- • 2 parties
- • No jurisdictional boilerplate
- • Basic union acknowledgment
- • Minimal terms
- • Mutual consent divorce
COMPLETE CLI WORKFLOW
STEP 1: INITIALIZE MARRIAGE DOCUMENT
Create a new marriage document with your chosen template:
$ anubis-notary marriage init \
--parties "Alice Smith,Bob Johnson" \
--template monogamy \
--jurisdiction "GLOBAL" \
-o marriage.json
| Option | Description |
|---|---|
| --parties <NAMES> | Comma-separated party names |
| --template <TYPE> | monogamy, polygamy, or simple |
| --jurisdiction <CODE> | Use GLOBAL for borderless, or specific like US-CA |
| -o, --out <PATH> | Output file path |
STEP 2: SIGN AS EACH PARTY
Each party signs the document with their vows (SHA-512 hashed for privacy):
# Alice signs
$ anubis-notary marriage sign marriage.json \
--party 0 \
--vows "I, Alice, take you, Bob, to be my partner..." \
-o marriage_alice.json
# Bob signs
$ anubis-notary marriage sign marriage_alice.json \
--party 1 \
--vows "I, Bob, take you, Alice, to be my partner..." \
-o marriage_signed.json
STEP 3: VERIFY SIGNATURES
Verify all parties have signed:
$ anubis-notary marriage verify marriage_signed.json
Marriage document: marriage_signed.json
Parties: 2
Signatures: 2/2
Status: FULLY SIGNED - Ready for on-chain creation
STEP 4: CREATE ON-CHAIN MARRIAGE
Register the marriage on Neo N3:
$ anubis-notary marriage create marriage_signed.json \
--network testnet \
--mint-rings \
--store-neofs \
--wait
| Option | Description |
|---|---|
| --network <NET> | mainnet or testnet |
| --mint-rings | Automatically mint NFT rings for all parties |
| --store-neofs | Store certificate in NeoFS (decentralized storage) |
| --wait | Wait for transaction confirmation |
================================================================
CONGRATULATIONS! YOU ARE NOW MARRIED!
================================================================
Marriage ID: 42
Transaction: 0xabc123...
Block: 12345678
NFT Wedding Rings:
Alice Smith: Ring #84
Bob Johnson: Ring #85
Verify on Dora Explorer:
https://dora.coz.io/transaction/neo3/testnet/0xabc123...
Certificate stored in NeoFS: bafybeig...
STEP 5: DIVORCE (IF NEEDED)
Execute divorce and burn all NFT rings:
$ anubis-notary marriage divorce \
--marriage-id 42 \
--reason "Mutual consent" \
--network testnet \
--wait
[✓] Marriage status: DIVORCED
[✓] Rings burned: #84, #85
[✓] Divorce reason recorded on-chain
NFT WEDDING RINGS (NEP-11)
RING PROPERTIES
Each ring NFT (NEP-11 token) contains the following metadata:
| Field | Description |
|---|---|
| tokenId | Unique token identifier |
| marriageId | On-chain marriage ID |
| ownerFingerprint | ML-DSA-87 public key SHA-512 |
| ownerNeoAddress | Owner's Neo N3 address |
| partnerNameHash | SHA-512(partner_name) |
| vowsHash | SHA-512(wedding_vows) |
| certificateHash | SHA-512(marriage_certificate) |
| createdAt | Unix timestamp of minting |
| updatedAt | Last vow update timestamp |
RING COMMANDS
Show Ring Details
$ anubis-notary marriage rings show 84 \
--network testnet
Check Ring Existence
$ anubis-notary marriage rings exists 84 \
--network testnet
Get Total Supply
$ anubis-notary marriage rings supply \
--network testnet
Update Vows (Anniversary)
$ anubis-notary marriage rings update-vows \
--token-id 84 \
--vows "Our renewed vows..." \
--network testnet
PRIVACY FEATURES
WHAT'S ON-CHAIN (PUBLIC)
- • Marriage ID (incrementing counter)
- • Party fingerprints (SHA-512 of ML-DSA-87 public keys)
- • Hashed names (SHA-512)
- • Hashed vows (SHA-512)
- • Marriage certificate hash (SHA-512)
- • Timestamps
- • Status (active/divorced)
WHAT'S NOT ON-CHAIN
- • Actual names (only SHA-512 hashes)
- • Actual vows text (only SHA-512 hashes)
- • Full marriage document (only hash)
- • Personal details beyond what parties choose to include
VERIFICATION WITHOUT DISCLOSURE
Anyone can verify:
- ✓ A marriage exists (by ID)
- ✓ Parties signed specific vows (by comparing hashes)
- ✓ Marriage is active or divorced
- ✓ Ring ownership
Without revealing:
- ✗ Who the parties are (unless they disclose fingerprints)
- ✗ What vows were exchanged (unless parties share text)
- ✗ Marriage document details (unless shared)
SECURITY FEATURES
QUANTUM RESISTANCE
- • ML-DSA-87 (FIPS 204)
- • NIST Level 5 security
- • SHA-512 for all hashes
- • Future-proof signatures
KEY MANAGEMENT
- • Keys stored in ~/.anubis/key.sealed
- • Key rotation supported
- • Secure backup recommended
- • ML-KEM-1024 encryption
LEGAL STATUS
- • Cryptographic proof of union
- • May require government registration
- • Utah allows virtual marriages
- • Full Faith and Credit Clause
DORA EXPLORER VERIFICATION
All marriages can be verified publicly on Dora explorer. The explorer shows transaction details, contract interactions, block confirmations, and event logs (MarriageRegistered, RingMinted, etc.).
ERROR HANDLING
Not All Parties Signed
Error: Cannot create marriage - party 1 has not signed
Resolution: Have all parties sign before creating on-chain.
Invalid Party Index
Error: Party index 2 out of range (0-1)
Resolution: Use 0-based indexing for party selection.
Marriage Already Divorced
Error: Marriage 42 is already divorced
Resolution: Cannot perform operations on divorced marriages.
Ring Already Burned
Error: Token 84 does not exist
Resolution: Ring was already burned (likely from divorce).
MARRIAGE REGISTRY STATISTICS
NETWORK DISTRIBUTION
MARRIAGE TYPE RATIO
RECENT ACTIVITY (LAST 30 DAYS)
BATCH CERTIFICATE GENERATOR
Generate marriage certificates for polygamous unions with 3-10 parties. Each certificate includes all party names, shared vows, and comprehensive blockchain verification with the same cryptographic security as standard certificates.
BATCH CERTIFICATE GENERATOR
Generate polygamous marriage certificates for 3-10 parties with shared vows and comprehensive blockchain verification.
These vows will be shared by all parties and displayed on the certificate.
* Required fields. At least 3 party names must be filled. The certificate will be downloaded as a PDF file.
MARRIAGE SEARCH
Search for any marriage registered on Neo N3 by marriage ID or transaction hash. View marriage details, status, and verify directly on Dora Explorer.
MARRIAGE SEARCH
Search by:
- Marriage ID (e.g., 42)
- Transaction hash (e.g., 0xabc123...)
READY TO GET MARRIED?
Install the Anubis Notary CLI and create your quantum-secure, blockchain-anchored marriage today.