Alpin Yukseloglu

But the tests need to be sort of written by a human, right?

You don't have this notion of like, we have a bunch of state.

We can make assertions about the state.

We can, for example,

Send a model on a new contract on a new EVM that's never seen before and make assertions about whether it's able to quote unquote drain money from it.

Like those concepts all would have otherwise needed to be hard coded into the program.

But because it's crypto, we and there's so many standards, it's verifiable.

And the models are just ramping up really quickly in capabilities.

There's a reason we started with security and not sort of general programming capabilities.

It's because it has this very nice shape of it's extremely economically valuable.

It's extremely sort of intelligence bound, right?

It's like you can't... Yeah, it's intelligence bound.

And it's very easily verifiable.

So we know when an exploit has happened.

So security capabilities, I expect, will develop very quickly.

And then we've talked about sort of all the implications of that.

Other crypto-related capabilities, I think...

For example, things in the domain of mechanism design or around market-related problems, like what is the mechanism for an exchange?

How do, if you have market of agents, right, what is the best way through which they should coordinate with each other?

These are, I think, open fertile soil.