As shown in the screenshot, Simplex is issuing a token primarily to address two issues:
1. Simplex servers currently have no revenue, which makes them unsustainable and gives no incentive for more people to operate more servers.
2. Providing short, memorable names (which would then require global consensus?).
For the first issue, an ecash sat “stamp” mechanism is simple and straightforward.
If users worry that an ecash mint might run off with funds, consider having the same operator run both the Nostr relay and the Cashu mint. Each time, users buy 32 stamps with 32 sats—just like purchasing stamps at a post office.
For the second issue, we still don’t understand why this would be a problem for a secure, privacy-preserving chat app.
View quoted note →
Keychat
npub1h0uj...rwx8
Keychat is the super app for Bitcoiners.
Autonomous IDs, Bitcoin wallet, secure chat, Mini Apps — all in Keychat.
Autonomy. Security. Richness.
Contact us for feedback 👇
https://www.keychat.io/u/?k=npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8
We need the best money, not every app issuing its own token.
session -> oxen
signal -> mobilecoin
telegram -> TON
simpleX -> "SMPX"
View quoted note →
It’s sad to see Simplex fall into the tempting smart-contract blockchain token trap.
This is also why Keychat uses ecash sats as postage stamps for messages.


In Keychat, sats are always within reach.


One advantage of building a podcast app on Nostr, compared to video or article platforms, is that it can immediately access the existing open content library through RSS, meaning there is virtually no content supply problem and very few copyright concerns.
With an open podcast content base, combined with Nostr’s social recommendation layer and Lightning Network payments, you get a uniquely positioned podcast application.
View quoted note →
We’re eagerly looking forward to the web version of Fountain offering full Nostr login support—including Nostr extension login—just like the native app.
Are you looking forward to it as well?
View quoted note →

We haven’t yet decided whether Keychat will get involved in the Nostr DM problem in this way.
View quoted note →
We have identified the main issues with Nostr direct messages (DM), listed roughly from most to least significant:
1. Different clients implement different DM NIPs (NIP-4 vs NIP-17), causing a lack of interoperability.
2. Users connect to different relays with little or no overlap, so recipients may never receive messages.
3. Message notifications are unreliable.
4. Spam — the system is vulnerable to unwanted messages.
5. Metadata privacy concerns: with NIP-4, others can see who is messaging whom; with NIP-17, others can see who is receiving DMs.
6. No forward or backward secrecy: if a private key is compromised, both past and future messages can be decrypted.
Note: “Nostr DM” here refers to the direct‑messaging feature of Nostr Microblog, not a standalone chat application.
They embody different design trade‑offs. This is why we ranked metadata privacy concerns and the lack of forward/backward secrecy lower in the issue list.
When you need to contact a Nostr microblog user, consider whether using Nostr DM is sufficient or whether you should use a dedicated chat app.
You can clearly see that Keychat's messages continuously update their sending address and receiving address, like a traveler who stays in a different hotel each day and sends and receives mail from those hotels.
View quoted note →
In Keychat, Keychat ID is the main entity and Keychat Browser is a plugin.
So logging into Mini Apps with an ID is more reliable and smoother.
View quoted note →
An ID plus a Wallet together constitute the digital Me; an ID alone is not sufficient.
View quoted note →
On iOS 26, Keychat Browser may sometimes have unresponsive mini-app buttons — choose "Refresh" in the options menu.
The problem is due to Flutter/iOS 26 incompatibility; we’re waiting on a Flutter fix.

GitHub
[iOS] Tap interactions not working on iOS 26 for webview_flutter · Issue #175099 · flutter/flutter
Background I'm creating this new issue in case of confusion with the original issue: #158961. This PR reverted the workaround to fixed the original...
The Lightning Network provides trustless scaling for Bitcoin and offers instant finality for payments.
Ark likewise offers trustless scaling, but Ark payments only reach finality after at least one block confirmation, the same as on-chain Bitcoin.
View quoted note →
