-
Notifications
You must be signed in to change notification settings - Fork 992
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
update masp conversions via write log #1108
Conversation
24ece92
to
9441d70
Compare
pls update wasm |
The expected keys previously omitted a newly written value, because iter prefix wasn't able to find it
To use storage_api, use WlStorage instead
da5a58b
to
27ea90b
Compare
pls update wasm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @yito88 for pointing out that there are possible storage write from goverance proposal that are committed directly to DB
dc9ceb9
to
76bc07c
Compare
I added the fix for gov - I've moved the gov module from |
76bc07c
to
17427fa
Compare
pls update wasm |
* tomas/protocol-write-log: [ci] wasm checksums update changelog: add #1108 shell/queries: refactor token query using storage_api token mod shell/gov: apply changes via `WlStorage` write log test/finalize_block: ensure that proposal doesn't commit to DB gov + token: refactor using storage_api move gov mod from tx_prelude to core storage_api test/test_vp_host_env: update to write via tx ledger: apply `update_allowed_conversions` storage changes via WlStorage wl_storage: apply protocol write log changes at block level test/ledger/shell: test that `finalize_block` doesn't commit storage
based on #913
This PR Improves the
WlStorage
to write protocol changes via block-level write log. This is then used to make sure that no storage changes are committed in ABCIFinalizeBlock
request handler and only in theCommit
handler.