GnoSDK

[moul]

Initial discussions for the upcoming GnoSDK.

GnoSDK is a customizable and modular chain framework, serving as an alternative to CosmosSDK. It can seamlessly run alongside CosmosSDK and has the potential to evolve into a module within the CosmosSDK ecosystem.

GnoSDK encourages chains with simple configurations, smart contract reliance, and streamlined chain upgrades that avoid restarts. Changes are automatically applied post-governance approval.

---

Strategy:

• Prioritize simplicity in feature implementation, starting with GnoSDK or gno.land/*; reusability can be addressed later, potentially for a second chain.

Key features to consider:

• Subscribe to emit events (emit & event built-in functions #575, WIP chore: guidelines for multinode testnet experimentation #871) for event-based functionality.
• Enable querying and looking up contract states (feat: add r/system/names #375) for easy access.
• Try to implement a contract method call if we can manage performance reasonably.

[moul]

New details here: #871 (comment)

• could make sense to expose much of abci to the smart contract layer
• using abci.EndBlocker to apply changes "decided" by a realm

[moul]

MVP version defined here: #2205

This issue should stay opened for future needs, such as std.Emit event catching and reading realm state without execution.