Category: Community
Road to NATURE ONE 2027
🔊 Listen to this article
An audio recording is not yet available for this article.
Trust grows when people meet. The Eventhacker® Chain of Trust aims to make those personal connections traceable, while keeping identity, skills and access rights distinct.
A voluntary community field test is planned for NATURE ONE 2027. This is not an announced collaboration with the organiser. The Eventhacker® ID shown here is a concept/sample, not an official festival pass or permission to enter. The functions and processes in this article describe the planned system.

Meet in person, confirm identity
In a crew, it matters who you are actually dealing with. A profile name alone does not answer that question. The Chain of Trust therefore starts with a personal encounter: two people voluntarily confirm which profile belongs to which person.
The confirmation is intended to make a narrowly defined statement: “I have met this person and associated this profile with them.” It is neither a guarantee of future behaviour nor an official identity document. Mutual confirmation consists of two independent decisions.
Trust paths have a direction
Every confirmation has a sender and a recipient. If A confirms B's profile and B confirms C's profile, a traceable path emerges:
A → B → C
This path does not mean A personally knows or has confirmed C. It shows the contacts through which a connection arises. Trust is not automatically passed along. Neither a long path nor a large number of confirmations establishes an objective measure of a person's worth.
Skills remain a separate layer
Confirming identity says nothing about someone's ability in lighting, networks, rigging or electrical engineering. Skills should be recorded separately. It must be clear whether a claim is self-described, confirmed by others or supported by specific evidence.
The skills on the sample are design examples. They do not replace qualifications, instruction or assessment. The people responsible remain in charge of assigning actual tasks.
Confirmations must be revocable
An incorrect association must be correctable. Revocation is therefore part of the concept: anyone who has issued a confirmation should be able to withdraw it. The system must clearly show a confirmation's current status and date. Revoked evidence must no longer appear valid.
A lost card or compromised account must also allow the link to be blocked or replaced. The card alone must not act as a permanent guarantee of trust.
Privacy belongs in the design
Participation should be voluntary. Users should decide who can see their profile details and connections. Not every personal encounter belongs in a public social graph. Data minimisation, clear visibility settings and understandable correction and deletion options are therefore prerequisites for the field test.
Private contact details and sensitive credentials do not belong in a freely readable QR code. A future service must check access rights and current consent rather than revealing information simply because someone possesses a card.
QR and NFC connect card and profile
QR codes and NFC are intended as convenient ways to open the associated profile. They are not security checks and do not create trust themselves. Before a confirmation, it must be clear which profile has been opened and exactly what statement is being made.
The QR and NFC elements on the card shown are design samples only. No production verification service or functioning NFC chip is claimed.

Neither a ticket nor a backstage pass
An Eventhacker® ID is intended to support cooperation within the community. It does not automatically grant access to a festival, stage, technical area or workplace. Tickets, accreditations and work authorisations are issued independently by the respective responsible bodies.
The road to 2027
The planned community field test at NATURE ONE 2027 should show whether personal confirmations and understandable trust paths help in everyday practice. The starting point is a small voluntary group, clear rules and honest feedback: what do participants understand? Where do false expectations arise? What data is actually needed?
The festival name describes the planned context of this independent initiative. No official partnership, organiser approval or recognition of the card is claimed. Technical, organisational and privacy requirements must be clarified before practical use.
Confirm identity. Assess trust consciously. Check skills separately. And always be clear about what a card can do.