Joan Alavedra

And the reality is that wallets evolve so fast that like two years ago, we had like a, you know, first a smart contract wallet.

Three years later, we have like completely different standards and

that, you know, like the first iteration you'd have to upgrade it, then you have maintenance costs, security costs, et cetera, et cetera.

And so that would be like the first level for many developers.

And yeah, when it comes to selecting the right provider, I think like everyone has...

There's pros and cons.

From the open-source side, we've been for long pushing towards open-sourceness.

Most of the stack that makes it vendor-lock-in.

And so that's kind of like the angle where we try to educate developers towards, which is, hey, if you're building with a provider, make sure...

That that provider helps you answer the question, hey, what happened if you go under the bridge tomorrow?

What happened if for whatever reasons I want to change providers, like how would it work?

Right.

I think like not enough people ask that question.

And it's an important one for like the sustainability and long term projection of your project.

Yeah, I think for the most part, there's two things that still need some work in the industry.

One is obviously like the way that you manage private keys.

And so you need to understand, like there's a lot of, for a traditional full stack engineer, there's a lot of security for like security involved and security topics whenever you, you know, integrate with these solutions.

You want to understand who controls the private keys, how you can regenerate private keys, what like assumptions you need to make, like the correct implementations and stuff like that.

So that would be like a first, you know, good angle for most developers to take good care on this.

Yeah, I mean, I think there's been a huge shift from developers that integrate software products by reading at the docs and integrating it to developers that are by coding it and integrating it.