Reacting to Web3

This is unfortunately just one of the bad puns that I'm going to be using today. So I am your token web 3 developer at the conference here today. My name is Jonathan Shealy. I work for Decentology and we build developer tools for people, for you, to be able to do React component based blockchain applications where you do not have to write any of the blockchain code.

So just like Webpack and libraries like Tanner's new TanStack, there's only a few people who actually need to build blockchain applications and package them up as modules to deploy for all of us to just use and not have to pay that cost and get the benefit. So our goal here is to provide web 2 developers like yourself to access web 3. So either if you're a manager or a client that asks you, can you just add some blockchain, you do not need to learn the programming languages like Solidity and Rust in order to actually deploy a blockchain app. It's as simple as just NPM installing the modules and away you go.

So let's see some code. That's why we're all here today, right? So this is what adding blockchain code to a standard React component would look like. You end up just importing some core libraries. You have an initialize function like if you ever use Stripe or Auth0 or anything like that. You just pick your blockchain, you pick the network and any modules that you want to add. In this case, we're using the ER721, the NFT module. So wrapping it in a simple React context, your main part of your app allows you to connect and log in a user. So similar to like Gmail or Facebook or anything like that, you would now just be able to have the user directly log in, which honestly is just simply public private key encryption, the same thing we use to connect to GitHub and do that kind of thing every single day. Now the user can just do that on your website. In order to use the modules, you just take another component and simply wrap it in a use hook. And in this case, one function should be able to mint an NFT. So you do not have to deploy that contract or anything like that. You just get that for free and it connects automatically to the wallet.

So what's in the box? So that wallet connection I mentioned, so authentication, you get the network negotiations. You don't have to figure out all of the different networks that are provided for each blockchain that might exist. All the contracts are already deployed for you. So we use a factory pattern we call like the tenant architecture, but it's simply a pre contracts already deployed and you just get to use them. Decentralized storage is also built in. So we have baked in modules for IPFS and Skynet. So anyone Terminator fan, that name is hilarious. And they're all TypeScript library. As Tanner mentioned earlier, huge fan of TypeScript and I could never build anything without it.

And we also create a testing harness. So we believe in order for you to actually see these things without actually installing them, everything is done in Storybook. So you can actually go in and play with them and see how it actually works and make sure the functionality is there that you want before. So no buyer's remorse, as it were.

So that's kind of what we have in the box. So the two questions I always get asked is what can I build with Web3 and why do I need it? So to answer the second one first, here is why you need it. You might not. But if anyone has any of these concerns of what you can build, so game engines and adding kind of microtransactions, which is sometimes a naughty word, but a lot of applications do need that. So being able to add that with a mobile application for payments. Anytime you have contracts where you just want to guarantee that both sides are sort of being honest, so a mediator type contract pattern. And then creating a business logic application where another developer could come in.

So let's say you want to focus on creating a game, but another developer can just read the blockchain and create a whole ladder-based engine based on your data and you didn't have to build that. The community can help drive information. And again, like I mentioned earlier, simple authentication. So if you just wanted people to be able to log in and you want to know something about them without having to use one of the big three authentication providers and you don't have to build an authentication provider yourself, because no one likes to do that. And then payments. So if you wanted to create your solo version of Medium, you could do a subscription-based model. And lastly, I want to say one of the things that we advocate for is for open source. So this kind of model allows developers to put in a small royalty fee into any of the paid transactions. So if the model has like a $5 transaction for me to give to you, you would be able to simply add in a tiny 1% markup and you would get that royalty forever as the developer. And that's something we advocate for to boost our open source. With that, we have some documentation here you can visit and go to our Discord. And thank you, Amsterdam. Thank you.