ClawHub

WEB3 Integration

v1.0.0

Integrate apps with blockchain providers, wallets, and contract calls safely.

⭐ 0· 71·0 current·0 all-time
byMauricio Z.@mzfshark

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mzfshark/axodus-web3-integration.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "WEB3 Integration" (mzfshark/axodus-web3-integration) from ClawHub.
Skill page: https://clawhub.ai/mzfshark/axodus-web3-integration
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install axodus-web3-integration

ClawHub CLI

Package manager switcher

npx clawhub@latest install axodus-web3-integration
Security Scan
Capability signals
CryptoRequires walletRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the instructions: steps focus on provider/signer selection, chain validation, wrapper modules, logging/audit, and tests. Nothing in the skill requires unrelated binaries, cloud credentials, or system access. (Minor metadata mismatch: SKILL.md claims 'RedHat Dev' while registry owner ID differs; this is a provenance note but does not affect capability alignment.)
✓
Instruction Scope
SKILL.md instructions stay within web3 integration scope: they validate chain/address/ABI, recommend environment-based RPC configuration, prevent storing secrets in repo, and explicitly forbid requesting/pasting private keys into chat or defaulting to mainnet.
✓
Install Mechanism
This is an instruction-only skill with no install spec and no code files to execute; therefore there is no installation risk from downloads or package installs.
ℹ
Credentials
The skill requests no environment variables or credentials in metadata (which is appropriate), and the instructions correctly advise using env/secrets managers for RPC URLs and keys. Users should ensure secrets are provided via secure secret management rather than chat or code. The lack of declared required env vars is reasonable but means safe secret handling depends on the implementer.
✓
Persistence & Privilege
always:false and default model invocation are set (normal). The skill does not request permanent presence or system-wide configuration changes.
Assessment
This skill appears coherent and low-risk, but before installing or using it: (1) Verify the provenance/author if you require vendor trust (SKILL.md says 'RedHat Dev' but registry owner differs). (2) Never paste private keys into chat—follow the skill's rule to use a secrets manager or environment variables. (3) When implementing, point RPC URLs to trusted providers and limit any server-side signing flows; require explicit approval and secure key storage if server signing is used. (4) Review any generated code (wrappers, logging) and run the suggested tests locally (including a local chain simulation) before deploying to production.

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

devvk9739tew5zc722780tqjv1sw6s85fjztlatestvk9739tew5zc722780tqjv1sw6s85fjzt
71downloads
0stars
1versions
Updated 3d ago
v1.0.0
MIT-0
Mauricio Z.@mzfshark
devlatest
Download

SKILL: web3-integration

Purpose

Integrate a frontend/backend with blockchain interaction (wallet connect, provider configuration, contract calls) using safe, testable patterns.

When to Use

  • A dApp needs to read/write contract state.
  • A backend service must index or react to on-chain events.
  • Wallet connection UX and chain gating is required.

Inputs

  • stack (required, enum: ethers|viem|web3js): preferred client library.
  • chain (required, string): chain name + chainId.
  • rpc (optional, string): RPC URL reference (env/config), not hardcoded.
  • contract_address (required, string).
  • abi_source (required, string): ABI path/artifact reference.
  • wallet_flow (optional, enum: injected|walletconnect|server_signer).

Steps

  1. Validate chain/contract coordinates (chainId, address format, ABI match).
  2. Set provider/signer flow:
    • frontend: user wallet signer
    • backend: server signer only when explicitly required and keys are secured externally
  3. Implement contract client wrapper:
    • typed interfaces when possible
    • explicit timeouts/retries for RPC
  4. Add chain gating:
    • refuse wrong chain
    • prompt network switch (frontend)
  5. Add logging/audit hooks for write operations.
  6. Add tests:
    • unit tests for wrapper
    • local chain simulation when available

Validation

  • No secrets stored in repo (keys only via secrets manager/env).
  • Wrong-chain behavior is safe (no accidental writes).
  • Errors are handled deterministically (retry policy is explicit).

Output

  • Wrapper module path(s)
  • Environment variable contract (what must be configured)
  • Validation commands (tests/build)

Safety Rules

  • Never request or paste private keys into chat/output.
  • Never default to mainnet.
  • Avoid “auto-sign” server flows unless explicitly required and approved.

Example

Input:

  • stack: viem
  • chain: base:8453
  • contract_address: 0x...
  • abi_source: artifacts/MyContract.json

Output:

  • src/web3/client.ts with chainId checks and a typed contract instance.

Comments

Loading comments...