gear-gstd-api-map

To select the right gstd API for messaging, start from your intent and choose the appropriate high-level gstd module like msg or exec, rather than raw syscalls. This structured selection workflow ensures you use the correct API for async reply flows without unnecessary low-level digging.

The best way to handle gas reservations for delayed messages is to identify the correct high-level gstd reservations and delayed send APIs. You can quickly map these APIs to their use cases using a quick reference table, ensuring guaranteed gas availability without sifting through raw syscall documentation.

You only need to reference gcore or gsys instead of standard gstd APIs when confirming low-level limits, gas shapes, or syscall behavior. For standard program creation, messaging, and execution tasks, you should prioritize high-level gstd APIs and drop to lower levels solely for edge case validation.

Yes, you can use gstd APIs for factory-style child program creation on Vara. The prog module provides the necessary high-level functions to handle this build task, allowing you to design and implement child program creation scenarios without directly interacting with low-level syscalls.

The gstd API map covers scheduled work with gas guarantees by providing scenario guidance for delayed scheduled work. It helps you quickly identify the correct reservation and delayed send APIs needed to ensure gas availability for timed execution flows in Gear applications.