The Index Podcast
Aug. 28, 2023

Mad Lads: Building on Solana with Armani Ferrante, Founder of Coral

Mad Lads: Building on Solana with Armani Ferrante, Founder of Coral

This week, Alex Kehaya talks with Armani Ferrante, Coral's founder and CEO, creator of Anchor—the first Solana framework, and the imaginative force behind the NFT collection, Mad Lads. Mad Armani shares his developer journey, shares his advice for building apps,  and the innovative Backpack wallet embracing the Solana xNFT standard.

The player is loading ...
The Index Podcast

Armani Ferrante

Twitter - https://twitter.com/armaniferrante

Mad Lads - https://twitter.com/MadLadsNFT

Website - https://www.madlads.com/

 

Host - Alex Kehaya

Producer - Shawn Nova

 

 

Transcript

Speaker 1:

Welcome to the Index Podcast hosted by Alex Kahaya.

Speaker 2:

Plug in as we explore new frontiers with Web 3 and the decentralized future, hey everyone and welcome to the Index brought to you by the Graph, where we dive into the minds of trailblazing entrepreneurs shaping the future of the internet. I'm your host, alex Kahaya, and today we have a guest who's revolutionizing blockchain and decentralized applications. Joining us is Armani Ferante, the visionary founder of Backpack and creator of Anchorling in the slon ecosystem. Been dying to get you on the show and really happy to have you here. Thanks for being here today on Memorial Day. Happy Memorial Day.

Speaker 3:

Yeah, thank you so much for having me. Happy Memorial Day to you as well.

Speaker 2:

I really want to talk about Backpack and Anchor and all this stuff you're up to. But before we get into that, do you mind? Just for people who've never met you or don't know about you? Who are you, what do you do? How did you get here? Let's go through that whole part of this spiel.

Speaker 3:

Yeah for sure. I think I have more or less a pretty typical story for a programmer that has made his way into crypto. So I studied computer science at Berkeley, started my career in the Bay Area, worked at Apple for a bit, worked on iOS and macOS applications and then in 2017, 2018, during that big bull cycle when Ethereum was taking over the world, this narrative of a decentralized, permissionless, censorship resistant world computer was making waves. I had, you know, read the Ethereum White Paper, fell in love with the concept and, you know, left my job at Apple and haven't looked back ever since. I didn't really have a job, or I didn't have a job lined up. I didn't really know what I was doing. I didn't really know how to, you know, program smart contracts. I knew a blockchain's worked, but that's about it and didn't have really a plan and just started committing to open source repos and eventually found my way into Ethereum land and got a job and have been bouncing around L1s and learning different projects and technologies ever since, most recently, I guess, over the past two and a half years at this point, have been in the Sony ecosystem, working on everything from wallets to DeFi to developer tooling and, most recently, this latest batch of work XNFTs Backpack and the MadLads.

Speaker 2:

I know you're passionate about open source, just from talking to you and hearing from you on Twitter and whatnot. But where does that come from? Why do you like working on open source projects?

Speaker 3:

It's honestly just like good fun, right? It's like your developer you want to work on cool tech. You want to be able to you know open PRs and be able to experiment with stuff and being able to like dive through source code to learn things or solve whatever problem that you want to do. I don't know. Open source is just more fun than closed source and it's really as simple as that for me. I don't think I have any purpose for my love for closed source beyond it just life's more fun as an open source developer than it is as a closed source developer.

Speaker 2:

I'm not a developer, I'm more of like a BD guy, but I love working on open source stuff too. I like the idea of just building a business around open source software. The thing I always go back to is legacy and impact, and I just feel like if you're building something in the open, the whole goal is to help people, like help other developers and like make sure they have access to that software kind of forever. It's challenging to build a business that way. I mean there's a lot of fear around that, which I actually think is mostly unwarranted. I think it's mostly just about execution. I mean, saas businesses that are closed source are pretty easy to copy. But that is what's exciting for me is like the legacy piece of it and I got read by my business partner, brian Fox, who's the author of the Bash shell. You probably used Bash. He helped write the GPL licenses back in the 80s or whatever, or whatever those were written, and I think it was last year. Nasa used Bash on the quadcopter on Mars and it was because they needed something that they could update remotely. That would be like a really small program and Bash was the easiest thing for them to update. And so I just bring up that story because if you build something useful that's open source, you have no idea how big it can get and the impact it can have. Like, literally his software is on Mars and on every computer.

Speaker 3:

So Bash is a big deal, so that is a super cool story.

Speaker 2:

Yeah, Tell me about Anchor. That was the first. My first exposure to you was just kind of learning about Anchor and that framework. But can you walk us through why you worked on that and kind of how it came to be and what it is?

Speaker 3:

Yeah, I mean, the story behind Anchor was quite simple. I joined the Salana network and started working on smart contracts and very quickly came to the realization, after writing my first program, that it was really hard to write secure smart contracts and to do it quickly. I think my first smart contract was definitely exploitable and if you look back at all of the developers at the time and all the you know up and coming projects during the first couple of hackathons, most of them were exploitable because the programming model is very unique. It's not something that people are used to, especially if they're coming from, you know, a web development background or even a solidity EVM background. Solana has this unique property where you have to actually specify the storage or they call them accounts on Solana that you are going to read and write upfront, and so what that basically means is that you're injecting data into your program and then your program is operating over that injected data and then immediately, this should be raising red flags. So, like any experience like back in developers right, you know immediately think of, like sequel injections and untrusted form inputs and all these things that are known from the web world, but now applying them to a smart contract context where you have this adversarial environment and, you know, in the context of DeFi, in particular In NFTs, dealing with high value assets with, you know, people all around the world, and it's a very kind of hard problem. And this kind of, you know, unique feature of the Solana runtime is what gives it it's, or one of the things that gives it, an incredible performance its ability to parallel Lee, execute Transactions at the same time versus, like you know, some of these other systems like Ethereum or Bitcoin. They're all kind of single threaded, and Solana, on the other hand, you know, is it's multi-threaded, it's very fast, but it has this idiosyncrasy and, you know, in the early days, not a lot of people could really wrap their head around this. It was very new to most of us and the tooling at the time wasn't really prepared to deal with the massive growth that it was about to experience. And so I basically just came on to the network. I saw this stuff, I saw it was a big problem. I kind of came to the conclusion that I didn't think that Much of this would work at all and I didn't really see a developer community that was gonna rally behind this tooling Because it was just too hard and we saw it at the time with a lot of early projects that would like come see Solana. They would try it for a week and then they would leave because they're like, oh, this is like horrible, like I'm not, I'm not programming in this. I basically saw this and thought it was a big problem. And you know, I think at the time there was a bunch of other tools in the crypto world, right, I think, like parody had ink, ethereum obviously had solidity for EVM, and so, like, the ideas behind anchor were, you know, not necessarily innovative. It was just engineering work. And so I ventured into the Solana discord at the time and asked you know, are you guys gonna build this stuff? And I think Michael Vines responded, you know, saying like no, you know, I we're not gonna build it. We really hope somebody else builds a framework around for the programs on the network. And I said, well, I guess I'll do it then, because you know, if nobody's gonna do it, then you know nobody's gonna use this stuff. And and one of the kind of fun parts about being a developer and blockchain is that, well, all the problems become your problems.

Speaker 2:

And so, yeah, just took it upon myself to to write the framework and I think the the proof was kind of in the, in the pudding, so to speak, and haven't looked back since and then you interesting I don't know how that story happened, like to get you guys building backpack together and X nfts, but maybe you can walk us through how you went from anchor to actually starting a company.

Speaker 3:

So I built the anchor, I was working on the Solana network, but I was like very much like in my own world. You know, I was in California at the time just like kind of you know, working remotely, didn't have a team, just kind of like working on open source, and anchor was super successful. And, you know, had all these people reaching out to me basically saying, you know, armani, what are you doing? What are you doing Like, and basically kind of came to the conclusion that I should scale the team and build more cool stuff. That would continue to be impactful. So I thought, well, you know, I build this really successful public. Go to the anchor, let's, let's scale it up and and do more good stuff, right. And so the original kind of idea was like, oh alright, let's make a business around this. And that was kind of validated when you know there's people saying, hey, like you know, are you gonna do, you want to raise money, basically this kind of what happened? That was the original Motivation and so, you know, I think originally I was starting out thinking, well, what are the services that I can build around anchor and and, and you know how can I scale the anchor team right? And so we had a couple experiments, for example, like the anchor program registry was like another kind of public good that we kind of worked on for a bit, where I was kind of like ether scan verified contracts, but for Solana, right. So we'd build Solana's Rust programs inside of a Docker image, basically, and have deterministic builds and publish the source code to you know central repository that everybody can use and create some CLI tooling for folks like Dows and multi-sakes actually verify the upgrade binaries that were, you know, being sent to the network. Until we had a couple you know experiments around this Eventually started, you know, thinking through the idea maze, like, well, what are the big problems to solve in crypto? One of the first big things that you know, immediately after smart contracts was, well, it's just thinking through like incentives and this was like kind of its own side quest, where I was thinking through like things like rabbit hole, gg and things like what are the roles of tokens and what are the roles of NFTs and how do you get people to, like you know, coordinate with each other? This is like really the interesting part about crypto, you know, other than all of the payments infrastructure that's we all kind of love to talk about, it's really just global coordination of humans to work on problems together, right, I think open source is like just an incredible example of this, where, in crypto, it's like no coincidence that everything is open source and it's because everybody's incentivized to do it. And I think if you take out, you know Everything in crypto other than just like the open source. That is like a huge achievement in and of itself. And so I started thinking about these problems and thinking about protocols and thinking about you know all this stuff and basically came to the conclusion that it's gonna be really hard to build protocols, it's gonna be really hard to like build this type of incentives infrastructure until we have a wallet. Basically, you know, at the time, all the wallets were closed source, so it was really hard to work to get people's attention. Everybody has their own priorities. They had all experienced such huge growth. I basically came to the conclusion that, okay, well, we need to create a wallet, because this is the only way to create protocols.

Speaker 2:

Let's break that down a little bit for people. Why does a wallet matter For a protocol developer? What does a protocol need a wallet for? Give us some examples and talk through the logic there.

Speaker 3:

Yeah. So the wallet is more or less the gateway to crypto. It is the central point of contact that everybody must interact with. The reason is because, well, it controls the private keys. And then you might ask yourself the question why does it control the private keys? Different apps have different logins. Why don't you just do that? Well, it's for security reasons. The wallet is the single trusted point in crypto and everything else is more or less untrusted. Every website, every DNS record, every app they're all untrusted. But the wallet, whether it's MetaMask or Backpack or whatever, that is the single point of trust that everything is built on. And so if you want to connect with an application, if you want to sign transactions, if you want to upgrade the user experience in any meaningful way, you have to interact with a wallet. And particularly on Solana, you have this kind of I mean really on every blockchain. The wallets are really the gatekeepers because they are the ones that interpret the protocols. They interpret all the data on the blockchain and then render it to the user. So when you open up your, your Backpack or your Soulflare or your Phantom or your MetaMask or whatever, those teams are deciding what you see. There's tons of protocols that they can show, but they ordain what is the canonical asset representation of basically anything, whether it's an NFT or whether it's tokens or whether it's something like applications like XNFTs. The wallet determines that and you see this friction and you see this problem manifest itself in the Solana ecosystem when you take a look at the recent drama around MetaPlex, where you have this really challenging social problem where, on the one hand, you have this private company, metaplex, that has every right to do what they want to do to build a sustainable business. They own the program that represents NFTs on Solana, they control that upgrade key, so they basically control all NFTs on Solana. But then, on the other hand, you have this decentralized network. You have all of Solana with all of these heterogeneous companies and developers and contributors that all rely on this central company and those incentives don't necessarily always kind of work out and it creates a lot of drama. The challenge is that, well, the ecosystem has ossified around this singular program implementation, and whether this is good or bad is like, maybe besides the point. I think there's trade offs, there's good things about security, but I think really that what I'm referring to is, like the challenges at the social layer where you have this company, metaplex, where they have the right to have fees. They should have infinite fees if they want to. If they want to have infinite fees, they can do that, but the challenge is that there was a huge uproar when they did it, because everybody's like wait, wait, wait. I thought this was a public good. We're all stuck with this program. Why are you doing this? It's really important that the ecosystems can be flexible enough to adapt around any given company, any single point of failure. If they do the wrong thing, right. If they go out of business, if they're hacked, if they do something malicious or if they just do something that is maybe a silly business decision, which they have the right to do, it's their business. Circling this back into wallets well, you know who determines who that canonical representation is. It's the wallet, right? It's a wallet in the marketplace. Those are the two companies. You have to convince MagicEaten and you have to convince Phantom on Solana, right. If you don't do that, it's over. You're not doing anything on Solana without doing that. That's a really good example of why this is so important. If you really want to innovate, you have to create your own distribution channels, you have to create your own demand, and that's basically what leads you to creating a wallet, or it's what led us to creating a wallet, which is that we don't want to go begging hat and hand to these companies. We want to just be able to do the things ourselves, because there's too many important problems to solve. The first very good example of this was XNFTs. We cannot have built XNFTs without having built the wallet, because nobody would have given us the time of day.

Speaker 2:

Yep, that's 100% on point. As a builder in this space, I 100% appreciate it that there's this option that we can contribute to as an open source company, like at Olaplex. It's one really important piece to protect us from the platform risk that it exists. I think you've probably saw me on Twitter weighing in on this with Metaplex specifically, but I want them to have a sustainable business model. I don't think there's anything wrong with that. There's a lot of experimentation that can happen around open source business models, especially at the protocol level. The big issue that I have is they were a GPL license. First they were Apache and then that got closed source, forked a bunch, so they changed it to GPL. Gpl allows forking as long as you open source the code. That was awesome because we could contribute to that and fork it if we needed to. If the incentives were misaligned, if they just made a business decision, that really would hurt our business. We had protection there. I don't want to build a new NFT standard of a fork of theirs that is potentially insecure and doesn't have a thousand developers building on it. That doesn't make any sense. That's like a last resort for our business. But when they change the license to the current new Metaplex license that prevents forking. If you fork it and you remove the fees, you're in by the license. That creates a lot of business risk for us. We can't really continue to invest in that standard knowing that they could one day just change their minds about fees or do something with it. That breaks our business and then we have no other option. We're actively looking to develop and invest in other infrastructure Standard all the way up to the marketplaces. Actually, we worked on a project called Night Market which is just open sourced, which is a fully functional open source marketplace. Now it doesn't have the eyeballs Magic Enier Tensor does, but it is there. It is a fully-fledged NFT marketplace that you can fork and use and deploy, with a whole reward center built in and all the stuff that you need to build a business with a marketplace business. What I'm really interested to hear from you is okay, wallet and marketplace, right, but what other pieces of infrastructure need to be built to support a new standard that's actually open source?

Speaker 3:

Yeah, I think really the big challenge that the ecosystem is facing at the moment is there's two conflicting requirements. On the one hand, you have a single canonical representation, a single instance of a program, and then on the other hand, you have the desire to fork and have multiple competing asset representations, and this is basically what leads you down the conversation to having interfaces. I mean, it is a wallet problem in the sense that the wallets need to implement the interface and interpret that asset representation, but ultimately you want to be able to fork, and that's a really important property for decentralization. And there's a trade-off there. If you have multiple token programs and somebody implements their own version and maybe they're malicious or maybe they're just incompetent, those assets could maybe have a problem with it, right, and so there's this trade-off. My theorem has kind of gone the path of interfaces and so there's a bunch of security kind of foot guns and problems, but they've seemed to have built a robust kind of social layer around it, given what we're seeing with the conversations around MetaPlex. I'm updating my opinion in real time, but I feel like right now I'm a pretty big advocate for interfaces and feel that the added competition and flexibility that it gives the ecosystem outweighs the potential security consequences, which can be overcome with just good user experiences.

Speaker 2:

Yeah, I 100% agree with that and I think also because wallets and marketplaces can still be gatekeepers with interfaces right, you can still audit an open source interface. You can require that it be open source but to be used in backpack, like you can say if you want me to render your standard in our interface, it needs to be open source, we need to be able to audit it, and that's how you provide the protection. That's the responsible thing to do as a company. That's like a critical piece of infrastructure, but it gives the flexibility for competition to happen much faster. Right, like the mode that MetaPlex has right now around the stack to get distribution of these assets and like get users is pretty, pretty significant. So for me, it's just about reducing the barrier and that's just for safety, like for safety of the ecosystem, not for safety and the security standpoint, but just making sure that there's like other options and the platform risk goes down. I think it's an important conversation to have and I still think MetaPlex can do things to improve there too, like on the open source side, especially on the license, if they so choose. I think that the license issue is actually going to force, is accelerating the path to competitive standards and it's going to backfire. Mark those words and let's check back in six months and maybe nobody cares. Maybe, like I'm the only one. Last thing I'll say is I do love the team over there. I like a ton of respect for the all the builders and the devs Like they've worked with the Olaplex a ton over the last two years and I just have nothing but respect for them and I understand. You know building an open source business is hard. It's really hard. I know that firsthand. You know kind of got to throw spaghetti at the wall at sometimes and see what sticks.

Speaker 3:

Yeah, I mean maybe to like wrap up this topic. I feel like it's not on Metaplex to solve this problem. It's really on the ecosystem to solve this problem. Metaplex is a business. They should do whatever it is that they think is strategically in their best interests. They have shareholders, they have a token without privy to their corporate entity structure, but they should be able to do whatever they want to do. They should be able to have infinite fees. That's their right, but it's the responsibility of the ecosystem to maximize competition and decentralization. The only way I think that's going to happen is with interfaces. I think they've been in both a fortunate position where they've been able to build this mode, but also an unfortunate position that they've been on the receiving end of a lot of this hate, where you have these conflicting requirements, where you have a business on the one side that's looking out for itself and then an ecosystem on the other side that's also looking out for itself. It's a tough situation, but I'm confident that we can overcome it collectively.

Speaker 2:

Yeah, I couldn't agree more. I think it's really well said. I think that just part of it is just crypto, twitter and crypto in general. It's just so toxic sometimes it's my least favorite part of the space that we work in for sure. Let's change topics here a little bit. We talked about backpack and the important of the wallet, but talk about XNFTs. That's a huge innovation that I really want people to understand. It even took me a while to grasp it. I would love to try to break that down a bit so people can understand what a big deal that idea is.

Speaker 3:

Yeah, xnfts. It sounds like a load of jargon. It is a load of jargon. The idea is very simple. In the same way we can tokenize images those are NFTs, right, you have JPEGs in your wallet In the exact same way you can tokenize code. You have ownership of code that's tracked on a blockchain. The way this manifests itself inside of a wallet or inside of any app really, it doesn't even have to be a wallet is simply on-chain applications. The way I like to think of it in the context of backpack is WeChat mini programs on Solana, where you have these plugins or these mini apps that can do whatever they want. They're their own sandbox little world where you can build an app store around it, or you can build an NFT collection around it. When you go to open a backpack and you click on your madlad, it's not just an image, but it's actually a full-blown application. You can get this token-gated experience right to the wallet If you can combine this protocol with an ecosystem of services around it. So everything from like user names, profile pictures, bi-directional friends ie a social graph, push notifications, an app store, developer tooling this starts creating a compelling ecosystem, if you will, around this XNFT concept, where you're simply just creating a new way of running applications directly inside of the wallet. That's the entire idea.

Speaker 2:

Give me some examples. Was your top three apps that you're most excited to see get built or that you want to build? That are XNFTs, yeah.

Speaker 3:

There's been a bunch that have been built. If you go to xnftgg you can see the whole store. I think there's a couple of different categories. The first category, I think, which is just maybe a good starting point, is just games. Games are simply just tried and true. We've seen this playbook run multiple times before, whether it was WeChat and Facebook, html5 games or iOS and Android mobile apps. Many games that you run on your phone that hook into the crypto economy, are just fun, especially on-chain game assets. Especially when you start looking at these larger NFT projects, whether it's Klanosaurs and their mobile app, or Yuka and their Metaverse or Star Atlas and their entire just incredible game. These game assets are coming on chain the whole ecosystem of gaming. In particular, mobile gaming is something that I think we've yet to see, but I think makes a ton of sense to live in the form of in-wallet applications. That's one category. Another category is NFT token-gated experiences. These are things like MadLads, smb, rogue Sharks. These are these big profile-pick NFT communities that are creating utility or digital experiences or community hubs around that NFT token. When you open a backpack and you click on your SMB or Slalom Monkey business one of the biggest projects on Slalom what you'll actually see is not the image, but you'll see their newsletter. They have the banana split. It's this awesome newsletter that they do every week. They have that NFT right there inside of the wallet or they have that newsletter right there inside of the wallet. The story about this is basically twofold. On the one hand, you have what I would consider the best token-gated experience that you can possibly have. There's no extra wallet connect, there's no matricure connect. You literally just click on the NFT and you're inside the token-gated experience. It's just like a great onboarding experience, great UX. Then the second thing that you have here is distribution, with the banana split in particular. The way this came about it was as I was in Taipei at the hacker house with NOM, who's one of the leaders in SMB, and he was showing me the banana split. I was like, well, how have I never seen this before? I'm an SMB holder. Smb was the first collection I ever bought where I was just head over heels with excitement. I was like oh yes, this is the best collection. I'm so excited to have a monkey. I never heard of this newsletter ever. You have this challenge that creators have where they have distribution, they have these rabid communities. It's just that they're not leveraging that distribution to the fullest extent. This whole idea of discovery and distribution is another huge value proposition, particularly for profile pic communities. With SMB, you get their newsletter. With Rogue Sharks, they've been doing their whole videos through their NFTs. With the MadLads, we're doing all of the token-gated staking and rewards through the MadLads. We're going to have something similar to Hotel Airline Reward Points or American Express Cashback, just like loyalty rewards programs for the people that are using the products. That's going to be used through the MadLad itself. When you click on it, it's actually the MadLad itself will have its own wallet. It'll be like an inventory view, like World Warcraft or RuneScape, where you have soulbound assets that are attached to the MadLad. You have this nice composable protocol where other companies can come and target market the MadLads to get distribution or to bootstrap whatever product they want, whether it's a pizza shop wanting to give coupons or a game wanting to airdrop in game assets, or an NFT project wanting to share a whitelist for their experiences. I think there's all these forms of token-gated utility that is built around NFT projects. That's really exciting. But ultimately XNFTs it's a very low-level primitive. It's like saying, oh, an indexhtml files. Who cares about each of these files? It's just a file, and then on top of it, what you build right these different types, these different websites, these different plugins or primitives is really where the action's at, and you know, all this kind of comes together to like build, like an awesome kind of, I think, consumer application, which is what we're trying to do with backpack.

Speaker 2:

And I think it's the web free, native way to create good UX. A lot of what we've done with Olaplex is you know, we use Castile wallets. This would brand. We work with big brands and enterprises, right. So they want to use like Fireblocks as a Castile wall provider and like I need to log in with Gmail or Facebook or Twitter and like create an account and then like do whatever the experience is like claim the NFT, get access to some content, like do a lot of things you're talking about, but we just cover in hub, like our product, we cover the payments of the transaction costs in the back end, like nobody even ever is aware of crypto, versus what you're doing. For people who maybe haven't used a wallet before. You know, the normal way to like buy an NFT or go to a website and unlock some content is they have to install the wallet connect piece on the site. That developer does, and then I, as a user, I have to go click a button. I have to sign a transaction sometimes multiple transactions. I have to unlock the wallet, then I have to sign a transaction. It's all these steps right, whereas with backpack, I want to go unlock some token gated content, like a newsletter. I just open the app and I click my the picture of the of the Solana monkey business JPEG and it shows me the newsletter. I mean it's like the gated chat functionality you guys have for MadLats, right, like I just click open chat and it opens it. I mean, the only difference is that it's through a wallet extension, like a Chrome extension, and not like a browser itself. Like, the Chrome extension is essentially like a browser. At this point, the wallet itself is like a browser. I just rearticulate all this because I think it's like for people who might not have been as deep as us, like using these products in the two different worlds you've. Really it's such a conceptually so simple but so big from like a conversion standpoint, like I don't even want to. Like I have no idea what the drop off rates are. When, like, a wallet pop up extension doesn't work, it's probably like a hundred percent, right Like you click it, it's like I've been there. Like you're clicking the button it's not working. Like the pop up keeps coming back or something Like just something weird happens and you just leave. You know, if we're going to get mass adoption and you want to do it like a fully web-free way, then you have to have something like what you guys have done with XMC and backpack. I think the use cases you mentioned are super interesting. One thing I want to break down a little more as you mentioned like being able to advertise to like MadLats holders, is that like a permissionless thing? Like how would that work If I want to send MadLats holders something through backpack? Like how do I do that?

Speaker 3:

Yeah, so what we're currently building right now is a simple protocol that basically allows you to soul bind assets to a MadLat. So when you buy and sell your MadLat on like MagicEden or Tenser, those like assets travel with the MadLat. So you can open it up and you can see oh yeah, there's like a game attached to here or whatever. Basically, there's like two parts of the system. There's the first part, which is like kind of an email inbox is one way to think about it, where you can get airdrop stuff and you have to permission that stuff to like enter into your MadLat, basically, and then once it's in there, it's obviously it's in there. But what's cool is like if you do it with XNFTs, then when you airdrop an XNFT and you allow it into the MadLat, that can actually interpret any type of asset. So it's just, like you know, permissionless asset interpretation, which I think is pretty unique, like, for example, if you wanted to create your own NFT standard, right, you can just like give that to the MadLats and it's right there, and so it circumvents a lot of these kind of distribution problems on protocols that we were talking about with the MetaPlex conversation. But it's a really challenging security problem because it's spam. Yeah, it's a spam problem. Basically, that's like the big challenge around this particular airdrop target marketing product that I think is unique to wallets.

Speaker 2:

Yeah, I don't have a solution for that one. It's a really hard one to solve. I've been noodling on this idea for a while where I really wish there was a website where I could just order, like e-commerce site, where I could just order stuff in USDC. I just wish I could use USDC for everything I love. Paying for things, and USDC on Solana versus like entering my credit card in and doing it through backpack would be even better, right, because I could just hit buy and it would be like I mean, it would be optional to put a confirmation in there, like, do you really want to buy this? Do you really want to sign this transaction? Because it would just sign it if it was X NFT. But like, is that something you could do? You could just like send someone an X NFT. That's like, let's say, I built a storefront that, like will turn your NFT your MadLad into a painting. Like it will drop, ship it to you. And so you hit like buy, enter your mailing address and it just drops, ships it to you as an X NFT like the actual physical one. Like you could do that in backpack using an X NFT.

Speaker 3:

Yeah, that's exactly right, and it would like detect what MadLad you have. It would detect your address. You'd have to put in the you know your home address or whatever and click confirm on the transaction and it'll pay it and go to your backend. And as long as you can figure out how to do the shipping, then yeah, that should just work.

Speaker 2:

Yeah. So we're getting towards the top of the show and I always ask, like what have I not asked you that you wanted to talk about, or that I should have asked?

Speaker 3:

I don't know if there's anything in particular that I am trying to evangelize or talk about at the moment. I think a lot of your questions have been great talking points. I don't know nothing in particular.

Speaker 2:

All right. Well, I've loved having you on the show and wish you the best of luck, and we'll obviously keep supporting all the open source work you're doing. If people want to build X NFTs or like, come build with you, where should they go?

Speaker 3:

The main place is follow us on Twitter X, nft underscore backpack and on Discord as well, if you can get links there. Those are probably the two best starting points. And then GitHub obviously has links to the repo, the local backpack, build documentation, all that stuff. So those are probably like the three main points of contact to get started.

Speaker 2:

I have a question for you that I probably should ask that I think would be helpful If people were listening to this story. Developers out there are inspired by your action, which is like you showed up. You started building open source and contributing in meaningful problems that you found. What are some meaningful problems that you would like solved as it relates to what you're working on? What are some areas where somebody could come contribute or start doing some research on how to contribute?

Speaker 3:

That's a fantastic question. So there's a couple areas. Some of them are being solved, some of them are not being solved. The first big one, I think, is still around. I think just testing in general on Solana, I think, still needs a lot of work, just like the whole environment for pulling in remote data testing against the token program and the metadata program and minting NFTs. I think we're like 80% of the way there, but we're not 100% of the way there. To make it really frictionless it still requires a lot of source diving and context understanding. So I think there's some good DevX problems to be solved there still, especially if you have some nice declarative programming model for initializing test state. That's one area I think. Spam and wallet confirmation signing or trusted transaction signing screens basically, is like a big one. I think these are mostly being solved by various different companies, but it continues to be way too easy to get rugged. This is obviously something that we're actively thinking about at all times and pushing quite hard on, but that's like another big area where just more mines is better. Yeah, those are probably two of the bigger ones that I think about regularly.

Speaker 2:

That's great. Well, you heard it here first. If you're looking to follow in the footsteps of Armani and solve some hard problems and make some open source contributions, I think those are two really big problems that, despite the fact that other people working on them they're so complicated Dive in, ask questions, get in Discord, start doing some research and make proposals, just push stuff out there on what might be possible solutions. I think that's a good way to get going and just start building. Thanks so much for being here. Appreciate you.

Speaker 3:

Yeah, thanks, alex, appreciate the time.