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

Create platform design proposal for future cryptography key needs.

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

Description

The proposal needs to cover the following:
* multiple keys in memory, supporting key rotation
* reading keys dynamically from disk without restart
* multiple key types, RSA, BLS, Schnorr, EC, etc.
* Multiple encoding schemes: PEM, PKCS#8,12,etc, ASCII Armored
* Lifecycle Management
* How do we guarantee destruction?
* Storage on disk
* Key Management Practices

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Review the existing cryptography and key-management approach in the repository, then draft a platform design proposal covering key rotation, dynamic loading, supported key types and encodings, lifecycle and destruction, disk storage, and management practices.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.