Alba Demo

[rrtoledo]

Why

We intend to do a public presentation on Alba and its library.

What

This issue aims at choosing the list of issues and their priority to incorporate for the demo

[rrtoledo]

Here is my take: As we already had given a presentation on Alba (for the innovation team only), the demo should show more. My plan for the demo hence is to 1) present Alba and 2) its applications/where it could be used, 3) its pros and cons. We can then 3) discuss about the progress done, 4) what's left to do (with a wink to the design and roadmap) and finally 5) run an example.

This might seem quite ambitious, but we are already working on most steps needed for it. Ideally, I would like to have the current issues handled as such:

To merge before:

• Benchmark
• Tests
• Error handling
• restruct(2)
• license
• centralized docs
• sample distribution error
• lottery (would be in "nice to have" but we're already working on it)

Nice to have:

• generics
• hash from user
• decentralized (lottery + centralized) + decentralized docs

Not needed (yet):

• all others

[rrtoledo]

@curiecrypt @tolikzinovyev @djetchev What are your opinions on what the presentation should be?

[curiecrypt]

@rrtoledo I think the agenda seems good. About the content, I would do the following: To merge before:

• Benchmark
• Tests
• Error handling
• restruct(2)
• license
• sample distribution error
• Generics
• Public function docs

Nice to have:

• lottery
• decentralized (lottery + centralized) + decentralized docs
• Cargo docs: Intro, overview, centralized, and lottery and decentralized if we tend to implement.