You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue defines the V1 or MVP version of the future GnoSDK (#873). This version is essential for test4 and the launch, while the broader GnoSDK issue focuses on making GnoSDK reusable for new TM2+GnoVM chains, which isn't a current priority.
Goals
Simplicity and Reliability: Prioritize simplicity and reliability, even if performance is not highly optimized.
Clean API/Usage: Ensure the API and usage are clean, especially for smart contracts. Avoid using the recently introduced std.Emit event system for data exchanges, as emitted events are not as explicit and simple to test as returned typed values.
Suggested Implementation
Develop helpers to call a contract's functions from the gnoland app.
Implement proper error management and data marshalling.
Include options such as "read-only" (execute without saving realm changes).
This issue defines the V1 or MVP version of the future GnoSDK (#873). This version is essential for test4 and the launch, while the broader GnoSDK issue focuses on making GnoSDK reusable for new TM2+GnoVM chains, which isn't a current priority.
Goals
std.Emit
event system for data exchanges, as emitted events are not as explicit and simple to test as returned typed values.Suggested Implementation
Expected Usages
r/sys/names
Namespace support for package paths #1107r/sys/valset
feat(PoC,gov): initial sys/validators and gov/dao contracts #1945r/sys/vals
feat: add/r/sys/validators
#2130r/sys/teams
feat: add r/sys/teams #2184r/sys/eula
r/sys/vars
The text was updated successfully, but these errors were encountered: