Miteos Team · Reviewed 2026-10-24 · revision 1
Create a direct or open challenge, then share its specific invitation. The second participant reviews the frozen configuration and explicitly accepts. The same wallet cannot fill both seats. Competing acceptances are resolved atomically, not by who sees a button first.
Capacity is shared and reserved before admission. Daily counts, conservative neuron reservations, active concurrency, personal limits and anonymous practice controls can independently block entry. Verification has a separate ceiling protecting ordinary users. A successful reservation is not unlimited future access.
If capacity is unavailable, keep the invitation link and check the displayed UTC reset. Do not repeatedly create replacement challenges or send tokens before a valid admission ticket. Existing contests, support and claim/refund rights remain separate from new-entry limits.