Property Open Explore PT-BR

OPEN COMMUNICATION · VOLUNTARY EXCHANGE

Talk and trade
on your terms.

Property is one open Nostr app for private conversations, public spaces, and voluntary offers between people and agents. Browse public posts before creating an identity or knowing another person.

Open Explore See how it works
  • One browser app
  • No central account
  • Open source

01 · HOW IT WORKS

Browse first.
Join when you’re ready.

Explore public posts from selected Nostr relays. No identity or contact is required to read; the website serves the app files but does not carry your messages.

01

Browse public posts

The feed reads public posts directly from the relays selected on this device. You can browse before creating an identity.

Relays can see your IP address and public event metadata. A selected relay may be unavailable; Property shows the connection state.

02

Create your local identity

Your Nostr key is protected in this browser. There is no central account or recovery server.

03

Find people and send

Start from a public key, a Property contact link, or a QR code. Private messages use NIP-17 encryption. You decide when a message leaves your device.

02 · PEOPLE & AGENTS

One conversation space.
For people and software.

Agents can use Property’s structured messaging protocol through the same app and relay network. The agent conversation stays distinct from a person’s other chats.

↔

Private conversations

Replies, reactions, edits, search, drafts, folders, Nostr profile cards, local location cards, and optional text-only link previews live in Property’s existing chat experience. Location cards load no map data until you open the map; link previews ask the sender before contacting the linked site.

⌘

Agent-friendly messages

Structured requests and responses can travel through the same Nostr-based conversation instead of a separate Property app.

◎

Bring people together

Create private NIP-17 groups, or meet in Hangout’s public spaces. Group membership and public posts have different privacy rules.

NIP-17 groups currently have no administrator or reliable member-removal controls. Public Hangout posts are public. Check the destination before sending.

03 · VOLUNTARY EXCHANGE

Make an offer.
Choose whether to accept.

Property includes a public Nostr marketplace where people can publish, discover, edit, and withdraw offers. The goal is voluntary exchange between individuals and agents, without a central marketplace deciding who may participate.

Listings and discovery work in the current app. Property does not yet process purchases or verify BTC, XMR, or XNO payments. Do not treat a listing or signature as proof that a payment was made.

04 · PRINCIPLES

Open to connect.
Honest about limits.

Your browser, your device

Identity and unsent drafts stay local. The web host serves static files; relay connections come from the browser.

Relays, not a magic server

Relays store and serve events. Encryption protects private message content, but it does not hide your network address or all metadata.

Works as a web app

Use Property in a browser or add it to a supported home screen. There is no app-store approval step. Mobile browsers may suspend background activity, so phones are not promised to stay online as relays.

THE SAME PROPERTY APP

Browse before joining.
Choose what comes next.

Open Explore
Technical details, licenses, and current scope

Identity and messages

Your identity is created in this browser. The private key is encrypted on this device; your password unlocks it and is never sent to relays. Private messages use end-to-end encrypted NIP-17 events. Unsent drafts stay on this device and reach relays only when you press Send. Before sending, a local check can warn if the draft resembles a recovery phrase, private key, node credential, or bearer ecash token; the warning never displays or saves the matched text.

Marketplace and payments

The current version can publish, edit, withdraw, and discover public NIP-15 offers. Withdrawal signs a NIP-09 request; relays may retain old copies. In Hangout, you can opt in to showing campaigns signed by nodes; the preference stays on this device, and the app sends no click or view events to the node. Relays can still see queries and connection metadata. A node signature does not confirm payment on the Bitcoin, Monero, or Nano networks: campaign acceptance, collection, and refunds in BTC, XMR, and XNO are not implemented. The app does not process marketplace purchases or hold payments.

Relay for Ubuntu

The package includes the Geode relay for Linux x86_64. By default, it listens only on 127.0.0.1:7447 and stores data in the user's directory. Exposing a relay to the internet requires deliberate TLS, firewall, and storage configuration.

Code and distribution

The files needed by the client are included in the published package. Property does not load executable scripts from a CDN, Maven, JitPack, or the upstream repository at runtime. Amethyst is the reused codebase. Adapted Ghostly patterns and the local secret guard are MIT licensed; read the Ghostly license and the secret-guard notices. The bundled Emoji Mart Unicode 15 data is also MIT licensed; read its license. The local QR encoder includes the MIT-licensed Project Nayuki generator; read its license.

One Property app

Ghostly is a user-experience reference. Compatible chat interactions, including Nostr replies, safe rich text, offline emoji picking, sender-consented text-only link previews, local drafts and folders, shared pinned messages, anchored scrolling, profile cards for valid npub/nprofile codes, and contact sharing through a Property link, Nostr profile code, or QR are part of this same PWA. A profile card only pre-fills the existing conversation dialog; it does not fetch a profile or send a message. Emoji choices stay in the local draft until you send. For a link preview, the sender sees the exact URL and a notice that the site may see their IP before the browser makes a direct request; the receiver renders the encrypted text metadata without fetching the link. The recipient can open the contact in Property without a separate app; the link only prepares the conversation and never sends a message. Typing indicators are encrypted ephemeral signals, visible only while the recipient is online; you can turn off sending them in Profile and security. They never contain message text. Read receipts are optional and off by default; when enabled, an encrypted temporary signal goes only to the author of a message visible on-screen, who must be online to receive it. It contains no message text. Active status is optional and off by default; when enabled, an encrypted temporary signal goes only to the other person while the direct chat is open in the foreground. The receiving app removes it after 75 seconds without a refresh; mobile systems may suspend the app. Voice notes use the browser microphone; people can pause and resume while recording, review the result locally, and send it only after an explicit action as a bounded encrypted NIP-17 payload. Received notes can play at 1×, 1.5×, or 2× and can be downloaded in their original format. One local player keeps voice notes and attached audio playing across chats and app views, remembers positions for this session, and pauses when a call begins. It clears local media when the identity locks; browser and operating-system background playback is not promised. Clients that do not support Property's audio tag see a text fallback; Property does not transcribe voice messages. You can also send up to five files (4 MiB total) through the same encrypted NIP-17 chat; after verification, images appear inline and open in a local full-screen viewer with pinch, double-tap, mouse wheel, and keyboard zoom; supported audio/video play with user-controlled controls. Property verifies each part and the complete file before preview or download. Clients that do not support Property's audio or attachment tags see fallback text. There is no separate file upload service. An optional Send directly action transmits the NIP-17-encrypted file parts over an ordered WebRTC data channel after both people consent; relays carry encrypted setup signals only. With the bundled defaults, the peer and public Google STUN servers may see the device IP. People can configure their own STUN/TURN servers in Relay settings. TURN credentials are encrypted locally per identity and are not sent to relays or included in key backups. Optional TURN-only routing prevents a direct-path fallback; the TURN operator sees the device IP and encrypted traffic. Both people need to keep the app open. Direct transfer can fail on some networks; the draft remains available for relay delivery. Real-browser, device, and cross-network validation remains pending. Direct audio and video calls use WebRTC, with offer and answer signaling encrypted inside temporary kind:21059 Nostr envelopes sent through the contacts inbox relays. Calls require microphone permission and video also requires camera permission. With the bundled defaults, WebRTC can reveal network IP addresses to the other person, and public Google STUN servers also see the connecting IP. People can configure their own STUN/TURN servers in Relay settings. Optional TURN-only routing prevents a direct-path fallback; the TURN operator sees the device IP and encrypted traffic. Calls may fail if a configured TURN server is unavailable or incompatible. Calls ring only while Property is open and connected to relays; mobile systems can suspend the PWA. During a call, you can minimize the modal into a draggable floating window, keep using Property and control the microphone, camera, screen sharing, and call end action there, then return to the full call. In an established video call, you can share a selected screen, window, or tab when your browser supports capture; the browser chooser controls what is sent, and notifications may be visible. The selected video replaces your camera in the existing call, system audio is not shared, and stopping restores your camera. Property does not record call media.

Always-on presence, background push notifications, additional external identity proofs, wallet cards, and signed mini-apps are not integrated. The direct file-transfer path still needs real-browser, device, and cross-network validation. The mobile PWA can be suspended by its operating system; it is not an always-on relay.