Abstract
In the usual syntax of digital signatures, the verification algorithm takes a verification key in addition to a signature and a message, whereas in ECDSA with key recovery, which is used in Ethereum, no verification key is input to the verification algorithm. Instead, a verification key is recovered from a signature and a message. In this paper, we explore the BUFF security of ECDSA with key recovery (KR-ECDSA), where BUFF stands for Beyond UnForgeability Features [7]. As a result, we show that KR-ECDSA provides BUFF security, except weak non-resignability (wNR). It is particularly noteworthy that the KR-ECDSA verification algorithm takes an Ethereum address $$\textsf{addr}$$ addr as input. This address is defined as the rightmost 160 bits of the Keccak-256 hash of the corresponding ECDSA verification key. Crucially, the algorithm verifies that the hash of the recovered verification key matches $$\textsf{addr}$$ addr . Our security analysis shows that the procedure, namely checking whether the hash value of the recovered verification key matches the address, is essential for achieving provide BUFF security. We also discuss whether wNR is mandatory in Ethereum or not. To clarify which part is mandatory to provide BUFF security in KR-ECDSA, we show that the original ECDSA does not provide any BUFF security. As a by-product of the analysis, we show that one of our BUFF attacks also works against Aumayr et al.’s ECDSA-based adaptor signature scheme [2] and Qin et al.’s blind adaptor signature scheme [35], which is based on Aumayr et al.’s scheme. We emphasize that the attack lies outside their security models.
Funding Information
  • Japan Society for the Promotion of Science (KAKENHI Grant Numbers JP21K11897 and JP25H01106.)
  • Kanazawa University