-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
staking TendermintUpdate Store should be in a transient store #1013
Comments
I wonder if we should consider this when charging for gas (somehow)? At the moment we'll charge for storage reads/writes irrespective of whether they actually map to real disk reads/writes. |
I don't think it's a problem - we should just have a transient store which is charged at a lower rate (or not at all?) |
Agreed, that's what I mean. |
From discussion, this is only used as a cache store so never written to disk. Closing for #1288 |
not closed? it would be good to make this more obvious as a developer that this only ever lasts in the cache - right now the process train looks the same Maybe we could introduce store writes that automatically clear at the end of the block, and make it clear when you're writing to this store that this is what happens |
Need to make sure implementation would be clean, but I think we could have an option to mount a substore as "transient", and update |
Can't see where this has been updated in the codebase? reopening |
https://github.com/cosmos/cosmos-sdk/pull/1481/files doesn't effect anything in |
ON this one now! |
Tendermint updates will only ever last within a block
** Verify that this may already be happening with caching the existing store implementation?
The text was updated successfully, but these errors were encountered: