Real estate closings without a receipt rail are unrecoverable when something goes wrong. DeedLock fixes that.
Every closing state — disclosure, offer, acceptance, escrow, title, notary, deed signed, recording, wire — bound to a dual-signed, post-quantum-ready receipt that title underwriters, county recorders, lenders, and courts verify offline. Eleven cents of receipt cost stops the $269K wire-fraud loss, compresses audit cycles, and earns E&O premium credit. Live in production today.
The ROI on a single closing
A typical residential closing runs roughly 11 attested state transitions. At $0.0096 per event that is 11 cents of receipt cost per closing. The numbers it moves on the other side are these.
wire_disbursed blocks rerouted-instruction attacks at protocol level.deed_attest at each state transition. No data model changes. No customer-facing UI changes. Same MISMO / PRIA wire format.A platform doing 10,000 closings a month spends roughly $1,100 / month on Standard-tier receipts to make every closing post-quantum-attested. The wire-fraud math pays for that on the first blocked attempt of the year.
DeedLock is the receipt rail under any closing platform. Propy, RON vendors, title underwriters, county recording aggregators, and SoftPro / Qualia / ResWare-style settlement systems all integrate the same way. We do not compete with the closing platform — we make the closing platform's audit trail cryptographically defensible.
Receipt rail, not another platform
Closing platforms own workflow, parties, documents, and customer experience. DeedLock owns one thing: the cryptographic receipt for every state transition. That separation is the point. A receipt rail is a horizontal layer; it sits under everything and competes with nothing.
Every closing platform writes the same kind of receipt. Every title underwriter, county recorder, and lender verifies the same way. The receipts are platform-neutral — that is what makes them defensible to a court.
How a $1.4M wire fraud is blocked
A specific, narrated example. The mechanic is the chain_verify primitive enforcing chain-of-custody from prior signed states before a wire is released.
recorded. The deed_signed attestation id is captured into the recording attestation as prior_attestation_id. Both receipts are dual-signed and time-anchored.wire_disbursed can be attested, DeedLock requires a valid chain pointer to the prior recorded receipt and a matching property_id. The escrow platform calls deedlock_chain_verify on the property.deed_signed. chain_verify returns a discrepancy code: WIRE_BENEFICIARY_DID_MISMATCH.Live verification — what a verifier sees
A title underwriter, county recorder, lender, or court receives a CBOR-canonical envelope. Verification is offline against the issuer's published public keys — no Hive call required. The panel below is the same shape every verifier renders.
k1:8c2a…kq:b71d…notary_session attested 2026-09-14T17:38:11ZThat panel is the entire product surface a verifier needs. No demo. No login. The receipt is its own proof, and the proof works in fifty years on a laptop with no internet.
Standards alignment and the gaps DeedLock fills
DeedLock field semantics align with the standards a real estate closing already speaks. Receipts drop into existing title, escrow, RON, and recording stacks. The third column is what a receipt rail adds on top of the standard.
| Standard | Coverage | What DeedLock adds |
|---|---|---|
| ALTA UCD | Closing Disclosure data fields, settlement statement reconciliation | Tamper-evident dual signature on every UCD field set; offline verifiability |
| MISMO 3.4 | Loan, property, and party schemas | Stable DID anchor for every PartyRole; receipt envelope round-trips through MISMO transports |
| RON Standards v1.4 | RON session metadata, AV logs, identity proofing | AV log hash binding directly into the receipt; notary commission DID |
| PRIA recording XML | Recording document submission, status callbacks, county recorder integration | Document number + jurisdiction bound to a chain-of-custody pointer from deed_signed |
| FinCEN GTO | Geographic Targeting Order anchoring (Cosmic tier) | Filings derive from already-signed event metadata; the audit trail is the source of truth |
| 1099-S | Seller proceeds reporting (Cosmic tier) | Proceeds and party DIDs already attested — the form is a projection, not a re-entry |
| HUD-1 | Settlement statement reconciliation (Cosmic tier) | Line items reconciled against signed escrow events; no separate audit pass |
3-step integration path
deed_attest on each state transition. Roughly 11 calls per closing. No data model changes. Existing MISMO and PRIA wire formats round-trip through the envelope.chain_verify against published public keys. No Hive call required after issuance. Receipts remain valid through key rotation via signed key history.The 12 MCP tools
| Tool | Purpose |
|---|---|
deedlock_deed_attest | Attest a state transition with a dual-signed receipt envelope. |
deedlock_deed_get | Retrieve a stored attestation by id. |
deedlock_deed_verify | Verify both signatures on a stored attestation. |
deedlock_notary_session | Multi-document notary session — in-person, RON, IPEN, mail-away. |
deedlock_recording_attest | County recording with chain-of-custody from prior deed_signed. |
deedlock_chain_verify | Verify the full state-machine chain for a property. |
deedlock_by_property | Full transition chain for a property, ordered by timestamp. |
deedlock_by_buyer | Paginated history by buyer DID. |
deedlock_by_seller | Paginated history by seller DID. |
deedlock_by_notary | Paginated history by notary DID. |
deedlock_pricing | Read live pricing surface. |
deedlock_health | Health probe. |
Twelve tools, all live in production. Contact for MCP integration credentials and the full well-known manifest.
The attestation envelope
Every deed_attest call returns an envelope containing buyer DID, seller DID, property id (typically the APN), event type, event hash, timestamp, optional notary / title agent / escrow agent / lender DIDs, optional recording document number and jurisdiction, and dual signatures (Ed25519 + ML-DSA-65). The signatures bind every field. Any tamper attempt invalidates verification.
The envelope is CBOR-canonical. Verification works offline against the issuer's published public keys. ML-DSA-65 (NIST FIPS 204) is the post-quantum signature; Ed25519 (RFC 8032) provides classical assurance. Both must verify for the receipt to be valid.
Chain-of-custody enforcement
The closing state machine has a defined topology. Recording cannot precede signing. A wire cannot be disbursed before recording succeeds. DeedLock enforces this at the protocol level — recording_attest requires the prior deed_signed attestation id, and chain_verify reports any out-of-order transitions, missing states, or recording mismatches with explicit discrepancy codes.
Amendments and cancellations are valid from any state. Each is its own attestation, signed by the originating party, anchored against the prior chain.
What this is not
Calibrated expectations are part of the product. DeedLock is narrow on purpose.
The receipt rail underneath every one of the things above. Closing platforms, NFT deeds, custodians, cash-leg settlement, title insurance, MISMO / PRIA / RON pipelines — all run cleaner with a dual-signed receipt under each state transition.
Pricing
| Tier | Per event | Per closing (11 events) | 10K closings / month |
|---|---|---|---|
| Standard | $0.0096 | $0.106 | $1,056 / month |
| Cosmic | $0.0192 | $0.211 | $2,112 / month |
| Unlimited | — | flat | $2,999 / month at any volume |
Settlement: USDC on Base 8453 via x402. Treasury exists. Volume contracts available for title underwriters, recording aggregators, and closing platforms above 1M closings / year. Receipts settle in seconds; invoicing is monthly net-30 by default.
Field map
DeedLock binds every closing state to a dual-signed receipt that drops cleanly into existing closing infrastructure. Each attestation accepts the closing-native correlation fields below; the receipt envelope round-trips through standard MISMO / PRIA transports via the Hive Receipt primitive.
| Field | Format | Maps to |
|---|---|---|
buyer_did / seller_did | did:hive:… | MISMO PartyRole; ALTA UCD borrower / seller; closing instructions party block |
property_id | APN string | MISMO ParcelIdentification; county APN; ALTA legal description anchor |
notary_did | did:hive:… | RON Standards v1.4 notary commission id; NNA registry |
event_hash | sha256 hex | Document snapshot digest at the state transition; PRIA package hash linkage |
recording_document_number | string | County recorder document number; PRIA recording response |
recording_jurisdiction | string | County / state code; PRIA jurisdiction identifier |
notarization_type | enum | RON Standards v1.4 modality (in_person, ron, ipen, mail_away) |
prior_attestation_id | UUID | Chain-of-custody pointer to prior state in the closing |
Receipt envelopes are CBOR-canonical and fit inside any MISMO / PRIA / ALTA UCD transport. Cross with ProcureLock when the closing has a B2B procurement leg, or stamp directly into title-underwriter / recording-aggregator pipelines.
A real conversation, not a demo black hole
If the receipt rail framing fits the way you already think about closings, the fastest path is a direct note. No qualification gate, no SDR. Steve reads them.
Questions buyers actually ask
What does DeedLock attest?
DeedLock binds every closing state — disclosure, offer, acceptance, escrow, title search, notary session, deed signed, recording submitted, recorded, closing, wire disbursed — to a dual-signed (Ed25519 + ML-DSA-65) post-quantum-ready receipt that title underwriters, county recorders, lenders, and courts verify offline.
How does DeedLock fit with ALTA UCD?
DeedLock binds into the standards already in use. Receipt envelopes are CBOR-canonical and round-trip cleanly through ALTA UCD, MISMO 3.4, RON Standards v1.4, and PRIA transports. We do not re-implement those standards; we make every state under them auditable.
Is DeedLock a notary service?
No. DeedLock is not a closing platform, an NFT mint, a custodian, a settlement layer for the cash leg, a replacement for title insurance, or a re-implementation of MISMO, PRIA, or RON. It is the receipt rail underneath every one of those things.
What does each receipt cost?
Standard tier is $0.0096 per attested event, which equals $0.106 per 11-event closing. Cosmic tier (FinCEN GTO + 1099-S + HUD-1) is $0.0192 per event. Unlimited is a $2,999 per month flat at any volume. Settlement is in USDC on Base 8453 via x402.
How long are signatures valid?
Signatures are valid offline against the issuer's published public keys. ML-DSA-65 (NIST FIPS 204) is the post-quantum signature; Ed25519 (RFC 8032) provides classical assurance. Both must verify for the receipt to be valid. Receipts remain verifiable for the lifetime of the closing record.
Does DeedLock prevent wire fraud?
DeedLock makes wire disbursement chain-of-custody-bound. A wire cannot be disbursed before recording succeeds; recording_attest requires the prior deed_signed attestation id. Eleven cents of receipt cost stops the $269K wire-fraud loss on the first blocked attempt of the year.
Hive runs the receipt rail underneath the broader A2A · agent-to-agent commerce category.