gear-builtin-actors

Implement Gear/Vara Sails calls to runtime builtin actors with correct ActorId, encoding, decoding, and gas budgeting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common errors Sails program builders face when calling Gear/Vara runtime builtin actors (such as staking, BLS12-381, proxy, and ETH bridge), including incorrect ActorId usage, failed reply decoding, insufficient gas allocation, and ED rule violations that cause transactions to fail.

Core Features & Use Cases

  • Correct Builtin Call Workflow: Provides step-by-step guidance for deriving valid builtin ActorIds, encoding requests with gbuiltin-* helper crates, and decoding builtin replies without relying on Sails IDL routing.
  • Gas and ED Budgeting: Covers proper gas allocation against builtin max gas weights and Existential Deposit (ED) rules for value transfers to builtin actors.
  • Use Case: For example, if you are adding staking functionality to a Sails DeFi app, this Skill guides you to implement the call correctly, handle gas costs, and decode staking responses without runtime errors.

Quick Start

Use the gear-builtin-actors skill to add a staking feature to your Sails app that correctly calls the runtime staking builtin, budgets gas appropriately, and decodes the builtin's response.

Frequently Asked Questions about gear-builtin-actors

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

FAQPage Schema
How do I call Gear/Vara builtin actors from a Sails program?

To call Gear/Vara builtin actors from a Sails program, you must derive valid builtin ActorIds, encode requests using gbuiltin-* helper crates, and decode replies without relying on Sails IDL routing.

Why does my Sails builtin actor call fail with a reply decoding error?

Sails builtin actor calls fail with decoding errors when relying on standard Sails IDL routing instead of decoding the raw builtin reply, which requires specific handling using gbuiltin-* helper crates.

How do I allocate gas for Gear/Vara builtin actor interactions?

Gas allocation for Gear/Vara builtin actor interactions requires budgeting against builtin max gas weights and adhering to Existential Deposit rules for value transfers to prevent transaction failures.

Does Sails IDL routing work for Gear staking and BLS12-381 builtin calls?

No, Sails IDL routing does not work for Gear staking and BLS12-381 builtin calls; you must bypass IDL routing, derive correct ActorIds, and manually decode replies using helper crates.

What is the correct workflow for adding staking to a Sails DeFi app on Vara?

The correct workflow for adding staking to a Sails DeFi app on Vara involves calling the runtime staking builtin, budgeting gas against max weights, and decoding the builtin response without Sails IDL routing.

Can I use Sails to interact with the Gear ETH bridge and proxy builtins?

Yes, you can interact with Gear ETH bridge and proxy builtins by deriving valid ActorIds, encoding requests with gbuiltin-* crates, and decoding replies while managing gas and Existential Deposit rules.