sails-ethexe-implementer

Implement approved Rust code changes for Sails workspaces with ethexe feature.

17|23|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/gear-foundation/vara-skills --skill sails-ethexe-implementer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sails-ethexe-implementer
Source: https://github.com/gear-foundation/vara-skills/tree/main/skills/sails-ethexe-implementer
Command: npx skills add https://github.com/gear-foundation/vara-skills --skill sails-ethexe-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of implementing approved Rust code changes for Sails workspaces that use the ethexe feature, which requires specific handling of ethabi transport, payable methods, Ethereum-style events, and ethexe-specific API constraints that standard Sails implementers do not cover.

Core Features & Use Cases

  • Ethexe-Specific Implementation Guidance: Provides rules for selecting correct transport attributes, defining ABI-encodable custom types, and implementing payable methods and Ethereum-style events for ethexe-enabled Sails services.
  • Guardrail Enforcement: Includes explicit constraints for ethexe, such as gated syscall restrictions, maximum 3 indexed event fields, and reserved event name prohibitions, to avoid runtime errors.
  • Use Case: For example, when you have an approved task to add a new method that accepts ETH value and emits an Ethereum-style event in a Sails ethexe service, this Skill ensures the implementation follows all ethexe requirements without violating core Sails or Gear rules.

Quick Start

Use the sails-ethexe-implementer skill to implement the approved Rust code changes for your Sails ethexe workspace's new payable method and associated Ethereum event.

Frequently Asked Questions about sails-ethexe-implementer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement payable methods in a Sails ethexe Rust workspace?

Implementing payable methods in a Sails ethexe workspace requires applying the correct ethabi transport attributes to Rust functions so they can accept ETH value. The implementation must adhere to ethexe-specific API guardrails to ensure valid ABI encoding.

What are the limitations when defining Ethereum-style events in Sails ethexe?

When defining Ethereum-style events in Sails ethexe, you are limited to a maximum of 3 indexed event fields. Additionally, you must avoid using reserved event names to prevent runtime errors within the Gear or Vara environment.

How does Sails ethexe handle ABI-encodable custom type definitions?

Sails ethexe handles custom types by enforcing strict ABI-encodable type definitions within your Rust code. This ensures that the data structures used in your smart contracts are compatible with ethabi-exported methods and the ethexe runtime.

Can I use standard Sails implementers for ethexe-enabled smart contracts?

Standard Sails implementers do not cover ethexe-specific requirements such as ethabi transport, payable methods, and Ethereum-style events. You must use an ethexe-specific implementer to satisfy gated syscall restrictions and other unique API constraints.

Why does my Sails ethexe smart contract fail due to gated syscall restrictions?

Sails ethexe smart contracts fail due to gated syscall restrictions when the Rust code violates ethexe-specific API guardrails. Your implementation must strictly follow the ethexe feature constraints to avoid these runtime errors on the Gear or Vara network.