Paper contracts get lost. Government registries can be corrupted. Cloud storage companies close. But a Handshake NFT lives forever, belongs entirely to you, and can be verified by any court in the world without calling a notary. Today, we're going to learn — step by step — how marriage, commitment, and the major milestones of a human life can be anchored on the Handshake blockchain. Class is in session.
Why Your Marriage Certificate Deserves Better Than a Filing Cabinet
Let's start with a simple question: where is your marriage certificate right now?
If you're like most people, it's in a drawer somewhere. Or a scan buried in email. Or a certified copy filed with a municipality that uses 1990s database software. You needed it once — when you opened a joint bank account, or applied for a visa, or changed your name — and you proved it by handing a stranger a piece of paper and hoping they believed it was real.
This is the friction at the centre of all life contracts. Legal relationships between people are enormously important — and enormously fragile in how they're stored, proven, and transferred.
Marriage. Prenuptial agreements. Property co-ownership. Wills. Inheritance rights. Custody arrangements. Cohabitation contracts. These are the documents that govern how two people build a life together. They should be permanent. They should be tamper-proof. They should be instantly verifiable without phoning a government department. They should belong to the people who signed them — not to a registrar, not to a courthouse, and not to a cloud provider whose terms of service can change overnight.
Handshake NFTs make all of this possible today.
Lesson 1: What a Handshake NFT Actually Is
Before we build a wedding contract, we need to understand the tool. Let's be precise.
A Handshake NFT is a name — a domain name — that lives on the Handshake blockchain as a UTXO: an Unspent Transaction Output, the same model Bitcoin uses to record ownership of coins. The key insight is this: on Handshake, you don't rent a name. You own it.
On ICANN — the traditional internet naming authority — every domain is a lease. You pay GoDaddy or Namecheap every year, and if you miss a payment, your domain disappears. The registrar can suspend it. A government can seize it. ICANN can revoke the TLD entirely. You are a tenant in someone else's namespace.
On Handshake, a TLD auction is won with HNS coins. Once you win, the name is recorded in your wallet as a covenant — a permanent on-chain commitment. No registrar above you. No annual renewal. No revocation mechanism. The name exists as long as the Handshake blockchain exists — and that blockchain, like Bitcoin, is secured by proof-of-work with no central authority to shut it down.
Second-level domains (SLDs) beneath a TLD follow the same logic. If I own .marriage on Handshake, then hiro-and-sakura.marriage is a name I can issue — and whoever I issue it to holds it in their wallet, permanently, as cryptographic property.
This is the foundation. Everything we build on top of it — wedding contracts, life milestones, lifestyle NFTs — rests on this single property: a Handshake name cannot be taken away from its owner without their private key.
Lesson 2: The Architecture of a Wedding Contract on HNS
Now let's get practical. How does a wedding contract actually work on Handshake? There are three layers, and each one does something the others can't.
Layer 1 — The Name: The Permanent Address
Every wedding contract starts with a Handshake name. This is the couple's permanent, sovereign address on the decentralised internet. The naming convention should be human-readable and unambiguous:
kenji-and-yuki.marriage— a couple's shared identity domaincontract-2026.kenji-and-yuki.marriage— the specific marital agreement, versionedprenup.kenji-and-yuki.marriage— prenuptial agreement anchoranniversary.kenji-and-yuki.marriage— a lifecycle milestone namespace
The TLD owner (.marriage) issues these SLDs as NFTs. Each SLD is minted as a distinct UTXO on the Handshake chain and delivered to the couple's wallets — one to each party, or co-owned through a multi-signature configuration.
The name itself carries no document yet. It is the address — the permanent pointer. What it points to is layer two.
Layer 2 — The Document: IPFS + Arweave
The actual wedding contract — the text of the agreement, the signatures, the witnesses, the date — is a document. In the HNS wedding contract model, that document lives on two permanent storage layers simultaneously:
IPFS (InterPlanetary File System) gives the document a content address — a cryptographic hash that changes if even one character of the document changes. If someone tampers with the contract after the fact, the IPFS hash no longer matches. The tamper is mathematically provable.
Arweave provides permanent archival storage. Unlike IPFS (where data can be unpinned if no node holds it), Arweave uses an endowment model — you pay once, and the data is stored forever by the Arweave network. A wedding contract uploaded to Arweave in 2026 will still be there in 2126.
The IPFS content identifier (CID) and the Arweave transaction ID are both published in a DNS TXT record on the couple's Handshake domain. Anyone with an HNS resolver can look up contract-2026.kenji-and-yuki.marriage, read the TXT record, retrieve the document from IPFS or Arweave, and verify that the hash matches — with no intermediary involved.
Layer 3 — The Proof: Digital Signatures
A document without signatures is just a draft. The wedding contract model requires cryptographic signatures from both parties — and optionally from witnesses, a religious authority, or a civil registrar.
Each party signs the IPFS CID of the document using their Handshake wallet's private key. The resulting signatures are also published in the TXT record. The verification process is fully open:
1. Resolve contract-2026.kenji-and-yuki.marriage via HNS
2. Read TXT record: ipfs_cid, arweave_txid, signature_kenji, signature_yuki
3. Fetch document from IPFS using ipfs_cid
4. Verify: SHA-256(document) == ipfs_cid ✓
5. Verify: secp256k1.verify(ipfs_cid, signature_kenji, kenji_pubkey) ✓
6. Verify: secp256k1.verify(ipfs_cid, signature_yuki, yuki_pubkey) ✓
7. Conclusion: This exact document was signed by both parties ✓The full chain of proof — from the name, to the document, to the signatures — is public, permanent, and requires no trusted authority to verify. The blockchain is the notary.
Lesson 3: The Lifestyle TLD — Your Life's Namespace
A wedding contract is one document. But a marriage is a life. The Handshake model allows couples — and individuals — to build an entire namespace around their identity: a sovereign, permanent record of the milestones that define who they are and what they've built together.
Consider a couple that owns kenji-and-yuki.marriage. Over time, they build out a full lifestyle namespace beneath it:
contract-2026.kenji-and-yuki.marriage— the original marriage contracthome.kenji-and-yuki.marriage— their shared property, linked to a real estate NFT on ROSSOBAY/will.kenji-and-yuki.marriage— their joint testament, signed and hashedtrust.kenji-and-yuki.marriage— a family trust agreementchild-1.kenji-and-yuki.marriage— the birth record and naming covenant for their first childbusiness.kenji-and-yuki.marriage— their co-founded company's founding agreementvow-renewal-2036.kenji-and-yuki.marriage— a tenth anniversary ceremony, on-chain
This is what we mean by a Lifestyle TLD. The family's Handshake namespace is not just a website address — it is a sovereign, permanent, cryptographically verifiable record of a shared life. It is their digital estate. It can be passed to heirs. It can be used as evidence in court. It can be read by any application, anywhere in the world, that supports HNS resolution — without asking anyone's permission.
Lesson 4: The Prenuptial Agreement — Contracts That Can't Be Disputed
Of all the life contracts a couple may sign, the prenuptial agreement is the one most likely to end up in a courtroom. And yet it is the one that is most often contested on grounds of authenticity, coercion, or alteration.
"I never signed that." "That version was changed after the fact." "There's no proof I agreed to that clause."
On Handshake, these disputes become technically impossible to sustain.
A prenuptial agreement minted as a Handshake NFT has the following provable properties:
Immutability. The IPFS content address of the document is mathematically tied to its exact content. If even one word changes, the hash changes — and the change is detectable by anyone. A lawyer claiming the document was altered after signing needs to explain why the hash still matches the signatures.
Timestamp. The Handshake blockchain records the block in which the TXT record was written. This block has a timestamp — and because the blockchain is a public, distributed ledger, that timestamp cannot be backdated. The document existed at that time, in that exact form, because the chain says so.
Mutual consent. Both parties' signatures appear in the TXT record. Both signatures were produced by their respective private keys — keys that, by definition, only they hold. The cryptographic proof of consent is complete and public.
Witness records. Additional signature fields can include a third-party witness, a notary public, or a religious authority. Their signatures are added to the same TXT record, each independently verifiable.
A Handshake prenup does not replace the legal system. It anchors it. The document on-chain can be presented in any court as evidence of the original agreement. It is proof that is stronger than paper, stronger than email, and stronger than any witness's memory.
Lesson 5: Cross-Border Marriages and the Problem Handshake Solves
Here is a scenario that is more common than most people realise.
Two people from different countries marry. Their marriage is valid in both jurisdictions. But ten years later, when they need to prove that marriage — for a visa, a pension, an inheritance — the country they're in doesn't recognise the certificate from the country they married in. The relevant embassy is slow to respond. The original civil registry was partially destroyed in a flood. The translated document requires apostille certification from a jurisdiction that no longer has a diplomatic relationship with the requesting country.
This is not a hypothetical. It is the lived reality of millions of cross-border families every year.
A Handshake wedding contract has no jurisdiction. It is on a global, decentralised blockchain. Any HNS resolver in the world can verify it — whether the couple is in Tokyo, Singapore, São Paulo, or Oslo. The document, the signatures, and the timestamp are available to any application, any court, and any government that chooses to accept on-chain cryptographic evidence — and increasingly, they do.
The legal evolution is already underway. Courts in Germany, the UAE, and the United States have begun accepting blockchain-anchored evidence in civil proceedings. The question is not whether this becomes the standard. The question is which couples will be early enough to benefit.
Lesson 6: Lifestyle NFTs Beyond Marriage
The wedding contract is the most emotionally resonant use case — but it is far from the only one. A Handshake lifestyle namespace can anchor any life milestone that matters.
Birth and Naming Covenants
A child's name, date of birth, and parents' identity can be recorded as a Handshake NFT at birth. The domain hana-born-2027.family.marriage is a permanent record of a person's existence — one that neither a government database failure nor a hospital record system migration can erase. The child inherits the private key when they come of age.
Wills and Inheritance
A will anchored on Handshake cannot be contested on grounds that it was altered after the testator's death. The document hash and the testator's cryptographic signature are permanent and public. The domain can be registered as a multi-sig: the will is executed when a defined threshold of signatories (executor, witnesses, notary) countersign the execution instruction.
Business Partnerships
Two founders building a company together can anchor their shareholder agreement, co-founder equity split, and vesting schedule as Handshake NFTs on the day they sign. Disputes about who owned what percentage at which date become technically impossible to fabricate — the chain records the agreement, the hash, and the signatures at block height, with a timestamp no party can alter.
Cohabitation Contracts
Couples who choose not to marry but build a shared life together — shared property, shared finances, shared children — have historically had the weakest legal footing of any family structure. A cohabitation contract on Handshake gives those relationships the same cryptographic permanence as any other on-chain agreement. The absence of a marriage certificate is not a weakness when the cohabitation agreement is on the blockchain.
Lesson 7: How to Actually Build This — The Technical Path
Let's make this concrete. Here is the step-by-step path to creating a Handshake wedding contract, from zero to verified.
Step 1 — Win or acquire a Handshake TLD. Use Bob Wallet to participate in a Handshake name auction. TLDs like .marriage, .family, .vow, .covenant, .union are all available for auction. Winning a TLD gives you the root from which to issue all couple-specific SLDs. If you don't want to run a TLD yourself, watch for registrars and protocols building in this space — the infrastructure is growing.
Step 2 — Draft and finalise the contract document. The actual agreement text — prenup clauses, property arrangements, inheritance instructions, whatever the couple agrees to — is prepared as a PDF or plain-text document. Both parties review and agree to the final version. Nothing goes on-chain until both parties sign off on the document content.
Step 3 — Upload to IPFS and Arweave. The finalised document is uploaded to IPFS. The resulting CID is the document's permanent fingerprint. Upload to Arweave for permanent archival. Record both the IPFS CID and the Arweave transaction ID.
Step 4 — Sign the CID with each party's private key. Each party signs the IPFS CID using their Handshake wallet's private key. This produces two signature strings — one per party. Add witness signatures if desired.
Step 5 — Register the SLD and write the TXT record. Under the couple's TLD, register contract-2026.kenji-and-yuki.marriage as a new SLD. Set the DNS TXT record with the IPFS CID, Arweave TXID, and both signatures.
Step 6 — Verify with an HNS resolver. Use the SkyInclude Browser — the Chromium-based browser with a built-in HNS light node — to resolve the domain and confirm that the TXT record is correct and the signatures verify cleanly. The contract is now live, permanent, and publicly verifiable.
Step 7 — Store the private keys safely. Both parties store their private keys in hardware wallets. These keys are the only path to updating the TXT record in the future. Treat them with the same care as a physical title deed.
Lesson 8: What About the Law?
A frequent question from students: "Is a Handshake wedding contract legally binding?"
This is exactly the right question, and the answer is nuanced — which is why it deserves a full lesson of its own.
A Handshake contract is not, by itself, a substitute for a civil registration in most jurisdictions. In Japan, the EU, the US, and most countries, a legal marriage requires registration with a civil authority. The Handshake contract does not replace that registration.
What it does is something arguably more valuable: it creates an incontestable evidence layer on top of whatever civil record exists. Think of it as the difference between having a receipt and having a receipt whose authenticity can be verified by anyone in the world, instantly, without asking the shop that issued it.
The legal evolution is moving in the direction of blockchain evidence. Several jurisdictions already accept blockchain timestamps and hash proofs in civil proceedings. The Arizona Blockchain Act, the EU's eIDAS 2.0 framework, and the UAE's blockchain strategy all move in this direction. A couple who registers their agreement on Handshake today is building an evidence layer that will only become more legally recognised over time — not less.
For prenuptial agreements specifically, where the document's authenticity is precisely what gets contested in divorce proceedings, an on-chain anchor is not a luxury. It is the strongest possible foundation for enforceability.
The Bigger Picture: Decentralised Identity for the Whole Life
Zoom out for a moment and consider what we are really building.
A Handshake wallet is more than a cryptocurrency wallet. It is a decentralised identity system. The names in your wallet are your on-chain identity — sovereign, permanent, and portable across every application that supports HNS resolution.
Your vehicle identity on .city — as in the BlockCity Singapore model — is one layer. Your financial identity on a Handshake banking namespace is another. Your property on ROSSOBAY/ is a third. And your family — your marriage, your children, your will, your life's agreements — on a personal lifestyle TLD is the fourth.
Together, these namespaces form a complete decentralised identity: one that spans your legal relationships, your assets, your civic participation, and your financial life — all anchored to keys you hold, on a chain nobody controls.
This is not a distant vision. Every piece of the infrastructure exists today. Handshake auctions are live. IPFS and Arweave are live. Bob Wallet runs on any computer. The SkyInclude Browser resolves HNS names natively. The only thing missing is the cultural shift — the recognition that the most important documents of a human life deserve a home as permanent as the relationships they record.
Frequently Asked Questions
Can I use a Handshake NFT as a legal marriage certificate?
In most jurisdictions, a civil marriage requires registration with a government authority — a Handshake contract does not replace that step. What it does is create an immutable, cryptographically signed evidence layer for the agreement: the document, the date, and the signatures of both parties are permanently on-chain and verifiable by any court. As blockchain evidence standards mature globally, this layer will become increasingly legally significant.
What happens to our Handshake domain if we separate?
The domain is owned by whoever holds the private key — or, in a multi-sig configuration, requires a threshold of keyholders to update. The TXT records (the contract, the signatures) remain permanently on-chain and cannot be deleted by either party unilaterally. This is actually a feature, not a bug: in a separation or divorce proceeding, the original agreement is incontestably preserved exactly as it was signed.
What TLDs are available for wedding and lifestyle contracts on Handshake?
Any TLD that hasn't been auctioned yet is available to win. Names like .marriage, .family, .union, .covenant, .vow, .wedlock, and .lifelong are all potential roots for a lifestyle namespace protocol. Check current availability via Bob Wallet or the Handshake explorer at namebase.io or shakestats.com.
How does my wedding contract survive if IPFS goes offline?
The Arweave backup is precisely for this reason. Arweave's endowment model funds permanent storage from a one-time upload payment. Even if IPFS as a network were to degrade, the Arweave copy persists. The Handshake TXT record contains both addresses — if one source is unavailable, the other retrieves the document. The document's IPFS content hash in the TXT record still serves as the tamper-proof fingerprint regardless of where the document is retrieved from.
How does my child inherit the family Handshake namespace?
A Handshake name is a UTXO in a wallet — it can be transferred like any blockchain asset. The family lifestyle namespace can be passed to heirs either by transferring the private key directly or by writing a smart covenant that releases the name to a specified address when countersigned by a threshold of witnesses. The inheritance mechanism itself can be anchored as a TXT record on the family domain — making the estate plan as permanent as everything else beneath it.
The Bottom Line
The documents that matter most in a human life — the contracts that define family, property, commitment, and legacy — have always been fragile. Paper burns. Databases fail. Registrars get compromised. Governments change. And the people who depend on those documents pay the price in courtrooms, at border crossings, in probate hearings, and in family disputes that should never have been possible.
Handshake changes the foundation. A wedding contract on HNS is not a digital copy of a paper document. It is a new kind of record — one that exists in no single location, belongs to no single authority, and can be verified by anyone in the world with a standard cryptographic tool. It is permanent in the same way Bitcoin is permanent: secured by proof-of-work, distributed across thousands of nodes, and requiring a private key — one that you hold — to alter.
The lifestyle namespace you build on Handshake is your family's digital estate. Build it carefully. Update it faithfully. And pass it down — the way every generation passes down the things that matter.
Your marriage deserves better than a filing cabinet. The technology to give it that is here, it is live, and it costs less than a notary appointment.
Architecture and original research by NIHON — Handshake Infrastructure & Web3 Identity, June 2026. To resolve Handshake domains natively, download the SkyInclude Browser. For more on building with HNS, explore LearnHNS.