Skip to content

Staircase

Private, end-to-end encrypted group chat over Nostr. Uses MLS (RFC 9420) for secure messaging with replies, reactions, and file sharing. Supports multi-device sync via QR codes and allows choosing your own coordinators and relays.

Staircase is a private group messenger built on Cordn: end-to-end encrypted MLS groups (RFC 9420) whose messages are ordered by a coordinator you choose and carried over Nostr relays. No phone number, no account on anyone's server, and nobody in the middle can read along.

  • Group chats with replies, reactions, @mentions, pins and encrypted photos and files
  • You decide who's in: admins, invite links and QR codes; members join with their own Nostr key
  • Your keys: a local key or Amber (NIP-55); nothing leaves the device unencrypted
  • Multi-device: link your phone and desktop to the same groups
  • Open network: pick your coordinators, relays and Blossom servers
  • Works with other Cordn clients such as cordn-web; also available for Linux desktop (deb, rpm, Arch)

Summary generated by Zapstore from source.

Original description, as the developer published it.

Latest release

Oct 21, 2026

Claimed app No Google servicesSource available · MIT

Uses the camera to scan QR codes for joining groups or linking devices.

Permissions

  • Camera CAMERA Take photos and record video To scan QR codes.
  • Notifications POST_NOTIFICATIONS Send you notifications
  • Always running REQUEST_IGNORE_BATTERY_OPTIMIZATIONS Keep running in the background without limits

Release notes

Added

  • Verbose logging now says how late each notification was. With Settings › Diagnostics › Verbose logging on, every notification Staircase posts for a chat is followed by one newlay.notify line naming the chat, how many messages it carries, the seconds between the newest message being sent and the notification appearing, and the delivery mode in force — the number to read when comparing Periodic, Frequent and Instant on your own phone.
  • A fourth way of being told about messages on Android: "Frequent", in Settings › Notifications and on the first-run notifications step, beside Off, Periodic and Instant. It wakes the phone with an alarm about every 5 minutes (or 10, your choice) to check for messages, then disconnects: no ongoing notification and very little battery. It works while the phone is awake or charging; in deep sleep Android holds the check until its own window, so a message can then be as late as on Periodic. The Settings list's Notifications row reads "Frequent · about every 5 minutes" while it is on.
  • On Android, a background check in Periodic or Frequent that finds no network, or the app being left while offline, is now followed by one check the moment a network is back, instead of waiting for the next scheduled wake (after airplane mode, a tunnel or a dead spot). At most one such check every two minutes, so a flickering connection does not run them back to back; Instant is unchanged.

Fixed

  • Starting the app no longer raises a notification about your account that has nothing behind it. On an account with multi-device sync on, every start of the app read its own messages — the ones you had sent from your other devices — as another app using your account: a "Your account" notification appeared, this device's own sends were held for a moment, and the notice cleared itself a second or two later, so anyone who tapped it arrived at a checkup with nothing in it. The app now knows whether this device syncs with your others before it judges any of that, and a real finding still appears and still opens the checkup. A notice that stops standing now also takes its notification with it, instead of leaving it in the shade until it is tapped (#72ed6bbe).
  • Zooming into a picture on Android now shows the detail that is in it. Every image was decoded down to 2048 px on its longest side before being shown, so pinching into a large or a tall one — a page of small text, a long screenshot — only magnified what had survived, and the text stayed blocky however far in you went. The image viewer now decodes for the screen it is drawn on: as much detail as its zoom can use, bounded by what the phone can draw in one go and by what it can hold while a chat full of pictures is swiped through. Chat bubbles, thumbnails and group pictures keep the smaller decode, which was never visible there. The viewer's decode also moved off the drawing thread, so opening a large picture no longer holds the screen up while it is read.
  • Asking to join a group no longer leaves you waiting for ever. The row in your chat list sat on "Waiting for an admin" with a spinner indefinitely, so an admin who had turned the request down and an admin who had not looked at it yet were the same thing for ever — nothing is sent to you when a request is declined. The row now stops claiming to be waiting once nobody is holding the request for an admin to answer any more, says only what is known (it was dealt with, or it expired; Staircase cannot tell which, and you were not added), and offers to ask again. On the admin's side, declining a join request has left its place directly under Approve, where it was a mis-click away, for the request's own menu, and now asks first: it cannot be undone, and the person who asked is not told (#e5d1ab0d).
  • Scrolling a chat whose senders this device has not seen before no longer pauses as their names arrive. Each name Staircase looked up redrew every message on screen, including the ones whose own sender was already known and whose text could not have changed, so scrolling into a run of unfamiliar senders cost a redraw of the whole screen for every batch of names that landed. A message is now drawn again only when a name it actually shows changes — its sender, somebody it mentions, the message it replies to, or whoever reacted to it. Looking up a name no longer reads this device's stored profiles while the screen is being drawn either (#6393ec4b).
  • Relays you type while adding a coordinator are now kept. In Settings › Coordinators › Add a coordinator, a relay address typed into Relays was stored as though the coordinator had published it, so the next time the Coordinators screen opened it was replaced by the coordinator's own published list — silently, and without the screen ever having said the list was yours. A list you type is now yours: the card reads "Set by you · kept until you choose the coordinator's published list", and it stays until you do. Relays that came from an nprofile1… you pasted are the operator's rather than yours and still give way to a published list, as before (#74a96a4b).
  • Starting the app no longer reads every account's whole message database into memory. To decide which accounts had a database on this device, Staircase read each file from end to end as if it were text — tens of megabytes of it on a phone that has been in use for a while — and then threw the text away. On a database of about 40 MB that meant asking Android for a single 128 MiB block at every start: granted, it made start-up several seconds longer; refused, the failure was silent and also skipped the pass that brings a signed-out account's database up to date with how databases are stored now. Staircase now asks whether the file is there. Start-up on such a phone is several seconds shorter and some two hundred megabytes lighter (#ac10a449).
  • The account checkup no longer tells you your held messages have gone out when they have not. Where the checkup could not settle what it found — a coordinator that has stopped answering, or a finding no clean-up touches — it still ended on "Done" and "1 message sent · What was held while this was unsettled has gone out", and the message was back to "Held · another app uses this account" a moment later. The last screen now says your account is still held, how many messages are still waiting, and what is left, and it offers "Continue anyway, and let my messages out" and "Check again" right there instead of behind the question a step back. Nothing is counted as sent unless the hold has actually let it out. "What we found" also no longer reads "No keys but your own" while the card on your Inbox says a key belongs to none of your devices: where a key is served that nothing here can account for, it says so and names the coordinator that did not answer. The clean-up step, reached with nothing it can clean up, offers Check again rather than a button that cannot be pressed (#fb3cf2cc).
  • Adding a coordinator you already have no longer replaces it. In Settings › Coordinators › Add a coordinator, a key that was already one of your coordinators was stored over that coordinator's record: its name, its relays and your choice about its relay list were replaced by whatever was in the sheet, no second card appeared, and nothing said so — a coordinator holding your chats could be left pointing at a relay that does not answer. The sheet now recognises the key, names the coordinator it belongs to, and offers to open it for editing instead (#78b9d8be).
  • Renaming a coordinator no longer stops it following its published relay list. In Settings › Coordinators › a card › Edit, saving a new name pinned the relays the dialog had filled in for you, so the card went from "The coordinator's published list · follows its changes" to "Set by you" and the coordinator's own later changes were ignored. A save that leaves the Relays field as it opened now changes nothing about the relays: one that was following its coordinator still follows it, and one whose list you had set is still yours (#d08f27b6).
  • A poll that names somebody now reads their name in the chat list and in a notification, not their npub. A poll asking Did @Avery see this one read that way in the chat, but in the chat list as 📊 Poll: Did nostr:npub1yhc0d7g… — sixty-odd characters of npub taking the whole of that chat's line — and the notification in the shade did the same, pushing the question out of sight. Both now read a question the way the chat does: a mention as @their name, or as a short npub where no name for them is known on this device, and a quoted message as a short link. The question in the poll's own bubble reads that way from the moment it is sent too, instead of showing the npub for the second the poll is in flight and then changing (#673c006c).
  • A finished account clean-up no longer brings the same notice straight back. After the checkup had removed a key that belonged to none of your devices and told you it was done, the "Your account" card on your Inbox could reappear within seconds naming the key that had just been removed, inviting you to walk the same checkup again over a key no coordinator serves any more; a second walk cleared it. A check of your coordinators that was still running when the clean-up finished reported what it had read before the removal, and that reading was taken as a fresh finding. A reading taken before a key was removed is no longer counted, and a key that is published again after that is still found (#77b8c55e).

Comments

Loading comments…

See more

Get Staircase the private way

Updates checked on your device, and every release verified before it installs.