Owner · submit property

A deed first. Then a listing.

The registrar checks the encrypted deed before any room token can be minted. The public record never contains the address, the document, or a cleartext storage pointer.

Back to dashboard

Step 1 · Identity and wallet

Required

Connect a Hedera-compatible wallet.

The property application is bound to this wallet. The same identity cannot submit from a second wallet.

Step 2 · Property details

Private until approved

Property nicknameThis is the public name. Do not use a flat number.

Number of rooms

Locality

City

Short property description

Find property on map

Select a map result or share this device’s location.

The location pin will appear here.

Latitude

Longitude

Address searches are sent to OpenStreetMap. The selected pin is encrypted with the application, then becomes public and permanent on Hedera if listed. Browser GPS and map search are owner-supplied signals; the registrar must check the pin against the deed.

Step 3 · Deed and privacy notice

Encrypted before upload

Upload the property deed as a PDFPDF only · up to 3 MB · encrypted before it is stored on Swarm

The deed is never public.

It is encrypted, stored privately, and visible only to the registrar through an authorised, audited review route. The public index sees an opaque application ID only.

I understand the deed and proposed location are encrypted for registrar review, the exact pin becomes public and permanent if listed, and neither the pin nor this process is a title guarantee.

Step 4 · Submit for review

Registrar reviews the deed

Connect a wallet to continue.

On submit, the backend normalises the property, creates a random salt and commitment, encrypts the deed, and writes only an opaque pending application to Arkiv.