# Meeting Notes

## Combined training

What topics to cover ?

* How polynomial commitments work
* How plonk arithmatization works
* How evm works

* Hermez is spcificying mul mod. Would be good to multiple specs for mul mod
* 20 lines of assembly code
* assumbely assumes big int arith
* There are some assumpiotns from ohter state machines
* Many layers, and not always cut the smae palce
* Maybe specs won't be hte same

* Haichen
* Generally agrees
* shold we spec evm from yellow paper ?
*

* Jordi
* Yes
* We should inderstand what we are building
* Spec should list differnces
* Opcodes could be differnt due to limitations
* not so many custom gates in hermez compared to scroll
* These differnces might lead to incompatibilities
* We probably can't have a sinlge spec for both teams
* Or even a very similar spec
* Maybe we should start exploring the differences ?

* Haichen
* Definely some overlap
* common sessions for polycommits, plonk arith, evm specs
* Common errors in join sessions
* Differnt teams can do in depth sessions

* Daniel
* What are timelines ?

* Haichen
* After devcon start audit / training session

* David
* Starting to look for auditors
* Plan to start training mid October
* Would be good to coordinatae on that also
* Just after devcon

* Jordi
* Maybe before devcon
* Limitaiton is getting the people
* We should start now, the soner we can start the better

* David
* Mudit is working on that

* Jordi
* A good starting point is to confirm the list of topics
* This is what the training sessions wil be about
* this is the first thing to do
* Other thing is to setup the list of bugs
* Shared knowledge
* Should spec out differnt peices and compare

* Haichen
* Should compre keccak
* Who will decide if to include both of these

* Jordi
* We should comprea and show the auditors

* Barry
* should start with sth simpler eg. MULMOD, not Keccak

* Jordi
* Agree on mulmod
* On goveranace side
* If we decide to have a single document, we should just try and agree or not

* Barry
* Agree on consensus
* EF does not want to impose anything

* Haichen
* Agree on starting with multisig
* Mulmod could be similar
* Keccak could be differnt
* Lets do case by case
* Same auditors to review boht parts if they are simliar

* Barry
* EF has some people to audit both implementations

* Haichen
* Next steps
* prepare stuff for learning gorup
* Spec out thing and compare
* Tentative timelines is after devcon
* Who should we invite ?

* Mudit
* We are looking at
* Trail of bits
* Spear bit (EFpeople s independt auditors )
* Hexchange

* Barry
* Quan
* EF security team
* 0xp

* haichen
* We have some people to include also
* Gonna prepare a doc to descibe how to audit

* Daniel
* Spread sheet of known vulvneartilbiltes

* Haichen
* Good call.

* Jordi
* Lets call next week and discuss specs ?

* Ye
* Quick summary
* Gonna have join learning session after devcon
* Because ther eis some differences in implmentation there may be differnces for differnt peices
* So differnt teams can have different sessions around the main sessions
* We can put togetehr some common parts and for different parts differnt teams can scedual differnt parts

* Jordi
* This sounds good

* Ye
* Next steps is to find common spec
* And create list of vulneratibilties

* Jordi
* Yes i think that is it
* Okay lets scheudal a meeting for next wee or something sooner ?

* Haichen
* I think we can do this next week. Put down more details and review tha tnext week
* I will sent out another invite later

* Ye
* We can put forward a scheaudal and list of attendees who might join