ecashprotocol_skill

This skill helps you mine ECASH on Solana by guiding agents through reading puzzles, normalizing answers, decrypting blobs, and triggering on-chain solves.
  • Python

1.2k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill ecashprotocol

  • _meta.json462 B
  • SKILL.md32.8 KB

Overview

This skill lets an agent participate in the Ecash proof-of-intelligence mining protocol on Solana by solving cryptographic riddle-poems to earn ECASH SPL tokens. It bundles the API endpoints, normalization rules, scrypt decryption parameters, and on-chain commit-reveal steps needed to verify answers and claim rewards. Use it to automate puzzle discovery, local verification, and transaction orchestration for mining.

How this skill works

The agent fetches unsolved puzzles from the Ecash API, reads the poem, formulates and normalizes an answer, and attempts to decrypt the puzzle blob with scrypt using the normalized answer as the password. If decryption yields valid JSON (salt and proof), the agent constructs a commit hash and runs the on-chain sequence (register → enterBatch → pick → commitSolve → revealSolve) to claim ECASH rewards. The skill includes RPC, program IDs, token mint, and exact cryptographic parameters for deterministic behavior.

When to use it

  • Automate discovering and filtering unsolved puzzles from the Ecash API
  • Validate answers locally by decrypting puzzle blobs before spending gas
  • Automate the full on-chain commit-reveal flow to claim ECASH rewards
  • Integrate an agent into a mining pipeline that handles staking, gas checks, and balance management
  • Archive or audit historical protocol data using the provided endpoints

Best practices

  • Always normalize answers exactly as specified (lowercase, alphanumeric+spaces, collapse spaces) before attempting scrypt decryption
  • Test decryption locally to confirm answers before committing on-chain to avoid wasted fees
  • Ensure the wallet has required ECASH and SOL—enterBatch burns ECASH and revealSolve is gas-costly
  • Respect the wait requirement: reveal must occur at least one slot after commit to avoid rejection
  • Cache API responses (puzzles, idl, stats) for short intervals to reduce load and latency

Example use cases

  • An agent scans /puzzles for unsolved items, tries candidate answers, and only commits when local decryption returns salt and proof
  • A mining bot normalizes human-provided guesses, runs scrypt with the prescribed N/r/p/keyLen/salt, and automates commit/reveal transactions
  • A researcher archives puzzles, leaderboard, and activity streams for historical analysis using the API endpoints
  • A light client verifies a puzzle locally and prepares proof arrays for revealSolve without exposing secrets

FAQ

Use N=131072, r=8, p=1, keyLen=32 and salt="ecash-v3-{puzzleId}" where {puzzleId} is the numeric id.

How must answers be normalized?

Convert to lowercase, remove non-alphanumeric characters except spaces, collapse multiple spaces to one, and trim leading/trailing spaces.

How do I avoid spending gas on wrong answers?

Always decrypt the blob locally with scrypt and the normalized answer; only commit on-chain when decryption returns valid JSON containing salt and proof.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational