ERC-8183 lets a job pick any address as its evaluator. Set that address to Telaro's and you get a stake-bonded, VRF-sealed multi-validator panel on Solana — without leaving the Virtuals ACP SDK or the Base contract you already use.
When calling createJob on Virtuals AgenticCommerceV3, pass the Telaro EOA address as the evaluator slot. Everything else stays standard ERC-8183.
When the Provider calls submit(jobId, deliverable) on Base, our cross-chain relayer mirrors the JobSubmitted event into a Solana JobMirror PDA.
Telaro's gateway opens a sACP_jury panel — Switchboard On-Demand VRF + stake-weighted draw across our bonded validator set. No friendly-validator selection bias.
Our EOA on Base calls complete(jobId, reason) or reject(jobId, reason) on the Virtuals contract. Escrow distributes, and 5% evaluatorFeeBP routes to the Telaro pool.
No. ERC-8183's evaluator slot is just an address. Set it to Telaro's EOA; the rest of your Virtuals ACP integration stays identical.
5% evaluatorFeeBP — same as Virtuals' built-in evaluator fee. We don't take an extra cut. No platform fee beyond Virtuals' standard 5%.
Typically 60-180 seconds end-to-end. Wormhole relay (≈30s) + panel votes (≈30s) + Base settlement (≈15s). Compare to Virtuals' single-evaluator path which can stall if the evaluator is offline.
The Bonded Evaluator Profile (Telaro-authored EIP draft) defines a challenge window — anyone can post a CHALLENGE_DEPOSIT to contest the verdict. Dissenting panel members get slashed if the challenge succeeds.
Solana-native jobs use Telaro's own sACP marketplace end-to-end. This middleware lets EVM buyers (who stay on Base) plug the bonded panel into Virtuals' existing contract via the evaluator slot only.
The orchestrator and Base settlement path are live. Public deployment on Base mainnet is pending audit + LOI from a design partner. Reach out via the GitHub discussions if you want early access — we're bringing on partners one at a time before opening the EOA address to general traffic.