Creators

The problem with a guest list is not who gets in. It is that nobody checks what the people who got in gave back. It is a cost that appears on no line of the budget, because there is nothing to measure it with.

Here the exchange is set out — two posts a week tagging the venue, say — the system verifies on its own that it happened, and access unlocks at that point. No delivery, no access.

How it verifies, which is where the difficulty is

Verification works from screenshots, and the system treats its own reading as deliberately untrusted: it validates, stores a hash so the same screenshot cannot be reused, isolates the storage and flags the quality of every check. And nobody approves their own guest pass — that sits in the permissions, not in trust.

What was a hole becomes a channel

With the exchange measured, your guest list turns into a media channel with a real CPM, comparable to what you pay for reach anywhere else. And with two figures that exist nowhere else in this sector: the fulfilment rate per creator — how much of what was agreed actually arrived — and what each pass gave back, counting both the purchase that followed and the one that came recommended.

What this engine opens up next

Anyone can run a “share and win”. What almost nobody can do is check that it was shared, and that is where those campaigns fall over: prizes go out for reused screenshots, for posts deleted two hours later, or to people who never posted at all.

The verification engine already running is exactly that piece. With it, a challenge stops being a good-faith promise and gets a checkable condition: it happened or it did not, and the prize only goes out when the first one is true.

The campaigns themselves are not built yet. The engine is, and it is the hard part.

Where it is today

In production, at allaccess.es, with a community of 220+ creators across the Canary Islands and its own scoring. That community is not a software feature: it is the asset that goes on the client’s side of the table on day one.