verifysignature

What it is

verifysignature is a Verus RPC call that checks whether a signature is valid for the claimed identity and data hash. You pass in the signer's i-address, the data hash (in this project, the mmrroot), the signature block, and the VDXF key it's bound to. The daemon returns a boolean.

The call is public, read-only, and stateless. It runs against any Verus node — your own, or a public RPC endpoint like api.verus.services. No authentication, no rate limits, no account creation.

In the viewer, this is step 4 of the six-step verification theatre. The viewer calls verifysignature live against mainnet and streams the result as you watch.

Why it matters

Any system that produces signed assertions needs a way for third parties to verify them independently. On most platforms, verification requires an SDK, an API key, a specific library, or trust in the issuer's infrastructure. On Verus, it's a single RPC call that any node can answer.

This makes verification accessible to autonomous agents. An AI agent evaluating a credential, a supply chain robot checking a provenance claim, or a smart contract on another chain can call verifysignature and get a cryptographic yes/no — no OAuth flow, no API key management, no rate limit negotiation.