Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ics10 requirements #36

Merged
merged 2 commits into from
Feb 5, 2024
Merged

ics10 requirements #36

merged 2 commits into from
Feb 5, 2024

Conversation

crodriguezvega
Copy link

Description

This PR builds upon the work of @@blasrodri to add more information to the requirements.

closes: #XXXX


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

Copy link

@blasrodri blasrodri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

docs/requirements/ics10-requirements.md Outdated Show resolved Hide resolved
| 2.02 | Once a light client Wasm contract has been stored, every light client will be created with a new instance of the contract. | TBD | `Drafted` |
| 2.03 | The bytecode for each light client Wasm contract is stored in a client-prefixed store indexed by the hash of the bytecode. | TBD | `Drafted` |
| 2.04 | The size in bytes of bytecode of the light client Wasm contract must be > 0 and <= 3 MiB. | TBD | `Drafted` |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should there be more information of the functional requirements wrt updating the client and consensus state or is it fine to have it expressed it must fit with the -2 client interfaces? I'm wondering if it would be good to split it up a bit more as there will be some acceptance tests linked for this functionality

@blasrodri blasrodri merged commit 8428666 into ComposableFi:wasm-client-requirements Feb 5, 2024
3 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants