ZeroDust Chain Exit

Do not use this skill with real funds until you can verify the backend and codebase. Specific steps to take before installing or using: - Verify the project: ask the publisher for a canonical homepage or public source repo (GitHub) and review the server code and docs. The skill currently lists no homepage/source and points to a railway.app backend—this is not a proof of legitimacy. - Validate supported chains: confirm the chain IDs and names the service claims to support; several names/IDs in the SKILL.md look uncommon or fictional. Try a tiny test amount first. - Protect keys and signing: never paste private keys into the agent. Ensure signing is done via a secure wallet UI (e.g., MetaMask, hardware wallet) that only signs the intended typed data. Prefer in-wallet signing over copy-pasting signatures where possible. - Question pre-signed revocation: ask the operator to explain why a pre-signed revoke is required, how long signatures are valid, and whether the revoke signature can be replayed or misused later. Prefer a flow where revocation is executed deterministically and immediately, or better yet where the revoke is controlled by the user. - Limit API key exposure: treat ZERODUST_API_KEY as highly sensitive — possession appears to allow batch/agent sweeps. Only provide it to agents you fully trust and consider using a scoped/test key first. - Ask for independent audits or references and for an official domain and contact/support channels. If these are not provided, avoid using the skill for any significant balances.