leanConsensus Call #1: Team intros

Transcript

hello and welcome to beam call number one uh we have 64 participants right now and uh and folks are still flowing in uh this is a a very special call uh dedicated to the the social layer uh we have many many different teams that have come forward in addition to the consensus layer teams the six existing consens layer teams uh that want to you participate and contribute towards this uh this beam chain proposal and so today really it's an opportunity for these teams to say hi uh you know share who who who they are uh and and their plans and and disclose a little bit more information and to also you know um

share contact details so that we can we can start collaborating and and and creating telegram groups and and and whatnot so I've uh prepared a little presentation um so I'll be sharing my screen real quick and then we'll get started with the the presentations okay so uh beam call number one uh dedicated to the social layer and uh just as a heads up my plan is to have uh beam call number two in a couple weeks uh on uh February the 28th uh at 2m UTC I'm shifting things by one hour uh just to be slightly more

friendly to people uh in Australia and New Zealand and uh Oceania because we actually have three different teams uh that have uh quite quite a lot of people uh based there uh and the second call will be dedicated to all of the technical progress uh that we've made uh since the deathcon talk uh and there has been a ton of progress so this slide here shows some of the the new consensus layer teams that have come forward uh we have eight new teams and um you know some of them have a new name for their client for example Z and re Lantern kri and afre uh and we also have three existing teams

that don't yet have a name uh for their for their clients and uh these uh teams uh you know span multiple different languages some that are kind of new to the to to to ethereum for example uh Zig um so lots of of client uh sorry lots of diversity here at at the language level uh and I think this is you know particularly relevant because we're moving to a paradigm where we want to be snar friendly and so maybe there needs to be some some adjustments around Which languages that we use to build these consensus layer clients one of the things I do want to highlight is that the the death count here well first of all it's it's provisional like these teams are still

in formation uh and for almost uh every one of these devs they're still part- timers right we're still setting up all of the infrastructure socially uh with team formation and funding and and and things like that um one thing that I'm super excited about is that these teams are extremely uh geographically diverse uh we're now spanning all of the continents uh including South America Africa Asia I guess we're not yet covering Antarctica so uh there's room for more um and um you know you can see here from where all of these coordinators are are based in

in different countries and usually um the the team uh you know around the coordinator is in a uh proximate geography so here's some of the um the websites and GitHub orgs that you can go check out uh some of these uh teams have already started uh development work uh for example um working on libraries like lip P2P or ssz or doing some early experiments integrating with with ZK VMS and if you want to track some of their progress you can you can check their their code uh and another interesting aspect here is that um some of these teams are completely new from from scratch uh and

some are existing teams with existing business models and especially for the the existing teams that that brings uh funding diversity so uh you know a surprisingly large amount of these these teams at least for 2025 are are self-funded so for example uh never mind uh Lantern and and and Lambda class and that really adds to the uh robustness uh of uh of the the diversity now one thing that I do want to highlight is that uh Proto I am expecting protocal gild at some point uh hopefully to to to support uh the the beam initiative especially if it kind of graduates from a proposal to something that the community actually wants uh to

to build um but I do want to highlight um that there are like going to be you know requirements in order to to get that so if you uh right now we have this uh six-month Cliff uh requirement um to be part of of protocol Guild um and I I I expect that there's going to be a rule change relatively soon which is going to uh require protocol Guild members to be to be working full-time uh on on L1 uh R&D and um just as a as a heads up as well um the protocol Guild funding is going to require some sort of a formal approval so someone possibly me or one of the the be coordinators uh will have

to uh submit uh a formal proposal and it going to have to be voted upon by the the protocol Guild uh d now um one thing that I want to highlight is that um so far you know I've largely been a a bottleneck in in in in progress uh and it's been especially difficult for me because I'm not only working on the beam chain but I'm also working on the native rollups and and the base rollups and so part of what I've been really trying to do in the last few weeks is remove myself uh as a bottleneck and I'm really really uh you know pleased to say that now I have uh you know a ton of support uh you know coordinators who can who can really you

know connect the dots and you know lubricate things and reduce friction and and and and and basically make sure that things keep on running even when I'm sleeping even when I'm on holiday or whatever it is um and uh I think most of you will know Josh uh Josh has been with us for for for several years now he's doing a tremendous amount of work and we have two uh new faces here so we have uh lisl uh and we have will and these are the the telegram handles so do feel free to to to Ping them to to DM them and uh and to to make use of these uh coordinators which hopefully will allow us to to uh really move much much faster than

we've been uh moving already uh and we have been moving you know pretty fast already now um one of the things that I want to uh talk about as a little interlude um is actually a setback that we've had um uh ironically it's it's not one that I expected it's not uh a technical one it's not a social one it's not a financial one it's actually a legal one so just as a piece of context U we have um other projects uh that have the same uh name uh within the blockchain space so there's two other um tokens well there's two tokens that have the the the ticker beam one was launched

in uh 2019 one in 2023 and uh it happens that the the the second one here uh has a trademark on the the English word beam and um you know shortly after I uh I gave my my Devcon talk uh I actually received a c and assist so they sent me a c and assist on uh my my my personal email address as well as my my personal uh Twitter account and you know it's been a a discussion with the the the the the the lawyers uh you know within the FM foundation and we also had a conversation with the with with with the beam team and basically the the

outcome of of all of these conversations is that we uh we need to change the name so um one of the uh things that lisl is going to be working on is basically um trying to to to gather suggestions uh from from the broader Community for for for a new name we already have quite a few suggestions that have been brainstormed uh within the within the Firm Foundation research team and basically trying and curate them and and hopefully we'll get to to a better outcome like an even better name and and maybe one which has kind of richer law in the sense that uh the name will not have been just chosen top down but instead kind of uh chosen in a more in a

more decentralized way now one of the things that I want to uh briefly touch on before we do the the intros is that um in addition to the the these new Dev teams that are being set up uh there's also you know a lot of work uh on on on the research side of things like one of the the big deliverables uh for for this year is to have this this beam spec um and you know there's there's because we're we're taking a very holistic uh picture there's there's actually a lot of modules that that are being worked on in in in in parallel um and what I expect will happen is that you know this

research is going to really mature uh this year uh and the the devs will also have an opportunity to learn about the the state of the the art research so that in 2026 and Beyond if the beam proposal you know does graduate uh to something that we want to do um you know the devs will will have a lot of context and hopefully will be able to to imple implement things um you know understanding deeply what's going on and and and hopefully doing it uh faster and and better um now one of the things that I wanted to highlight is basically some of the the the coordinators or or or leaders uh that are um you know bringing bringing the leading the the the

research um or the coordination around these these important topics um uh so we have uh you know on the on the cryptography side of things we have uh Benedict um sorry Dimitri uh who's working uh on on uh on padon and is is is is generally very much interested in making things more more snar friendly uh we have Benedict um that's working on the the post Quantum signatures we have aners sorry Andes in in in addition to to uh to Ansgar and and Casper working on on insurance we have Franchesco uh

working on on finality and things like orbit we have tomama uh working on on fossil and actually we have a we have an EIP uh that's already ready and we have uh Julian uh who is you know basically dedicating himself to attest a proposal separation APS and is doing a very uh forough and comprehensive um design space exploration so if you are interested in these topics I I uh kind of encourage you to to go talk to these people and they can show you um the you know where to go to get more information now another thing that I

wanted to to talk about is the the zkv M accelerationism uh that that we we're doing a different Foundation like a big bet uh of of the beam chain is on on ZK being able to take AUM to the next level um and uh you know my hope is that uh over the course of the next few years uh the tech is really really going to mature and going to be uh mature enough uh to basically uh secure like a a multi- trillion dollar uh a network uh such as such as etherum and uh we have right now we have uh four different kind of accelerationist tracks but I expect that uh we're going to have more more in the

future so right now we have uh a $20 million formal verification effort which is led by Alex Hicks uh we have a padon uh crypto analysis initiative uh with with metri we have uh e proofs uh.org uh which is a zkm uh benchmarking and uh you know uh will you know as as one of his first projects might be might be working on on on on on that uh and then we have the the native rollups effort which is um you know adding a lot of motivation as well uh at a different layer of the stack um and we have Matthew who's organizing calls and

actually um just in a few hours we have a native rollup call number two so if you are interested in in joining that call do DM Matthew directly or DM me and I'll I'll put you I'll put you in touch with the the right people now without further Ado uh time for time for intros uh so what I've done is that I've actually ordered these teams in Reverse alphabetical order which kind of coincidentally roughly matches uh when these teams were were were formed um and I guess we'll just go go in that order so I'd like to invite gajender uh to kick us off uh on behalf of the of the Z team thank you Justin uh let me start a small

presentation that I have to present I have there to present here perfect so every team will have like um a few minutes to to present um to share about their background and then there will also be time for for Q&A like two 2 minutes or so per per team of Q&A so I hope everything is coming through yep all right so thank you Justin for giving me the opportunity to talk about

Z in this call so Z is a zig beam client which is work in progress and I'll talk about us I'll talk why we believe in beam and why we created Z and what are our 2025 mission objectives so when eum transition to proof of stake uh basically it was my first heart work for loar so go loar uh so when etherum transition to proof of stake basically topen up opportunities for scalability and decentralization and we believe that uh zero knowledge Technologies often offer another opportunity which is quite unique to fundamentally look at the

problems of scalability universal verifiability latency and Quantum resistance and uh it's going to be quite hard to bring these fundamental changes in be Beacon consensus so that's why it makes sense for that for uh for beam to have a separate initiative to sort of formulate this new stack of consensus uh new consensus stack with zero knowledge Technologies so when Justin gave his first presentation uh to uh Beacon client devs within 2 minutes Z was formed uh and uh why we chose Zig because it is a modern uh uh systems

language with a modern type system and we wanted to bridge the gap of representing Asia on ethereum client ecosystem uh so that brings to us uh so me and gam are the founding team members of Z and here is a small puzzle for you to figure out who's who so I'm on the right and I also get confused when I look at the slide but that's why I left it this way and I and we have a uh growing zma community so please join us on our telegrams and follow us on our X handle and we have have a very active

code base uh that you can explore and see what we are doing and uh for 2025 uh our mission is to have a PC to prove gossip and validate uh basic straight transition function basically it will be a very basic client uh which will have most of the things uh Cho down just to make sure that you know we are able to do a PC uh with one node with multiple nodes uh and then we basically have ongoing Integrations with the various dkms like powder sp1 Cino and right now the Integrations PC's that we are doing

they are a bit broken in the sense that they are a lot of manual steps that are happening so that is what we will smooth out in our ZM client PC where everything will work exactly as a client and while we are doing uh all this we are basically building the zigo system and Community uh with ssz Snappy hash B signatures lip2p and hopefully by the time uh uh beam specs uh drop we are ready to build the client and again going with the ethos of ethereum uh we are uh collaboration we believe in collaboration and uh if you want to contribute uh to beam

development in Z we are placed to to and we happily seek and invite your contributions and I uh in the end I would just like to sort of acknowledge various people we are working with various entities we are working with and uh or will be working with then I hope to put many more of you over here after this call thank you amazing thank you Ginza do we have any uh questions for for Gad there feel free to uh just raise your hand or to on mute and ask the

question I one of the I guess uh unique things about Z is that it's the the first team that has received a a grant from the foundation um and I'm I I'm I'm hopeful that we'll be able to to to give out more grants uh over the over the course of this year uh and you can think of it as a a seed Grant almost like seed funding um and um you know we'll we we'll see uh how far we can get in 2025 with with that kind of money thank you your information okay great uh next up we have the re team with uh oh

the floor is yours hey I also have a screen to share I hope it's up now um yeah so my name is anut or more casually known as o I'm one of the contributor to reaps um reaps is basically a research and development team uh dedicated to experimenting um prototyping building the beam chain uh client uh by doing it one piece at a time uh we were formed in uh December right after just being uh actually late late November right after Justin's um beam chain announcement at defon C and for the past few months we've been working on different components um we work on our foundational rust code base um mostly based on the beon chain specs for now uh

we are also working on proof concepts of the CK State transition functions uh and using different ckvm backends uh namely right now sp1 and rero and also like uh benchmarking them actively we are also documenting our work uh in progress on hack MD as well and we're also uh running study groups since like November and the past Monday was actually our 10th uh study group around beam chain and consensus ler ethereum consensus ler in general so far um for 2025 we are working on mainly three three different components first is the P2P layer for our re client um with dis V5 and gossip sub mainly based on the beacon chain specs um just to get ourselves

comforable and familiar with the spec consens specs um the second thing is we do state transition certification um based on also a subset of beon chain specs as well and uh we try to fit them into different CK VM backends and and and Benchmark them the third thing is we'll try to implement a post Quantum signatures um later this year um but we haven't started any work on that so hoping to do that maybe later in Q3 or Q4 of this year um I also have to note that while I'm from Thailand uh the team is is actually very distributed globally um we have here hoppenheimer um Kaden and Kobe based in the US we have jiun and Jun based in South Korea we have

PARTA based in the UK we have I think Philip based in uh Germany and us and we have Vin uh based in India so very geographically distributed um except for Antarctica maybe uh as well um so yeah that's like six countries represented uh for the room laps um yeah so we are very happy to be here and excited to be a part of beam shade effort amazing thank you honor uh any questions so one piece of information um that I uh shared in the in the initial table is that uh re is the the second

team that has applied for for Grant um and basically the the strategy that we've you know we're thinking of taking is basically using the Z Grant as a template um you know and and trying to to treat all of the teams as as as fairly as possible um and yeah for question is that that's okay why is RIS so suitable for a client so I I think the rest of my team can jump in here but I think one of the main reason is the tools available especially that um so far like we have been working a lot on the ckvm layer and apparently um working with Russ being

able to compile down to risk five um is probably like the default for for most if not all ckvm available right now thank you yeah R Russ is a default but what I expect will happen is that more and more languages maybe to a very large extent thanks to the beam chain uh will have will have support for and Integrations with with ZK VMS I know that GOM has has put in you know quite a bit of work to get Zig uh to to to work on the on the on the various Z kvms thank you so much uh uh oh uh next time uh next up we have uh Camille uh

from quadrivium he he everyone let me share screen okay cool uh yeah that's us yeah super happy to be here um yeah we are quadri uh yeah we are basically blockchain infrastructure company uh with headquarters in Kazakhstan we also have an entity in Singapore um yeah in our uh our main project right now is called KAG it's basically C++ implementation of P Rel client like not many people know but um yeah in addition to ethereum maybe salana yeah poka do also has multiple clients implementation and actually our

client is well fully uh compatible uh with the protocol uh it's written from scratch in C++ C++ um but it was chosen uh to be the language for our project because uh it's one of the most widely if not the most widely used uh language in the in the world we have a lot of developers a lot of libraries that we can use um so yeah that's why uh we chose to uh implement the C++ client for uh beam chain as well or I don't know maybe in future it will be renamed I'm glad we didn't select our name so far because it seems beam will not be uh the name of this protocol yeah uh so in addition to uh KAG uh because

when we were just getting started there was no C++ implementation of lip Library we also implemented the Le P2P from scratch to the level that was sufficient for us to use it uh in poodot but since our first call I think with Justin uh we already integrated uh our library to uh interop framework of lip so can of make sure that it is compatible with uh with other libraries um yeah before it was kind of battle tested in poka do in which also uses l2p but it well they have only Ras client so we only were able to check it against R but now we we kind of check it against other uh implementations as well well um yeah in the past our team uh was also working in

some other protocol implementations like guys were working on filecoin um also there was Project called hyper ler AOA where we also were involved uh it's basically the blockchain that is used in combodian cbdc right now um the fact that I'm really proud of is that the majority of our team is kind of working together for more than five years uh so you can see here the main um contributors main developers in our company um so yeah we have experts in lowlevel optimizations in multi threading uh environment programming and well experts in consensus in uh well storage peer-to-peer networking yeah so really excited to be here hopefully our

expertise will be helpful and yeah I think that's it about us happy to answer any questions thank you Camille I guess one piece of context here is that uh quadrivium is the team that uh I believe uh is maintaining and even potentially created uh the the C++ uh implementation of lip P2P and uh poad do is migrating away with Jam uh from away from the P2P so um I guess ethereum is a a very appropriate home uh for for for this uh Li P2P implementation

okay if there are no questions uh then we can uh move on to the next team uh never mind I think H couldn't make it uh but uh I believe Mark might be here instead hello yeah um I can speak really for NE mind team I don't have any slides but so I'm Mark I work as a core developer from the NE mine team um and I'll be involved in the beam chain project along with hir and others from the team um so nethermind is one of the existing client team so we build the nethermind execution client which is written in C but there's also like wider business we do other stuff auditing

research AI like um outside of that um yeah the whole team is very excited about the uh the beam chain project and uh at the moment we've been working on uh just building expertise around the consensus layer um started to look into ZK proving net for the ne mind client um and for the beam chain client um and we've also uh got a net Li PTP implementation we've working uh been working on um yeah amazing thank you um any questions for the never mind

team I guess one question I have is uh have you started thinking about a name for your your client uh no I don't think we've uh decided on on one yet but yeah it's good to know about this um copyright issues with beam so we'll have to have a brainstorm I think yep makes sense Gom you have your hand up yep um I yeah I had a question actually I saw Wes said you guys were working on an evm like a RIS 5 32 implementation of the evm I was looking into doing the

same thing for for GU but the go compiler does not really support R 532 so I'm just curious how you approach one uh so I can I can answer that so uh okay so we tried uh going through wasm and then going through lvm and that existing tools didn't help us we are also tried going through C and similar thing happened uh now the two approaches is to either develop our own uh translational layer from I Intermediate Language that's kind of the bite code of net to llvm uh or going or modifying the the uh risk 64

compiler uh that is being developed uh and being supported by Microsoft to Support 32 bits wow that's that's pretty intense uh it's pretty intense we do have some some some hardcore people so I think we will do it it just may take a bit of time MH yeah um I I know some zkm I think is also targeting risk 564 so for for GU which is not part of the beam effort I was thinking of actually just targeting Lita as as a first step at least but yeah okay thank you okay thank you so much uh Mark um

next up uh we have the Lantern team uh with me here thanks Justin um I'll just share my um okay yep we can see that all right okay sounds great um yep hi everyone my name is MI here and I'm from the P2 team uh so just a bit more context about like what who P2 is uh so P2 is a Australian company uh that basically provides taking services in the APAC region and as well as we run a bunch of different infrastructure for um a number of different blockchains and um as well as uh we've been working on building a l

line for ethereum consens like lines uh named Lantern in C and last year we basically got to uh showcase it at the defc event um and uh as well as we got to learn about the beam chain so um I guess like the most exciting thing about beam chain is that um the fact that uh like Li devices with limited compute be able to verify uh the state route uh with zik proofs so um we have some ideas about uh working on new kinds of use cases um where uh iot devices are like tracking the ethereum state and they're just using that uh information in the smart contract uh for their use case so

um our plan is to basically just build um prerequisite libraries in C um uh for the beam clients um and the main component that mentioned in the Justin's presentation were basically SEC lip PDP and Discovery um our recent work has just been building uh s library in C uh that we've recently uh open source on GitHub um at the moment we've just been working on um like the test vectors and um once we made sure that it works on number of different platforms um we'll be able to move on to the sort of next modules that are required by lipid um but yeah that's uh that's pretty much it but yeah really appreciate

it thank you m uh and as I understand the name Lantern is also a nod to uh where the the project started in Thailand uh which has a lot of lanterns any questions for me here I also just wanted to say thank you for joining this call I know it's like 230 a.m. certain time um yeah time zones are are really hard yeah hopefully next call will be slightly more friendly uh for you thank you m here uh next up uh we have fed from Lambda

class hey I'm fed from Lambda Lambda is a company an engineering company and research company that started originally originally in Argentina and now it's in Argentina a year ago by uh France and Spain we have Engineers uh mostly in Europe on Latin America and we have been working on the core of ZK development with different partners ZK sync stet polyon uh Mina outside theum ecosystem Alo outside the ecosystem we're working also in distributed systems with egg and layer on other partners on in the last year we have created an elixir consensus client to learn more about the L1 it's already

working the last week it only failed once because of a a back that we were aware of we only Built it with two people on it was more like an MVP to learn now we want to make it production ready but our main focus on that one is to work on the rust execution client that we created that is already fully sying um with mainnet um we're improving the performance on it and we should have some announcements in the next few um weeks um we work a lot with rust elix here uh on other programming languages on the beam we don't have a name it's going to be probably Lambda on the the

new name of the of the beam chain uh we're not very good with naming we have the same issue that nether mind uh I think most Engineers are good at creating things but not very good at at naming we should find a better name um we finally found one for the execution client was it's called e Rex uh like a T-Rex but with a t u because our Engineers found it funny so probably we might find another funny name for this um uh it we're going to probably build it in Rust but since there's many uh I'm pretty sure many people will build things in Rust uh it's very likely you will also do it with concrete it's a programming language we're developing uh

that is similar to rust you can check it out I can show it afterwards it's like a rust but simpler due to due to linear types and we might do it um to have some resiliency on also because we have fun building we're having a lot of fun building execution on consensus CLA for team amazing thank you so much fed um any any questions yeah I I don't want to overstep my limit of questions but this thing about the concrete sounds really interesting if it's like U because with rust you often

see that one of the problems is complexity uh for wi adoption and I never heard about concrete but it seems to maybe solve that issue would it be helpful if that quote would be more accessible for more people in some way um so one of the criticism I have inside ethereum engineering is that it's pretty complicated the code basis the last few weeks I have been I don't want to name name things but we all have good and bad things obviously you can go to our code bases and F bags and complexity but I have been like learning a lot about some code bases I didn't know about and they're super complicated they're super

abstract researchers are very good at abstracting things but when you implement code from my point of view needs to be very simple and very clear actually G it's incredible in comparison to many things it's I'm surprised by the how good it is for the amount of years it have been uh done used on the amount of people involved also there's not a lot of people that work on it so yes like I think the programming language is important and I am a huge fan of rust I have been using rust in production since 2014 we have donated money to the r Foundation we know the court team of R we work closely with them we organized we helped organize in Europe why uh one of the biggest conferen in Rust the problem is that rust is very complex like the micro the trades um the yeah

the amount of crates uh from my point of view young people love it to make things more complicated to show off um I actually remember that vitalic said one time uh that he uh one of the things he learned is to simplify ideas that he used to call um uh a hyper cube of uh a binary hyper Cube instead of an array of bits to something and that's normal we all start like that and we want to simplify things I think the same things happens in engineering I believe that rust has an issue it make it lets you make things too complicated on one of the reasons is how the borrow Checker works so you can check concrete there's um we're working on it that obviously we

won't make money uh out of it it's only a losing money thing but I think long term it could help to have a very simple it's more like Zig but that safe uh system uh program language with linear type system and hopefully it can also bring new developers to ethereum like zigg is is building with G gajinder I don't know if I'm saying your name correctly but I think it's pretty cool to have people working on on seon eum that's going to bring new developers more programming language more people get into the community yeah amazing thank you so much thank you fed uh next up we have uh York from the kri project awesome hi yeah so the C project

like the client we call it CBR so as team we're we're part of um Corpus teams consisting so far of Simon Stefan and myself and we're all based in Germany um so Simon is an old school lad so he has been involved in the da in 2016 his brother wrote The Da and yeah he was not an insignificant part of that and so the last startup so we we've been together already in slockit where they already worked on a stateless client but that was like for the good old proof of work ethereum chain and uh yeah that that was something that was always in the back of our mind and now we're we have a venture studio with two

more co-founders and after deathcon um like like we have we have the opportunity to to check out different things and work on stuff and so after um the talk Justin gave on on the beam chain we also discussed and inally whether this would be interesting for us to participate in the beam effort and yeah we decided to join and um also work on the ultra ultra light side of client development with the experience that we have and with a unique approach um and so the client name kre so that stands for bird that also reflects the the likeness of we we are striving for in client development so as you've seen

already we are still open and we're discussing which language to use but we currently tend to C++ and yeah um let me hand over to Simon he wants to also share some technical details of our approach sure why not um yeah as y already mentioned we've been around for quite a while almost 10 years now focusing especially on connecting blockchain especially ethereum to iot and with iot we really talk about embedded devices with really low resources that's why also we chose C for the imple for for the implementation with 200 kilobyte of exe executable with 200 kilobyte we are able at least to

verify imp um everything that's uh at least important enough and relevant and on an application Level and so this is also one why when when we started a few years ago with incubed also with the same goal um with a client targeting on those low resource devices we focus of course on the existing proof of work at the time but implementing the whole evm there and and all the protocols and libraries needed from scratch just to be small enough to fit on the embeded dev Dev and we did the same now all again for the beac chain as a c and all the stuff there so and we

expect this to be released at least at the first version pretty soon it's already working quite wise but of course now we are looking forward to also contribute to the specification for the beam um chain especially always looking from the angle how can we make sure that all of those things can be verified on low resource and embedded devices so I'm really looking forward to going that way excellent thank you Jo and and and Simon um and yeah like the the promise of blockchains was that we would you know be able to verify everything on on mobile devices and that to be fair

hasn't happened yet uh but hopefully the beam chain is uh what really uh unlocks this because dramatically reduces the friction to to full verification even even on a smartwatch any questions for the C team so we have uh one more uh new consensus layer team and then we'll we'll have the existing teams uh speak as well so um the last uh new Beam Team is a uh a the floor is yours yeah thank you very much everyone good okay good evening from here I don't know my camera

is not opening so I don't know let me see why is not opening now okay I just I'll just go the camera if it's not working so so my name is a let me see if I can share I just have one p it's not something not something very uh complete just like one slide so are we working on AF AF is new we decided to like go with after Justin's talk at defon hadot people looking for me I was like it's time to have a client in Africa like okay why are you guys looking for me to do this like you have enough guys you have developers to do this so my name is I I am the founder at Bridge uh over the

last five years we've trained quite a number of developers who have worked in some of the teams who are on this call either directly or learning from their program and we've had a lot of people talk about building consensus client and all sort of client for a while now so we decided that it's time to do it since there's lot of learnings that have gone into this scope we've trained over 200 developers in the last five years and number of these guys are full protocol guys I have Longs on this call who works with block who's the co-founder block fuse lab block fuse is founded by Alum of we Bridge Longs in the last three years I've worked with a number of protocol protocols building stuff with them is focused more on gets Goan gets

but then we decided we're going to be doing this with c or rust so we we are more like very new and why we doing this is because we believe that there's lot of issue about consensus clients in Africa so we are doing this to do an not just an experiment see how we can also contribute because we believe that apart from the economic part of it education part is very important we've started running NES at we bridge for the last Almost about four six months now uh to see how consensus n though to see how this is run to also like Ser as education purpose for the developers themselves so we're going to be doing this we started we have our guys learning ZK and rust over the last uh

they started in January so we have some other guys who are so we have like like I told te yesterday we have six actual developers who are protocol Focus who are going working on this and we have a cheat load of deel researchers who are also developers who are going to be contributing to whatever we're doing our study group is officially opening on Monday we we have people who have been studying in silos we are pulling everybody together as a group so that we can start like formal Stu our documentation will be live next week so everything will be shared and uh we look forward to doing this Challenge and see where uh good actually get thank you very much thank you IO H yeah super exciting to have uh uh an African client um I'm

uh I'm yeah really really looking forward to to supporting you guys um any any questions for AF if not uh well that concludes the the introductions from the new teams um next up we have the the the existing consensus um layer teams who who who will speak to what are their current thoughts uh and plans uh regarding the the beam chain I think without the support uh of the are you can you guys still hear

me yeah yeah okay perfect sorry uh um yeah without without the support uh of uh of the existing consensus client teams I think it's going to be you know very very difficult for for for the beam proposal to to graduate to to an actual thing uh so I'd like to uh invite invite uh let me check my spreadsheet uh Terren uh from from Prism to to give a few words about what their thoughts are on the the beam chain project yeah thanks for having me this is great so I guess like I can speak perhaps more on my individual perspective just because like I don't know like my team hasn't fully like I don't we don't have Co like cohesive

consensus on like what to do here yet but I'm just one of the many that got to like lucky contribute to consensus layer for the last six years and then I work on Prison I'm one the consensus layer K in death in prison team and I I think the whole bean chain idea makes a lot of sense because it allows us to move fast basically to do this update in batch I I I definitely agree with this approach I think it's the right one to making the consensus layer that's more competitive for the years to come I think one word of cautious for me is that I think a lot of a lot of devils are in the detail there are knowledges and details that on consensus layer today that unfortunately

only handful of people that know I think they made me feel better I see a bunch of franchesco's name on the current design Franchesco is like a for choice asper and a lot of the devil in the details are on the for stuff today so I think like we want to move fast but at the same time we also want to make sure that we Loop the existing people in because of they have the knowledge they have the lesson it doesn't make sense to like reinvent the old will we want we don't want to repeat the same mistake so yeah I'm I'm definitely very supportive I'm excited to follow alone definitely want to provide unconditional support and then for the time is right presting will also jumping as well to contribute to the beam Cham as a whole thank

you thank you so much Terren yeah and 100% agree on on the fork Choice rule uh just historically speaking we kind of YOLO it and then we found a bug we tried to fix it and the patch introduces a new bug and then we do this cycle multiple times of of cat and mouse and I think what we want to do with the beam chain is just get it right first time uh and that means having something which is like provably secure uh and and you know Franchesco has been doing you know excellent work on in that perspective and not just getting you know something that that's provably secure but also getting something that is that is simple um you know striving for for maximum Simplicity um and yeah that is one of my my guiding I guess Aesthetics uh for for

the beam chain is to try and keep things as as simple as uh as as possible while at the same at the same time having all of the robustness of of provable security or or whatever the the equivalent is thank you Terren um yeah if you have any questions feel free to just raise your hand I'll just keep on um moving forward uh next up we have the the Nimbus team uh Dustin would would you like to share a few words yeah yeah so so yeah first thanks for for organizing this this call and and sort of in general kind of maintaining the momentum on on this project and and it's great to see that moving forward and I'm I'm looking

looking forward to uh the call number two as well when we get to hear more about the technical progresses on that so the first thing I just want to say is I want to signal that Nimbus is indeed uh sort of it support uh of the beam chain or not not beam chain whatever the name we arrive on is and so at the moment we including uh Agnes who is here on on this call as well are sort of certainly going to be closely monitoring tracking participating in inspect development as appropriate uh and uh ensuring that we're kind of ready on the code infrastructure side uh so I will say that from the perspective of I'm very

talked about building up their that that part of things obviously we have that as you know prism has theirs and we have ours and so so that that part is a you know we're kind of Fredy there uh I think I mentioned in chat but so we use Nim in the name uh n relevant to the risk uh risk five ckvm proving Etc so this already compiles through 32bit op uh sort of sort of targeted C among other targets and platforms you can B them Etc so we we have no real concerns about being able to Target something proof for for Z kbm this is there there are other

questions outstanding but we'll see and yeah as as uh some specs solidify we will definitely be ramping up implementation efforts and doing so and basically be treating it as part of our consensus layer in general um this is I mean if to the extent that this is where the consensus layer is going have a consensus layer teamw you know weing with everyone else and we will continue to do so as that migrates over to beam yeah amazing uh yeah thank you Dustin um and not only is Nim like really friendly to to compiling to R 5 but as you said like the existing consensus client teams have a a big leg up because you have a lot of the the libraries that have been set up whether it's

s um and um yeah um one of the things that I'm I'm hoping we can do with the existing uh client teams is is basically not overburden them like there's they have there's a lot of pressure on the existing teams to basically ship all of the incremental upgrades that we want to see in the coming you know months and and and couple years uh and so really in 2025 My Hope Is that uh there's a light light touch approach uh where Mo most of the existing devs can you know you know keep an eye on developments but otherwise uh you sit back and and mostly relax I want to com oh oh okay um I say

something go ahead yeah so about about that that timeline or schedule um so one of the things that's in parallel and I mean I don't know how closely people here who are not already sort of part of ethereum development and deploy Loop let's say uh ACD and all that are are tracking this but there's already a lot of pressure to actually increase the tempo for just the releasing of of this of the you know faka glamster Dam all that so putting aside not saying good or bad on that but what it does mean is that what we used to have and what in terms of the existing kind of Cl and El teams there used to be a long period in between like aough approximately a year

between sort of hard Forks where kind of spec work was fairly light um for the most part and and so there was a lot of uh leeway to to to to play with this kind of stuff um what may end up being happening uh or happening over the next couple of years is if the EF gets what it's signaling um then that that leway may decrease for a lot of the existing implementation teams okay that's it got it yeah thank you for for the note uh Arie yeah just a really quick quick general question out of pure curiosity is is anyone targeting anything besides the risk five instruction set like is

any client currently for for the ZK compilation part of um of what they're doing is every single client so far that's on board all using risk five under the hood so the only team that has signaled not going with risk 5 potentially is stockar um so uh they're not included in the list of of of a client teams because I think it was more of an idea than an actual serious project uh but there it was floated at one point uh that that stock where might be interested in building a beam client you know to feature uh basically the the power of of of of using Cairo um I guess one of the things I'd be very interested to see is

how Kakarot evolves uh with with DV M um you know this is a a long-standing you know very complicated project uh to to have um you know the evm uh run run on Cairo but you know if it can be done uh and if the performance you know is really really good uh then that would be a strong motivator for someone to do a similar effort for the beam chain and hopefully uh the beam chain is like significantly simpler than uh than than an evm execution client uh and specifically the only thing that needs to be snar ified of course is the the state transition function which will be custom designed to be extremely snot

friendly thank you Dustin next up uh we have uh Greg from loar yay nice to see you all and welcome all the new folks working on C def it's amazing to see like way more people here um yeah heard a lot of you know much like Terren and uh you know the Nim team we've been around for quite a while kind of just pushing the boundary on what's possible in jsts um and you know we are here to make sure ultimately that Network's stable and as we go into future Dev Nets with you know potentially more um you know

riskier software especially in the like beam future uh that things continue to do that um and we continue to have like stability across you know all the the main net and as well as our Dove nuts so um we're looking pretty deeply at it um it's you know about making load star more performant as an as a client itself um and basically looking at like how can we also kind of kill two brids with one stone and future proofing um I do want to introduce Peter though um from our team he's our head of protocols and kind of leading like future R&D efforts at chains saafe and I think that's really important um I don't have a lot of time to do core Dev anymore um I think the last stint I did was a a laughable

reference implementation in bash back in the day but um yeah I'd love to introduce Peter who can give a little bit of a tidbit um and kind of main point of contact looking forward if you want to like you know really get into the experimental weeds of loadstar R&D hey hey everybody nice to meet you all uh thank you Greg thank you Justin and coordinators for this call uh yeah from the lar perspective I think uh as soon as beam was introduced last year it become part of our road map conversations uh one of the big uh efforts that we do currently is to improve performance because within the jsts land there's only so much you can

do with the nodejs itself uh there is a consistency problems unexpected garbage collection hits and and stuff like this so we are experimenting with some system programming languages like Z we are experimenting with the different R time environments for the uh gsts like bun for example and uh yeah we're trying to be as performant as possible we thinking uh uh pretty extensively about uh how lar will be able to uh handle more like a tighter uh timing constraints uh uh there are some uh tooling uh that we building uh around gsts and the zig itself that hopefully

uh will be uh will help us to to adopt to Future changes uh beside performance itself uh we just uh keeping up with the underlying crypto cryptography uh and specs following uh with the help of of of of of Ginder we uh trying to understand the the difference between the consensus speack the the beIN speack and how we can how we can uh navigate this this Waters and yeah uh we definitely ready to embrace the future we more than happy to adopt some of the of the tooling like uh JS lb2b or something uh uh that that is needed and of course provide any feedback uh for

the implementation uh where it's possible and yeah happy happy to go towards this future thank you amazing uh thank you Greg and Peter uh and yeah really cool to see that there's there synergies with with other teams you know around Zig and and z um actually one thing that I want want to say is that uh historically speaking what we saw with the beacon chain is uh 10 different teams kind of come up uh when when you know aerum 2.0 was announced and that over time kind of Consolidated down down to to 5 uh and I do expect some amount of consolidation uh from the from the 14 teams and you know it might make sense um not saying

this necessarily makes sense here but uh it might make sense for for projects that share a language uh at some point uh to to join forces but at at this point in time I'm you know very much uh you know celebrating the diversity um that that that comes with with having so so many teams okay it looks like we have no question questions oh g go ahead yeah so uh for a client like lar where basically it run it mostly operates on uh uh a JavaScript runtime uh so so when when they will invoke State transition they can basically prove the state transition through

system Library Integrations and I think what that is what lot start team is anyway building its uh uh uh its score uh uh its score specialty uh that you know they they are integrating various system languages into uh into the nodejs runtime and when basically uh so it's basically more so the client is more about more than just straight transition function and I believe uh even uh uh a client uh a typescript client or typescript JavaScript client can basically you know participate very well in uh for example beam ecosystem by basically invoking State transition

proving and verification on a system layer yeah that's a very interesting point that maybe architecturally what we're going to see is some specialization in the consensus layer teams there's going to be some that might write you know only the state transition function to be you super SN friendly and and super easy to to to prove and then there might be some teams that use that as a library and just write you know wrap a logic around it you know the the syncing the the fork Choice rule um you know the the caching and and all the other stuff that that you know to a very large extent is is arguably most of the complexity of uh of writing a

client great uh next up we have Sean Lighthouse hello thank you Justin um yes so I work at Sigma Prime we the lighthouse consensus client I've been working on Lighthouse the last 5 years or so um so broadly the team's very excited about the idea of making more radical consensus layer changes for me personally that was one of the reasons I was attracted to the the the beacon chain project was it was like a more radical set of changes to ethereum um and yeah so our intent is to deliver a a rust client for the beam chain um and eventually roll this into

Lighthouse to provide like continuity for our users um and we're hoping to expand our team to support this um we're hoping to upscale a bit with the ZK Tech um we currently maintain Russ P2P and we've written SSC libraries so there are obviously like synergies there um and our intent is to treat the process for the beam chain as we do the consensus layer process um and by that I mean like stay very involved in the the the spec deep understanding of the spec and lots of feedback um stay very involved in the testing process development deployment um and that's it thank

you thank you Sean um and yeah um I agree with you that like as this this project blossoms uh we're going to have more and more people involved we're going to have the you know the the devups team with have you know Dev Nets and te Nets we're going to have you know academics that will want to write uh you know academic papers analyzing subsets uh of the beam chain just like they did for for the beacon chain uh we're going to have to involve you know uh security Auditors and uh and we're going to have to you know educate the the the broader Community including the the stakers the staking operators um you know uh pretty much pretty much everyone so um you know we're we're we're just getting started

here we're we're incrementally ramping up uh you know we have these these two coordinators uh that that that joined recently and uh you know hopefully by the end of this year uh they'll be fully ramped up and uh and we'll be able to to move really really fast on on on multiple fronts thank you Sean again uh next up uh we have enrio from teu yeah hey guys um enrio from from te here so is historical consensus client like others now and we are running currently 20% of the validators in the

network which is good and we are a team of seven people based on EU and apak Australia New Zealand we have lugas here today which is yeah barely wake you time zone and we are starting a discussion around beam support we are pretty early now it's just an idea floating around but we are pretty excited we want to share the excitement for sure from the team is a small team but we want to at some point start following what's going on there and uh we would like to track essentially the

specs when they are kind of uh ready is so we can then start evaluating what will be our our impact in the current client design and uh we haven't heard anything about Java so far we are a Java client and we are uh maintaining also the jvm lip2p and Java Discovery libraries for for the ecosystem and um yeah in terms of ZK support so we hope that we will have a jvm um Java run time support for risk 5 architecture soon we will plan to

Monitor and experiment uh uh reasonably re uh um recently about that and we will follow what's going on there and yeah that that's it from te perfect thank you um yeah and my my understanding is that for the jvm like RIS 564 bit is kind of more friendly and I think uh at least I I hope that we're going to see more more ZK VMS Provide support for for that um as I'm told there's actually not a heavy lift uh so so hopefully we'll we'll have more diversity at the risk 5 level which will

mean U more support for languages like like Java and and and go yeah and I think it's still relevant what also gender said that in the in the worst situation you could always um yeah externalize the state transition and do some something about that and still maintaining our high level architecture Java Java based jvm based yep exactly yeah great Point okay so we have uh one more existing um consensus layer team um and then after that I will invite the two new coordinators to to to wrap things up

uh and and close off the call so uh next up we have uh Solus uh from grandine hello sorry for background uh noise hopefully you will hear me fine so yeah I'm a sers from Grand team and we building coner client and obviously we are excited about uh the beam chain uh we already working on uh on kind of related thing that uh that we are trying to do a existing Bon chain uh State transition function approving so there is already some good progress on that part essentially our state transition

function is uh is already working on on sp1 Z KVM so yeah it's it's exciting and uh we hope that uh by working with uh the existing Bon node implementation uh essentially doing the similar goals that beam chain is trying to achieve with something like a like rectification uh and so on we think that this should help beam chain to be shipped faster so yeah so this is the the direction that we are thinking to move forward yeah that's all if you have question let me know thank you sius um and yeah I'm I'm

in some of these these telegram groups you know where where Solus is trying to integrate with existing ZK VMS and he he's really kicking the tires and finding all sorts of edge cases and and bugs and uh uh you know this is just a reflection of the fact that the the ZK VMS you know are are still in a process of maturation um but uh you know the the the great news is that directionally speaking you know all of the the Stars should align from a timing perspective that you know in a few years time ckvm should be uh like really hardened production grade pieces of infrastructure that are super simple to to to integrate with uh and all of the knowhow that uh that is being learned today uh by SN ifying the beacon chain

even if the performance is absolutely terrible uh will be will be useful uh for to inform uh the the the beam chain So yeah thank you thank you thank you soers for for all of that work that that that you're doing it's uh quite quite exciting okay so uh to to close off the call uh I'd like to invite uh lisl and will I guess let's start with lisl yeah hi folks uh great to meet you all my name is lisl um I'm uh yeah helping uh or I'm about to join the uh EF to help with the research uh adjacent uh tasks such as coordination tasks and

um yeah helping with the with the beam uh beam Vision so to speak uh was kind of a no-brainer for me because it was the The Beacon chain I think five years ago which which brought me into sort of the more core protocol related um ethereum um um uh working groups so to speak um yeah so very excited to to move forward the content is St and um as Justin mentioned earlier um if you have ideas creative ideas around the uh the naming of our uh project please reach out on telegram I'm Lis La ZX uh also on Twitter and yeah please will go

ahead thank you Lis L um and um yeah one thing to mention if you're watching the recording on YouTube and you'd like to join these calls uh well first of all congratulations for making it this far uh and secondly like these these these calls are are public so if you if you do want to join uh just send me a DM uh I'm not sharing the link publicly just because I I don't want uh people to disrupt a call uh but otherwise it is a very much an open call uh and just you know DM lisl DM will uh and we will add you to the the calend invite as well as the the internal uh tracking spreadsheet that we that we have um well if you'd like to to close

it off the floor is yours uh thanks Justin I'm will I'm going to be joining the EF uh next week as a coordinator currently at the Stax Foundation where I'm the ecosystem programs manager and uh do a lot of coordination like this between core developers between orgs uh RFP style grants governance uh the the validating Network um node operators things of that nature and prior to that I Was An Architect and did a lot of large uh project coordination and the construction industry so uh just really looking forward to joining everyone and uh helping uh keep things streamlined and and moving

forward one piece of context on will is that he he used to build uh Skys skyscrapers and you know to build a skyscraper you need to coordinate hundreds of people across many many different teams uh and so that's that's exactly the kind of of skill set that uh that we need we're building a digital skyscraper uh in some sense and it's uh you know super exciting to have uh to have well on board um and one of the things that I want to the Highlight is that in addition to the beam calls uh which I'm hoping we're going to have at least once a month but you know maybe several times uh per month uh we're going to have you know iners events as well so I'm thinking of organizing beam days uh maybe around ECC and death

connect uh as well as potentially a whole beam Retreat a beam week uh where we can spend several days uh in person and read accelerate things uh it's that's maybe potentially you know towards the end of the year when we have um more visibility uh on a spec uh and you know it will be an inflection point as to you know whether or not we we do want to charge ahead with uh with with with this new uh exciting uh Direction so um this is pretty much the end of beam call number one um you know maybe we'll we'll have a hundred more of these calls uh and then we'll be able to ship uh the the beam chain so you know we are really at the very very beginning

of a of a of a long journey and uh you know I'm just uh so so so excited uh to be working with with so many inspiring people um and yeah can't wait to see um what what uh what the future brings and the the next call as I mentioned at the very beginning uh will be in 2 weeks time on uh February the 28th at uh 2 p.m UTC we'll be sending calendar invites that's it folks thank you so much for joining and uh enjoy the rest of your day thanks by goodbye thanks everyone bye bye thanks bye