Support legacy format to integrate with Chainweaver and pact CLI tools.
On input, try current format, when that fails, try legacy format (sign, combine-sigs commands)
In combine-sigs, accept -l switch to output in legacy format.
This allows workflows like the following:
Author a safe transfer in Chainweaver that needs three sigs, two offline.
Send legacy YAML from Chainweaver to first kda-tool offline signer. Output is current format.
Send current YAML to second kda-tool offline signer. Output is in current format.
Second signer uses combine-sigs to convert to legacy format and sends to final Chainweaver signer.
Final Chainweaver signer puts YAML in SigBuilder, signs and sends to network.
Note that since combine-sigs accepts both old and new formats, steps 2-5 could happen asynchronously and have a kda-tool user combine outputs and send.
I've tested roundtripping with old and new formats.
Support legacy format to integrate with Chainweaver and pact CLI tools.
sign
,combine-sigs
commands)combine-sigs
, accept-l
switch to output in legacy format.This allows workflows like the following:
combine-sigs
to convert to legacy format and sends to final Chainweaver signer.Note that since
combine-sigs
accepts both old and new formats, steps 2-5 could happen asynchronously and have a kda-tool user combine outputs and send.I've tested roundtripping with old and new formats.