You are viewing a single comment's thread from:
RE: Why does steem use this canonical thing instead of strict secp256k1?
This has nothing to do with the secp256k1 implementation in use but rather with the canonicality check and the way k is derived and updated if canonicality isnt achieved.
libsecp256k1 even offers an optional API to overwrite how to deal with a deterministic k and tret it if necessary.