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.

Sign up for GitHub

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

Jump to bottom

gov: add prune wasm codes proposal #999

Open
alpe opened this issue Sep 13, 2022 · 2 comments · May be fixed by #1542
Open

gov: add prune wasm codes proposal #999

alpe opened this issue Sep 13, 2022 · 2 comments · May be fixed by #1542
Assignees
@pinosu
Milestone
v0.52

Comments

@alpe
Copy link
Member

alpe commented Sep 13, 2022 •
edited

In order to release storage space for unused contracts a prune proposal makes sense.
When executed wasm codes without an instantiation would be removed from CodeInfo and wasmvm.
The proposal may include a relative height (or fix one in the past?) as a threshold to not delete new uploads.

  • Should exclude pinned code ids

Follow up on:
#840 (comment)
@alpe alpe mentioned this issue Sep 13, 2022
Closed
@webmaster128 webmaster128 mentioned this issue Sep 13, 2022
Closed
@ethanfrey ethanfrey added this to the v0.31.0 milestone Nov 4, 2022
@ethanfrey ethanfrey added the optional Not absolutely required for the milestone label Nov 4, 2022
@alpe alpe added blocked and removed discussion labels Dec 7, 2022
@alpe alpe modified the milestones: v0.31.0, v0.32.0 Dec 7, 2022
@webmaster128
Copy link
Member

You can shedule this for 0.31 and start the work if you want to. The cosmwasm/wasmvm code will be ready as part of CosmWasm 1.2.

@alpe alpe removed the blocked label Jan 31, 2023
@pinosu pinosu removed the optional Not absolutely required for the milestone label Jun 13, 2023
@pinosu pinosu self-assigned this Jun 13, 2023
@pinosu pinosu mentioned this issue Jun 16, 2023
Closed
@pinosu
Copy link
Contributor

pinosu commented Jul 3, 2023

#1455 was closed after doing some benchmarks because of poor performance. Most likely a different approach is needed e.g. a migration script. Since this task is going to take more time than expected, it is descoped from v0.41 milestone.

@pinosu pinosu modified the milestones: v0.41.0, v0.42.0 Jul 3, 2023
@pinosu pinosu linked a pull request Aug 3, 2023 that will close this issue
Draft
@alpe alpe modified the milestones: v0.42.0, v0.51 Aug 31, 2023
@chipshort chipshort modified the milestones: v0.51, v0.52 Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pinosu pinosu

Labels
None yet
Projects
None yet
Milestone
v0.52
5 participants
@alpe @webmaster128 @chipshort @ethanfrey @pinosu