So because I'm doing things from c++, I don't have access to eosjs-ecc.
Assuming that I have successfully packed the transactions (using fcbuffer, packed the action data using the ABI), which I've compared with that of eosjs and they seem to be identical, how does the signing process work?
I have heard that it's
secp256k1(privateKey, sha256(chain_id + packed_transaction + sha256(contextFreeData)))
but the sig output I see in the json has the prefix
SIG_K1 and even without that, it's longer than the base58 encoded version of what I outputted. Not only that, the results are different.
I'm in the process of reverse engineering eosjs-ecc and seeing what it does, but I was wondering if anyone happens to know how exactly it is done?