Create Presentation For ProgCrypto

[alv-around]

Presentation slides:

https://docs.google.com/presentation/d/1k0T-n4ZpEMKkXP1AApJ2TJhzP7na9KV-M4aIWmSdYmg/edit?usp=sharing

[alv-around]

Feedback from Sebastian:

F1 Title (3er Bilder anpassen)
F2 "to change: fotter"
F4 (pictures very small) - question about audience, will the audience believe that both zk-Rollups/ zk-ML are motivation enough or would you motivate why we wnat these things....
F5 center table
F6 the issue wasn't quite clear to me. (is there text on the slide that helps me follow me?)
F7 maybe add a meme of a overworked worker when talking about matanance issues
F9 I would add two service to the picture to make clear that manatance now is easier? mby just make one gray so its clear you only talk about one of them in detail
F10
F11 Q: is trustworthiness compromised in this service approach?
F12 (would have done thins already on F9
F13 Q: can I scale the prover without comprises to the trustworthiness?

Meta: I would introduce the hardware issues in the beginning if this is motivation... you motivated it through maintainability so far (F18+) also there seem to he a assumption of the usage where you need to regenerate proofs often? If so mby. introduce a use-case that needs this... instead of App A / App B find something that convince me this is an issue.

Meta: I think you ran out of time on F20 mby reduce the end to a sidle)listng challanges and accomplishments). E.g. Implemented a service for zokrates, better at scaling with experimetnes (talk to me for details) we belive we can now do folding/recurssion...

F18+ you kind of went to deep for 12 min ... very hard to follow the differnt issues in about 30 sec per slideds

Important: add a call to action instead of the "thank you" ... put your name/email/github there and the main points of the talk

ZAPI/NAPI/.... splitting your scope, feels defensive (e.g., why bring it up, lets ppl ask if they wonder)

JH: focus on ZAPI. the seocnd part could be improved

NL: was very well presented but... was not so clear who the audience is? Is it industry/developers? For that having something like background/motivation there typical?

KW: Architecture Slides could come come earlier (e.g. S12)

NL: I wouldn't go to the alternatives? I wouldn't touch programing langunages (shorten the beginning)

NL: not clear what you objecitve is. What should ppl ask you about. Pushing Zokrates at TU Berlin, is it this is a good idea...
10:27 AM

SW: Is it about adoption of the approach?

[alv-around]

Feedback

Slide 2: use figure
Slide 3: larger
Slide 4: make clear that there are more tools visually then you do not have to say it.
Slide 5:
Slide 6/7: introduce perspective (story not 100% clear)
Slide 8:
Slide 10: perhaps show the difference between “old” and “new” approach on one slide
Slide 12: make benefit “reusability” the title slide or visible somewhere else
Slide 13: same with “scalability”
Slide 16: can this really by realised so easy with other tools? CAPI, NAPI, ZAPI
Slide 17: make sure you distinguish what is technically feasibility because you demonstrated it and what is not
Slide 18:

Nikola

Good speed
Not clear what the audience is
Would rather present a use case in the beginning
Background may not really be necessary
Sebastian: what is the pain point?
Karl: The “can” slides could have been presented much earlier
“Can” slides: just show “can” slides and not all the background. No time for that.
General: slides 15-17: just show ZoKrates and then show what other tools can be used separately
Slide 18: what should the key take away be?
Not sure what is already known and what not.
Would be nice to push ZoKrates @TU Berlin.
Its important what the audience 

Stefan

Slide 17: in the table everything is green. You can show differences between the tools.
You can be proud representing ZoKrates.
Two important things
    Notion of service provider: Who owns the service? Everything resides on the same machine. You need to clarify what a service is to you. If a service is something that can be outsourced, it is much bigger thing. 
I have not seen anything cloud-native in the presentation.
To make it more constructive: your point is a different one: what is your current position and your roadmap, who are possible collaborators?
The beauty of your approach is: integration of many service into one.
Proving-as-a-Service notion is much larger than providing a separate API.
The audience may think about “Amazon” Services when hearing the term “PaaS”
Figures are partly confusing, e.g., regarding deployment. 

Sebastian

No thank you slide. But call for action: key points, contact information, offer for collaboration.
Be bolt, we are the first with in the next-generation of proving.
You can have one slide towards the end where you have the central take aways presented. 

Frank

People tend to forget details from presentations.
Optimize for hammering few (1-3) statements into the heads of the audience. 

Karl

Not clear what you can expect from the audience.
The word “ZoKrates” will appear only on slide X —> should be mentioned earlier.

Yixing

Use different colours. Color-coding was not clear.