Hi, ethereumjs-util PR 228 is upgrading secp256k1 from ^3.0.1 to ^4.0.0 and seeing a couple tests for invalid SEC1 keys fail in browser (karma) tests, but pass ok in Node 10. The tests worked in both contexts using 3.0.x

For example, one test case takes an invalid SEC1 key:

const key = Buffer.from('023a443d8381a6798a70c6ff9304bdc8cb0163c23211d11628fae52ef9e0dca11a001cf066d56a8156fc201cd5df8a36ef694eecd258903fca7086c1fae7441e1d',
      'hex',
    )

and passes it to publicKeyVerify expecting it to fail.

secp256k1.publicKeyVerify(key) // Returns false in Node, true in Chrome/Firefox

Do you have any advice about this? Is it happening because elliptic treats this key as compressed and as such its valid?