Blockchain Zoo (@blockchainzoo) header
Blockchain Zoo (@blockchainzoo) profile picture

Bringing Clarity to the Blockchain Jungle

global
Joined June 2017
Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)Photo by Blockchain Zoo (@blockchainzoo)
We just closed the first ZooBC 2.0 rewards period: 597 ZBC allocated to 13 people for bug reports, feedback and forum activity. Period two is open right now. Test it, break it, tell us what is wrong, earn ZBC. Join: t.me/zoobc_official #ZooBC #GiveawayAlert #blockchain
🤖 Made with AI
71
Blockchain Zoo retweeted
ClawHub's sandbox + allowlist is the right approach. Agent skill supply chain security is underrated — malicious skills can exfiltrate data, escalate privileges, or pivot laterally, just like malicious npm packages. Verify before you run. #OpenClaw #AIAgents #Security
5
1
6
62
(1/6) Your OpenClaw instance is only as safe as the skills you install. And in March, 1,467 malicious skills proved the bar for "trusting" a marketplace is way too low. 🧵
1
1
39
(5/6) Step 2-4: VirusTotal scan → Permission audit → Sandbox test. Free tools, manual review, isolated environment. None of these alone are foolproof. Together they work.
1
1
23
(1/6) ClawGo shipped as a dedicated handheld for OpenClaw agents. Five more manufacturers followed. "Harness lock-in" is the play: buy hardware, stay locked. Except one thing they can't control: your workspace files. 🧵
1
29
(5/6) SaaS-only stacks: hostage to API changes, sunset risks, vendor pricing. Proprietary frameworks: locked to one runtime. OpenClaw bundles: file-based, framework-portable, device-immune.
1
14
(1/7) The email loop that sent 156,000 messages had zero code vulnerabilities. It had a config vulnerability. OWASP's new AIVSS framework catches those. 🧵
1
14
(6/7) This is the framework language your security team needs. Instead of "Is this agent safe?" you now say "This deployment scores 2/10 on Autonomy (well-gated), 4/10 on Tool Scope (explicit allowlist), 2/10 on Context Integrity (Git-backed), 3/10 on Observability (cost-monitored)."
1
16