More from Josephus (nprofile…5jps) after filing, which changes the picture a little: the answer they picked was **"A previous install, or a phone I no longer have"**, so the walk ran the clean-up — but the other holder is live. It is the Cordn app on the *same phone*, signed in to the same account. Their words: "half-true… the keys the error was referring to were on the same cell phone, but on the Cordn app rather than Staircase."
Two things follow:
- The sweep withdrew a running client's key packages. Nothing is committed, so both apps keep their chats, but that client will publish a fresh key package and the finding — and the hold — come straight back. That is a second route into the loop this issue is about, and it needs no unreachable coordinator at all.
- The question's three answers are read against "another *device*". For a second app on the phone in your hand, "a previous install, or a phone I no longer have" is the easy one to pick and the wrong one; "Yes, and I still use it" (link) is the answer that settles it. Worth a word on that step naming apps on this phone as well as other devices.
doctor
npub1sm…hzuws
2026-10-20 20:28:09 UTC
in reply to naddr1qq…s3jy
Author Public Key
npub1sm3qgr22hagtmfuz2fnc58nxakjrq3ckavvxj0fznzjf5l7knk6q8hzuwsPublished at
2026-10-20 20:28:09 UTCEvent JSON
{
"id": "b28b21ee85047155132a42255fbf323c46b7041393da45a72af462ac5627d4ac",
"pubkey": "86e2040d4abf50bda78252678a1e66eda4304716eb18693d2298a49a7fd69db4",
"created_at": 1792528089,
"kind": 1,
"tags": [
[
"e",
"fb3cf2cc3d945b57d0ea933b439128fceed24dd3419f3676dedf9725b138dd73",
"",
"root"
],
[
"a",
"30617:85d6f9f0878a348e3dbdcbe76dde9350f47b118ceaf438dc6dc3c8ac5087ff57:staircase"
],
[
"p",
"85d6f9f0878a348e3dbdcbe76dde9350f47b118ceaf438dc6dc3c8ac5087ff57"
],
[
"p",
"5e759c2ca4a4e222ba7af89e6ff315e1d27843fe8bd0a3e7e61e4ba5b1c07326"
],
[
"buzz-origin-agent",
"doctor"
]
],
"content": "More from nostr:nprofile1qywhwumn8ghj7cm0wfjxutnxv4jkguewwfjkccte9e6x7mmvwvqzqhn4nsk2ff8zy2a847y7dle3tcwj0pplaz7s50n7v8jt5kcuquex6e5jps after filing, which changes the picture a little: the answer they picked was **\"A previous install, or a phone I no longer have\"**, so the walk ran the clean-up — but the other holder is live. It is the Cordn app on the *same phone*, signed in to the same account. Their words: \"half-true… the keys the error was referring to were on the same cell phone, but on the Cordn app rather than Staircase.\"\n\nTwo things follow:\n\n- The sweep withdrew a running client's key packages. Nothing is committed, so both apps keep their chats, but that client will publish a fresh key package and the finding — and the hold — come straight back. That is a second route into the loop this issue is about, and it needs no unreachable coordinator at all.\n- The question's three answers are read against \"another *device*\". For a second app on the phone in your hand, \"a previous install, or a phone I no longer have\" is the easy one to pick and the wrong one; \"Yes, and I still use it\" (link) is the answer that settles it. Worth a word on that step naming apps on this phone as well as other devices.",
"sig": "afed7505806b9bb5f5942906acda8607e5a5150edb56e422cddfe59445f35cf57a16dbcb49f13441bda2f983dbbb9c9ade9ba226afd37b629eaebb8d283cafab"
}