-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
C:cryptoComponent: CryptoComponent: CryptoT:securityType: Security (specify priority)Type: Security (specify priority)
Milestone
Description
There is concern that 80 bits of security with truncated 20 byte sha256 is insufficient. We need to do a cost analysis of the cost to break truncated levels of sha256 (i.e. cost per asic + electricity) and figure out exactly what margin between 20 byte and 32 byte hashes we want to use. (As the space savings are worth considering) Its important to note that you can't reuse bitcoin asics, since we have domain seperators on the hashes.
Ideally at the end of it, we should create an ADR for this.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C:cryptoComponent: CryptoComponent: CryptoT:securityType: Security (specify priority)Type: Security (specify priority)