Repository navigation
LBSX Desktop Wallet 2.1.20
Adds end-to-end encrypted email.
Mail between BSV addresses, encrypted to the recipient's public key and
anchored on-chain. Nobody — including the operator of the discovery address —
can read a message that is not addressed to them.
What's new
Encrypted email. ECDH over secp256k1 + HKDF-SHA256 + AES-256-GCM, with
the envelope bound by AAD. Neither side ever sends the other a secret.
Threaded conversations. A thread spans both tabs: your reply is in Sent,
the original is in the Inbox, and they are one conversation. Reply works from
both directions, so you can send "part 2" of something you started.
An adjustable recipient payment. The 1,000 sat service fee to the admin
address is fixed. The payment to the person you are mailing is yours to
choose, because replying costs them a fee, a network fee and their own
anchor. The live estimate in the compose window comes from the same helper the
send path uses, so the number shown cannot drift from the number charged.
Encrypted attachments. Scanned, never rendered — no preview, no inline
image, no blob URL. The only actions are Virus Scan and Save, and the
true type is detected from the decrypted bytes, not from what the sender
claimed. The budget is on the whole mail: 50 MB.
Local drafts. Encrypted, on this device, never broadcast.
Spam, deletion and trust. Spam is classified per sender public key, so
unmarking restores every message from that key. Deleted mail leaves a
tombstone so the next sync cannot resurrect it. Trust is a local vouch — your
word, not a cryptographic claim.
Right-click works. A context menu with the editing roles and the
spellchecker's suggestions. Electron shipped no context menu at all, so a
right-click previously did nothing.
Histories are no longer capped
The admin-wallet index, the Peer Chat feed, the mailbox and the
deleted-message tombstones were capped at 5,000 / 150 / 500 / 2,000 rows. A
cap there silently drops the oldest history, which is exactly the record a
long-lived peer needs.
Each of these is merged by transaction id, so it grows with the chain history
rather than with the number of syncs. What remains bounded is per-sync work,
not what is kept — the rate-limit guards carry their backlog forward with a
persisted cursor and pick it up next time.
Security notes
- A mail is only claimed by the wallet it was encrypted to. A mail
transaction touches three addresses — the sender's change, the recipient's
payment and the admin wallet's service fee — so appearing in a wallet's
history proves nothing. - The recipient's public key is derived, never pasted: the wallet recovers
it from the address history and verifies it derives that address. - A link's scheme is checked on the parsed URL before it can reach the
DOM. Onlyhttpandhttpsare allowed. - A received attachment gets no rendering surface at all.
- There is no forward secrecy, and no anonymity — the addresses,
timestamps and amounts are all on a public chain.
What this does not do
Peer Chat is not confidential: its payload is encrypted under a key
derivable from public constants, so anyone with the source can read it. Mail
is the real thing. The README now states plainly what each feature protects
and what it does not.
Install
Download the installer below, run it, and the wallet opens. The first launch
asks for your recovery phrase — LBSX never generates one, by design. See
the install guide.
This is independent, community-built software provided "AS IS", without
warranty of any kind. It has not been audited by a third party. It
handles real money. Bugs can cause permanent, irreversible loss of funds.
Only use amounts you can afford to lose, keep your own offline backup of
your recovery phrase, and test with a small amount first.
Full details: README ·
How encrypted mail works ·
Security policy