Benny Vasquez

Trust me, once you experience this AI-optimized sleep, you'll wonder how you ever slept without it. How do I know? Because that's exactly how I feel. They're currently shipping to the U.S., Canada, United Kingdom, Europe, and Australia. Once again, 8sleep.com slash changelog and use our code changelog and get $350 off your very own Pod 4 Ultra.

What is the idea of staking? I don't understand it in crypto as normal, but if I bought in and I staked against a project, what does that do for it? You get a yield. Describe that to me. Like four, five percent.

Interesting. When I buy in initially, who am I buying the token from?

Gotcha. Do you all keep a large percentage of the token as creators of the token?

Right. And it makes sense because you're investing in it, making it. There's obviously economic incentives involved.

17,000.

17,000. So that's a lot of... It's a decent amount of projects. What does it take to onboard? What's the incentive? Obviously the incentive is to be able to have, what is it called, T? Is it called T or Chai?

Okay, T token.

Sorry, I'm uninitiated here, so a lot of my questions are from the uninitiated standpoint here. Okay, so you have the T token, and me as an open source maintainer developer, I go and put my open source T-enabled, onboard, what is that like?

Is it challenging to determine ownership at that standpoint? Because you've got multiple maintainers, core maintainers, trademark holders, especially with the WordPress world, you've got a lot of things happening in this ownership state of open source. There's a lot that can happen.

How do you determine who is the true owner, I guess, of the token when it comes in, if it does become valuable enough to... Cash in, so to speak.

Do you anticipate challenges there that you will get mud on your face from, regardless if, I guess, maybe egg in your face is probably the better term? Because you're kind of leaving it to them to decide, and it might cause drama?

Sometimes it's easy to squash that to some degree with the why. Like, why did you do this? It's one thing to have a capitalistic intent, either personally because you're creating a company around this with venture capital and incentives, and then to enable open source developers to get paid. So there's lots of reasons why, I'm sure. But what is your personal reason why?

As he was describing the dependency graph, it reminded me of the way, I suppose, Google or a search engine attributes weight to or importance to a website, which is backlinks. It's the same kind of idea where you sort of define some sort of perceived value based on being in the dependency graph of a project. And I imagine that totally makes sense.

And it's not based on whether I think your thing is cool, whether I think your thing is worth funding. It's a matter of, yeah, it's like, is it literally being used? How deep is its importance? Then you can't scrutinize back to the Nebraska XKCD drawing and cartoon because... You can see the weight. You can see the graph there that says it truly is important.

And going back to what you said with Patreon or even GitHub sponsors, you spend most of your time marketing and promoting the fact that you could be paid, not doing the things that should get you paid, which provides the value. And so it seems like if you can get past this, I don't know how to describe it, I guess, the idea of crypto.

Yeah, the anti-crypto sentiment. if it couldn't play out well, because it seems like it should. Because you can't argue with the graph. You can't argue with the importance that gets placed on it, or the weight, the perceived weight and value that comes from that as a result. And the developer can keep doing what they're doing. Not remapping around this new idea of how to get paid.

They can just keep doing what they're doing. The dependency graph predicts their future. He can stick against it if he wants to, which increases my yield, increases his yield. Seems like it has the right kind of ideas. What's the reception so far? Like, you're in the percolation stage. What's the sentiment?

Or at least, let me see if I understand this right. And this is where my idea comes from. What if, let's play out a scenario. What if the developer world rejects this because they're anti-crypto? What if T, because you can still determine the dependency graph with or without onboarding, right? You can still determine the graph because it's in Git.

So long as it's open source and available, you can determine that graph and its importance. What if it becomes a speculation engine so the people who do care about speculating can leverage it as crypto, whether developers or not, and now it's sort of like maybe this adjacent engine this adjacent proxy to value. And not me saying this, but I'm going to say it.