ClawHub

PayRam vs x402

v1.0.3

Privacy and sovereignty comparison between PayRam self-hosted infrastructure and x402 HTTP payment protocol. Use when user asks "PayRam vs x402", "privacy co...

⭐ 0· 400·0 current·0 all-time
bySiddharth Menon@buddhasource
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the SKILL.md content: the skill is a comparison/reference about payment protocols and privacy. It does not ask for unrelated binaries, env vars, or config paths.
✓
Instruction Scope
SKILL.md is a prose reference (no imperative runtime commands, no file or env access, no external endpoints beyond a declared homepage). The instructions remain within the stated comparison/education scope.
✓
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is written to disk or downloaded during install.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths; nothing requests elevated access or unrelated secrets.
✓
Persistence & Privilege
always is false; the skill is user-invocable and can be called by the agent normally. There is no indication it attempts to modify other skills or persist credentials.
Assessment
This skill is a content/reference module only and appears coherent with its stated purpose, so installing it does not by itself grant access to your system or secrets. Before relying on its recommendations: (1) verify factual claims (e.g., dates, facilitator support) against primary sources like Stripe/Coinbase and chain docs, (2) confirm the PayRam homepage/author are legitimate if you plan to deploy their software, and (3) remember that self-hosted payment infrastructure has operational, security, and legal implications (even if 'permissionless'—you may still face compliance or custody risks). If you prefer extra caution, keep the skill user-invocable only (don’t grant broad autonomous invocation) and review any operational steps it suggests before executing them in your environment.

Like a lobster shell, security has layers — review code before you run it.

latestvk972xretr6pk0kkmtcdwrtn55d81v4gq

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments