Decentralizing Cardano's Core Development

تاريخ التسجيل: Nov 10, 2026 المدة: 1:26:37

تسجيل المساحة

فتح المساحة الأصلية
0:00 1:26:37

النص الكامل

Hi, Matthew. Hello. How's it going, John? Good, good. Good to be on another X space with you.
It's always a pleasure. Yes, yes. I was just thinking. It's been a while since I've done really
any X spaces, but I used to do a ton, both both here for IO and also even just like personally
with friends and things. The coming back and hearing the music is yeah, it's it's a feel good,
it's a feel good kind of situation. Roman. Hey, how's it going? Hi Jen, hi Matt.
Thanks for inviting guys. It's a pleasure to be with you here. Absolutely, absolutely.
And we have Envy. Envy, how's it going? Good to good to see you in the space. All right,
we have we actually have let's see three other speakers I think who will be joining us shortly.
So I'll just give each of them a ping and we'll get started in a minute here. I will.
I'll start by giving you guys just a reiteration of the purpose of today
and what the agenda is going to look like. So we didn't have a ton of promotion time for
for this space, so I expect that will be relatively small and quiet this time.
But it's it's a good a good what would you say? I mean the thing is like you guys
have been talking extensively, obviously both with teams that you work with on a regular basis,
and also people in the cardinal ecosystem. But there hasn't been as much of like a sort
of public facing engagement with everybody from like SPOs to DRs to whoever happens to be interested
in. Involved in thinking about core development, and that's in large part
because these various teams have been housed and these functions have been housed at I O
for a long while. But I mean, as we've been talking about, the teams are now matured,
the the functions are matured, and you know it's time for them to stand on their own
and become autonomous. And so, I mean, this is in a way, it's kind of daunting. Right,
but it's also very exciting for this last piece of the sort of this last mile
of the decentralization journey to finally be actualized. So anyway, I'm excited to talk to you guys
about that today. We're going to have five of These functions, which are now their own teams
and housed in their own companies, still working in close collaboration with IO
and you know through the like mediation of Intersect, etc. But but now you know self-standing,
and so we have here in the room right now Roman and we have Chan, and we're going to start in
a moment with Chan. We're going to take about Ten minutes per team. Just basically going to have
a conversation here, sort of on the record for people about who you are, your background,
the work that you do, what you've sort of the trajectory from the team's place in IO
into its independent work and what your vision is going forward. So I think with that said,
I'll actually get started right now with John. So John, could you tell us a bit about yourself
and also about iCan? Thanks, Matthew. It's great to be here again with you on an on an X space.
So let's talk about myself briefly. I'm I'm a software engineer by background, and I've done
professional jobs for a while, for mainly in telecommunications industry for a very long time.
And then I founded iCan Group in the United Kingdom in 2015. And okay, ICAN Group.
We were established in London. Now we have a satellite office in Istanbul as well.
But we are fully remote, so all our engineers work across the globe. And we are
an engineering company. The founder, I'm a software engineer and I love it.
And I like to say that we are a software engineering company. And we work on
zero fault tolerance systems. That's where we focus on. And in ICAN, we have
site reliability engineers, quality assurance, DevOps engineers,
performance engineers, and an applied. That's who I am, and that's who I can is.
Awesome, awesome! Thanks, thanks, John. Yeah, so I guess my and actually by the way
we've got a few more of our speakers have just jumped in, so I'm excited.
And maybe it is worth mentioning the connection with Cardano as well, right?
How this Cardano comes into this picture. Firstly, I'm not new to Cardano.
I was leading input outputs, SRE, creative ops, performance, and cryptography teams for over
three years. And the engineers that I can today are those same people that have been here since
the early ages of Cardano, and the zero downtime record of Cardano comes from the work
of these teams. The work of these teams, and every node release is benchmarked by these teams,
tested by these teams. So nothing is changing in that sense. And the cryptography
underneath the change is kept correct and secure by the same cryptography team.
So I think that summarizes I can and how Cardano fits into that picture, Matthew. Yeah, thank you.
And by the way, guys, a construction. Matthew unmutes himself, but we can't hear him. Oh,
can you guys not hear me? Can anybody hear me? I I hear you. Oh, okay. Well, possibly.
And I can keep going while we are waiting for Matthew to. Sorry, sorry.
I just knocked uh knocked Chan down from speakers, so hopefully he comes up
and his audio will reset. I also got distracted there for a moment because a construction team
just pulled up outside my window and started started going at it. So let me let me know guys
if there's sound coming through for me which is distracting. Hopefully it won't won't be an issue.
But yeah, so maybe what we'll do here is while we work out Chan's audio issue
and we'll get back around to getting into the work that his teams have been.
Holding down for years now, and the new sort of structure and vision that they have with Icon.
But in the meantime, I'll actually turn over if we can Roman to you to get an intro,
an introduction to yourself and Sarah. I'll start to throw you into this,
but I just want to jump in real quick and help John figure out the audio issue. So
if you could help us hold down the fort with an intro to you and to Sarah, that'll be great. Sure,
Matt. Take your time. I can speak a lot about myself and Ceracle. So, hello, guys.
It's my first time actually at that space, and I'm like very excited to take apart
in our today's discussion. So, thanks again for inviting me. Yeah, I'm Roman.
I'm I'm responsible for the business side of things with our team at Ceracle.
A few words about myself. I'm less engineer and more a guy from a finance side. I master. I have.
I hold a master's degree in corporate finance. And through my entire career,
I was working actually an intersection of like finance, fintech, software engineering,
consulting startups, helping with fundraises and helping with software building. And actually,
Circle is definitely my main passion. I spent last ten years with the team,
and through all of those amazing years, we've built many, many, many fantastic things that
I would love to tell you about. So. We, our company was actually we started this company to focus on
functional development stack. So our main passion was always Haskell, and we were dreaming to build
as many Haskell projects as possible. Since then, we worked with I think
almost all leading Haskell companies in the market. We also have a very very nice Rust department,
so we're working a lot with Rust. And actually, our verticals—they are different—but the main one
is definitely blockchain. So we've been working with eight, I think, yeah,
I think eight most well-known networks on a protocol level, or helping you know
private organizations to build something on top of them, like smart contracts or whatever.
So these include the Ethereum network, Solana, Tezos, now it's Canto and like many, many others.
And yeah, so here comes the question: How did we get here? Actually, Serico was the very first team
of IO, and we are the team behind the very first node and consensus and infrastructure of Cardano,
which exists today. Actually, we've been building and we've been behind it from 2015. And actually,
as I mentioned, we were dreaming to build something in Haskell, and one day we met. Charles,
who had a protocol with a name which was which name was our Boris, and he was looking for a team
to implement it using Haskell, and that's how the first node appeared.
Today we have a team of around 100 people, and we still have folks on board who were original
from the original Cardano team. For example, our chief technical officer
Ivan is was actually leading the node development back in the days. So, starting from January first,
we will be responsible for Cardano consensus. It's like very exciting.
It's something that we started with in the ecosystem, and finally it's back to us. And yeah,
we're very happy about it, and we're absolutely happy to work in a decentralized manner
with other organizations. Please, Matt, tell me where should I go next? Yeah. Yeah. Well, actually,
yeah. Just a follow-up on on that in particular in the in the transition here, obviously, Layeros.
Is a significant, you know, consensus upgrade that is underway at the moment.
What does it look like for, you know, that function and its team to make the transition
with Layas underway? Are you guys, you know, coordinating around that?
Is it effectively exactly the same people in the same work, but you know,
just sort of the management label changes? Like, how are you thinking about that? So yeah,
I would love to talk about it. So technically, yeah, we are. The transition process is
is actually underway, and we are working extremely intensely. Like from every day, from morning
till evening, all of our departments are engaged. Our HR guys are working with with engineers.
Our technical team is already working on on our ideas for like proposals
and how actually are we going to you know maintain all of the delivery starting from. January first,
and yeah, as the great news here is that for guys and engineers who were responsible
for consensus delivery from the IO side, they actually also transit to our team.
So we are going to get seven new colleagues starting from January first. That's absolutely exciting,
and the best thing is that, as I mentioned, yeah, we still have in house guys who were responsible
for the node back in the days. So we are thinking about how to build the best performing team
and mix it from amazing experts coming from IO and from our and with our guys. So yeah, yeah.
That's the thing right now. We are focused on handover until thirty first of December.
The current team is going to work under IRO management, yeah. And since and starting from
January first, we will start to work together on it. Yeah. Perfect. Yeah.
And so you mentioned at the moment Circle has one hundred people in in the company altogether.
So I assume you guys have. Sort of a wider clientele and experience as well.
Could you tell us a little bit about how, like, what Ciracle does in the just like the market
for this type of work more generally? Just to give people a sense of, like, yeah, the wider company
and how this team will fit into it. Sure. So, well, speaking the truth,
we are technically a bit less than one hundred, but yeah, something around it. The team is divided.
Well, let's divide it at first into like sub teams. Which is the first one is technical,
so the team of engineers. Other one is management. So we have our own in house.
Chief Marketing Officer, who is responsible and his team. Yeah, for example,
I believe many of you heard about this, but we run one
of the most popular functional development blog on our website. So we have many, many readers.
We run amazing interviews with different guys who work with Haskell and like and other technologies
and big corporates like Facebook, Vodafone, Meta, like Mercury Bank or other names you should know.
So please, yeah, everyone, reach me out if you want to be highlighted in our blog. We would love to.
We would love to make an interview with you. So going back to our technical department, yeah.
So this this one is divided into like sub teams as well. We have like the blockchain team,
which is responsible for working with different protocols. So we have
different protocol-oriented teams. We have Solana team here. We help different companies
to build something mostly. I would say smart contracts. The last thing we did was
we are finishing it right now is new DEXs for Solana. We have Ethereum experts who work also mostly
with With EVM smart contracts, I would say not only Ethereum but other EVM-based networks. Canton,
yeah, we are very interested in building the brand inside of the Canton ecosystem
because Canton uses their own specific language for the smart contracts,
which is basically based on Haskell. So it's very near to our expertise zone
where we are working nicely with Canton Foundation to build something interesting together. Tezos,
we've spent many many years to help them. Definity and Internet Computer,
which also been built on Haskell before, but now they use mainly Rust. So again,
like our sweet spot here. We also have a team that works not only with blockchains, like,
but with other I would say general type of startups, mostly U.S. Companies, mostly VC backed,
starting somewhere from Series B and higher. We've been working with very very Big public company
from the U.S. Focused on, I would say, public security. We've been working with
a very nice biotech company building devices for drug discovery labs, and we were responsible there
for building software, middleware, and even like I would say some parts for their hardware. Yeah.
Yeah, for for people like the relevance. I mean, you have a long list here,
and I'm sure you're you could continue. Just yeah, the reason the reason why I ask is
because I mean often, you know, one of the things that people have sort of wished in the past
at various times is that. IOS like core engineering had more connections to like the wider market
and sort of this fear that like maybe we're siloed into just like Cardano's world of like
you know we're working on our cathedral alone and we're never gonna
like you know we're not connecting to other areas of the market other domains of knowledge and so
for actually the consensus team now to be housed in a company that has this wide of breadth not only
in like established established ecosystems but also like you know new startups et cetera et cetera
that's it's pretty cool. That's correct, and to be—I—I do not really want to, you know,
say publicly too much right now. But to be honest, we have many ideas on
how can we leverage our experience and our, let's say, well—well-built connections
with other networks. So we have many ideas, and we really do hope to like leverage our position here
in between of different foundations in future to bring best practices,
to connect with other networks, to find the ways to you know maybe to bring new partnership,
collaboration, liquidities, whatever. But still, it's just purely you know to announce publicly.
But we definitely will take care of that together with other Io teams responsible
for the other directions. So yeah, we will try our best to bring. The most interesting things
inside the community. Nice. Well, my last question for you, Roman, is going to be about
your your future vision. I mean, you've talked about it a little bit there already.
So you know how potentially your connections with other ecosystems and other industries
may help to inform what you you know sort of what you sort of has an influx into. Hopefully,
the inspiration that goes into the Cardano consensus. But just more generally, what? What I mean,
obviously, you guys are working on Layeros now. But looking forward into the next sort of
six months to a year, what is exciting that you guys have on your plane? Again, Matt.
Going back to my previous answer, I would not—I would prefer not to talk too much about very,
like more. I would say longer-term plans here about our ideas because we have many. However,
as I mentioned at the beginning of my speech here, we are really overhauled right now
on the smooth transition and what we are really focused on. Well, for instance,
is just let's say continuity. So. We want to hand over the product. We want to hand over
repositories, like the processes and delivery manner, not to distract and not to you know to make
it as smooth as possible. We want to deliver best monthly public reports. We want to still maintain
reliable node performance, and that's probably the most important our short-term goal. Yeah,
so we want to make mainnet and we want to keep mainnet safe and stable. On the other hand,
we want to be as transparent as we can. So we want to. Keep consensus running without any incidents.
We want to be transparent. We want the D reps to see what exactly are they paying for.
We want to be transparent. So those are the highest priority tasks for us for today. Meanwhile,
we will definitely think on next themes and possible future improvements and like blah blah blah.
So would love to speak a bit, but let's keep it for our next tech space. Awesome. Sounds good. Yeah.
All right. Well, I mean, that's honestly that is a great, a great vision to say like having
the foundation of being trustworthy and reliable and carrying everything over effectively
from the previous paradigm. So yes, I commend you for that, Roman. Yeah,
and I think now we'll thank you, Roman, and for jumping in there. I think we had you
significantly later in the agenda, maybe even last, but you were you were you were ready to hand
and ready to go. So thank you so much for helping with that when John and I had some audio issues.
Now, John, we do have you back on the space. Are you able to unmute and speak now?
And can you hear me? Yeah, we can sure try. And I don't know what happened. And apologies. No,
no worries. Yeah, and I can hear you now. So hopefully we're good. Yeah.
So let's let's do just a quick review of the initial question. Just introducing yourself. I can,
but also the functions, the underlying functions that you're taking over for my own now. So yeah,
just give us that intro again. We'll we'll get back into it. Okay, so because I wasted a few minutes
of everyone's time, I'll keep it very concise. So ICAN Group we were established in London in 2015,
and now we have a satellite office in Istanbul. But all our engineers and consultants work across
the globe. And me myself, I'm a software engineer by background, and I love software engineering,
and that's why I'd like to call ICAN as an engineering company. And we work on
zero fault tolerance systems. And during that transition, the site reliability engineering team,
the quality assurance team, the performance benchmarking and performance tracing team,
and the applied cryptography teams—they moved over to ICN. And I'm not new to Cardano;
some of you might already know me. I've been leading input outputs, SRE, QA,
performance engineering, cryptography teams already for over three years.
And the engineers at ICN today are those same people. That have been here since
the early ages of Cardano, with me being in the leadership team for more than three years
for this very same domain. I think that gives a quick recap of what I was trying to say in
the introduction. Yeah. And I think now I can dive deeper into. Answering the questions
you already asked to Roman, because I was listening the nice conversation between you two. Well,
yeah, actually, I do. I I um I have one follow up question just for your um
for your initial response there, Sean, which is um so engineering enablement,
performance benchmarking, testing, cryptography, etc. Like, what is the through line for somebody
like myself, say, who you know doesn't have as strong a grasp of like the end to end
of core development? What sort of unites these functions, and how do you think about that as like
one whole picture that ICAN is housing now? Yeah, very good. I think let's take a step back
and also emphasize that this change happened in August. So since August,
ICAN has taken on most of the car donor maintenance work that I used to do.
So these teams are responsible for quality assurance, performance benchmarking,
and all the teams that I mentioned. And in plain terms, what does that mean? That means testing,
shipping high-quality Ne releases, and making sure all the bugs are found
because before they make it into the release, before they go to the SPOs,
measuring the performance of the changes, the performance benchmarking of every release,
so the network never slows down. Benchmarking the cost of running a node,
so that SPOs can rely on Ne releases without worrying how much it will cost to run the Ne node.
Running the CI infrastructure, compilers, and test nets so all the builders in the Cardano ecosystem
can run their applications on. Maintaining the cryptographic libraries so they are always up to date
and with the topmost security possible. And I think very critically being on call
when something goes wrong. So when there is a high incident, high or critical incident,
we have the responsibility to be on call with certain assets that that I can share.
So these are the things that these teams do. Awesome. Nice, yeah, and I suppose probably
the next place to go. Although you might have something that you want to slip in here based on
your what you heard so far from Roman and how he inspired you. But I think I think it would be
helpful to just look at like the the current state of maintenance, what it's what
it's actually like, what you guys do at the moment. I think when we had a space about maintenance
during the treasury proposal cycle. You know, it's sort of a little bit harder to you know get
people to have an intuition for what it means to actually execute maintenance work
on a regular basis. So yeah, I mean, what is it that you guys currently have underway?
What is the workload like, and what is it going to look like as you guys continue to make
this transition leading into the new year? I think the topmost priority for us was continuity
in August when the transition was happened. Now I think Cerel is in that timeline
where their top priority is continuity, but I think we've proven already
since August that we've taken over smoothly and we made sure nothing falls through the cracks
during the move because the proof is I think very few people even noticed the change, right?
That's a good thing when you're actually managing a change. So I think we are over that part now.
We established and have proven that we've successfully transitioned teams. So where are we now?
The teams are highly focused on layoffs. It's a big change. We can't tolerate even a small mistake.
But at the same time, we can't slow down the train. It it has to go out. This needs to go out.
So to achieve this, the for example, the performance benchmarking team have been working at
the weekend. So we have the latest. Changes benchmarked in terms of performance,
so we know that the changes that the team has built in the last one week is not going to cause
any performance issues. The quality assurance team constantly tests every change that goes into
the note, and when these are ready, the DevOps and SRE team they package that and release the note.
And when there is a problem, the very same teams stay on call and listen to SPOs
and users on a 24/7 basis. And answer to all of the incidents in real time.
And another thing that that's, for example, keeping the team busy is the response
to security incidents. And especially since LLMs became very easy to access for everyone,
we have a big flood of reports coming. But most of them are not valid.
Most of them are actually related to things that were already fixed. But you can't ignore
because when there is a report, you have to go through all of them, triage all of them. Even
if you know most of them are not valid, so that's another thing that we take care
of the security incidents and the reports that we receive. I think that summarizes the activities
that's keeping the team busy now. But I think that's just business as usual for these teams.
It's layoffs now; it will be something else next time when we have Paris.
They are also going to benchmark and do the coalition's for every change happening in Paris.
And every small change as well. Even when there is a single line of change happening,
these teams make sure there is no quality issue, there is no performance issue issue in any
of these changes. And all the developers have the right CI tools and compilers to create
a note release compiled. But that's business as usual. I want to talk about what's next as well.
Awesome. Yeah. Yeah. Is that all right? Yes. Please. Yeah. That was my next question, actually. No.
Very good. So we talked about continuation. That was, I think, for us phase one,
and I think we've proven success. And for me, the success criteria is no one even noticed
that there has been this change. Things are still working very smoothly. But in my scope,
I always look at improvements. So what can we do better? Doing the same thing year on year is not
a good achievement for for me. Soon, in January, we'll be talking about
the next maintenance support proposal and how it should look like. It will be a direct continuation
of I/O's last one with the same scope, same team, same people, but with a big plus,
with an emphasis on committed service level objectives for each activity we execute.
So our next step, what the team is working on, is to create service level objectives for all
of the activities that I mentioned when I talked about what the teams are doing.
All of these activities will be mapped to service level objectives that we will make
publicly available, and we will commit to them. And I want to explain why I think that's important.
When you look at enterprise contracts, which I've spent a lot of time in at ICAN,
I've worked with clients like Unilever, big companies like Anglo American, large enterprises.
They always include service level objectives and SLAs. So, if any builder on Cardano wants to create
an enterprise-level application and work with these enterprise companies,
they will have to commit to SLAs. How can they commit to SLAs if there is not an entity
who takes accountability for SLAs? And that's what I want Icon to do. We want anyone building on
Cardano to be able to commit to such large-scale enterprise contracts because we will be taking on
the accountability on the service level objectives. So that's the next big thing for us.
But that's only for us. If we also talk about Cardano a little bit, like what the success
looked like for Cardano, I think on a macro level, for me, success for Cardano is to become
the blockchain where people build large-scale projects and run critical infrastructures.
I'm not saying one of the blockchains, but it becomes the blockchain when there is
a critical infrastructure and they are looking for a blockchain to run it on.
The first thing they should Think about should be Cardano. That's that's where I see
Cardano to become awesome. And Chan, just a quick follow up on what you mentioned earlier
with the SLAs: is this that you know you can assure say potential adopters of Cardano for whatever
their you know enterprise etc solutions are that you know Cardano has
these certain certain properties? Is that is that what I'm understanding? Yeah, exactly.
Because if you are building an enterprise application. The customer will put put in SLAs
like you will have to respond to incidents within I don't know one hour.
It depends on the company project, but let's say one hour. They don't care about the infrastructure
you are using. They say you have to respond to it and resolve it in a certain time.
And if this is related to Cardano blockchain, in order to commit to such an SLA,
they need to know that there is an entity out there who is looking after these conditions
and who has as committed SLAs that they can rely on. Yeah, that's awesome.
That's a you know it's one thing to I think oftentimes we think of like evangelizing simply based on
like the inherent properties of the technology or something, but you know from
a business perspective, actually having you know the counterparty who is willing to guarantee
an SLA, you know, right? You you can understand the technology and the reason why the SLA
makes sense, but it's you know better for business not to try to require them to be like
true believers in blockchain in order to have the confidence to put their solution on it. Yeah,
exactly, exactly. For example, in our let's say closed ecosystem, we know.
How the SLA team is responding, how quick they are, right? But you can't when you're talking to
another enterprise customer. You can't say, yeah, this team is so great,
so you don't need to really worry about it. What you need to do is to refer them
to a certain committed SLA documentation publicly auditable, and say, look, these are the SLAs,
and this is the history of these SLAs that they have been successful, right?
And then when you can do it, then the enterprise customer will have the trust. Yeah, awesome. Well,
thank you, John. I really appreciate it. And yeah, I just want to comment on this. Both now
Roman with Serkel, and I mean in particular, what stuck out was the um,
just the diversity of different areas that they're involved in, and sort of the breadth
of that company. And with Chan and I can, you know, this like business sort of practicality.
I think in both cases it's good to see these functions having their own, you know,
like fully their own strategic and managerial home in. These respective companies,
because it's actually tightening the feedback loops between the function
and their actual purpose for the Kubernetes ecosystem. At least this is, you know,
this is what I see. If if you know others have different perspectives and see some kind
of significant disadvantage, there I'd be curious to hear about it.
But I'm pretty much like purely excited for for this element of things. So yes, thank you again,
Chan, and we will. Go now to our next speaker in the agenda, which is I think I don't think
we have Tarragon with us. So I think we're going to go to Robertino with Always True, Robertino.
It's been a while since we've we've spoken, so it's great to great to have you on the space today.
Hi, Matthew. Hi, everyone. Yes, it's been a while. Yeah, awesome. Well, can you? I mean,
like I'm pretty sure everybody here knows you, Robertino, but still, give us a quick intro
to yourself, but especially in the context of Always True. And the functions that
you are carrying on from IO into this new home, right? Thank you, Matthew. So yeah. So hi everyone.
I'm Roberto Martinez. I worked at Input Output for many years. I worked defining
and executing strategy strategies for Cardano developer onboarding education,
leading deliverable across like multiple projects. Include like courses, educational platform,
hackathon events. We created blockchain laboratories in several universities. Alongside that,
that's my I start. I think I started at the middle point. So that's my that that's my work day job.
But way before that, like I worked as software engineer, of course, as as most here.
And I have my own product company. We build products, and everything was going well until one day
I found this Cardano blockchain in 2021. It was like wow, this looks crazy.
These guys are doing like like crazy research, like going super deep way before building like
like the actual MVP. I was impressed. I also was a Haskell developer from before Cardano,
so I was like, okay, this is like This ticks two of my boxes. It's Haskell
and and it's like well thought out architectures, well thought out research. So I say okay,
I'm going to like get into this and and yes, that's how I I I got into Cardano to begin with.
And as a product company, we say okay, what can we build here? Um, so like we we try out
the the technology, and very very soon after that, we realized it was super hard work
to create anything useful in 2021. It was almost impossible. We suffered for months,
and to the point that I started in Discord. I started teaching other engineers.
I think this was like Bluetooth Pioneer one or two. I started teaching other engineers, like, hey,
no, you should do, you should this, you should that. The I/O G education team picked up on that,
and I was like, hey, this guy is teaching for free to everyone. Let's onboard him. So yeah,
that's that's sort of like how I got recruited into AIO. I was very I was very excited
because like I even though I wasn't prior to 2021, I wasn't part of the blockchain
in general community. Um, I knew that AIO had crazy good engineers that I already knew by name from
like their their individual CVs and track records. So I was super excited to join like
such a high caliber engineering company, and that's how I started. And that's how i I started doing.
Little by little, more and more, I would I take more and more responsibility,
and I ended up leading delivery at the team. And then last year, around November December,
we started talking about the Developer Experience Initiative, and I had a lot of opinions about it.
So many opinions, in fact, that they that they were like, "Okay, Robertino, you know what?
You have so many opinions. You you do it." So I took over. I spearheaded the proposal,
and of course. What do you do when you want to like try to make it as as better as you can?
You ask for opinions. So I started talking with as many developers, both app developers,
tooling developers, also infrastructure developers about what do they what do they want?
Because of course I have my opinions, but I could be wrong. So luckily I had a lot of over the years
of working, I made a lot of friends in the community, and they and they also had of course
software developers. They have strong opinions. So I managed between everyone.
I managed to pull out, I think, a pretty good proposal last year, and we started executing. Luckily,
the the D reps agreed that it was good enough for to to to execute. So we we got the opportunity
to execute, and and that's when we started working on that. So now, uh,
as we started this developer experience initiative, started as an IO. Project it was led by me.
Now we moved it to Always True, and it's still led by me. So both the lead and the team, everyone,
DevX and DevRel teams are part of Always True. So there's complete continuity there.
There's no nothing changed. Nothing really changed in the on the delivery side.
It's more like a level and name side. So yeah, that's our main focus number
or focus number one is to deliver all our milestones from the IOGs
former IOGs Developer Experience Initiative. Nice, nice. So Robertino is now supreme leader
of Developer Experience for Cardano. This is what I'm hearing. No, no, no, no. I'm, I'm actually.
It's more like I'm, I'm the slave. Like because everyone is angry, everyone wants to change,
everyone wants its own way, and I'm, I'm the one that everyone goes to complain, complain to.
And I'm happy to be that guy because that gives me a lot of perspective. Yeah. So I'm,
I'm sort of like in service of the people. Exactly. Yes. This is this is what
the the the benevolent. Leader, I must say, I'm in service. No, it's absolutely true.
But the reason why I'm teasing you, Robertino, is because I think just yeah, I mean,
the story of you getting more and more authority from you know just like volunteering
and teaching people during the Plutus Pioneers course is like very like so so natural,
and I think has been whatever like you've been affirmed at every step along the way,
and I've always seen how much the engineers and the ecosystem respect. Respect to you,
so it's just like basically. I think it's really good to see you have that power, I guess,
as it were, now to pursue this. And you know, obviously, the next question is like,
what is there to be done still? And you know, like, we're going to be able to overcome all
of the various challenges associated with it. Maybe you could start, if you will,
by telling us about the progress that you've made so far and like what you've been
able to accomplish. Then you know what's still on the table, and we can go from there. Yeah.
So besides, so the the whole team is not just me. So there's more to it.
The the rest of the team is all was also worked previously. Forgot to mention on audits
like we we audited good honey, we audited austeria and and other products. And from that, from
both my experience. And actually, editing code from from other teams. We also learn a lot
about this, like how the structure of a contract should be, and that's why one one
of the main deliverables that we're working on is in the Cardano contract library.
We want to have something closer to to what OpenZeppelin has in EVM. It's a sort of
like a ready-to-go library, so that's one of our main deliverables. We're still working on it,
but it's the first five contracts which are like the whole like we. We our milestone was
five contracts. We ended up doing six, so these six contracts are ready.
Like they are now being we're doing the the final pass on the code quality and spec quality checks,
and and during the next few weeks we're going to deploy the website, and it's going to be
ready to use by the community. So. They are not audited as of now, but the whole point is
that the high assurance team already started formally proving these contracts.
So they are now formally—they are now setting up to to prove basic shared properties
of all the contracts, and then they're going to start proving one by one. So at the end of the day,
we're going to have this. This library of contracts that are composable, that have they're scalable,
etc. We we use as much as possible from other communities. So like we we got a lot of inspiration
from design patterns from Anastasia and hopefully we'll be able to like give back from that
for all the work they did. So that's one thing. Like we hope to have this contract library done by.
Ready, like sort of like a beta test. We don't we don't recommend you to deploy on the mainnet
with these contracts as of now. Also, especially since the hard fork is coming.
But we do really want people to start trying out, and hopefully it's going to be ergonomic
and easy to use. Then we have Cardano NIT, which is like the CLI that just sets up everything
for you. That that was a huge complaint that everyone, like all my Students
and hackathon participants, university, when we take courses, university, etc.
Like setting up the whole thing, it's it seems easy for us because we've been doing it forever.
But for a newcomer that has no idea which of the sixteen SDKs off-chain SDKs you have to use
and which one works with what and why, etc., is complicated and not everything is easily. Reachable,
so you may start working on something and you realize two months later, oh,
there was this other tool, right? So that's sort of like the problem of that Cardano in itself.
Like it's a CLI that you just run single command. You choose whatever tool you want to use,
any off chain, any on chain, any DevNet, and it will just generate a fully wired project for you.
That one is is ready, so it's been used already by plenty of engineers. We got feedback,
and actually likely tomorrow. We'll cut a new release with currently 20 tools.
This gives us like a really good, not only like it helps like now as a tool because like it does
the work for you. You you can just start working on your actual product,
but it also gives us a huge. Advantage for us, for developers to see where the interfaces
between tools are lacking, and there's a lot of like edge cases and lack of.
Some tools don't follow the specifications fully and stuff like that. So we have to do a lot
of boilerplate to sort of like cover those issues, so the end user doesn't see them.
And that gives us a bunch of tasks to say, okay, we see that this is wrong.
Maybe we should upstream a fix for this. Maybe we should create a CIP for this.
Maybe we should like we we we have sort of like the platform to in try to upstream fixes
to all the underlying tool that we use. So Cardano init is ready to use if anyone is interested.
It's really easy to and actually like. It's also made for clankers. So if you if you want to just
if you want to release your agent, it should be able to just use it and create everything,
add remove tools, and it will just work. And yeah, then we have like a bounty program. I mean,
we overhauled the developer portal to improve for onboarding. That was also
like a huge a huge bottleneck that was identified by virtually everyone that was new to the
To the ecosystem, that's also like it's being reviewed by the CF and should be merged in this week.
So looking forward for that. And finally, like the the bounty program,
we have a hackathon end of the year, which is mostly to measure the effectiveness of our tools.
So that's mostly for non Cardano people. So you're not invited if you know how to use Cardano.
You're not invited. And finally, the the bounty program. Which is still like we are creating
the whole framework. We're trying to make it as thorough as thorough as possible.
But the whole point of the bounty program is there's a lot of paper cuts,
and it's not about a specific tool. It's not about a specific framework, specific tool,
a specific website. They spread around the whole ecosystem. So the whole idea of the bounty program
is we identify these paper cuts and we offer bounties to the owners of the of the repositories
to fix them. So ideally, after we spend all of our available money on that,
the overall ecosystem will have the better developer experience, both for humans
and agent developers. So that's sort of like everything we're working on now as part
of the initiative. I should say that there's one thing that is extra outside of the initiative,
and it's due to the times we're living. The extra hard work is coming, and the whole ecosystem.
If you if we don't do not if we don't do anything about it. Most tools in the ecosystem break
because it's such a huge change. It's not an issue because we have time and we have a new release,
11.2, that has most of the things that will actually break the tooling. Layout is not there yet,
but layout is not a huge problem for in that aspect. So what we are doing right now is
we are devoting a lot of effort to make sure or to at least do our best to help
downstream community tools that all of our DApps rely on. To fix and update their tooling
before the hard fork comes, so that's that's a little bit extra outside of the yeah,
but it's part of one of the central yeah work streams right now and always true. Awesome, yeah.
Okay, so you guys have a ton going on. Um, this is this is good, and yeah,
it's hard to it's hard to have to make software engineers happy. Yeah, um, yeah,
but it's very it's a very good thing to do though. Um, and yeah, that gives I think gives me
a strong sense. Of what you guys are up to at the moment. So thank you, thank you Robertino.
I you know I have some more questions on my mind, but unfortunately we have to keep moving along
because we're a little a little over time here. So thanks Robertino.
It's I think also well anyway you you guys have an X account here too. So
if you guys haven't seen that yet, Robertino, I don't know if that's in your profile or something,
but you should go follow that as well as Sarah Cal and I can et cetera et cetera.
But now we're going to turn to Leonard with Block PQR. So, Leonard, great to have you on the space
today. Thanks for being patient with the initial sort of switch around in our in our agenda.
I think you got knocked back a couple of places. So appreciate your. Your patiently for us there,
but yeah. I mean, first of all, yeah, go ahead. First of all, can you hear me?
Can you hear me clearly? We can. Yes, we can indeed. Okay. Cool. Cool. Okay.
So I launch straight in. I know time is time is precious. So yeah, I've been involved in.
I guess historically, I'm a C++ engineer. Pricing models worked at IBM
and many investment banks building pricing models at Deutsche Bank, Morgan Stanley. Diwa and HSBC,
for example, and yeah, I rolled out so many platforms which are still there
fifteen twenty years later, which is always cool. Recently, I guess I probably since 2021.
Previous that actually worked in market making, which actually quite interesting
because market making is kind of where we actually the height of our crypto world
and blockchain world is building dexes, centralized exchanges, etc., smart contracts,
and taking what we we did maybe. In 2015, across you know some 12 years later into blockchain,
quite interesting. So 2021 was when I got involved in Cardano. I previously involved involved in
Ethereum and also on on Bitcoin. So yeah, so I joined and and probably a project many people
have not heard of called Get Cardano Done, and we basically worked out the relationship
with the the original contracts what was promised to the community and made sure that we lived up
to those contracts. And probably went from there to wanting to get back into technology pure,
and joined the the team who were developing performance changes in 2022.
Had worked with the team back in 2022, becoming the head of technology for Voltaire.
And then the head of delivery for the Cardano core team, working with Kevin, Sam,
and others—probably folks who a lot of people know very well—and yeah,
the first implementations around smart contracts were just out. So some some interesting projects.
And yeah, working working in in 2022, a big big launching event for what would be the age
of Voltaire. So started working on Voltaire. What would look like the Cip 1694.
Traveled around with some of those workshops and to to various locations.
Quite good getting to meet community members and getting the first taste of
how how in you know embedded Cardano was and the passion that people had for Cardano.
So really happy and and fortunate to have worked through 23, four, five rolling out many projects,
but culminating in the Cardano Constitution in Argentina, which was super cool. And yeah,
it's great to be kind of still involved in Cardano developing. Actually,
I still develop code in Rust. And more at the start of this year, I was asked to wheel out
having done a number of forks, hard forks. I was asked to join Midnight, so I went over to Midnight.
Within 63 days, I think we had brought Midnight to mainnet, and since then, only last weekend,
we actually also performed a protocol upgrade of version two. So that was quite a big moment,
and very proud of the work we did on that project. In terms of Block PQR, well,
Block PQR officially opened our doors on the 16th of September, and as in any good project,
the reality of working on a project like this and the importance of it, we had our first issue,
and all a number of the team and I sat from 7 p.m. Till 4 a.m. In the morning, basically.
Looking at an issue, working with a lot of folks from the performance and tracing.
So this is a sign of things to come. Working with with ICAN, you know, bringing people into room,
understanding the issue, and yeah, rolling out a VIX two suite very quickly at 4:00 AM
in the morning, and it was a successful fix. So very proud to have day one issue landed on
the table. We started up a war room, and there we were. Now just a little bit of headline block PQR.
We have the ledger team, of course. Ledger team is is you know beating heart of of of the proof
of stake. Blockchain, and we also have proud to have the API CLI team.
So working very close with Jordan and obviously Ledger team is Alexian folks.
And we also our stewardship for the formal specification. So the formal specification
in the same way as we did for 1694, worked very close on that, working with
the formal specification, define it, iterated, bring the model, work on the conformance testing,
and ultimately property based testing. So. Quite a busy raft of things, and last but not least,
we have high assurance. So high assurance again is looking at tools in the future, like Blaster,
where we will actually use those to check contracts, not just in Plutus but also across Aiken,
and hopefully in the future languages like Compact on Midnight, for example.
So we're very busy at the moment. All the team are busy on, largely busy on,
busy wrapping up Dijkstra. So as folks have mentioned before, 11.2 is out there.
Nested transactions, lots of exciting Babel fees, nested transactions. What we can do?
How we can get all those and get ultimately? How can we get more value and? To and get
more power to the users in terms of what they can do on the Cardano blockchain. So I'm very,
very proud to be here. We are very busy at the moment, of course, on Layeros.
Our team are deployed working on Layeros closely with Consensus team, obviously Circle. But yeah,
it's great to actually have to reach into many of the teams who worked so close to me for two,
three years when I was head of technology. But now we're in the situation where we are delivering in
a new, in a new era, many new features which are going to come up in the future. Matt,
does that give a good introduction? That does, and in fact, I mean you actually covered like most
of the bases of the questions that I had in a very smooth and comprehensive way.
So we're almost like, yeah, I think we're almost good. But I just want to ask a follow up question,
which is, um, actually have a a couple of them. But the first one is just for the the teams that
you worked with at. I/O, like the number of people that you have there. Like what? I obviously,
I think really my curiosity is around having just started out block PQR and you know, you know,
being under the pressure of you know delivery immediately, obviously. And like you said,
you guys had an immediate success with an issue that came up that you were able to resolve.
Just what what has that been? Like you know, what is Block PQR like at the moment? Yeah.
How are you guys? Yeah, one of yeah one of the things we did from day one was we
we literally tool up for want of a better word with all the communications tools that
people would expect, and we we also there's a transition of folks across which we we abided by
straight away. People, you know, as soon as it was announced, you know. In August,
I suppose we we basically reached out to people, made them aware what we were going to be doing,
and we had an amazing warmth of people wanting to kind of understand where they were involved in
the journey. What we would even surprise people looking at 27, 28 in terms of the actual proposal,
what we'd be doing, and and also I think coming back to earlier conversation that you asked is
where do we want to go? We we have our own view in terms of the the agentic AI space.
We've already set up a team looking at protocols that are already existing in our ecosystem, using
the Cardano L one, looking at our L two variants, and even looking across at Midnite in terms of.
Confidential contracts, and you know, trying to ultimately push Cardano to
where boldly go where maybe it hasn't gone before. So an agentic economy protocol is something
we're looking at internally. What's the application infrastructure for that around discovery,
negotiation, you know, escrow, reputation, agent agent execution? And we have a view
that you know we have a lot of technology, and we have we're going to find a lot of use for it.
But we're also going to be pushing the bounds of Not just you know extending the protocol,
which is which our team has our teams I should say amongst other teams on the call.
We have a huge we have a very big footprint, but we intend to you know to work closely with with
with the other entities find an excellent collaboration which we've always had which goes back
for my for myself personally to 22 three onwards. So you know all the teams we we all we all know
each other each other's names. We just have different folks that are going to be heading up
those entities, but I think it's a great opportunity for us to push through the glass ceiling of Of
of what we're really good at, we're really good at research. We're really good
at formal specification, and I want us to be really good at pushing the economy of Cardano forward.
And and that's really that's the exciting part for me is we we know we write great code in Haskell.
Okay, we write a lot of checks, but we want to be able to stress that.
And it's it's it's refreshing today to come from a call where the team are involved in you know
talking about x you know orders of magnitude in terms of throughput on Cardano,
and and I firmly believe we will achieve things, and that sets the runway for.
Larger planes to land, so we're going to be really pushing that boundary to say utility, utility,
and utility. I'm not going to go down to Steve Bamber, but we will be saying utility, utility,
utility, value, value, value, customer, customer, customer. So I, I really feel
that we're going to engage with what people want to do, what's important to them, and we're gonna,
gonna bring we, we've been bringing the bacon home for quite a while, but now we get to show people
what we're all about. Nice, yeah. Good and yeah, I think in a more direct way as well.
Like just to follow your analogy, bringing home the bacon now also in a more direct way
you you can kill what you or sorry you can eat what you kill to because there's like a direct
yeah a direct feedback loop right between what you your success and the you know the the reward that
this team and these teams that you're leading now get to yeah and it's Another point here,
just to level this up, we know, for example, that you know we've looked at themes
and we've been asked to think about themes. And we we think, of course, of DeFi.
We think about onboarding without data. We think about stablecoins. We think about canonical ledger.
We think about nodes in any language. They're out there. But we also think about, you know,
building the USPs for blockchain. And you know, it's going to be an exciting engagement with
with all the entities, with all the D reps, with with folks who are who are now seeing there's
a there's a new opportunity. And the new opportunity is to engage with us, what you know,
talk to talk, walk to walk, get out there and start to you know make those applications,
build those applications, and to scale on Cardano. So it's a it's a big time ahead.
Have I lost you out? Oh, sorry about that. I know I was I was unmute. Um,
I was yeah not an audio issue this time. Just just me not hitting the the unmute button. Um, yeah.
So yeah, I was just I was just saying um that that's that's great. I think we're pretty close
to wrapping up the space for today. Uh, however, um, I wasn't actually expecting Phil to be
able to join us, but Phil is Phil is here and obviously the guy behind Midgard. Um.
And which is the the new home for the Plutus function at IO. So, Phil,
would you like to jump in here and talk about your experience taking over the Plutus function
and all this? Are you just here to you know to give us some companionship and moral support today?
I'm happy to talk about. Can you guys hear me? First off, we can. Yes,
the the audio is not being so unkind to us that we we can't hear you. So yes,
I I think that would be good. So obviously, I mean, you guys have been sort of working
and collaborating, and I mean, you've had think been vocal about opinions about the design and.
These sorts of things around Plutus, but now you're actually taking in that function from IO
into Midgard. So can you tell us, yeah, just the history of your relationship with the function,
what sort of team members are moving over, and how things are going forward? Yeah,
so I've been working, I'd say, on Plutus for the past couple years. Midgard Labs as a whole,
Anastasia Labs have been Core contributors. We've written a number of SIPS,
which have you know defined some of the recent roadmap items. Our expertise sort of comes in
the application domain, right? So there are two aspects of Plutus, there's Plutus from a perspective
of language developers, right? Which is the core team, and then there's Plutus from a perspective
of end users. So the people who are writing the language, and then the people who are using
the language to go write smart contracts. And you know, historically there was some disconnect
there, which led to the roadmap being unclear and the value of the items not being meeting
the expectations of end users. And so I've sort of spent the the past two years trying to
really address that and make sure that the things that get introduced to Plutus are the things that
the people developing applications on Cardano really want, and and that will benefit them.
And a lot of this is is just outreach, knowing all these teams. I mean we we have either audited
or directly worked on you know the top twenty apps by TVL on Cardano at some point, and we we have
direct communication channels with all these teams, and so. On top of just having our own feedback
for Plutus, we're collected. We've been collecting feedback from these teams and asking, you know,
what features they want and what are the pain points currently of smart contract
and application development on Cardano. And this sort of has been provide.
This feedback has been provided via a number of SIPS that we've created that have then been added to
Plutus that have been, you know, highly regarded and well received by the majority of the community.
Um. And so, yeah, it's sort of a natural place for a natural new home for the Plutus team
because you know we've been working so closely with them for the past two years.
I know I'm good friends with all of the the core developers of Plutus;
they you know jokingly used to call me their product manager, and yeah, so.
My my goal here is to sort of expand on on that relationship, on bridging the gap between the people
writing the language and the people using the language, and make sure that the the feedback channel
is more iterative. Right? Instead of just me consolidating all the feedback
and providing it via sips, now we can have a direct communication channel with the community
where people can you know developers of applications on Cardano can post their the pain points,
the features that they need to unblock certain application domains. Really,
we're concerned about one: making the execution layer of Cardano competitive
with the execution layer of the sort of ecosystems that are performing well
in application development, like Solana and Ethereum. And two, especially now more than ever,
security. I strongly believe that sort of the next two years is do or die for blockchains. Everyone,
you know, no one will make it through this AI security nightmare unscathed.
Cardano has invested a massive amount of development effort, time, money, and and sacrificed
many features and huge amounts of of iteration and improvement to to sort of maximize security.
And these sacrifices, previously before this AI era, were not highly regarded by the market.
The market did not value to the extent we wanted it to or we expected it to the sacrifices
we made towards mission-critical development. The market valued sort of quick iteration. Features,
features, features, and the argument of well, Cardano is more secure was intangible because,
for instance, people who used Ave, you can't convince them that Cardano is more secure than perfect
because they've been using Ave for six years and they've never experienced an exploit.
So any argument of oh yeah, Cardano applications are more secure. And so,
you know the the pain points are justified. Did not land well because they would say, okay, well,
more secure is an abstract thing. I've never, I've been using this application for six years
and never experienced any security incident. And so that it it was poorly received.
Now that's changing. Blue chip protocols across the board, Ethereum, but not just Ethereum,
everywhere are for the first time experiencing large scale exploits. And so that you know,
impeccable record is cracking now. Security is becoming very tangible for end users.
The founder of Open Zeppelin, the CTO of Open Zeppelin, one of the founders,
famously stated that Open Zeppelin created essentially what is the Ethereum native token.
Every token on Ethereum is created using this Open Zeppelin standard. And he famously said
that he would advise all of his friends and family to withdraw all of their money
from DeFi applications right now because of the risks. And so, the the market value
how the market values security has suddenly skyrocketed, and we're seeing you know chains' value
across different chains consolidate. We have like 200 plus chains. If you go through
Coin Market Cap, of different chains that all have different security assumptions
and different levels of budget to handle security and different, you know, volume trading volume
and liquidity. And 200 chains are not going to make it through the next two years. It's impossible.
The surface area is too large, especially for the chains that that are less funded.
You're going to see a consolidation, and we're already seeing this. We're seeing
large scale exploits across many of the chains that are like you know past place twenty
on coin market cap. And as a result of this, liquidity is moving around,
looking for sort of a safe haven, looking for whatever financial instruments that they were using on
those chains for a home where they can sort of continue doing what they were doing without the risk
of you know the extremely disproportionate risk of losing all their money due
to a security incident. And I I hope to make Cardano the de facto location for that.
I think that well, yes, this whole AI nightmare poses a existential risk to the blockchain industry.
On the other hand, with risk comes opportunity, right? If if Cardano is the only chain that makes it
through these next two years unscathed, it's it's going to become very attractive
for liquidity providers. That everything that we've traded to achieve this level of security
so far is going to be justified. And because the execution layer is, you know,
where all of all of these exploits happen, which drain funds. Yeah, that this is
sort of a high priority for for us taking over the Plutus team is to make it the execution layer
of Cardano as safe as possible, especially against sort of this
these AI-native red-teaming slash exploits. Yeah, awesome. That's great.
It's good to have the like overall strategic perspective on blockchain at the moment too.
This is something that I've been feeling a need for. Like, I feel like
often people are sort of backwards looking, so sort of still stuck in like twenty twenty one
like narratives and things that that originated in twenty twenty one. It's like
where are we actually today? So it's I appreciate your your thinking and leadership on that, Phil.
Just one follow-up question. You already touched on this to some extent, right? You know,
having Plutus in Midgard helps to position well. Is having the the Plutus team be successful
and operate well positions Cardano well overall with relation to this market condition.
Following from the potential AI exploits across the industry, but just specifically for Midgard,
and it might just be like a function of the answer you already gave. But specifically for Midgard,
what are the like synergies or the cross pollination, or you know, the benefit generally speaking
that you are hoping to see from Plutus joining your team? Um, sorry, the.
Can you repeat the last part? Yeah, yeah. So basically, like you've you've collaborated with
the Plutus team, like your your team at Midgard has. But like, what's the benefit of actually having
them be part of Midgard? Like, why? I mean, is it just essentially and maybe this is the case,
just essentially you know so that they have a home and that basically it's going to
still be business as usual? Or is there like any specific benefit to actually having them be a part
of the the Midgard sort of Midgard? Team directly. Oh yeah, so historically, right?
My contributions have been mostly in whenever I have free time, right? I'll draft a SIP,
and I've wrote written many SIPS, and many of of these items have been included in the roadmap.
But we haven't had dedicated time to make this a priority consideration, right? Of you know,
the the roadmap still was defined externally, and there there was still, of course,
some level of an ivory tower. And having it with Midgard, which is a community team, with you know
many community application developers at Midgard Labs, it's going to make this feedback cycle much,
much more direct and ensure that the roadmap is defined by the community.
A lot of it will include sort of opening the communication channels that we had previously
with the DAP teams, and then would sort of consolidate and relay that to the SIP process.
Opening that communication channel directly to the Plutus team, right? So just
as DAP teams can reach out to me, and right now or historically I'd be like, oh,
I'll see what what I can do, right? How I can draft a SIP, how I can get get something in.
Now the actual You know, proposed roadmap will be a result of direct communication from
from those teams and from developers throughout the ecosystem. So it it will sort of get rid of of
the ivory ivory tower, right? We plan to make these the core development accessible,
make the feedback mechanisms accessible. Also, I think it's natural that the team, the Plutus team,
should get some experience in application development. Right? It gives you a different perspective
when you actually use the language that you're developing. You yourself will, well, you know,
it's one thing to hear pain points; it's another to experience them. Yeah, absolutely.
I bet that Robertino is excited about that too. Yeah, seeing the one hundred, one hundred
plus emojis. Uh, okay, awesome. This is this has been great. Um, and it's I'm
glad to hear confirmed, um, from several of you guys what I was suspecting here that this uh,
you know, these functions actually becoming autonomous and joining dedicated teams that are closer
to their direct work in the ecosystem seems to be tightening feedback loops like across the board.
Um, and you know, in a way that sort of Goes beyond what we could do before,
aligning like the direct incentives of specific teams and people with their place in the ecosystem.
So I'm pretty excited for the new paradigm. I'm excited for you know I mean I think as we go into
funding season sometime in the next like three or four months, I think that this will be this sort
of thesis about how this affects the work and the teams will be borne out.
You know we'll we'll see in the interaction with with d reps and with the rest of the community.
How things are shaped and how things are led under the new paradigm. So I'm excited for it.
Thank you guys for, I mean, both for doing the thing in the first place,
taking on these new responsibilities and doing it boldly, and also for coming
and having this conversation today. Hopefully we'll have
many more like it in the future. All right, thanks guys, and we'll see you next time.

هل تريد مزيدًا من TVL لبروتوكولك أو سلسلتك؟

تنمّي AlphaGrowth قيمة TVL للبروتوكولات والسلاسل من خلال استقطاب الأصول ودمجها، والمنح، والحوافز، وصفقات LP. نحن من بنى هذه البيانات ونبقيها مجانية.