Gno: An interpreted, stack-based Go virtual machine to build succinct and composable apps + Gno.land: a blockchain for timeless code and fair open-source
This PR introduces a new pattern for arbitrary govdao proposals using Gno code using contexts. It involves wrapping the provided closure with a system that configures a context.Context with a field indicating that the execution occurs in the context of an approvedByGovDao proposal. This opens the door to a new ACL system, not based on PrevRealm(), but on a context-based "certification" system.
I believe this pattern makes sense to exist; however, here are some drawbacks I can see:
context.Context is not yet needed (no goroutine support), and we may eventually never need this package depending on how we implement goroutines internally. (h/t @thehowl)
context.Context is used like an environment variable, which introduces implicitness—something we usually try to avoid to make Gno a very explicit language. Explicitness brings “simplicity” and “verifiability.”
The usual Go idiomatic way of using context is to pass it as the first argument. If this becomes more common, it will result in more contracts having exposed functions that are not callable by maketx call (though they can be called with maketx run or via an import).
This PR introduces a new pattern for arbitrary govdao proposals using Gno code using contexts. It involves wrapping the provided closure with a system that configures a
context.Contextwith a field indicating that the execution occurs in the context of anapprovedByGovDaoproposal. This opens the door to a new ACL system, not based onPrevRealm(), but on a context-based "certification" system.I believe this pattern makes sense to exist; however, here are some drawbacks I can see:
context.Contextis not yet needed (no goroutine support), and we may eventually never need this package depending on how we implement goroutines internally. (h/t @thehowl)context.Contextis used like an environment variable, which introduces implicitness—something we usually try to avoid to make Gno a very explicit language. Explicitness brings “simplicity” and “verifiability.”contextis to pass it as the first argument. If this becomes more common, it will result in more contracts having exposed functions that are not callable bymaketx call(though they can be called withmaketx runor via an import).Depends on #2379
Related to #2386