The short version, for everyone: Kengele is a free safety alarm for activists. If captors force an activist to unlock their phone and say "I'm safe", the alarm now keeps ringing. Only 2 of the activist's 3 trusted contacts can switch it off, and only after seeing or hearing them on a call. The rest of this post shows exactly how, with code you can run yourself.
Kengele is an open-source alarm for activists in East Africa. Ukinyamaza, kengele inalia: "if you go quiet, the bell rings."
Why it exists
- Amnesty International counts over 83 enforced disappearances around Kenya's 2024 and 2025 Gen Z protests.
- When someone disappears, how fast the public finds out often decides how fast they are released. Today that depends on someone noticing and phoning around.
- The closest tool for human rights defenders, Círculo, says on its own site that its service shut down on 15 November 2026. It depended on one organisation's servers.
How it works, in plain words
- Before a risky event, the activist sets a time window, for example "2pm to 8pm, check in every 90 minutes".
- They check in from their phone. Each check-in goes to 3 to 5 guardians: family, a lawyer, a trusted organisation.
- If a check-in doesn't arrive, each guardian's phone raises the alarm on its own. There is no central server, so there is nothing to shut down or seize.
For developers: check-ins are signed, encrypted Nostr events (NIP-17/44/59) sent over public relays. The watcher logic runs on each guardian's device.
The problem this update fixes
Kengele already had a duress PIN: a second PIN that unlocks to a normal-looking screen but quietly raises the alarm. But a captor can force someone to give their real PIN and send "I'm safe". Before this change, that was enough to end the alarm.
The new rule (PR #31)
Once an alarm has gone off (a missed check-in, a panic button or a duress PIN):
| Who says "safe" | What happens |
|---|---|
| The activist alone | Guardians see "the activist says they are safe". The alarm keeps ringing. |
| The activist + 1 guardian | Not enough. The activist's word never counts towards the vote. |
| 2 of 3 guardians | The alarm stands down. |
Each guardian also has to speak to the activist by voice or video before their "safe" can be sent. The app enforces this. It isn't just a guideline.
And the activist's "I'm safe" never delays a public alert. If guardians are already confirming the alarm, their confirmations keep counting.
Proof
Without reading code: every change is public. Open pull request #31 to see what changed, when, and the written reasoning. The cover image shows the project's automatic checks (tests) running. Each PASS means the rule held.
For developers: the guardian's all-clear is built by GuardianAllClearEvent, which returns ErrNotVerified unless it receives a record of a voice or video call (body.go#L128-L140). The record stays on the guardian's device and is never sent.
The core test (confirm_test.go#L328):
func TestActivistAllClearAloneEndsNothing(t *testing.T) {
// After a panic, captors force the activist to unlock with the real
// PIN and send an all-clear. The alarm must stay, and the release must
// still happen when a second guardian confirms.
...
o = expect(t, None)(f.clearFrom(t, tl, f.activist.priv, 1, t0, t0))
if !o.ActivistSaysSafe || o.By != NotCleared || tl.Epoch() != 1 {
t.Fatalf("activist all-clear ended the alarm: %+v epoch=%d", o, tl.Epoch())
}
...
// The pending confirmation survived, and the second one releases.
expect(t, Release)(f.confirm(t, tl, 2, 1, t0.Add(time.Minute), t0.Add(time.Minute)))
}
Run it yourself (needs Go 1.24 or newer):
git clone https://github.com/altradits/kengele
cd kengele
go test -race -v -run 'AllClear|PlusOne|Coerced' ./internal/confirm
Our run (Go 1.26.5, commit 00783f7):
--- PASS: TestSingleCoercedGuardianCannotPublish (0.16s)
--- PASS: TestActivistAllClearAloneEndsNothing (0.09s)
--- PASS: TestActivistPlusOneGuardianIsNotEnough (0.07s)
--- PASS: TestGuardianAllClearNeedsVerification (0.00s)
--- PASS: TestAllClearByTwoGuardians (0.07s)
--- PASS: TestAllClearRaces (0.27s)
--- PASS: TestConcurrentActivistAllClearAndConfirms (0.14s)
ok github.com/altradits/kengele/internal/confirm 2.142s
What it still can't stop
Being honest about the limits matters more than the feature (threat model §4.5):
- Captors can pressure the activist during the video call too. Pick guardians who know the activist well, and agree a spoken code word in advance.
- If 2 of 3 guardians are compromised, they can switch the alarm off. That's the trade-off by design, so pick guardians who don't live, work or get arrested together.
Status and how to help
Kengele is still being designed and is not for real use until an independent security review is published.
- No coding needed: digital-security reviewers, Swahili translators, and anyone who works with activists and can tell us what we're missing.
- Developers: Go, Android/Kotlin, Nostr, Bitcoin (miniscript, OpenTimestamps).
Start with CONTRIBUTING.md.
Top comments (0)