Feat/t31 qc serde

[philippecamacho]

Closes #31. Some remarks:

• The QC and the QC parameters can be (de)serialized.
• Some minor changes to Jellyfish were required: see https://github.com/EspressoSystems/jellyfish/tree/fix/signature-scheme-serde
• QCParams.stake_table_digest has been removed because (1) it is not used and (2) it creates complications for serde with Jellyfish (Schnorr signature).

[chancharles92]

LGTM, some minor comments.
OTOH, do we also want to create a PR in Jellyfish for below?
https://github.com/EspressoSystems/jellyfish/tree/fix/signature-scheme-serde

[chancharles92]

@philippecamacho So later when we implement SNARK-based QC, we are going to put the hash_digest into Proof correct?

[philippecamacho]

@philippecamacho So later when we implement SNARK-based QC, we are going to put the hash_digest into Proof correct?

You mean the stake table digest?

[philippecamacho]

LGTM, some minor comments. OTOH, do we also want to create a PR in Jellyfish for below? https://github.com/EspressoSystems/jellyfish/tree/fix/signature-scheme-serde

Yes, the PR has been created: EspressoSystems/jellyfish#271

[chancharles92]

@philippecamacho So later when we implement SNARK-based QC, we are going to put the hash_digest into Proof correct?

You mean the stake table digest?

Yes

[philippecamacho]

@philippecamacho So later when we implement SNARK-based QC, we are going to put the hash_digest into Proof correct?

You mean the stake table digest?

Yes

Ok then yes, it make sense to have the stake table digest be a public input of the snark circuit.