Decide whether platform or services should manage BLS private keyshares

hashgraph / hedera-services

Crypto, token, consensus, file, and smart contract services for the Hedera public ledger

Apache License 2.0

290 stars 124 forks source link

Decide whether platform or services should manage BLS private keyshares #5416

Closed swirlds-automation closed 1 year ago

swirlds-automation commented 1 year ago

Since BLS keyshares will be entirely generated by the platform, it might make sense for platform to assume responsibility for managing these keys, rather than services (as is currently the case with RSA keys)
RSA signing will continue unchanged even after the addition of BLS, so there isn't any apparent reason to change how RSA keys are managed: this issue is constrained to BLS key management only

swirlds-automation commented 1 year ago

_{migrated from:
url=https://github.com/swirlds/swirlds-platform/issues/6721
author:alittley, #:6721, createdAt:2023-02-16T21:34:15Z, updatedAt=2023-02-17T20:02:23Z
labels=Question,Platform BLS,Migration:Hashgraph}

litt3 commented 1 year ago

BLS is not happening anymore