Service console

Service console

Connecting…
Agents in the tree
Staked in the registry
Verified requests
Slashed, paid out

Live requests

connecting

Rows show nullifiers, never callers. A repeated message id with a different request is a violation: the server recovers the agent's secret and starts a slash.

This server

Epoch
—
Stake per message
—
Slash share to the slasher
—
Slashing on this server
—
Violations seen
—

Protect your own API

A service is configured in code, not here. The limit per epoch is whatever stake each agent put up; you choose a minimum by rejecting proofs from the registry you do not accept.

app.use(quotaExpress(new QuotaVerifier({
  serverId: "my-api",
  vkey, roots: new RegistryRootChecker(client, REGISTRY),
})));

See the docs for the 10-minute quickstart.

Slash history

Claims go through commit then reveal (not BTX)
TimeAgentCommitRevealState
Needs the demo server feed. Total on-chain: —. Full history on the explorer.