You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have a single SaplingProvingContext which we initialize, use to create each Spend and Output proof (along with extra fields for the Spend description), and then call binding_sig to produce bindingSig. The reason for this workflow was that there is a data dependency on the entire transaction to create it. However, this data dependency is only a blocker on creating bindingSig due to computing bsk; the remaining components can be created independently of the whole transaction.
We should extract the per-proof creation logic from SaplingProvingContext, so they can be run independently.
The text was updated successfully, but these errors were encountered:
Currently, we have a single
SaplingProvingContext
which we initialize, use to create each Spend and Output proof (along with extra fields for the Spend description), and then callbinding_sig
to producebindingSig
. The reason for this workflow was that there is a data dependency on the entire transaction to create it. However, this data dependency is only a blocker on creatingbindingSig
due to computingbsk
; the remaining components can be created independently of the whole transaction.We should extract the per-proof creation logic from
SaplingProvingContext
, so they can be run independently.The text was updated successfully, but these errors were encountered: