{"version":"2.1.269","anchor":"signed-cache-identity-telemetry-added-alongside-shadow-check","canonical_anchor":"signed-cache-identity-telemetry-added-alongside-shadow-check","heading":"Signed-cache identity telemetry added alongside shadow check","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/signed-cache-identity-telemetry-added-alongside-shadow-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Signed-cache identity telemetry added alongside shadow check\n\nSigned-cache validation now also resolves an identity and reports it via a new telemetry event\n\n**Unclear.** What the resolved identity represents or is used for is not described.\n\n**What**\n\nThe existing signed-cache shadow validation (a background check that compares cache behavior without affecting results) now also resolves an identity asynchronously and fires a new telemetry event, `tengu_signed_cache_identity`, once that resolution completes, alongside the existing shadow-check event.\n\n**Why**\n\nThe finding does not say what this identity represents or what it's used for beyond being reported in telemetry.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}