Skip to main content
Status: Live (v1) — VAP v1 is operational. VAP v2 is validated (234 tests passing) but not yet deployed.
VAP exists because creator engagement needs to be trusted by more than the platform reporting it. If advertisers, creators, and the network are going to route value against participation, that participation has to be verifiable. VAP is the proof layer for participation. It helps Render Network Protocol distinguish real sessions from reported sessions, so engagement can be used with more confidence in campaign buying, creator economics, ranking, rewards, and settlement.

​
Why VAP Matters

Advertisers buy against engagement. Creators build around engagement. The network routes value around engagement. VAP exists so that engagement does not have to be taken on faith.

​
Advertiser trust

Brands need confidence that the participation around a creator is not falsified. VAP gives the network a stronger signal for advertiser-facing inventory.

​
Creator credibility

Creators should not have their economics determined by opaque or inflated metrics. VAP ties creator economics to verifiable sessions rather than platform-reported estimates.

​
Rewards and ranking

The network needs a fair basis for points, leaderboards, and payouts. VAP provides the verification layer underneath ranking and reward logic.

​
Settlement

Verified participation feeds into value routing. The economic cascade depends on having a credible input signal.

​
Protocol Mechanics (v1 — Live)

VAP v1 operates over a secure WebSocket connection. It is a bidirectional, cryptographic handshake between the Client and the Server (Verifier).

​
1. The Handshake

When a session begins, the client authenticates and establishes a secure channel. Client → Server (INIT) 
{
  "type": "INIT",
  "payload": {
    "appId": "sector-13",
    "wallet": "HuW...9zP",
    "timestamp": 1717171717
  },
  "signature": "Ed25519_Signature_of_Payload"
}
Server → Client (ACK) 
{
  "type": "ACK",
  "sessionId": "sess_88239123",
  "nonce": 0,
  "difficulty": 1
}

​
2. The Heartbeat (Pulse)

Every N seconds (dynamic based on trust score), the client sends a Pulse proving liveness and state continuity. Client → Server (PULSE) 
{
  "type": "PULSE",
  "sessionId": "sess_88239123",
  "nonce": 1,
  "delta": {
    "inputHash": "sha256_of_mouse_movements",
    "gameStateHash": "sha256_of_memory_snapshot",
    "score": 150
  },
  "signature": "Ed25519_Signature_of_Delta"
}

​
3. State Channels and Settlement

To scale to high concurrency, VAP uses state channels. Not every pulse is written to Solana.
  1. Off-chain aggregation: The VAP Verifier maintains a session ledger in an in-memory store. It verifies signatures and the hash chain (nonce N must follow N-1).
  2. Dispute window: The session is kept optimistic. If the server detects anomalies, it can flag the session immediately.
  3. On-chain settlement: When the session ends, the Verifier submits a settlement transaction to Solana. Only the result is written on-chain.

​
Integrity and Anti-Abuse

VAP is designed to make falsified participation harder to use as economic input. That matters because advertiser spend, creator revenue, and protocol rewards all depend on participation being credible enough to route value against.

​
Layer 1: Cryptographic Integrity

  • Signature verification: Every packet must be signed by the participant’s wallet.
  • Replay protection: Nonces ensure packets cannot be replayed.

​
Layer 2: Behavioral Heuristics

The VAP Verifier analyzes the inputHash and gameStateHash.
  • Entropy analysis: Human input has high entropy. Automated input patterns can be distinguished by their uniformity.
  • Timing analysis: Reaction times below physiological thresholds are flagged.
  • Reputation: Long-term wallet history affects trust score. Higher trust can mean longer pulse intervals.

​
Layer 3: Active Challenges

At random intervals, the server sends a CHALLENGE packet.
  • In-game overlays that must be responded to
  • Input sequences within time constraints
Failure to respond results in session termination and reputation adjustment.

​
Integration

Developers can integrate VAP into any HTML5 game using the VAP SDK. 
import { VAP } from '@555x402/vap';

const vap = new VAP({
  appId: 'sector-13',
  wallet: window.solana,
});

await vap.connect();

game.on('update', (state) => {
  vap.recordFrame({
    score: state.score,
    position: state.player.position,
    inputs: inputBuffer
  });
});

vap.on('challenge', (challenge) => {
  game.showOverlay(challenge);
});

​
VAP v2 — Validated Design (Not Yet Deployed)

VAP v2 is a validated research design. It is not deployed. This section documents the design direction. See VAP v2 Research for the full specification.
VAP v2 research is complete with 234 tests passing and all 5 attack trees validated as SECURE.

​
Key design changes in v2

Entity-agnostic participation Zero protocol components check entity type. No differential rates between human and AI participants. All staked participants are treated equally. Epoch-based system
  • Epoch duration: 6 hours (4 per day)
  • Batch auctions: Advertisers bid for attention credits within each epoch
  • Attention Credits: 1 AC = $0.001 USDC
Stake-based participation
  • Minimum stake: 55,555 $555
  • Stake weight: logarithmic formula capped at 5.0 to prevent whale domination
  • 7-day warmup, full weight at 90 days
The burn loop
  1. Burn $555 at oracle price to mint Attention Credits
  2. Advertisers bid ACs in epoch auctions
  3. Contributors earn ACs based on stake-weighted verified engagement
  4. ARP (10%) distributed from auction proceeds
ContributionProof 296-byte proof format containing session data, stake reference, and cryptographic signature. Entity-agnostic by design.

​
Validated security results

Attack VectorROIStatus
Sybil (identity splitting)-81.7%SECURE
Fabrication (fake engagement)-179.7%SECURE
Collusion (coordinated manipulation)NegativeSECURE
Eclipse (network isolation)NegativeSECURE
Griefing (economic disruption)NegativeSECURE

​
Governance trinity

  1. ve$555 DAO: Token-weighted governance for protocol parameters
  2. Algorithmic layer: Automated parameter adjustment within DAO-set bounds
  3. Alice layer: Real-time operational decisions within algorithmic bounds

​
Go Deeper

VAP v2 Research

See the full validated design specification.

Arcade Overview

See how VAP verification appears in the player layer.

For Advertisers

See why verified participation matters for campaign buying.

Security & Fairness

See the broader integrity model across the network.