Skip to content

Analyze cost to attack truncated SHA256 #1990

@ValarDragon

Description

@ValarDragon

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C:cryptoComponent: CryptoT:securityType: Security (specify priority)

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions