Feat/cw law stone spec #143
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
size-limit report 📦
|
amimart
force-pushed
the
feat/cw-law-stone-spec
branch
from
72a8a24
to
193960d
Compare
Codecov Report
@@ Coverage Diff @@
## main #143 +/- ##
==========================================
- Coverage 92.76% 89.34% -3.43%
==========================================
Files 11 13 +2
Lines 235 244 +9
==========================================
Hits 218 218
- Misses 17 26 +9
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ccamel
reviewed
Mar 15, 2023
bdeneux
reviewed
Mar 16, 2023
ccamel
approved these changes
Mar 17, 2023
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Purpose
This brings the specification of the new
cw-law-stone(the name can be discussed) smart contract, providing a mean to expose immutable governance rules as Prolog programs, and to question them by querying the OKP4 logic module.This idea is simple, the contract ensure the rules availability until the stone is broken. It relies on the
cw-storagecontract to ensure the availability of the Prolog program by pinning all the loaded objects.Instantiation
The provided Prolog program defining the law is stored and pinned in the provided
cw-storageaddress.To ensure availability of eventual loaded files, the logic module is queried to identify and pin them, I think to avoid breaking a governance we must enforce that all the loaded files are stored in a
cw-storagecontract.Query
Ask: Takes a Prolog query and ask the logic module by providing the main program.Program: Retrieve the law stone program location information, thecw-storagecontract address in which it is stored along with its ibject id.Break
If not used anymore, I think we need a mean to free all the related objects on
cw-storage, this is the purpose of theBreakStonemessage which can be invoked only by the contract admin.