Anatomy of an application, Part 1: Introduction

[alberto]

@cwgoes

You mean specifically this definition, right?

Yes

@cwgoes

Which commitments and nullifiers is a VP expected to check - only their own, or also those of other notes? One concern I have (while reading this and thinking about it) is that it seems like we might end up checking the well-formedness of the same commitments and nullifiers multiple times.

Only their own. In the case of an input note vp, that the nullifier is derived correctly from the contents of the note. In the case of an output note vp, that the commitment is computed correctly from the note.

@cwgoes

As I understand this, both configure and synthesize are called statically (i.e. the values are known at Rust compile time) - the separation is for clarity of concerns - is that accurate?

Not exactly. configure is called statically (see that there is no self to have access to the witnesses or private values. synthesize is called both statically to generate the verifying key (in this case we need to pass dummy values - see this explanation) and dynamically with the prover’s witnesses and public inputs