Velocity is RP1’s workflow layer for scripted and intent-based actions that do not fit a single synchronous bank message.
Public model
- A runtime and action are selected from an allowlisted set.
- The intent carries a bounded payload, timeout, creator, and lifecycle state.
- Synchronous Wasm operations can return a result in the same transaction path.
- Bitcoin and Solana-style operations are asynchronous and settle through InstaWrap and relayer workers.
- Queries expose supported runtimes, intent state, creator/status indexes, and parameters.
The EVM precompile at the documented Velocity address provides a Solidity-facing facade for supported methods such as runtime discovery, execution, and bridge-address lookup. Treat the exact ABI and gas behavior as versioned source contracts.
Safety boundary
Velocity is not a Bitcoin script VM, a Solana runtime emulator, or an unbounded arbitrary-call router. Payload-size caps, timeout caps, executor authorization, replay protection, idempotency, and failure acknowledgement are part of the public protocol boundary.
Use programmable workflows and EVM integration for composition patterns.