ClawHub

NexusWeb3 Safety & Compliance

v1.0.3

Read-only API reference for NexusWeb3 safety protocols 21-30 on Base mainnet — kill switch status, KYA verification, audit logs, bounties, licensing, milesto...

⭐ 0· 98·0 current·0 all-time
by@nexusweb3dev
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 claim a read-only API reference for safety protocols; SKILL.md provides contract addresses, view function examples, and read-only usage. No unrelated env vars, binaries, or install steps are requested — the requested surface matches the stated purpose.
✓
Instruction Scope
Instructions only show how to query on-chain state and provide Solidity / call examples. They explicitly state write operations require a separate 'nexusweb3' financial skill and operator key. The skill does not instruct reading local files, environment secrets, or posting data to third-party endpoints beyond the declared RPC.
✓
Install Mechanism
No install spec and no code files — instruction-only. This minimizes risk because nothing is downloaded or written to disk by the skill itself.
✓
Credentials
No required environment variables, credentials, or config paths are declared or referenced. The SKILL.md does not request secrets. Write-capable actions are explicitly deferred to a different skill that would need keys.
✓
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent system privileges or to modify other skills' configurations.
Assessment
This skill is consistent with its read-only purpose and does not request credentials or install code. Before using, independently verify the contract addresses and GitHub repository (to avoid typo-squatted mirrors) if you will rely on them for production actions. Be cautious about installing or enabling the separate 'nexusweb3' financial skill mentioned for write operations — that one will require signing keys and should be evaluated separately. If you plan to perform transactions, never supply private keys or operator credentials to a skill unless you trust and have audited the signer integration.

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

latestvk97cgesekz0fxv4tdmfhqee2v1832xzv

License

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

Comments