fix: removes hash from ZeekMessages contract on Atlas #1
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.
Description
I was working through the zkSync documentation and noticed a discrepancy between the ZeekMessages contract example in the docs and the version in this repository.
Changes
The documentation presents a version of the contract that stores messages directly as strings, while the current version in the repository hashes the messages before storing them.
To ensure consistency between the documentation and the codebase, I've updated the ZeekMessages contract in this PR to match the version presented in the documentation:
Modified messages storage from bytes32[] to string[] to store messages as plain text.
Removed the hashing step from the sendMessage function.
This change aligns the contract implementation with what users would expect based on the documentation.
I have tested this updated contract on the Atlas platform to confirm that it compiles and functions as expected.
Please let me know if you have any questions or require any further adjustments.
Thank you!