Tamper monitoring & recovery

Obsign continuously checks that your identity document (your DID) still says what it should. If something changes that you didn’t initiate, Obsign tells you: in words, with an icon and a place in the list, never by color alone.

A detected change surfaces on the home screen as a banner with text and icon, not color alone.

Reading a status

Every identity shows a status. The status is always carried by text + icon + position, so it is legible without relying on color:

Monitoring

Nothing unexpected. Obsign is watching and the identity document matches what you last approved.

Change detected

The identity document changed in a way you did not initiate. You have a window to review and, if needed, override it.

Action needed

An override window is closing, or a change would remove your ability to recover. This state is paired with an explicit label and a persistent banner, not a red dot alone.

The 72-hour override

ATProtocol’s PLC directory gives the higher-precedence key a 72-hour window to contest a change. Your device key sits at the top of that list (see Who holds the keys), so you hold that power:

1. Obsign detects a contested change and starts the countdown.
2. You review what changed, in plain language.
3. If it was not you, you sign an override with your device key, and the change is reversed within the window.

The alert detail: what changed, and the time remaining in the 72-hour window, shown as a duration rather than a color.

Tip

An override is signed by the device key already on your phone — no share to reassemble and no scramble in the moment. (Your Shamir backup is the separate safety net for getting a key back onto a new device.)

This page describes did:plc identities

Monitoring and the 72-hour override are properties of the PLC directory, so they apply to did:plc identities — the default. A did:web identity is anchored to your domain instead: defending it means defending the domain.