From 88b7facf8adb126d129cfee5b7c62ba3d668a472 Mon Sep 17 00:00:00 2001
From: fria <138676274+friadev@users.noreply.github.com>
Date: Mon, 31 Mar 2025 11:18:15 -0500
Subject: [PATCH] add more token info

---
 blog/posts/privacy-pass.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/blog/posts/privacy-pass.md b/blog/posts/privacy-pass.md
index c67e8be41..49067be5b 100644
--- a/blog/posts/privacy-pass.md
+++ b/blog/posts/privacy-pass.md
@@ -150,6 +150,12 @@ The client presents tokens to the Origin once they're provided by the issuer.
 
 <small aria-hidden="true">Illustration: [Cloudflare](https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/)</small>
 
+The tokens need to identify which issuers are trusted.
+
+They can also be interactive or non-interactive. Interactive means that you need a fresh token based on the challenge, whereas a non-interactive token can be stored for later use.
+
+Tokens can also be constrained to one specific Origin or they can be used across Origins.
+
 ### Private State Tokens
 
 [Private State Tokens](https://developers.google.com/privacy-sandbox/protections/private-state-tokens) are a [proposed browser API](https://github.com/WICG/trust-token-api) by Google as part of their [Privacy Sandbox](https://developers.google.com/privacy-sandbox). They're based on the Privacy Pass protocol.