sails-ethexe-architecture

Design Sails ethexe app architectures with dual-transport, payable methods, and event constraints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of designing non-compliant Sails ethexe app architectures that miss critical constraints like gated syscall incompatibilities, incorrect transport strategies, or invalid event designs, which would cause implementation failures or ecosystem compatibility issues.

Core Features & Use Cases

  • Transport Strategy Guidance: Selects the correct transport type (dual, scale-only, ethabi-only, payable) per service method to balance Gear and EVM compatibility.
  • Ethexe Constraint Validation: Checks for incompatible syscalls, enforces indexed event field limits, and ensures type requirements for ethabi methods are met.
  • Use Case: For example, if you are building a Sails app that needs to accept payable calls from Ethereum wallets and emit Ethereum-style events, this skill ensures your architecture accounts for all ethexe-specific requirements before implementation begins.

Quick Start

Use the sails-ethexe-architecture skill to design the architecture for your new Sails ethexe app that supports dual-transport payable methods and Ethereum-style events, following all ethexe-specific constraints and guardrails.

Frequently Asked Questions about sails-ethexe-architecture

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

FAQPage Schema
How do I design a Sails app architecture that supports both Gear and Ethereum?

To design a compliant Sails ethexe app, select the correct transport type (dual, scale-only, ethabi-only, payable) per service method to balance Gear and EVM compatibility while meeting all ethexe-specific constraints.

What are the ethexe constraints for Sails event design?

Ethexe event design requires enforcing indexed event field limits and ensuring ABI-encodable type requirements for ethabi methods. Validating these constraints prevents implementation failures and ecosystem compatibility issues.

Can I use Solidity interfaces with Sails apps on the Gear network?

Yes, Sails apps generate Solidity interfaces for Gear/Vara networks. Your architecture must use payable transport methods and ensure ABI-encodable types so Ethereum wallets can interact with the Sails app seamlessly.

Why does my Sails ethexe app fail syscall validation?

Sails ethexe apps fail validation due to gated syscall incompatibilities. You must check for and avoid these incompatible syscalls during architecture design to maintain ethexe compliance and prevent implementation failures.

What is the best way to handle payable methods in a Sails ethexe app?

The best way to handle payable methods is selecting the payable transport strategy during architecture design. This ensures your Sails app accepts calls from Ethereum wallets while meeting ethexe dual-transport requirements.