The chain signature contract will be updated to accept a non-hashed payload, key derivation path, and hashing algorithm. This is a breaking change from the current implementation, which accepts a hashed payload and key derivation path.
Action Items:
Update the frontend code to call the contract with the new input parameters for ETH transactions.
Investigate solutions for signing non-hashed payloads in BTC transactions:
a. Research libraries that support signing non-hashed payloads. Currently library only exposes a method to sign hashed payload.
b. Explore implementing the signing algorithm ourselves. - HARD, the signing algorithm code is extensive and contains numerous conditions, making it challenging to implement from scratch.
c. Consider extracting and adapting code from the existing library. - HARD, the signing algorithm code is extensive and contains numerous conditions, making it challenging to implement from scratch.
Update the frontend code to call the contract with the new input parameters for BTC transactions.
The chain signature contract will be updated to accept a
non-hashed payload,key derivation path, andhashing algorithm. This is a breaking change from the current implementation, which accepts ahashed payloadandkey derivation path.Action Items:
Update the frontend code to call the contract with the new input parameters for BTC transactions.