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

feat(contracts): delete resolved challenge data to save gas costs during resolution #243

Closed
Tracked by #259
merklefruit opened this issue Sep 27, 2024 · 0 comments · Fixed by #202
Closed
Tracked by #259

feat(contracts): delete resolved challenge data to save gas costs during resolution #243

merklefruit opened this issue Sep 27, 2024 · 0 comments · Fixed by #202
Labels
C: smart-contracts Component: smart contracts

Comments

@merklefruit
Copy link
Collaborator

Relevant idea: #239 (comment)

The BoltChallenger doesn't need to hold the full challenge data after challenges are resolved.
Just the ID, the address of the operator that broke the commitments, and maybe other metadata should remain in storage.

This will free up a significant amount of storage, reducing resolution costs up to 20% (max SSTORE refund).
@merklefruit merklefruit added the C: smart-contracts Component: smart contracts label Sep 27, 2024
@merklefruit merklefruit mentioned this issue Oct 3, 2024
Open
@mempirate mempirate linked a pull request Oct 16, 2024 that will close this issue
feat(contracts): new registry (V1) #202
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: smart-contracts Component: smart contracts
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(contracts): new registry (V1) chainbound/bolt
1 participant
@merklefruit