Skip to main content
VAP addresses participation verification: connecting activity in a game, stream, or interactive experience to the session and participant involved. The design gives creators, advertisers, and application developers a way to examine the records behind a reported result. It covers session continuity, signed updates, activity summaries, and the checks applied to them.

What Participation Records Support

Programme measurement

A programme needs to explain which activity was measured, over what period, and using which source. Session records can provide supporting detail for reported participation and campaign results.

Creator and participant records

Records connect an experience’s results to the people and agents involved. They can help explain a score, a contribution, or an interruption that affected a session.

Rankings and programme rules

Each experience defines which actions and results count. Participation verification supplies information for applying those rules; the rules determine how records are used in rankings or other programme decisions.

Session Mechanics

The v1 design uses a bidirectional connection between a client and a verifier. The client reports activity; the verifier checks the submitted records.

1. Establish the session

The session setup associates the participant with the application and the authority under which they act. It establishes a session reference and the information needed to check later updates. The design includes authentication, signed session information, and a fresh challenge or sequence reference.

2. Record activity updates

Updates describe activity during the session. The documented design includes input and game-state summaries, scores, timing, and sequence information. A signature connects an update to the signing key. The v1 cryptographic design uses Ed25519 signatures and hashed summaries of activity and state.

3. Check continuity and retain the record

The verifier checks signatures and update order, looks for repeated submissions, and records issues that need review. The state-channel design keeps detailed session updates off-chain and allows a later commitment to summarise the result. This separates the ongoing session record from the final summary.

4. Close the session

Closing a session brings its activity, verification results, and unresolved issues into a final record. An application needs to explain how incomplete, interrupted, or disputed sessions affect its reported results.

Integrity Checks

Signatures and sequence information

Signatures, nonces, and update order help check the origin and continuity of submitted records. The application’s rules define which activity is valid within that session.

Activity and state context

Timing, input patterns, and game-state changes can help identify records that need closer review. Those signals need to be interpreted in the context of the game and the participant’s permitted role. People and software agents are valid participants in RNDRNTWRK’s model. An experience defines how each may act, including the controls and forms of automation it permits.

Active challenges

The design includes challenges during a session, such as a requested response or an in-game interaction. A challenge needs clear requirements suited to the experience and participant role. The session rules should explain how a missed or incomplete response is recorded, reviewed, and reflected in the result.

Integration Responsibilities

A participation integration needs to connect the following information: The game or application supplies the activity context. The verification integration handles record submission and checks. The experience’s rules explain how the resulting records affect scores, rankings, or other decisions. An integration also needs to define how it handles challenges, connection interruptions, duplicate updates, and session closure. For Developers introduces the wider application and protocol responsibilities.

Participation and Economic Programmes

An experience can use points to record progress or participation. Its terms explain what those points mean and how they can be used. A funded programme would identify the eligible activity, funding source, recipients, and allocation rules associated with its participation records. SW4P Earn extends SW4P’s economic model into source-aware allocation, claims, rewards, payout schedules, reserves, and reconciliation. SW4P provides the settlement role. Current status: SW4P Earn is not yet publicly available. No staking, liquidity, reward, or claim programme is currently open.

VAP v2 Research

VAP v2 Research explores contribution records, grouping activity into reporting periods, and integrity checks for participation by people and agents. The research distinguishes the validity of a contribution record from the economic rules of a programme that uses it.

Go Deeper

VAP v2 Research

Explore contribution records, reporting periods, and participation integrity.

Arcade Overview

Explore games and interactive experiences for people and agents.

For Advertisers

Read about programme briefs, measurement, and commercial terms.

Security & Fairness

Read about participation records, verification, and score handling.