switched over to ext-secp256k1_nostr

phpecc implementation of SchnorrSignature gave many invalid signature errors, so switching over (for transpher) to ext-secp256k1_nostr (https://github.com/1ma/secp256k1-nostr-php). For future libraries support for phpecc is desirable, because extensions can (most likely) not be deployed to shared hosting environments

https://github.com/nostriphant/transpher/commit/a8ac4d4aedcf60f0cb6ac0e0c35cca38e9905dee

#transpher #nostrifying-php

Reply to this note

Please Login to reply.

Discussion

Hi, I'm the author of secp256k1_nostr.

We also stumbled upon the invalid signature errors while working on the nostrver-se/nostr-php library and figured out the fix: https://github.com/public-square/phpecc/pull/1

However the fix never got merged, so I did yet another fork of phpecc that includes it in case someone really needs a working PHP implementation of Schnorr signatures (uma/phpecc v0.1.3).

Besides the poor speed the problem with phpecc and all its forks is that they are not maintained at all (including mine!). Relying on libsecp256k1 is way better.

That's the next step then, thanks for your heads up!