hiero-ledger / hiero-ledger/hiero-consensus-node

Update hederaCryptography version and WRAPS proving key

Open
#26,716 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

### Background

If a new version of hederaCryptography is released, we need to do the following:
- Update `hiero-dependency-versions/build.gradle.kts` with the new version

When there is a new WRAPS proving key artifact we will need to do the following:
- Update `hedera-node/hedera-config/src/main/java/com/hedera/node/config/data/TssConfig.java`, the `wrapsProvingKeyDownloadUrl` and `wrapsProvingKeyHash`.

Additional work:
- Update `hedera-node/test-clients/scripts/solo/e2e-block-stream-cutover/solo-075-to-076-tss.sh` to the new release version where TSS will be enabled (0.77).
- We need to update the release/0.77 branch default configs for TSS (hints, history, wraps, download enabled, the above changes)
- Update the latest release versions/tags in `hedera-node/test-clients/scripts/solo/e2e-block-stream-cutover/solo-077-to-078-cutover.sh`
- Update the latest release version/tags in `hedera-node/test-clients/scripts/solo/e2e-block-stream-cutover/solo-e2e-block-stream-cutover.sh`
- Update the wraps proving key image build and publish a new artifact for use in CI runners `.github/workflows/105-user-publish-wraps-key.yaml` we will need to run this workflow with the new URL. We should update the default URL as well. Make sure this new image is mounted to the runner.

### Acceptance Criteria

Implement the above changes

### Dependencies

_No response_

### Definition of Ready (DoR) Checklist

- [ ] Clear acceptance criteria
- [ ] Clear and detailed description
- [ ] Dependencies identified
- [ ] Links to documentation
- [ ] Should be completable in 2-3 Days
- [ ] Initial draft of Low-level design document
- [ ] At least high level test plan
- [ ] Groomed/Estimated

### Definition of Done (DoD) Checklist

- [ ] Acceptance Criteria complete
- [ ] No Codacy issues greater than minor (in new code)
- [ ] JavaDocs updated/created
- [ ] Code commented
- [ ] Unit tests created/updated
- [ ] 80% test code coverage (in new code)
- [ ] Happy Path and major negative cases in HAPI tests as applicable

Contributor guide

Open the contributing guide

Research direction

Start with hiero-dependency-versions/build.gradle.kts and TssConfig.java to identify the current hederaCryptography version and WRAPS proving-key URL and hash. Then inspect the listed solo cutover scripts, release/0.77 default configs, and .github/workflows/105-user-publish-wraps-key.yaml for version, tag, workflow, and runner-mount changes. Done means all requested defaults and scripts use the new release values and the updated proving-key artifact is published and available to CI runners.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, java, kotlin, shell
Domain
build-system, ci-cd, cryptography, release, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.