Adam Liposky

Like you still have to just keep your head down and focus on utility, keep your head down and, and ignore the naysayers.

I think that's the number one thing that I would tell

Somebody that builds in the space is like, you've got to go focus on your customer.

You've got to go focus on utility.

You've got to go focus on the value you're creating and not necessarily be distracted with the money over here or over there.

Just because you can go and get that money doesn't mean you should.

Yeah, I think it's such an interesting question.

I think we've done a lot of things right.

I think one of the things I probably would change is sort of our order of operations and how we've built.

It seems very in the weeds, I know.

But, you know, like we...

We started by building kind of the bigger picture.

We built the framework to build the Canopy solution, and then we built the launchpad that enables that to happen at a highly accelerated pace.

I think if we had the option, it would have been nice to kind of fast forward a little bit and say like, okay, how do we get this in the hands of developers as soon as humanly possible to get more feedback?

And so that getting that feedback is just starting to come in over the last like, like four or five, six months or so.

But, you know, having more feedback early on when we were designing the protocol and designing exactly how it all come together would have been great.

It's hard to go at somebody with a white paper or a light paper and say like, hey, give us feedback on how all these mechanisms work and how it's all going to come together.

It's just, you know, like it speaks to how difficult this process is to build in L1.

And, you know, like if I could do it faster and get things in the hands of developers sooner, I probably would have.

Yeah.