Decentralised identity for mega-events is changing trust models

At a glance

What this is: This is an analysis of how decentralised identity could change trust for mega-events by using reusable digital wallets and verifiable credentials instead of repeated account-based verification.

Why it matters: It matters because large event ecosystems force IAM, identity verification and access governance to work across ticketing, mobility, payments and venue access without multiplying data exposure or verification friction.

Context

Mega-events create a temporary trust network that spans ticketing, border crossing, hospitality, payments and venue access. In that environment, centralised accounts, QR codes and repeated document checks become brittle because every interaction asks the same question in a different system: can this person be trusted?

The governance problem is not simply fraud prevention. It is proving ownership, eligibility and transfer rights with less data exposure, while keeping trust current across the full journey from purchase to entry to post-event services.

For IAM and identity architects, the article sits at the intersection of identity verification, selective disclosure and lifecycle trust. It is a better-fit model for fan journeys than for static enterprise login flows, because the credential itself must travel and be revalidated in multiple contexts.

Key questions

Q: How should organisers govern verifiable credentials for large events?

A: They should treat verifiable credentials as governed identity artifacts with explicit issuance, transfer, revocation and dispute rules. The main control question is not only who can present the credential, but who is trusted to issue it, when it becomes invalid, and how downstream verifiers should interpret it across ticketing, travel and venue access.

Q: Why do centralised ticketing systems create more trust friction at mega-events?

A: Because every step asks for the same assurance in a different system, which multiplies repeated checks, account recovery paths and data collection. That design increases exposure and makes it harder to prove ownership, eligibility and transfer rights once a ticket moves between holders or across services.

Q: What breaks when selective disclosure is not available for fan identity checks?

A: The organiser ends up collecting more data than each verifier actually needs, which increases privacy risk and makes fraud control harder to scope. Without selective disclosure, a border check, a hotel booking and a stadium entry event all push toward the same oversized identity record instead of the minimum proof required.

Q: How do teams know whether decentralised identity is improving event trust?

A: Look for fewer repeated identity checks, lower reliance on central account recovery, clearer transfer provenance and better separation between entry rights and broader personal data. If those outcomes are not improving, the wallet may be adding another interface without changing the underlying governance model.

Technical breakdown

Verifiable credentials turn a ticket into a proof object

A verifiable credential is a tamper-evident digital claim issued by one party, held by the user and checked by another party. In this model, the ticket is not a static QR code or account lookup. It can carry the match, seat, current holder and transfer rules as verifiable claims, while revocation lets the organiser invalidate the old credential when ownership changes. That changes the trust boundary: the verifier checks cryptographic proof and issuer status, not just a database record. The design is important because it reduces dependence on central account stores during peak demand, but it also shifts governance to issuance, revocation and verifier policy.

Practical implication: Treat the ticket as an identity credential lifecycle problem, not just a commerce or entry-control problem.

Selective disclosure reduces exposure without reducing assurance

Selective disclosure lets a person prove only the claim needed for the interaction. For example, they can prove age, travel eligibility or event entitlement without exposing their full birth date, passport number or broader identity record. That matters because mega-events involve many parties that need different levels of assurance, and over-sharing creates unnecessary privacy and breach exposure. The technical pattern is privacy-preserving by design, but it only works when each verifier asks for the minimum claim required and the issuer structures the credential with that granularity in mind. The control challenge is policy design, not just cryptography.

Practical implication: Define verifier-specific claim requirements so every step asks for the minimum proof needed.

Continuous trust checks keep credentials valid after issuance

A decentralised identity model is not complete if trust stops at login, ticket purchase or first scan. Continuous trust means the credential, device, transaction context and transfer state must remain valid as the interaction progresses. That is especially relevant in stadiums, where conditions change rapidly and different credentials govern entry, hospitality, media access and restricted zones. The operational shift is from one-time verification to ongoing validation of status and context. This is not a new authentication layer so much as a lifecycle model for access decisions that can change mid-journey.

Practical implication: Build revalidation points for transfer, device status and transaction context into the event journey.

Threat narrative

Attacker objective: The objective is to monetise illegitimate access or resell disputed ticket rights while bypassing ownership controls.

1. Entry occurs through centralised ticketing and verification workflows that rely on accounts, QR codes and repeated uploads, which create broad targets for fraud and phishing.
2. Credential abuse follows when resale, transfer or synthetic-account activity breaks the organiser's ability to prove who legitimately holds the ticket.
3. Impact appears as resale abuse, duplicated trust checks, privacy exposure and weaker control over who enters, pays and accesses restricted services.

Breaches seen in the wild

• SonicWall SSL VPN account compromises 2025: Attackers used valid credentials to log in to more than 100 SonicWall SSL VPN accounts across 16 environments in October 2025.
• Dropbox Sign breach 2024: A compromised back-end service account gave attackers Dropbox Sign customer data, including API keys, OAuth tokens and MFA information.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Decentralised identity for mega-events is really a lifecycle governance problem. The article is not just about better fan UX or stronger ticketing. It shows that ownership, transfer rights and revocation now behave like identity state, not one-time transactions. For practitioners, the key implication is that ticket governance should be designed as a credential lifecycle with explicit issuance, transfer and revocation rules.

Selective disclosure is the practical privacy control that traditional event systems keep missing. The article's core insight is that organisers do not need more data to get more assurance. They need fewer claims, better scoped to each verification point. That moves the problem from data collection to claim design, which is where identity teams, privacy teams and event operators usually diverge.

Continuous trust is the right operating model for multi-party event ecosystems. A single successful check at purchase or entry is not enough when the same person later books travel, enters restricted areas or receives post-event benefits. The broader lesson is that identity assurance must persist across context changes, because trust in a mega-event is not static. Practitioners should think in terms of revalidation windows, not isolated checkpoints.

Verified ownership will increasingly matter more than account possession in consumer-facing identity journeys. The model described in the article shifts emphasis away from central account recovery and toward portable, tamper-evident claims. That is a meaningful direction of travel for identity architecture because it aligns assurance with the specific right being exercised, whether that is entry, transfer or entitlement. Teams should expect more pressure to separate proof of ownership from proof of login.

Decentralised identity may reduce friction, but it does not remove governance obligations. Wallets and verifiable credentials still require issuer trust, verifier policy, revocation handling and dispute resolution. The practical consequence is that identity governance moves upstream into standards selection, credential semantics and operational accountability across ecosystem partners.

What this signals

Verified ownership changes the control plane for consumer identity. The important shift is not that a wallet exists, but that the right being exercised can travel with the person while remaining bounded by issuer policy and revocation state. For large events, that makes ownership, entitlement and transferability first-class governance objects rather than side effects of account management.

Mega-event programmes should expect decentralised identity to sharpen the split between proving a claim and proving a login. That distinction matters because many access journeys combine both, and legacy IAM controls often blur them until a dispute, transfer or fraud case exposes the gap.

For practitioners

• Define credential lifecycle rules Map ticket issuance, transfer, revocation and reissue as governed identity events, with clear ownership and verifier policy for each state change.
• Specify minimum claims per verifier Document exactly which claims each partner needs for entry, travel, hospitality or payments, and reject credential designs that over-disclose personal data.
• Design revalidation points Add status checks for transfer, device trust and unusual transaction context so verification continues after the first scan or purchase.
• Separate ownership proof from login proof Treat entitlement, ticket possession and account authentication as different controls, especially where the same person must move across multiple event services.

Key takeaways

• Mega-event identity systems fail when they rely on repeated, centralised checks that cannot preserve ownership or transfer context across the full journey.
• The article's core model is a fan-held credential that supports selective disclosure, revocation and reissue without forcing broad data sharing.
• For practitioners, the governance task is to separate proof of entitlement from account authentication and to keep trust active after the first scan.

Key terms

• Verifiable Digital Credential: A verifiable digital credential is structured identity data that can be checked cryptographically by a relying party. Instead of relying on visual inspection, the verifier validates issuer signatures and presentation rules, which gives the control a clearer trust basis than an image-based document.
• Selective Disclosure: Selective disclosure is the practice of sharing only the identity attributes needed for a specific decision. In credential-based systems, it reduces oversharing, lowers retention burden, and limits exposure when a verifier does not need the full record to make a trustworthy judgment.
• Continuous Trust: Continuous trust is an assurance model where identity and access are re-evaluated as conditions change, not just at login or issuance. It matters when credentials, devices or ownership can change during an interaction, because static validation leaves stale access in place.
• Digital Identity Wallet: A digital identity wallet is software that stores and presents credentials for a person or organisation. It is a portability layer, not an authorization system. The wallet moves verified proof between parties, while the relying party still has to decide whether the proof is sufficient for the requested action.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.