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.

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

Hash on chain in the Timlock #82

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ryangoree
Copy link
Member

@ryangoree ryangoree commented Apr 23, 2023

This would make it possible to see what actions have been registered.

It would also make it possible to see what actions are being proposed in CoreVoting. When the actions are hashed off chain, we can only see a callHash for Timelock proposals.

#83

@github-actions
Copy link

Pull Request Test Coverage Report for Build 4775851501

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.02%) to 94.207%

Totals Coverage Status
Change from base Build 4347624322: 0.02%
Covered Lines: 514
Relevant Lines: 531

💛 - Coveralls

Copy link
Collaborator

@aleph-v aleph-v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any real problems with this approach, there's only a minor cost increase which is not a serious consideration, so if it helps visibility that's useful.

However I'd prefer to not merge until we have a strategy on how we want to do alpha changes, our rollout timelines on new releases and security process for them. In particular I'd like to avoid a drift where this codebase's main branch has feature discrepancies with the deployed codebase(s), especially if the intent is to build front end and council kit features assuming those features exist.

@ryangoree ryangoree linked an issue Apr 27, 2023 that may be closed by this pull request
@sentilesdal
Copy link
Contributor

Closing for now since this is stale. We can open another PR if we want this feature later.

@ryangoree
Copy link
Member Author

Re-opening for increased visibility and consideration.

@ryangoree ryangoree reopened this Apr 18, 2024
@coveralls
Copy link

Pull Request Test Coverage Report for Build 8742545879

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.1%) to 94.093%

Totals Coverage Status
Change from base Build 8742493929: -0.1%
Covered Lines: 515
Relevant Lines: 532

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hash on chain in the Timelock
4 participants