Closed junderw closed 1 year ago
Depending on the version of libsecp256k1
that is now being used, this fix might also address the issue discussed in this thread.
If that's the case, two of the ECDSA test fixtures might require adjustments:
{
"description": "Strange hash",
"d": "0000000000000000000000000000000000000000000000000000000000000001",
"m": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
"signature": "7cb38cc5712e9e11a767615f6080dbc111c9cdd613eb98999fd92a86bafd45407923ca1f4d03471d2866f776ef8a6d3cac099b427331aeb245aa9dafeddcf115",
"recoveryId": 1
},
{
"description": "Strange hash",
"d": "fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364140",
"m": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
"signature": "a7f83b5963eaf5332c633327cc967be8f4166d3f1e0b77f9761d8f4e42211e9a58aae31be1eb1e496923bbe8ca5e843cfb89f4d986d61d4edfd7d6fc3c9cf62c",
"recoveryId": 0
},
EDIT: Oups! You already did!
This is annoying.
eslint doesn't support type assertions for json import statements, so linting breaks.
But the workaround is Node only...
I tried using babel for eslint, but that didn't work...
Should fix #118