Ika Operator
v1.0.0Guide for operating Ika network nodes - validators, fullnodes, and notifiers. Use when deploying, configuring, monitoring, or troubleshooting Ika infrastruct...
⭐ 0· 81·0 current·0 all-time
byOmer Sadika@omersadika
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description map to the requested binaries and files: 'ika' and 'sui' are reasonable requirements for operating Ika nodes and integrating with Sui. No unrelated credentials, installs, or binaries are requested.
Instruction Scope
The SKILL.md and reference docs stay within node operator scope (configuring, key generation, running, monitoring, and recovery). They do include destructive recovery commands (rm -rf on DB paths) and admin actions (key backups, event cursor overrides) that are expected for ops but are sensitive and should only be executed intentionally. The docs also instruct pushing metrics to external endpoints and show examples that include credentials—these are operational but could leak data if misconfigured.
Install Mechanism
This is an instruction-only skill with no install spec and no downloadable archives; it does not write code to disk or fetch remote packages as part of installation, which is low-risk for install mechanism.
Credentials
The registry metadata declares no required environment variables and no primary credential. However, the configuration examples contain optional fields that accept sensitive secrets (AWS access keys, metrics proxy username/password, certificate/private-key paths). Those fields are legitimate for node operators but are optional; there is no unexplained request for unrelated credentials in the skill metadata.
Persistence & Privilege
always:false and user-invocable:true (defaults) — no elevated persistence requested. The skill is instruction-only and does not modify other skills or agent-wide settings.
Assessment
This guide appears to be what it claims: an operator manual for Ika nodes. Before using it, verify the ika binaries you install come from the official GitHub releases referenced in the docs. Treat any commands that remove directories (rm -rf) or change event cursors as destructive — run them only with backups in place. Keep all generated keys (especially root-seed.key) offline and backed up. Be cautious when configuring metrics remote-write URLs or state-archive object stores: those configs can contain credentials (AWS keys, usernames/passwords) and will transmit data to the configured endpoints. Confirm any external endpoints (metrics push URL, staking portal) are legitimate and under your control; do not paste secrets into example endpoints. Finally, because this is instruction-only, the skill itself cannot exfiltrate secrets automatically, but following its instructions could cause data exposure if misconfigured — proceed only if you (or your operator) understand and control the targets and secrets involved.Like a lobster shell, security has layers — review code before you run it.
latestvk972qd2q0jp7e0p57f99haj8fd83b8t0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🖥️ Clawdis
Binsika, sui