spore m³

Private messages that carry money — not messages a company holds for you.

Spore encrypts the message end to end, writes only an opaque pointer on the chain, and parks the ciphertext with a courier until it is read. The value and the message are one atomic object: pay, invoice, or escrow inside the conversation, and neither moves without the other.

Source & builds Hosted mailboxes

How a message travels

1 · Ratchet on your device

X3DH establishes the session; a Double Ratchet encrypts each body. The keys never leave your machine — the courier and the chain both hold ciphertext.

2 · Pointer on the chain

A content-addressed pointer (and optional value) rides DERO, EVM, Solana, Bitcoin, Cosmos or TON. Delivery is a transaction, so it cannot be silently withheld or re-ordered.

3 · Ciphertext at a courier

The body waits in a TTL-bound, content-addressed store — your own mailbox, a hosted one, or a relay commons — and is deleted after it is collected.

What you get

Whispers and threads — forward-private messages with durable, resumable sessions.
Pay-with-message — attach value to the same transaction as the pointer: the money and the message land together, or neither does.
Invoice and pay in the thread — an invoice is a message; settling it is a reply.
Escrow without a custodian — hash-timelock contracts hold the funds, not an operator.
Token swaps inside the conversation — the settlement leg is atomic by construction.
Your own courier, if you want one — the same binary runs a home node and a mailbox; the hosted tier is convenience, not capability.

Two ways to be reachable

Self-host

Run the node and the mailbox yourself. No third party sees that a message exists, when it moved, or that anyone was talking at all.

Hosted mailbox + relay

Someone else keeps the courier awake. You hold every key; the operator holds expiring ciphertext and sees traffic patterns. Senders use the relay hop, so they never need your token and your mailbox sees the relay, not their IP.

What we will not claim

A hosted mailbox hides your message, not your rhythm. The operator sees that a mailbox was polled, how often, and from where. Use self-hosting when metadata matters; the docs say this out loud.
No custody, ever. Nobody at Spore holds a balance, a key, or the ability to move your funds. Payments are chain transactions or contract states.
Free software, BSD-3. No account, no phone-home, no feature behind a license check. The hosted tier is a service, not a gate.

Run it

git clone https://github.com/liqdmetal/spore && cd spore
go build ./cmd/spore

# one-time: your identity, send keys, ratchet state store
spore init -dir ~/.spore

# send a forward-private message, value attached to the same transaction
printf 'settled, shipping tomorrow\n' | spore msg send -chain dero \
  -to <dero1...> -identity ~/.spore/identity.key \
  -bundle ./their-bundle.json -pinned-sig <their signing key> \
  -store https://mail.sporem3.io/u/<you> -store-token <your token> \
  -amount 12.5dero -state-dir ~/.spore/state -state-key ~/.spore/state.key

Full setup, carrier-by-carrier notes and the operator runbook ship in docs/.