No maker code runs with value attached
A quest is data produced by our compiler and run by our own engine. Minigame code only runs in a sandbox, and its score counts only through a one-time ticket the server issued.
Developer platform
By invitationVerified companies build quests and HTML5 minigames with our SDK, and players open them inside the Seekprotocol app. Every build is signed, checked, reviewed and sandboxed before it reaches a single player.
Deployed on 7 November 2026 and switched off for the public. Every component is running, and only tester accounts can see maker content while the first companies are onboarded.
Principles
A quest is data produced by our compiler and run by our own engine. Minigame code only runs in a sandbox, and its score counts only through a one-time ticket the server issued.
Progress, rewards, risk and payouts are decided in one database. The edge workers accept, test, store and serve builds. They can refuse things. They can never grant anything.
Every build is signed with the maker's own key, checked automatically, reviewed by a person where anything is new, and then signed by Seek. The app verifies that signature before it runs anything.
Players are gated by a platform switch and a tester list. The console sits behind a second access layer with an allow list, on top of its own login and a second factor for staff.
Architecture
Makers and Seek staff work in Store Connect. The edge accepts, checks, stores, signs and serves builds. The core holds every decision and runs quests for players. Players reach maker content only through the app.
Release
At play time
Isolation
We assume a minigame could be malicious. So five independent controls sit around it.
A separate subdomain per game. Two makers never share a hostname or a player id.
Scripts and nothing else: no cookies, no storage, no pop-ups, no navigation.
Camera, microphone, location and payment are switched off.
Every file is pinned by hash. Anything else is a 404.
A valid launch token is required. An origin alone is never trusted.
Privacy
Statistics for makers are aggregated. Any group smaller than five players is shown as fewer than five.
Operations
Staff can stop one quest, one maker or every maker quest. Caches expire within 30 seconds.
A job compares a new release with the one before, and pauses it if players are refused far more often.
Crashes and logs per game and version, scrubbed twice before they are stored.
Before it opens
In progress
Company enrollment modelled on an app store's developer program, with a second factor for every maker account.
Open
The agreement is a draft. The lawyer-reviewed version replaces it before makers are let in.
Decision
The worker that writes the transparency log head to Solana is built. Switching it on is a decision still to be made.
Two steps
First the platform, then rewards for maker quests, as two separate decisions.
Build with us
We are onboarding the first companies by invitation. Tell us what you want to build.