At a glance
PropVault creates a tamper-evident, role-weighted ledger for real estate — turning every property into a verifiable, transferable asset.
1. Core principles
Property-bound record
All data is anchored to a property (parcel), not an individual. The record persists across ownership.
Append-only ledger
Entries are never edited or deleted. New information is added as new entries, preserving full history.
Verifiable integrity
Each entry is cryptographically linked to the previous one. Any modification breaks the chain and is detectable.
Role-weighted trust
Not all data is equal. Each entry carries a contributor role that determines its verification weight.
Controlled transparency
Access is permissioned. Scoring reflects only what is visible to the reviewer.
2. Ledger structure
Each Vault is an ordered sequence of entries. Entry n includes:
- Payload (document / data)
- Contributor role
- Timestamp
- Content hash
- Previous entry hash
- Chain hash (seal)
This creates a hash-linked chain where each entry validates the previous, and the full history can be recomputed independently.
3. Contribution model
Contributor roles
| Role | Tier | Trust level |
|---|---|---|
| Accredited Auditor | Verified | Highest |
| Municipal Feed | Verified | Highest |
| Trade Contributor | Corroborated | Medium |
| Owner | Attested | Base |
| System | — | Non-scoring |
Principle
Trust is derived from who contributes, not just what is uploaded.
4. Verification mechanism
A Vault is verified by:
- Recomputing each entry's content hash
- Recomputing each chain link
- Validating sequence continuity
Failure conditions
- Missing entries
- Broken hash links
- Payload mismatch
Any failure invalidates the chain.
5. Scoring inputs
The PropVault Score is derived from:
- Completeness — Coverage across standardized document categories.
- Verification — Weighted average based on contributor roles.
- Recency — Time decay of entries.
- Warranty coverage — Active protections on major systems.
For implementation detail, see the PropVault Score methodology and audit methodology.
6. Redaction model
Entries may be redacted at the document level. Redacted entries remain in the ledger and are excluded from scoring.
That preserves privacy without breaking auditability.
7. Transfer standard
At closing, control of the Vault transfers with the property. The ledger remains intact and the verification state persists.
No resets. No exports. No loss of history.
8. System outcome
The standard transforms properties into:
- Verifiable assets instead of opaque purchases
- Continuous records instead of fragmented histories
- Trust-layered systems instead of unstructured data