a2a-Market-Stake-Freeze
PassAudited by VirusTotal on May 11, 2026.
Overview
Type: OpenClaw Skill Name: a2a-market-stake-freeze Version: 0.2.0 The skill bundle contains metadata and architectural instructions for implementing a stake freezing and slashing system for Agent-to-Agent (A2A) transactions. The instructions in SKILL.md provide a standard software scaffold, including project layout and API contracts (e.g., freeze_stake, slash_stake), without any evidence of malicious intent, data exfiltration, or prompt injection attacks.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If implemented incorrectly, the policy could lock, release, or slash participant stake in ways that affect money, collateral, or market participation.
The skill instructs implementation of stake mutation and automatic penalty decisions. This is aligned with the stated stake-policy purpose, but it is high-impact business logic that should have strong approval, testing, audit, and rollback controls in the consuming project.
`slash_stake(lock_id, reason, evidence)` applies penalty and emits incident log. `evaluate_timeout_locks(now_ts)` handles automatic release/slash decisions.
Before using it in production, require explicit authorization boundaries, deterministic tests, audit logs, evidence validation, and a safe dispute or rollback process for slashing decisions.
A user might assume there is reviewed runtime code and test coverage when the supplied package is actually instruction-only.
The provided manifest contains only SKILL.md and no runtime files, so the claimed implementation and tests are not present in the reviewed artifact. This appears to be a documentation/provenance gap rather than evidence of malicious behavior.
Status: implemented in local runtime package. Primary code paths: `runtime/src/domain/stake-policy.js` ... Validation: covered by `runtime/tests` and `npm test` in `runtime/`.
Do not rely on the referenced runtime implementation or tests unless those files are separately supplied and reviewed.