Rick Mark
*raises hand* - I'm planning to do some work in this space - initially entitlements to replace the aging j's database
So I think we should move from `LinkeditDataCommand` to the idea of a meta-programming model where the various LC_ commands are mapped too a class (LC_CODE_SIGNING => CSSuperBlob). Today the...
Maybe this should be kicked up to python itself? It seems silly that if you install their package from the internet you get the Dylib / framework but when building...
> What is the motivation for wanting a different representation for secret keys? Well there are at least two common representations of private keys, raw 32 byte integers, and DER...
> > a private key in the future may also bring along its public to prevent multiple computation of the public key. > > Why not reuse the keypair type...
> * carrying the public key with it: that won't fit in 32 bytes anyway, and for that `secp256k1_keypair` should be used. I'm looking at the types `secp256k1_pubkey` and `secp256k1_seckey`...
> The only point that matters here is whether or not we expect to ever want a way to represent private keys in another way _that's guaranteed to fit in...
It seems to me one of the first steps here is to separate the library code from the test code better. (Compile the library, then compile tests that link to...
Created issue #909 to introduce the ability to query the version so that clients can decide if the version they bind to is SemVer compatible
Created #914 for this