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

feat: automatically generate transaction batch #6

Open
2 tasks
mfw78 opened this issue Nov 27, 2023 · 0 comments
Open
2 tasks

feat: automatically generate transaction batch #6

mfw78 opened this issue Nov 27, 2023 · 0 comments
Labels
good first issue Good for newcomers

Comments

@mfw78
Copy link
Contributor

mfw78 commented Nov 27, 2023

Problem

It's frustrating using this setup that after settings have been modified, a transaction batch needs to be created to be submitted to the CoWDAO Safe. This is currently a manual process, and subject to possible error.

Suggested solution

During the CI/CD, calculate the IPFS hash (CID) that will be generated and automatically populate the transaction batch with the correct IPFS hash for the snapshot TXT record.

This transaction batch could be part of the artifacts that are generated during the release process that is automatically triggered on merge to main.

Alternatives considered

Manually creating the transaction batch, though this is subject to error.

Additional context

An example of how to generate the transaction batch JSON can be found here (credit: @fedgiac)

Acceptance criteria

On merge to main:

  • settings.json is automatically uploaded and pinned on
  • batch.json, a safe transaction batch is automatically created for updating CoWDAO
@mfw78 mfw78 added the good first issue Good for newcomers label Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant