Wallet credentials need a verifiable timeline
A digital identity wallet can hold education credentials, professional authorisations, and attestations issued by public or private organisations. A signature proves who issued a credential, but a timestamp adds evidence of when it existed and when it was revoked or updated. Keeping those events independently verifiable helps relying parties distinguish a current credential from an old copy.
Designing for long-term verification
Wallet ecosystems should preserve the signed credential, its certificate chain, revocation evidence, and the timestamp token together. RFC 3161 timestamps can anchor issuance and status snapshots without exposing the underlying personal data: the timestamp authority receives a hash, not the credential. This separation supports privacy by design while creating an audit trail that remains useful across providers.