GripPilot. Prove. Own.
Grip is a physical-AI data market: you demonstrate manipulation skills to robots by piloting a simulated arm, physics proves the demonstration is real, and the proof is recorded to your wallet. Here is the whole loop, step by step.
Pick a task
12 missions, 2 robotsTwelve manipulation missions across two arms: a Franka Panda and a UFactory xArm7 straight from MuJoCo Menagerie, DeepMind's library of research robot models. Each task states its goal and what it pays: 50 points for closing a box, up to 150 for the hardest grasp-and-lift. Harder manipulation, more points.
Success is a physics condition
Every task defines its win as a condition on the simulated world, “the lid ends closed” or “the can ends above the pedestal”, never as a screenshot or a claim.
A legal starting envelope
Each task also defines where objects may start and requires the arm at rest, so a run can't begin half-done. The server enforces this before anything else.
Pilot the robot
MuJoCo in your browserThe whole simulator runs in your tab: MuJoCo, the physics engine used across robotics research, compiled to WebAssembly. No install, no GPU, no account. The keyboard drives the gripper through inverse kinematics.
The controls
Arrow keys translate the gripper, E and D raise and lower it, Q/W/A/S/Z/X rotate the wrist, Space opens and closes the fingers.
Everything is recorded
While you pilot, the browser logs your exact control input at every physics step. That log, not a video or a score, is the demonstration you submit.
Physics verifies
Bit-for-bit replayYour submission is three things: the initial state, the full control log, and the final state you claim. The server trusts none of them: it replays your log in the exact same MuJoCo binary your browser ran, and compares.
Admission control
Before any replay, the claimed initial state must sit inside the task's legal envelope. Claim the box began closed, or hand the arm free momentum, and the run is rejected before the physics even runs.
Zero tolerance
The simulator is deterministic, so an honest run reproduces exactly. The accepted difference is zero, on every coordinate: one bit off and the run is rejected, with the first divergent step named.
Fast
A five-minute episode is thousands of physics steps; the server re-simulates them in about a second before deciding.
Judged on the server's state
The success checker runs on the state the server computed, never on your claim. The verdict is PAY or REJECT: every point is earned, not claimed.
Own your data
One transactionA proven run ends in a single transaction on the GripData program, on Solana mainnet. You keep the proof; the ledger keeps the score.
A Data ID, recorded to you
The trajectory is hashed and that hash becomes the Data ID: an onchain account created in your name. One hash, one record, forever.
Metadata fully onchain
The program stores the task, points and sequence number in the record itself. No IPFS, no external host, nothing to go offline.
Airdrop points
The same transaction credits your points, weighted by difficulty. Points will weight a future token distribution (Phase 3 of the roadmap).
Free for the pilot
Piloting is free and the operator pays the transaction fees. You connect a wallet because the run is recorded to you, not to an account we hold.
Check it yourself
The ledger is public stateNothing above asks you to trust a dashboard. The counters on this site are live reads of the program, and the same reads are one call away from any terminal:
solana account AkLzcm8cBTufEFhjmE9BNRQZsWf5Yh84R2Ri2mzofNAQ \ --url https://api.mainnet-beta.solana.com
Demo records and contributor totals live in program accounts anyone can read. Program: AkLzcm…zofNAQ on Solscan
What we don't claim
Stated plainlyThe physics check proves the trajectory is real, not that a human produced it: per-wallet rate limits and movement analysis are on the roadmap. The verification server is the only record authority in this version: physics decides, the operator submits the transaction. And there is no token today; the points ledger accrues on mainnet now, the distribution comes later.
Five minutes to your first Data ID.
Pick a mission, fly the arm, hit Verify. Prefer the deep technical dive? Read the docs →
Browse tasks →