# Sanctions in Real Time: Why Revocation Matters?

#### *A KYC done once is a risk forever.*

#### The Risks

* **Outdated KYC**: Users change circumstances.
* **Sanctions evasion**: Bad actors slip in after initial screening.
* **Expired credentials**: Passports expire, licenses lapse.

#### Why This Matters

Institutions require **continuous compliance**. One gap can taint an entire pool.

#### The Solution: Continuous Compliance Lifecycle

```mermaid
flowchart TD
    A[User Credential] --> B[Epoch Revocation Check]
    B -->|Revoked| C[Access blocked]
    B -->|Valid| D[Access granted]

```

* **Epoch-based revocation** → Proofs expire after fixed intervals.
* **Rolling sanctions lists** → Protocols query updated negative attestations.
* **Issuer-managed expiry** → Credentials tied to validity periods.

#### Framework: Continuous Compliance

1. **Issue** → Credential minted.
2. **Monitor** → Periodic re-checks.
3. **Revoke** → Negative attestations if status changes.
4. **Audit** → Proof of compliance lifecycle.

{% hint style="danger" %}
Static KYC is a liability. Real-time revocation is the only safe path forward
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fairway.global/learn/compliance-and-risk-management-guides/sanctions-in-real-time-why-revocation-matters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.