This issue will extend the Wasm API of the svm_codec.wasm to support the new Signatures Schemes.
Consequently, the svm-codec-npm will have to be extended as well (@avive FYI)
The params Schema will consist of the keys algorithm and params.
The params is a JSON that the algorithm key will dictate its schema.
Encode sigdata
Given a JSON containing the Signatures, we'd like to encode them from the sigdata field.
The encoding can vary between different Templates. For now, it suffices to support the concatenate encoding.
(see svm_codec::concat_sigs under #483).
Similar to the wasm_sign the input JSON will always have keys abi and params.
The params schema will vary depending on the abi given. (again, for now we'll just deal with abi assigned to concat).
Depends on #483
This issue will extend the Wasm API of the
svm_codec.wasm
to support the new Signatures Schemes. Consequently, the svm-codec-npm will have to be extended as well (@avive FYI)Extensions to be implemented:
Transaction
tx
- a pointer to the binary Transaction (theEnvelope
and theMessage
parts).params
- a pointer to a JSON containing the data required for signing the transaction:The
params Schema
will consist of the keysalgorithm
andparams
. Theparams
is a JSON that thealgorithm
key will dictate its schema.sigdata
Given a JSON containing the
Signatures
, we'd like to encode them from thesigdata
field. The encoding can vary between different Templates. For now, it suffices to support theconcatenate
encoding. (seesvm_codec::concat_sigs
under #483).Similar to the
wasm_sign
the input JSON will always have keysabi
andparams
. Theparams
schema will vary depending on theabi
given. (again, for now we'll just deal withabi
assigned toconcat
).