arcanicanis on Nostr: Much of it's explained later in one of the replies at: ...
Much of it's explained later in one of the replies at: https://were.social/notice/Ag9m39s4aWr45TmKdE
Generally trying to build within the capabilities present in PHP 8.0, making use of common first-party binary extensions to PHP first (hence OpenSSL for secp256k1, or else libsodium when I deal with ed25519)
Hadn't known about the IETF publication, I actually had to dig in various forum threads and StackOverflow to find the math on how to accomplish it, as well as work off of other people's notes. The mentioned publication probably would have helped out much more, I'll probably highlight in on any future summary on that.
I do however need to dig deeper on the specifics about low-s with signature creation.
Much of the stuff with Multibase, Multikey, etc I've already read into plenty before when experimenting with Object Integrity Proofs in ActivityPub, just with ed25519 instead.
Generally trying to build within the capabilities present in PHP 8.0, making use of common first-party binary extensions to PHP first (hence OpenSSL for secp256k1, or else libsodium when I deal with ed25519)
Hadn't known about the IETF publication, I actually had to dig in various forum threads and StackOverflow to find the math on how to accomplish it, as well as work off of other people's notes. The mentioned publication probably would have helped out much more, I'll probably highlight in on any future summary on that.
I do however need to dig deeper on the specifics about low-s with signature creation.
Much of the stuff with Multibase, Multikey, etc I've already read into plenty before when experimenting with Object Integrity Proofs in ActivityPub, just with ed25519 instead.