EIP History, Documentation & Processes with Pooja Ranjan (Cohort 3, Week 6)

Transcript

hello everyone this is women in theorum protocol study group and we are already in the middle of cart's week six and uh today our office hours and we have a special guest huja huja Rajan from ethereum cat herders welcome fja thank you Kya it feels like being a guest at my own house but thank you so much for the invite and facilitating these meetings for us yeah exactly Pua is always with us she supports our calls a lot and uh today she will be our speaker before we start Puja could you please tell us about your way to the protocol how did you start thank you Kya for providing this a

stage to maybe talk to my own fellow girls here about my journey I think I started back in 2017 with the launch of a blogging website called ether world.co this website is um basically to share information about ethereum in terms of news project updates and Technical updates that we generally publish with that in 2019 people were looking around to support ethereum protocol development they were looking for some projects manager to help out and make this project as a proper project and do some other stuff that can help run the

protocol smoothly so I joined ethereum caters it was a working group at the time and my main job there was to document all codev notes I also helped facilitate Network upgrades uh in 2019 and since then a few years down the line in 2024 July we registered ethereum cat holders as a nonprofit entity in the United State now this is named as EC Institute so that's how my journey with ethereum protocol started however in in way I continued meeting people and I met ladana in 2023 yeah that was our first

meeting there during an event we talked about how we can onboard more women how we can make sure that women are feeling comfortable joining this space so that was the beginning of wiep we made the launch announcement in February 20124 it's been over a year and um I'm so happy that uh this study group coher is working well we are proud to share that we have graduated many women and some of them are now contributing to ecosystem I can suggest a few name right here but I don't want to name names but I know there are so many girls who have stuck around and trying to contribute to

ethereum protocol yeah for those of you who doesn't know yet uh Puja is one of the co-founders of women in theorum protocols so so thank you pja for organizing all this community wonderful community of women and what about eat herders I really love this team and they do a lot for the protocol they support ACD calls and other calls and they provide some more deep technical information about the protocol could you a little bit tell a little bit about your team what you normally do of course so ethereum caters are mainly around the protocol support ethereum protocol

support we are engaged with facilitating protocol meetings I can see Akash joining in here so sometimes he shares meeting recording in form of podcast caders also document notes Merc is here Mercy helps us document notes for certain meetings so anything related to codev conversation or protocol meetings we provide an all kind of support apart from that we facilitate different uh office hours meeting around eips we communicate the with the eips um infra and tooling providers try to educate Community with different podcasts that we run beep and E and ecosystem project demo podcast we

obviously work a lot around wi present cohort and uh we also encourage participants to contribute to ethereum repository especially because we are so closely working with EIP so I love to get some support on EIP bought and any related eips but yeah mostly we are into facilitation and support with respect to ethereum Improvement proposal and community building in general yeah I definitely I really recommend you ladies to join the calls of ethereum C heritors puah how participants can find the links to the calls you have a pep calls right that's right so I think we will share

some link with the presentation I'm going to have right after this but in general if you can jump on to E cat her this Discord you will find the meeting links for all the meetings that happens around we generally maintain an calendar on event section of Discord where you can be informed and obviously social media is a very good place to follow what's going on well Pua thanks for eat herders yeah I really appreciate it and I think we can start the floor is yours today we're going to talk about eips right that's correct so just imagine a world where anyone can propose change to one of the largest blockchain in existence and if the idea is strong

enough that can be included to reshape the entire ecosystem that's exactly how ethereum evolves the process is known as ethereum Improvement proposal process we are going to talk a lot about that but I want to start this day with sharing this slide this is a slide from my con talk and it is to provide a high level overview of how we see eips today some fun facts around that so as you can see there are some charts sharing some important details let me help you understand these every day we receive some proposal the right hand side chart suggests the number of proposals those

are received every year as you can see this is from 2024 so we don't have the data 2025 included in this particular slide we'll get there as well but just taking an example of 2024 we have received over 150 160 proposals right and out of those close to 100 proposals were EC's 58 were core and there were some other types and categories networking interface meta informational and rips we will talk all about it but I wanted to highlight this just to point you towards the number of proposals being received on different repositories every year every month every week and there's a lot

of work going on in the background and we would appreciate your help in facilitating this and supporting us make good standards for ethereum ecosystem more or less only 25% proposals makes it to the final status most of them are either in any other different status or maybe turned out to stagnant meaning they may not be may may not be moving the author is not around or they may not be very good proposals so far uh ethereum has deployed 64 core eips on network upgrade that means the present ethereum that you are seeing has been developed by these 64 proposals which helps run the

chain both on execution and consensus side the upgrades that included highest number of eips were banti and Denon upgrade and the number was nine but you would be surprised to know that they are going to break their own record with the Petra upgrade this time it's going to be 11 eips to be considered for the upgrade so what is an EIP in simple terms it can be considered as a maybe a formal process through which changes whether they are technical upgrade related New Standard Process Improvement or any application related proposals are considered and they are added to the

ecosystem once they are adopted implemented so we will talk about these and I feel like this is very important to have this process in place because with this we'll be in a position to maintain the consistency we will standardize the process so any new project who wants to maybe pick up a proposal and deploy a project on top of that or have some use cases of that may be able to work in that it provides a space of like you know open collaboration and obviously everything is transparent because ethereum is a big ecosystem with open-source code taking a step back how it all started so it was mentioned in EIP 1

that EIP 1 was heavily inspired by bip1 bp1 is basically Bitcoin Improvement proposal and this bip was inspired by python enhancement proposal so that's where we started but as on date there are so many blockchains which are trying to follow the process which ethereum is following I was in a conversation with the Bitcoin Community uh the other day and they were happily surprised to see how much evolved we have been here after following just initial process of BPS they even don't have that number of proposals there are very less contributor providing such a SS and making contribution in there so now they

are also inclined towards learning some lessons what ethereum community did and maybe upgrade their process in order to get more people involved because blockchain is all about decentralization and providing opportunities so the first commit to ethereum eips repository was made in 2015 right after the launch of ethereum blockchain um that was done by by Martin who is considered to be the early days contributor maybe the first um EIP editor however the EIP 1 was documented in 2017 mostly by Hudson Jameson I think it was an enhanced work on top of whatever

Martin did but yeah he has been a great contributor to update EIP 1 and help us with the process I'm happy to share Hudson Jameson was also one of the founders of ethereum cat Herer and we started together the EIP IP process about which we will be talking later this is an image again back from my def cont talk but I wanted to have this image right here to provide you a picture of how we are today if anyone is following codev calls they may see that there are so many developers joining both client side like consensus layer and execution layer and they are talking about I have this proposal I want to get it included I have this proposal I want to get it included but how how we can

include all of those proposals there are so many Brilliant Minds around us and they have so many good proposals so it will be difficult for us to have all those proposals in one upgrade and that's why we have started a kence of um getting Network upgrade even if pectra is not deployed on the network today if people have watched they may find that from today's discussion itself like people are working for devet for fusaka fusaka is going to be the next netw Network upgrade but the incoming eips are finalized like now they are working for the devet that means they are not accepting any more proposal so there is so much of work going on in parallel you can see again EIP score ercs and life

cycle we will talk all about it but I think this is a great inspiration to suggest that our community is so vibrant and we are full of Brilliant Minds around here all right so what do we do with these eips so one common example that most of the people know is like these eips are part of network upgrade thanks for the image uh this is created by Akash from etherium cat herders this basically depicts the network upgrade that has occurred on ethereum's both layer if you can see like starting from execution layer we were joined by consensus layer and we had been deploying multiple upgrades uh over the period of time now what is there Glam oh cool we have also included the

glamsterdam here we don't have any idea when it is going to be happening but if you take a look the upgrades are planned so much in advance so in all of these upgrades the eips those are deployed are called as core eips there are different categories as well but generally for any upgrade we accept a proposal which is into core category so core categories like fundamental changes to ethereum protocol like anything related to ethereum consensus this is like a early idea of how ethereum proposals were divided into type and categories so core as I mentioned was mostly for the upgrade side there is Meta Meta means which is kind of fundamental and everyone in the

ecosystem are supposed to follow that we can't ignore that so there are very few meta Eeps and these Eeps are General guideline EIP 1 is also a meta which is the guideline of how eips are documented and the processes are being followed next come interface so for interface you can understand it as like it is the proposals those are suggesting changes for user facing functionalities and apis uh next come networking networking is for node to node communication for client team and erc's basically are application layer uh proposals so erc20 the most popular proposal that uh helped

come up with the boom of all sort of like meme coin as well erc20 tokens and Def I mean erc20 is considered to be one of the fundamental proposal that helped run so many protocols so let's talk a little bit about the GitHub repository in earlier days there was only one GitHub repository it was called as github.com ethereum in which we had eips repo where we had all sort of proposals but back in 2023 people decided to work the repo and have eips and erc's separated the reason for this separation was mostly that they wanted to focus on protocol side the client

team wanted to focus on protocol proposals and they don't want to like you know discuss at the same time the application layer moreover our community was growing so it was a good idea to have this separation in place so people can form different working group and they can have their different meeting places and they can discuss the proposal as needed the reasoning the specs and the changes are documented in The Meta as I mentioned earlier this meta AP is number as 7329 documented by light Klein and Dano Farin light Kleine is one of the EIP editors as well and he has actively worked on helping out the separation of these repos as you can see here uh this first layer is called as

like type so we have three different type meta standard track and informational and standard track has further categories core networking and interface in ERC the standard taxs has ERC and interface because some of the interface proposals are related to wallet maybe to the application so we do have this category of interface on ERC side as well moving ahead as the ecosystem grew we shifted our Focus for for uh layer two projects as well because layer one was built to provide the basic infrastructure and we were hoping to have more projects grow on top of that so there comes the layer

two or rollup proposals so rollup proposals are proposals which are suggested as a standard for all sort of layer to projects in the ecosystem there is nothing mandatory as far as I know but they do follow the kind of like uh the same or similar uh type and category so we do have some core proposals some of the core proposals of layer 2 can be considered to be deployed on the etherium main it maybe a different version or have a different um pointers but core proposals are generally added here keeping in mind that it may be uh deployed on ethereum Manet at one point of time rrc rollup request for comment is very similar to

erc's that means the applications which are built on top of roller proposals should be categorized at rrc and there are others still to be defined this is very new repo and people are still working on it however the best part here is like they have documented how they want to evolve this repository or this set of information with rollup Improvement proposals and a meta AP The Meta AP number is 7810 this is very similar to EIP 1 and you would find all the instructions and guidelines of creating documenting reviewing and maybe implementing M menting guidelines for certain proposals right over here so this is how our current ethereum proposals GitHub repository look like

this is basically the standards that we are looking at so we have three different GitHub repositories depending upon your area of interest you can go and follow the repositories and try to either add or help us manage it even better if you take a look this line is all about type so we have meta standard tracks informational that is consistent throughout the repositories and we have code networking interface on EAP side on ERC the change here is ERC and here we have rollup request for comment as a new category let's take a moment and talk about the process that we follow so if we have to say that um how do we go if we have to structure that we can say

that this process involves mainly four stages the first one is call as like drafting we draft The Proposal then we discuss it third one could be collecting reviews and having some consensus around it and the fourth and the final one would be the implementation and adoption so these can be the four stages but during these stages an EIP has to go through these statuses so the draft is the very very first one when you are proposing your proposal uh you document it and we will talk about how can you even propose a prop proposal so we document this proposal add it to a GitHub repository and once that is merged we will find the proposal as

draft proposal next comes review so any proposal can be like basic just basic information added over their specs added over the motivation and then we uh have this proposal added to the website the official website then this proposal under goes review review of editor review of community review of Cent developers so there are so many participants of the EIP process we will talk about them in detail but on a high level these are the three main group of people who would be interested in providing reviews after review if proposal initiator the author or the champion thinks that uh the proposal is in good

shape and it can go to the final status The Proposal is moved to the last call the last call duration is fixed for 14 days for all all other proposals except the core proposals so if a proposal is an ERC that will be staying here in in the last call status for 14 days and during this 14 days if any specs related changes are suggested by the community the author may or may not consider but generally it is recommended that if there is significant change request please do consider and move it back to the review and try to bring it back in last call when they find that spec is stabilized once uh this 14 days duration is passed

the proposal can be moved to the final status and that's where it will be called as a standard to be used you may see a few different statuses as well so stagnant status is a bucket like you can say that we we have considered it as a bucket where proposals are pushed by a bot we do have a EIP bot which is add this stagnant status if the proposal is not moving for six months or more however these proposals are not generally dead anybody can revive these proposals by bringing it up back to the status from where it was moved to stagnant and pursue it with the normal process of like uh the life cycle of any

EIP next comes withdrawn so withdrawn is a category from where proposal can never be revived at least not with the same number even if a user want to revive a propose proposal which is exactly the same which was in the withdrawn category he may have to go back to the draft status and begin it from there by saying that we need a new number we need to follow the process because withdrawn is when an author decides to stop moving the proposal there's another status called living so this living status is for very special proposals which are expected to expect changes frequently and they are basically some guidelines so people don't expect it to ever reached it to the final status EIP 1 is

one of those proposals in previous slide I mentioned that um the last call duration is for 14 days for all other proposals except for core there is a slight deviation in the statuses provided to core proposals and this is defined with a new proposal suggested by Timo it suggests that when a core proposal is being considered for Network upgrade they may have to go to different stages here it is defined as proposed for inclusion considered for inclusion scheduled for inclusion included and one is decline for inclusion so proposed for inclusion means you are proposing this proposal for uh an upgrade uh for example for

Petra upgrade for fusaka upgrade for glamsterdam upgrade whatever you want to choose and you move across these depending upon where they are in terms of network upgrade progress like whether they are on devet whether they are on public test net whether they are on Main net so when they are on devet they would be considered for inclusion uh when they are on public test net they would be in last call and here the last call duration cannot be 14 days because generally um there are more than one public test net and they would like to keep it alive for at least 14 days each test net so it's definitely going to be longer than that and final when they are finally deployed on the main L how this decline for inclusion

is not the end of a proposal it may be end of a proposal for that particular upgrade but this proposal can be considered for a following upgrade so for example a proposal which was marked for DFI in in Petra can be considered for fusaka so that's the process that we are following in um Network upgrade and this is specifically for the core eips moving ahead this is our current status the present status so we have 942 remember in the initial slide I showed the data from uh from previous year and I think we are over 100 eips in next in just 3 months so just imagine the volume we are receiving here so this is our

present dashboard thanks to eips Insight team that they have provided a good visualization of how we are doing where our eips stand at any point of time if you take a look here only 222 proposals out of 9 942 has reached to the final status there are 33 in withdrawn and 233 in draft and look at the number here for stagnant 357 so my request to anyone who wants to suggest a proposal to ethereum ecosystem please do not leave the proposal in stagnant come talk to us we'll help you move it you move it to whatever status

you want to either it has to be in the final status or withdrawn but just don't keep hanging stay stick with us and we will help you move the proposal to the right destination this is another visualization of the number of proposals or number of um eips which we are receiving every month this is a great visualization you can check out on the link added over here so if you see that in the beginning there were only like you know core proposals like mostly the red orange and yellow line you would see here but after 2020 B3 there's a huge volume of erc's joining in like ercs are coming up now meta is also good like but there are not so many meta now this pink

is like late in 2024 may not be very clear with this diagram but when you look at at the dashboard you would find it good and just see this volume and just see this volume the numbers are like so unevenly separated spread over there okay now let's come and talk about how one can propose an EIP so proposing an EIP is not very difficult you know uh you just need to wet your ideas and ensure that that the idea has not been already proposed it is unique it is helpful and for that you should talk about it at a forum called Fellowship of ethereum magician so you just share your idea in Fellowship ofan magician to

collect your initial um feedback like whether it is good even worth documenting it or not say for example you get some support and you plan to document it then there are so many sources available for you to document it and move along the process so for writing this proposal you need to follow a template that is added in EIP 1 the EIP template and following those template you can have your input done and you can document it I will also share the tool with you all that helps document this proposal at initial stage if you are very new if you don't know how to do document them then you have to make a pull request to ethereum GitHub repository in earlier slides we shared that there are three different GitHub

repositories that we are considering from different standards as on date so whatever your proposal is you go to that particular repository and make a pull request over there getting feedback is like kind of loop until it reaches to final sometimes even after it reaches to final people still keep getting feedback which is not a bad thing to happen but yeah getting feedback is very important for a proposal standard so we should try to collect as much as feedback possible this is a very good tool developed and shared with us by eips Insight team so if you are documenting a proposal you can simply go to this new EIP and write everything over here this is already having uh the basic structure

that is required to make a pull request as well as it has basic bought checks so whenever you make any PR to GitHub repository there are four or five Bots that shows up and that will start checking whether your code is good enough to be merged or not so this is like already bot proof so when you are documenting your proposal right here if you're making a mistake it will stop you it will let you know that this is not right you should fix it and once it is done you can simply download this preview and this would be yourmd file that you can upload and make it a pull request similarly if you are trying to make any changes to an existing EIP you can simply import this EIP from here everything will be allocated here and

then you can update whatever updates you want to make download the code and make the pr making life simpler here so that's how we document a proposal now let's talk about the participants of the process I already have highlighted a few participants authors Champions and editors we have this great community and we try to collect their feedback code developers is another set of uh participants which are very vital for code proposals other than core proposal I think you would see code developers around mostly around networking and interface related proposal but they are less interacting with ERC related proposals so that's the main

participants here Champions are one who can either be the author or who is trying to pick up a proposal which is resting in um stagnant status and he wants to revive it or he just want to um move a proposal to final just giving or volunteering his or her time to support that proposal there is another group called EIP reviewers we have recently launched this program to on board reviewers to help us review these proposals and get quality standards for ethum ecosystem so we'll take a look here so I mean generally speaking author is the one who documents the proposal and reviewers are those who can add technical feedback

editors are people who are generally involved to um provide editorial feedback they can allocate the number to the EIP they can suggest okay whether it is as per the template or not but um they may or may not be adding technical feedback however we would want that proposals which are getting to final statuses and being considered as a standard should have good use Case implement ment ation and specs easier to follow so for that it is highly encouraged that anybody having any expertise in any category like we have so many categories you can be a reviewer and help us get quality document editor associate are people who are helping

allocate the EIP number to proposals which are added to the GI repositories this is again high level overview of a focus area of responsibilities of editors and reviewers I think I had a talk earlier this January so maybe you can follow the clip to get more about it okay so now we talked about the volume of proposals now here we want to take a look at uh the job done by editors and uh want to share our gratitude to to these people like they are looking at each of these po request every day and trying to help us s so this left side is uh for all the present editors and this

right side are from the reviewers we had launched this program in January 2025 and since then we have received a decent number of interest to help us with the reviewer leaderboard so I'm so very thankful to all these reviewers who have contributed you can see 55 plus proposals in less than three months so that's not bad it's it's actually very very good thank you all and Kos to your hard work over here now if you are considering to become an editor if you are considering to support with our reviewing process where would you get information so all these information are mostly documented in this EIP editor handbook which is again a meta proposal

and is in living status living status because depending upon the need of the ecosystem we will keep on updating this editor's handbook whatever works best for the present scenario we'll want our editors and reviewers to be working accordingly so the instructions will be updated here this just our organizational structure decision making process and any other EIP um editor related odds and ends meaning how we make decision it should not look like this five or seven people who are editors can make all the decisions there is a process in place and we will talk about those processes in a minute so for General proposals General PRS mostly it is not difficult to say

whether it can be merged or not we can add our editorial as well as technical input saying that okay this is the change you would want to make in order to get this proposal merged but there are some Corner cases and how do we deal about that I have taken an example of one PR that we received so when there is something which has some kind of like different divided opinion people want some people want to merge it and some don't then we take help of this process called call for input we try to collect input from all the editors as well as for the community this issue is created on E cat Herer EIP IP GitHub repository you can go ahead and find I think at present we have two open issues so you

can also add your feedback over there so there um one of the editor will open the call for input they will add every details here like what is the um question that we want to get answered what decision we are trying to make what if we get support what if we do not get support for the proposal and this is open generally for a month and after a month based on the inputs collected we make the decision and we either close or merge that PR so it's not that we these five six people are making all the decisions it is that we want to come to a rough consensus with collecting everybody's feedback even for decision making process over here and then we

decide whether to merge it or not this slides talk about some of the common mistakes that an author may do in process of documenting the proposal and suggestion of some best practices that may help them document a better proposal or you know even if it is an update better PR the first thing that everybody should do in mind if they are considering documenting a proposal please read EIP 1 EIP 1 is like Master document for us it provides a good guideline of how an EIP should look like different types and categories it is provided there so you can figure out whatever suggestion whatever proposal you are suggesting is belonging to which particular category

then the spelling and grammatical error we do receive like tons of PRS for typ ofix so if you can just run grammarly nobody will be sending this type of f kind of PR so it's a good idea to maybe go through that a spell check and grammar La kind of thing try to incorporate as much as Community feedback possible and uh people have generally been mixed up with what to add in motivation and what should be in abstract so be clear about that try to keep it precise and in simple language so people can understand it and obviously please please please please please do not abandon your work please stay here do not let the proposal

move to the stagnant status and it would be something good for Community you are doing it for greater good and it will be there if you stick around for a little longer as a best practice you can perhaps take help of templates and tools those are available make use of Fellowship of ethereum magician and other discussion forums and please work around to explore the chances of increasing adoption like for core proposals those are deployed on mainnet and there are different projects like infrastructure providers they may be making use of those but for application layer proposals it's highly recommended that you go and talk to different projects who are are open to implement your ERC and that would be good because

whatever you're suggesting is a standard and for a standard we would want that implementations are there how could you get involved so I'm very happy for whatever work ethereum cers have been doing in the ecosystem because I feel like we are in the center of the ecosystem we interact with each and every individual um if not directly maybe indirectly but definitely in touch with the ecosystem to collect their feedback and help them support them get involved with whatever they want to get involved with as on date ethereum caters are heavily engag with the EIP process and um we have tried to highlight what are the activities we we do around eips how you can get involved so we do have

an EIP IP meeting that happens once a month uh it is on every Wednesday at 1400 UTC you can find the agenda on ethereum / PM GitHub repository for the next meeting we do have um weekly EIP office hour uh so by weekly we do it for EIP plus ERC but um uh the alternate week we do it for EIP only so this office hour is a place where you can ask questions directly from editors help push your PRS get merged and if there is a blocker you can talk to editor and get it resolved so we are trying to create an environment where we can provide as

much support as possible so so you can move your proposal towards the final status we are helping onboarding with reviewers and editors to support this process and obviously get community's feedback in order to improve the present process yeah I think this is a very good quote right here ethereum is an open- Source ecosystem that thrives on Collective effort and every contribution big or small helps improve the present Network so please contribute the way UK can we have multiple resources available for for you to learn and to be able to you know participate uh you may follow the Discord link for ethereum caters there we talk a lot about EIP we do have a dedicated channel for EIP editors

where you can directly post your question and get help from EIP editors for all discussion we encourage people to create a thread at Fellowship of ethereum magician you can find the link for different standards we have different giab repository the official website is e. ethereum.org and you can follow the analytics at eips Insight yeah how to start contributing today review existing proposals take a look at that you can be a champion you can be a reviewer and you can help us so that's all about today's presentation and uh I would love to take any questions if there are any and would highly highly highly encourage you people to start from where wherever you

can I think the study group that we are having in um wiep can be a good Landing point for you who are new to the ecosystem and with some kind of um handholding you should be in a position to cont ecosystem one day thank you very much P it was so insightful talk yeah and I even knew a lot of uh like great resources I didn't know about them about EAP and and uh ladies if you want to contribute um feel free to tag Puja on our Discord on it's C herders Discord and you will have this recording on how to start this is really great topic

thank you do you have any questions ladies please feel free to raise your hand ask in the chat and while you are thinking on your questions I wonder are you familiar with any of eips uh or erc's uh feel free to drop some numbers into the chat I'm sure you know anything at least one Erp or probably ERC question from L why was there such a spike in eaps in 2024 that's a very good question so we had this separation of giab repositories in 2023 of EIP and ERC and we tried to like have different

working groups work on different proposal different set of proposals so I feel like the focused approach helped increase the number which was not like um very helpful to editors but definitely helpful for the community we received um about 50 plus yeah in in 2024 for um core proposals we did have some Network upgrades plan and so many more on the ERC side as well okay great so our participants familiar with ec20 this is the most popular here see yeah the talking Standard um okay well

2535 uh great Glory good job and we also have mercy here she's also a participant of this cohort and she's a reviewer right reviewer so feel free to ask here in our community Chan Channel if you have any questions on how she started I'm sure Mercy you can answer some questions for fellows well any questions ladies feel free to ask I would like to comment on ERC 2535 thank you glory for working on that I think um at the time it was one of the contentious proposals as well like it is an ERC but people have divided opinion it was really

interesting to talk to Nick about this proposal and we did record I believe a p episode on that so that was one of the good proposals thank you for your contribution there great thanks and if you are not familiar with any of them you will have a home assignment today's home assignment where you have to learn one of them so please read it carefully question from L do I need to know a lot about how ethereum Works to be a reviewer to be honest uh to begin your contribution I don't think you need to know a lot but as a reviewer our general ask is you should have technical

expertise it can be in a language and it can be in a domain there so while reviewing those proposals you can focus on the spec side of it and maybe able to support like okay this is the right spec and this will work uh that kind of review can be added as well however editorial reviews are also welcome so not too much of knowledge is required but having knowledge is good to have and this is an additional motivation for you to work hard on our cohorts if you're interested okay yeah on a high level you can consider it as like a standard process consist of three or four different phases first phase is idea phase where you document second is

review third is like when you are collecting feedback from community and making sure everything is in place and fourth is like when you are working towards getting adoption or implementation so these are the main stages and the process of a standardization are considered of different statuses but that will be same for all of the uh type and category but uh yeah I mean I don't think it is a difficult process but uh you can learn more about it with E1 happy to answer any question now or later as well if you have more questions on standardization process yeah p is in our disc court and it kept her d as well as she mentioned they have a special channel for eips so

feel free to ask pja do you have an experience of contributing into EIP maybe you're an author actually yes the EIP editor handbook 5069 which is actually a living and meta e this was basically a handbook I mean like the hackim defile that I used to maintain in the past I was trying to collect uh information how we can share what is required to become an editor or what is required become a reviewer so we put together all these information from hackmd to this proposal so eips and erc's um they have the same reviewers for now we do have dedicated reviewers as well like so we have a set

of EIP editors who are focused on code and networking and interface related proposals and we do have us dedicated editor for ERC and same goes with RP as well like we have a dedicated set of editors for rip related proposal but I think uh to begin contribution you don't have to focus on these things whatever your area of expertise is or your area of interest is just start lurking around and you'll be able to make some contribution one day if you look through eips and your you will find that some of them are really technical but some of them they are you can manage them yeah you can understand them and you can

manage them so feel free just to look at some of them that will be your homework with no questions more I believe that people have understood the process very well and next time when you hear about a major upgrade uh you will remember that it all is started with EIP so if you want to be part of ethereum ecosystem think of EIP as the first step I look forward to getting some support from each one of you yeah actually a lot of my a lot of my friends ask like I have an idea how can I start so now I and you can share the link to this video and we will have slides as well so how to start contributing to VIPs right this is the very useful session thank you

opportunity all right thank you again thank you herders for supporting the system Akash Mercy fja everyone who's here from the team and uh we'll see you on the next Thursday on the standup call thank you ladies thank you by see you around