Isaac Tools
Account

Verification

Verifiers run skills on their own robots and report the result on-chain. A skill becomes verified after the required number of passing runs (three by default) from different verifiers.

  1. Stake. On Verify, stake the verifier stake (25 USDG by default) with stakeAsVerifier.
  2. Pick a skill that your robot's class supports. You cannot verify your own skill.
  3. Run the scenario through the agent. It loads the skill, runs the scenarios from tests/scenarios.json, records a session tagged verification, computes the pass metric from the recording, and returns passed and evidenceHash = keccak256(recording).
  4. Submit with submitVerification(skillId, robotId, passed, evidenceHash). One submission per verifier per skill, one per robot.

Every submission, pass or fail, earns the verification reward. Once a skill is verified the verifier set freezes and the verifiers split the verifier pool from its sales; claim it from your account. The recording stays available for disputes.