JS GameDev Summit

JS GameDev Summit 2022

Web 3 Gaming: What it is and Why it Matters

Paul Gadi

TestJS Summit

TestJS Summit 2022

E2E Tests for Web3 Applications

Hello, everybody. I'm hafaela and I'm gonna share a bit of my experience with entuentes for web 3 applications. So just a bit about me. I have 15 years experience in QA that's automation test strategy architecture and Leadership and I got really passionate about the QA area. So I created these blogging 2011 where you know, you can find everything that I have learned in the past couple of years. So cold is napets programming the devops leadership and that's automation. Of course. I was born in raising in Brazil to be more specific come from a coastal city called Santos in São Paulo. And you can see the picture on the screen. I'm also a really big fan of Harry Potter as you can see and this is one of the reasons why I move it too long, though eight years ago. And the weather as well, but nobody believe when I say them. But yeah, the agenda is gonna be this one. We are gonna talk about what is Webber tree, then the architecture of the web 3 application some introduction about the ancient tasks and the challenge then the tools that you can use and we are gonna have to demos one just using a mock and another one using framework. He called singpress. And then in the end we are gonna talk about the trade-offs of each approach. So what is web 3 web 3 is just a new version of the web. We are on web2 right now. And this web 3 it comes with the ideas of this centralization talking Basin economics and also blockchain technology. So in offers are really right on model. So people they have Financial stake and more power over the online communities they belong to So they own the data, which is not the case right now. The online experiences expected to change as as cell phones and is smartphones and the pieces they did in the past. So it's gonna be a big change for you know a star we are living in this moment some business. They try to join these new market, but they encounter some pushbacks as you know with blockchain as well like, you know, the negative impact on the environment and the financial speculation as well. This is the evolution of the web. So from the first versions, you know, so the first version we had the static read-only Pages where you couldn't interact too much with them. And then now what we have is a bit more Dynamic and interactive so we can go there and post things so, you know Twitter we can just send our data away basically through these big corporations and the web 3, which is the one coming now is more private secure in this centralized. So the idea is, you know, our data is not gonna be on by these big corporations, but by yourself And the architecture of the Webby tree is also quite different because it's based on Smart contracts like blockchain. So if you we see now what we have is basically the front end backhand database inside of this web server, and this is controlled by, you know, the corporation or the company somebody and the web 3 we have just the front end in the web server. So this is going to be a part of the you know is being it's gonna be controlled by the company or the corporation. But then they smart contracts and the evm and the Italian blockchain. This is something that is going to be the centralized. and this March contracts they they have the business logic and are the protocol of these transactions and these business. So basically now what we have is just we are going to interact with the front end and then the front end is gonna interact with the is March contracts and then evm the ethereum virtual machine and this is gonna add the transaction to the blockchain. So it's gonna add a new block to these Italian blockchain. And this is the part where is the centralized? So this is the an example of our web 3 stack. So we have some examples of like tools in Frameworks, but you can see the layer so you have you know, the first layer with the centralized applications so you can be something called something like metamask, which is a plugin to authorize it identity have wallets. It's a cryptocurrence wallet. Then you have uni swap. Then you have another layer presentation layer, which is called then you have the developer environments where you can you know, that's your New York products and then you have the other layers like blockchain interaction layer and then that you work layer with the evm blockchains. So this is not all the tools that you can use is just like an example with the most popular ones, I believe but at least you have an idea of you know, how it is their web 3 stack. And then the taxes they are the ancient asses are more like the problem with web free. But if you want to do, you know, the unit tests is fine. You can use something that you already use it for, you know web to Applications. You can use a jazz you can use mocha issue the same kind of framework and then you can just verify, you know, if you if the components they are operating as intended. so UI UHS are also are not not a problem because you can still use on the same Frameworks that use it right now to do the tests. And yeah, the integration tests they are not a problem as well because you can just use the it's much contract libraries you mimic their own changes by just mocking the underlying evm. So the problem is when you go and you try to do the instrument the food when joint tests without the mocking. Because you have these 30 party provider that you need to use to communicate with the blockchain. And so we made the transactions and most of the Frameworks right now the that do enchantastic. They cannot access this plugin. So one of the most use the plugins is metamask, as I said is a cryptocurrence wallet and you need these two interacts with the term blockchain and sign in the private keys and do the full transaction cycle flow. So yeah faking this UI interactions is really complex and the test Frameworks that we have right now. They don't support these plugins even when running headless browser. So one of the approaches that I'm gonna show you after is just mocking the web stream, but these is basically what is the flow. So the user goes interact with the web 3 the interacts with the meta mask or the teleport party provider and then finally metamask is able to send this transaction to the Italian blocking and add the block there and this transactions. They are signed by a private scheme. So UI Frameworks, they cannot do that at the moment as well. And one of the approaches this the using the web 3 Mark, so now while it is a good practice anyway, no not using the Rio study party inter integration because you shouldn't be you shouldn't be like depending on these. Because you don't have control of these 30 putty you don't have control of the plugin. So if it crashes or if there's a bug you might need your policy or entire development just because you cannot test your own application for and to End Cycle. So one idea is to Mark the web 3 and then just Do the same send in transactions and then simulating this part with the Italian blockchain? And then yeah with the web 3 more key you can solve the problem by signing the transactions with a private key automatically and then sending to the the evm and the terror blockchain. Another approach would be using this framework called the same press which is a wrapper from from Cypress, IO. And has metamask support. But yeah, the problem of these you are tied to use only metamask with this is the only territory provider plugging that supports at the moment. And you need to use Cypress IO as well because it's a wrapper from Cypress Oil, but actually you can choose between you know, locking the version of the metamask so you don't have an unexpected failures. Or you can just make sure that you know sing press can just run the tests. But before the updates the metamaski plugin just you have the latest one so you can decide what you want to do. Basically if you want to lock the version or if you want to update with the latest metamask before running your tests. Which you would be good to figure out, you know, if your application has any problems with the new version of metamask. Um and New issue you can if you use any of other instrument as tools that are in the market already. And the only problem is they don't have something like singpress. They don't have a framework just to that is is build on top of them apart from cyprusio. Just you do the integration with these study party provider, but you can use it mock strategy. So you can issue use for example task Offa. I really like as well. You can use the and then mock the web stream. Um, but of course they have down signs as well. So if you want to use, you know if you want to use some. Something different from mathemask. You can use it with the mock. But then if you go with a site a simple, press the only thing that you can use is is the metamask plugin. so now we are gonna just See the first demo, which is with the mock. So it's gonna be Cyprus and the mock of web 3. Um, let me just go to the other screen. Whoops. Sorry. this one yeah, these This Is On My Guitar Hub and it's just off for keep from another project but But you can see already. How that works. So it's a simple you just need to use yarn starch you start the localhost web page simple page and then you can use yarn Cypress Run to run the tests. But basically it's just these testing is sending the transaction is really fast so you can all see like properly but the first one is just connecting to matter mask. You can see oops. You can see the connect with the login and this is the simple they created so you can see here is expecting to have the address of the the wallet that you connected. Then you are signing the messages as well. And then you need to check here, you know the data response if he's exactly what you expect and if he's doing this. The right transactions and then in the end. Yeah, try to send a transaction. Which you sent should these wallet these address these amount and then you should have yeah in this case. It's okay. If you have accessories This Server Services cannot send transactions, which was expected in this case and then signing out as well, which you should be is really really simple this one, but you can at least see how the mock is done. and oops and the other and the other this is the address. So if you want to have a look. And the other demo is gonna be using the simplest to so you can see that we are using the same press and we are. really integrating with mathemask So this one is just burning. Cyprus and it's loading Cyprus and then it's gonna load this packs. And just run straight away. So this is the metamask plugging you can see that is starting and it's not mocking. So if you go and install mathemaski plugging you can see that is exactly like that. And also on the top you can see Chrome extension. So it is the real plugin. Then now was just setting up in the metamask with importing the account and now it is using the plugin to send. Yeah to accept the connection request and just connect to these account. And now we just creating the natural work as well. And yeah, basically, this is another demo with the same press is really straightforward as well. But it's it's well maintained. You can also check on the on the official theme press repo on guitar. They they have other examples there if I'm not wrong. But this one is really simple and is on my GitHub. GitHub repo as well meet her back. I'm sorry. And yeah, of course the trade-offs so we have the test speed that we need to take into account. So when you use the mock, of course is faster then using the 30 party plugging and waiting too low and so the natural work all the problems that you have when you are. When you are not mocking these 30 party provider. Then you have the dependency on 30 party app when you are doing the full real instrument class. So if something crashes if there is a bug you might need to just you know, stop or reward the version that you are using before the bug and you might need to pause or if you are really testing and you want to make sure that it's gonna work with the latest with the latest version. If there is a bug you might need to wait until these bugs fix it just to make sure that is okay. And also enter and with you know, the instrument as we've seen press is the real world test. So, you know that this is is really what the user is gonna do. They are not gonna mock. Of course. And then the other one is mock containers. So you need to worry about that. If you are mocking just you keep you know up to date if you want to make sure the latest is working with your app. Um, and then you have the test app in isolation as well. So when you do with the mock you don't care about these study party if it's working or not. Then you are making sure that your app is always like working fine. You don't need to pause. You don't need to stop your development. You don't need to worry about you know, the third party should be fixed or anything like that. It is a good practice anyway to do that to Mark. So one thing that you can do as a strategy is just to have a good balance between the unit tests the integration task so you can mock most of the tasks. And then having I don't know maybe 10% or even less of ancient us so you can use something for example the framework and automating these 10% or you can have some exploratory tests doing the full one twin or you can just have manual tests for that. It's really up to you your project the strategy that I use. What are your needs? But a good balance always make sure that okay. We cannot test into an with the latest version of the teddy party, but we know that we've or we we know integration is working fine. We have everything covered. So it's more it's more robust. It's more trustworthy and then and yeah, that's it. So thank you or if you want to connect me to me, you know in any of these social media Just for future do so our sin any questions or feedbacks. I'm hoping for these as well. It's always good to improve. So yeah, that's it. Thank you.

Rafaela Azevedo

React Summit

React Summit 2022

A Frontend Developer’s Guide to Web3

 Welcome everyone to my talk a front-end developers guide to web3 really excited to be here at react Summit talking a little bit about web 3 and giving you an introduction to it. Here's a high level agenda of what we're going to be going through today. We're gonna be talking about what's smart contracts are going over how to develop them. We're gonna talk about how to connect to the blockchain talk about things like wallets and RPC endpoints. We'll go over that in a bit. Don't worry. We'll look at like how to actually fetch data from the blockchain and some really dope tools that you can use to build with and dive into the web 3 Rabbit Hole as I have. So a little bit about me, my name is Rahat. I'm a developer Advocate at a company called polygon previously. I've been a front-end developer as well as a freelance solidity engineer overall. I'm like an indie hacker web 3 Enthusiast and these are just some places. You can find me Twitter LinkedIn GitHub. If you ever want to look at some code examples of some of the things that we talk about during this talk. And polygon which is the company that I work for we're specifically going to be talking about one of our products, which is a proof of stake blockchain one of our popular offers. This is like pretty much our most popular offering it is a carbon negative blockchain. We're striving to be completely climate positive uses about 99% less energy than ethereum or other blockchains and it's a great way to start diving into the web 3 space without having to worry as much about energy wasting and usage as that comes up with like a lot of the other blockchains that are out there. But going to the actual main Crux of our talk smart contracts. Smart contracts are essentially the code of the blockchain. It's just a file contains some code some instructions for what your app or your app, which is a decentralized application needs to do when it's deployed onto the blockchain. How do we write smart contracts? What do we need to know about them? The languages that smart contracts are generally written in include solidity rust Viper or go. I'm going to be talking mainly about evm chains during this talk evm means ethereum machine meaning everything that we talk about all of the code that we do kind of like review and go over are all competed compatible with the ethereum blockchain. Our blockchain polygon is also compatible with theorem. So anything you learn on that side of things is one-to-one compatible on polygon. Although solidity is generally the most popular use language. Another popular one is Viper. So definitely if you ever wanted to go into smart contract development. Those are some good languages to know. now Let's say you've written your smart contract. You've written some solidity code you want to actually get that out onto the blockchain the deployment Works in a couple of deployment takes like a few different steps. Right? First you need bite code bite code is essentially machine readable code that is compiled from solidity solidity is a very high level language meaning, you know, it has some it has the code but it needs to be like a really Compiled down to something that the ethereum virtual machine can read and that's what this bytecode is. Next thing you need to know is what gas is gas. Not like, you know what you would use at the pumps but gas fees Associated to blockchain developments include essentially a fee that is needed to that. You need to pay in order to transact with the blockchain. This fee is comprised of like a base sort of like a base fee that may get burnt. So certain amount of coins or tokens on that black chain might get burned during this transaction and then a certain amount of it is given to what are called miners or validators and these are folks who have nodes or computers that essentially keep track of the blockchain have copies of it and are validating transactions to be added to the overall blockchain. next you need a deployment script a deployment script can be taken from environments like hard hat and truffle both of which are tools for creating like environments for deploying testing and essentially creating your smart contracts on your local machine. Finally you need an ethereum node. So ethereum nodes is just basically computer that has copy of the ethereum blockchain on it think of the ethereum blockchain as this gigantic database and the node essentially. Houses a lot of all the information that is on that blockchain and you have you have everything on what's called like a distributed Network. So there's nodes and computers all over the world keeping track validating transactions and they together form the consensus of what the blockchain data is polygon works very similarly. In this case. We have you know, several nodes all across the world and rather than You know using folks like minors who like mind these transactions we have validators who validate it. Next there are services like Alchemy and inferrah, which can help you with actually accessing an ethereum node, not everyone can run their own ethereum node or polygon node on their own computers. These services are essentially providing you with endpoints or RPC or What's called the remote procedure call and points that allow you to interact with ethereum that allow you to interact with polygon as well. Finally, let's talk about interactions. So interactions usually happen with a wallet wallets are usually inside of your browser. So I'm going to show you right now A what's called a metamask wallet, which is an in-browser wallet have a little bit of Ethan here, but I can switch between different networks. I'm going to switch to the polygon test net just to Showcase like, you know, this is the polygon Network you can have access to different blockchains via this wallet. The wallets all interact using an RPC endpoint so they have their own kind of like built-in endpoint from services like inferior and Alchemy. But for now, let's go ahead and break down what some of these interactions are. So I showed you a little bit about wallets, which is that metamask wallet. I popped up here. And what wallets really do is like ask for user consent for actually accessing their wallet and connecting to the blockchain many of the different interactions that you need to do require Sometimes some type of transaction fee. Usually this is like some type of mutation that needs to be done on the blockchain or sometimes there's a signature required from you to prove your identity to prove that you're the one using your wallet. This is all done, you know through your through a wallet like metamask or through Hardware wallets, like the one you see here from Ledger. These are great for when users need to conduct transactions, like minting or buying an nft transferring tokens anything that requires like interaction between you and the blockchain or you and some other folks who are using web 3 applications. The other type of interaction is just like a read-only type of interaction. So RPC endpoints like we mentioned before these are endpoints given to us by a node provider. These are great for depths that only have read transactions like a block Explorer block explorers will give you Essentially a UI that acts as like a full Ledger for like looking through transactions for looking through the history of those transactions for looking through any failed transactions that you might have. So like when you're trying to like figure out what's going on what's you know, the debugging certain calls in your you know application you can look at like block explorers to see like, okay. So what happened during this call? Why? Why was it rejected? Why was Why didn't it go through? These are great for debugging. So let's look at some code and take a look at like how do we actually interact with the block blockchain wallet Edition on my screen. I have a JavaScript function called handle wallet connect. This would generally be attached to something like a button. So this is an async function. And what I'm doing here is taking the ethereum object out of the window. Now you might be like, whoa. We're hot. What do you mean aetherium object in the window, right? So the reason I'm able to pull out an ethereum Magic from the window is because I'm considering that this person might have a metamask wallet like I have set up right here. As long as you have a browser injected wallet like that that wallet will also inject the ethereum object into your window. And then from there just a couple of little bit of boilerplate of like accessing the account Associated to that wallet and then accessing the address and logging that out. If the ethereum object doesn't exist, we'll just alert that. Hey, there's no wallet detected. The person should have should go and like install metamask or something like that and you can provide like a better alert than I did. So here's a quick demo on how that works. So on this page, I have this connect wallet button. I hit it. And once that happens my metamask pops up I hit sign in and it displays my address on the page. This is essentially half of what you would use for something like sign in with ethereum, which I'll cover in just a little bit as well. Now I'm going to talk about another common connect wallet pattern. This is done quite a bit through a lot of decentralized applications where we take that, you know handle wallet connect function. I didn't bother rewriting it here and put it inside of a use effect and call it right away specifically like on mounting of the actual application. Please do not do this. If you ever dive into the web 3 space what this essentially does is like as soon as I land on the website the website will automatically request that I connect my wallet. This is sort of like the same kind of situation of like you're going to a website music starts playing or a video automatically starts playing nobody wants to actually have that happen right away. This is a bad security practice and is something that just leads to bad bad ux overall in your application because it removes the ability for the user to give consent. One of the main things we talked about with wallets is that this is the this is the Gateway for user to consent to using the blockchain to doing certain transactions. This removes that ability and some folks might say, you know, you can still cancel the transaction, but no you you've got to stop because if your wallet immed He pops up that you don't have that opportunity to actually go through the application and understand what's going on. So I mentioned this a little bit just a couple slides go going Beyond connect wallet and using something called sign in with ethereum. One of my favorite things that have come up sort of like out of the web 3 space is this sort of like true single sign-on experience where you can take a wallet Connect connected validate your address as we kind of like looked at before and then from there do something like connecting to a server as you would normally do for like authentication for actually showcase for you know, pulling someone in creating like a user profile for them on your applicant on your dap or application and the cool thing here is like that user profile can travel with them anywhere. You know, they don't need to create a new email or password every single time. They go to a new Like a new application. They don't need to trust their credentials to a service like, you know, sign in with Google or sign in with Facebook. Everything is actually specifically owned by them that user profile is owned by them through this wallet and the way that while it works is that like the wallet gives you access through a key value pair a public address and a private address. The public address is the one we displayed on the page and then there's a private address that only they have access to that actually allows them access to the blockchain and is what allows them to approve transactions of view. They're Holdings and just access the overall web 3 space. So we talked about the wallet side of things of doing interactions of like actual user interactions. But how do we interact with the blockchain RPC and point addition in this case? We may only want to do read-only transactions. Maybe we want to create our own block Explorer. Maybe we want to just display some data in the form of graphs dashboards, whatever it is. On here. I have this provider and this provider is something given to us from the ethers package, which is a popular JavaScript package. You can use in your front ends and All you really have to do is just like use this method and enter an RPC endpoint. These RPC endpoints are basically just like a URL and HTTP endpoint given to you like the services. I mentioned earlier from Alchemy and inferior. And this is like a blob of information that you can actually get from the RPC endpoint. So here what I'm doing is I'm getting the information about the latest block on the blockchain. What is what does that mean? What is the latest block? So blockchain data is broken up into these blocks. They all have some type of number associated to them time stamp different hash values and the this is what houses all of the data on this block. So on this specific block, there's several transactions. There's only one displaying here. This is a timestamp and just some information about like the minor who actually validated this as well as just like additional data like the gas that we use and this is sort of like the information you can use to build out some of those dashboards some of those some of that information. I'm going to give you a quick demo of something that I built using that blob of data. This is just like a list of like the last 10 blocks on the polygon blockchain including their block number their timestamp and the number of transactions on each of those blocks. You can D. You can dive a little bit deeper into that. Json data that's returned from some of these calls, but this is just like a very basic implementation of like what a block Explorer might start off as so cool. But how do we actually fetch data from Smart contracts? Right? Sure. Maybe there's like someone wrote some like developer smart contract developer wrote contract for us and that houses some information. How do we access that information? We need a map. So solidity code like I mentioned before it gets compiled down to bytecode. We need instructions on how to actually Traverse that bytecode. So what we need is an ABI or an application binary interface. This is usually exported out by a solidity developer passed on to like a front-end developer and this is just a Json object with instructions on like the different types of functions that are available on a smart contract what input some of those functions need and the types of outputs that they give to you. This is just going to allow you allow JavaScript to use certain libraries Traverse through the blockchain and get the proper information that it needs. So rather than doing an HTTP request. It's using this ABI along with a Function given to us from a package like ethers to actually interact with the blockchain itself. So, how does this work? First you would import dependencies. This is done in like assuming you're looking at a react application. So you're going to import like ethers from the ethers library and an ABI that some smart contract developer may have can given you this is an example from a contract that I wrote where it showcases like a little Pokemon battle between two Pokemon. The next thing is you want the address of the deployed contract. So every single deployed contract similar to your wallet has its own address. So we need to get the address to see where on the blockchain that contract lives. We Supply the Abi. The car the address of the contract as well as the ethereum object into this contract method given to us from ethers. Once we Supply it all that we then get access to the actual functions listed out inside of the ABI file. One of those functions here is this attack functionality where our Pokemon is going to attack each other and then certain amounts of like HP or hit points are going to be taken away. So let's take a look at that in action. So what's going on here is I decided okay, I need to attack this Pokemon. I hit use flamethrower by metamask is going to pop up. I'm going to pay a small amount of gas to make sure this transaction goes through on the blockchain and once it's completed all of the hit points of the two Pokemon will go down and all this is tracked on the blockchain itself. So the main things to really understand here front end development in web 3 Remains the Same the UI is still built using all of the same practices. You don't as a front-end developer. You don't need to know the Deep sort of like intricacies of how to build your own smart contracts. You just need to know how to interact with them. Like we talked about you go from a shift and mindset from doing HTTP requests to using ABI code and libraries to call this smart contract. And the other main thing to remember is that mutations cost money read transactions are free mutations will always cost money. Some web 3 front end development tools that you can definitely dive into and learn more about are the ethers and web3 Library as well as the wag me library wagmie library provides a lot of react hooks for easily hooking into and transacting with the blockchain web through UI is an awesome library that gives you a bunch of react components that you can use as well and different block explorers, like polygon scan. If you're interacting with a smart contract on the polygon Network or either scan if you're interacting with a smart contract on the ethereum network. These are all tools that I'm going to be touching on as well during my workshop here at react Summit. So if you want to learn more about that, we'll be going into greater detail there. And overall if you feel like you want to learn more you want to check out how to build on the blockchain how to build on polygon. We do have a lot of resources on Academy dot polygon technology. There's a lot of like gamified approaches there of like learning and building your own daps. I also wanted to quickly call out polygon Village. If you decide to let go in and learn about web 3 learn about how to develop in it and start developing your own projects. We do give grants which are no strings attached grants for actually building out your projects. And eventually if you wanted to go into the web 3 ecosystem, we do have an ecosystem job board for that as well. So this is not just for polygon jobs, but for overall folks in the polygon ecosystem. So just to wrap up. I'm a hot and developer Advocate at polygon. These are just a few places. You can find me really awesome to have y'all dive into the to dive to dive into a little bit of web 3 with me. And really excited to see y'all possibly in my workshop as well. Thank you.

Rahat Chowdhury

JS Nation

JSNation 2022

Build Blockchain dApps using JavaScript

 Hello, my name is Russ festino and welcome to build blockchain depths using JavaScript. I'm a developer advocate for algorand. It's a blockchain devs need to know, you know, first of all what is adapt? And how can I build one? As well as what kind of solutions can I build I know when I first started doing blockchain development. That was a question. That was first and foremost on my mind. What kind of solutions can I build? And what programming languages can I use to build apps? How do I verify smart contracts in other words audits? So the agenda for today, we're gonna cover algorand blockchain layer one. Do a little bit on setup meet your development environment and then creating a simple tap which by the way stands for decentralized applications. And cover verification as well as some UI controls from pipeline. For those that are brand new to blockchain what blockchain is it's immutable decentralized Ledger consist of blocks which are periods of time. And then the transactions that are associated during that time interval. Now of course transactions are between sender and a receiver. So those would be your accounts. And each account has the association of assets to it as well as applications now assets can be your fungible or nonfangible tokens in applications are smart contracts. So with El Gran we use a Pure proof of stake protocol. The pure-prophistic protocol is extremely quick. And it really scales. The last Peg that 1400 transactions per second and block times created in under five seconds. But not only that there's infrastructure longevity. The entire project is open sourced and a lot of technical flexibility with all sorts of sdks and tools being created and available for developers to build blockchain Solutions. Transaction certainty there is no forking in the algorand blockchain very extensible platform as well as extremely energy efficient. It is actually a carbon negative blockchain and cost efficiency cost of a transaction is less than a 20th of a penny also provides to security because it is a read-only right once Ledger. That is distributed across the globe Defy is by far and away the biggest vertical Market or type of solution that you can build with our am blockchain stable coins. So what stable coins are still crypto, but they are tied to a US economy. So as the US dollar goes up and down so we'll the coin so fluctuates the same as the the dollar does so over three billion in circulation there you can see for USD see and we have decentralized exchanges or dexes things like tiny man. Algodex algofi what's happened here is that up until now you've had to go to a bank to use Financial tools. For example, say you want to create a stock portfolio. Well now the same tools are available to anybody that wants to use them and you can go to sites like these and apps like these to be able to create liquidity pooling and staking in a lot of other things the Italian Society of authors and Publishers another great implementation of blockchain. They're using nfts to identify copyrights. So nfts are unique and you can see here. They put over four million nfts on the algraham blockchain to close to a hundred thousand craters really this is a the future of the industry for doing copyright. Just think about it. There's no Global boundaries these this is and it's accessible to anybody that that wants to have access to it and all the use cases, you know list goes on and on here right a lot of different verticals. Mostly every vertical Market that really has a use case for a blockchain to the next session here on the heart and soul of your solution, which is layer one. El Grande accounts ASAS or El Grant standard assets Atomic transactions elgrand smart contracts as well as reporting with indexer. So first you have a standard account which is represented an individual. Let's say for example, and then he also have a multi-cig account which could be representative maybe of a board of directors for is an example there. Now with the multi-seek account. You do have the capability finding a threshold in other words. How many votes do you need out of the group here to pass the transaction or to sign it and then a logic say what you see on the right or logic account is a smart contract so that either returns true or false and if they returns true it'll go ahead and sign the transaction of returns false. It will not now. We'll talk about fungible tokens and what these are exactly. So ASAS are algorand standard assets can be either fungible or non-fungeable tokens. So we see here is a list of examples of fungible tokens. So things like stable coins loyalty points system credit, right? Each unit of the cryptocurrency is worth exactly the same amount there could be several of those. Then on the nft side of things with nonfigurable tokens. These could be used for in-game items when you're playing games. You got real estate identity certification Collectibles is a big item and that's really the best way. I like to think about nft is the fact that they are like a collectible. They're unique. They're one of the kind so some folks. I know collect baseball cards, for example or coins. Every one of these is in a different condition each. One of these is a different Rarity each one of these has a different trait to it. So these are all different a bunch of different metadata that can be used to differentiate these so these are each very very unique. So let's take a look at creating one of these I'm gonna bring up elbow Dio this is a visual tool. So it's going to use one of our three wallets that are available here. We've got Elvis hanger, which is a plug-in to Chrome. My eligible wallet is a web-based wallet and then the pair wallet is a wallet that's based in Android or IRS. We'll go ahead and use the algo signer here for the demo. We'll go ahead sign into our wallet. And I'm going to pick an account that's in our wallet to go ahead and use to create these assets. So we're going to do now is we're going to create an ASA. So we have ability to create a name test. Let's give it a new name of pizza after the very first transaction in Bitcoin was for pizza. Now if I make a supply of one that would be an nft. So what I'm going to do is actually create a fungible token. Let's create a hundred thousand of these. You also have the ability to put a decimal point in there. Also, we have the ability to put a URL that might be associated with this more information and then also metahatch. So next up. Let's talk about algorand Atomic transfers. So this is where all must succeed or all will fail. You have a person a for example wants to send 50 Algos to person being and then person being returned to send a concert ticket to person a Now when we used to do this through things like Craigslist or something like that, it was always a crap shoot whether this actually was going to work or not, you know, sometimes you'd pay the money, but you wouldn't get the ticket here this guarantees. The exchange of goods is what Atomic transfers actually do. And so this really does facilitate and and really is the secret sauce for many solutions that are built with decentralized applications very easy to do and it's secure. So some examples of this would be simplified expedited settlements circular trades group payments instant settlement for complex multi-party. Yes it transaction just sort of payments. And again, these could be utilized with all the other layer One features of el Grant standard assets and smart contracts. Speaking of which smart contract. So this is the transaction execution approval language is the Assembly Language that's used short name for that is teal. And it's assembly because it's very lean and mean it's got a perform on the blockchain and be very very scalable. So there's nothing leaner than assembly to do that. And then you have python enable compiler which you can use Python to generate teal and also JavaScript is is used in a product called re and there's a new Visual Studio extension as well and and using C sharp to create teal. So these are all basically teal generators as each one of those products. I just listed and more on the way smart signatures basically approve spending transactions and then smart contracts themselves provide the transactions and facilitate both Global and local storage local storage be at the account level Global Storage would be at the blockchain level. These are all combinable with other Grand Technologies, including Atomic transfers and Rain assets. So wrap up that architecture. Basically you have a UI for an end. Perhaps. Maybe there's some smart. You're going on there using the algorand sdks or rest apis and then you got three different transaction types shown here. You have a payment transaction would be 13. Your accounts asset transactions would be revolving around nfts and and and fungible tokens. And then application calls would be your smart contracts and those are facilitate local state and Global State out to the blockchain. So the index is basically just a postgresql database which offloads the algo D process and then it's indexed and searchable and a lot quicker and responsive. So it's a really nice reporting tool. Okay, next up. We're gonna cover set up development environment and what's involved there. Well, first thing you want to do is go out to the developer portal developer.io Grande, Oregon an award-winning developer portal in the black chain space. And then also El Grande Discord you want to sign up there in a really great for support and getting your questions answered. And then also there's a Discord server as well for reach and I've got both of those on here as well. So first thing I want to do is get the sandbox loaded up very simple just create a Docker instance and then clone the GitHub repo for the sandbox and then also default so private Network which includes indexer. We're just doing a Sandbox up. It also supports other networks that beta net testnet mainnet. These are all supported with the use of the sandbox. So mentioned some sdks. Those are the ones that are highlighting red are supported by algorand the ones down below it Russ PHP Dart C Sharps with and some more are supported by the community the ecosystem a lot of great tools on the right including algodest guy. Oh you saw that as well as Grand Studio aldea is a really great tool as well for doing very quick development with minimal amount of coding. So with pytale basically, this is what you have is the python and then you compile it and it Returns the teal and then she book teal looks like they're on the right. Great pytale course to go out to YouTube. There's a nice playlist there. Excellent work there by the instructor. So your first transaction. Let's go ahead and take a look at this in JavaScript. We're gonna bring up this page here on the developer portal. You see scroll down it gives you the step by step on getting started. This is where you install the sandbox like we talked about. This is where he installed the SDK for for JavaScript. You can see the information there. There's videos and each one of these there's also a try me live demo or right here that you can click on and just hit the Run button. You'll see it all execute and then you start getting into the code and creating accounts and instantiating your clients that brings us to reach. What is reach. Well, it's a programming language to high level language. It's also a compiler and it does deploy your adapt to blockchain. So the focus is on the business logic so reach programmers don't need to think about the details of things like contract storage protocol diagram State validation Network details. So you have the back end. Let's start there over there on the right you can see the this is responsible for generating and deploying the solution to the blockchain also to X with the smart contracts automatically. So it's a solution implementation at defines the interfaces for the front end that's going to be talking to and you define things like participants and apis as well as verification and commitment. On the front end now the front end can be done. The backend is like JavaScript like code. All right, and the front end this could be done in Python go or JavaScript or C sharp, and basically what you have here is a user interface that is provided and it does things like create accounts and a lot of traditional Al Green SDK methods. And you can also put blockchain specific code in there. So if you have something this slightly different between blockchains, you can tweak that a little bit on the front end as well in compile run it and then deploy it out to the blockchain. All right. It's pretty easy to install you just bring up Docker download or reach executable and you need the if you run it running this on Windows, you would need the windows substances for Linux. And then also this is the the code you right here you go ahead and create your directory for the project and then you curl the reach executable down giving it executable rights a simple dap walk through So this is the backend file we're looking at here. So either player Bob or Ellis gets the fingers. They played and gets a guess and sees who won the winning game and you can see that up at the top is really that's just the interface of the methods that are actually defined on the front end. And then also you have the participants that are involved, right? So the plane get fingers thrown and total guess and Publishing publish them and then commit means you're done you're committing that out to the blockchain. So the back end now also continues with rules and outcomes. So this is the logic to a game. I've got a game. I'm going to show you here Mora where you're throwing fingers and and a guess between the two opponents. And if either one of them guessed it correctly then they went that particular match. So by doing this everyone agrees on the rules for the outcome and everyone sees the outcome of the engine that we have now on the front end. This is a you know, you take the common number of 10 for example into whatever native platform support. So it takes like 10 Algos for example to microagos and then you have the ability to create a new test account in the dev environment with that starting balance. And then you see down below. This is where Alice's deploying the contract and then Bob's going to attach to the contract in other words opt-in and then we go ahead and run the game. And then also these are the interact methods so we saw the interfaces to these on the back end. And now this is the actual code in the JavaScript in the front end that this provides so you can see we're just using some random functions here next. Let's talk about verification. This is a very very important topic and this what it does is it protects against blockchain attacks and it guarantee tease things like the contract balances zero because think about you're creating accounts on the Fly potentially in these contracts and they're you're funding them and If it's created on the Fly it's in the contract only that contract knows what the private key is, right? No one else would know that and if the contract ends executing and there's funds still in that account and haven't been exhausted. Guess what you're gonna lose those funds. There's no way of getting at them because the contract gets done running goes away and the the you know, that's a problem. That's an issue and there have been, you know, some big money's lost in the past because of this particular problem. So what verification does and an audits do prevent locked away tokens right by the contract and hence become accessible? So with as far as auditing goes the non-reach solution is in auditor proves that the program with their their own analysis and and they're doing the verification of a version of the program. If you got a minor change, then the audit is useless for a prior version. And I have to do everything from scratch with the reach the compiler verifies and then the auditor verisite verifies that you provided to the reach compiler enough assertions and code changes. Well, the reach auditor just needs to check the right assertions were included on the code changes. So to see here lsutes four fingers and guesses a total five. This is just demonstration of doing some printing in the back end and then also you see Bob shoots zero fingers and guesses four. So the actual Throne is four and Bob wins the The Wager and so you see his account value increases what happens if I change this to just going one times the wager. So right now we have two times because each player is providing a wage your amount. So two times a wager is the total that's in the pot. So if we try to run this it's going to realize that hey, you know, this doesn't work because you're gonna leave money on the table. And now you can see some violations down below. So you can see here that message zero balance at application exit that assert failed. It's not a zero balance. There's some stuff left in there. I have a solution. I wrote up on the developer portal. Here's a link that really goes into detail step by step on on building that particular solution that we just looked at. So that brings us to the front end right pipeline UI. It's a vanilla JS SDK in react component library and you can see here. There are controls that are available that you just copy Snippets of code and HTML Into Your solution you can see on the right is an example showing an account but not only the account number but also QR also there are Grant specific rack components as well and we got Twitter spaces, but I'll granddev Twitter and follow our algo devs Twitter. So in summary, we took a look at Al Green blockchain at a high level as well as some use cases what you can build a Solutions with and we've looked at all the layer One features. Then we took a look at what was involved in setting up an environment. We took a look at reach in building a simple Gap and this is a fascinating product. It does build in things like verification as the as part as a good benefit. But again, you're you're writing in a JavaScript like code get back in the front end can be I mean JavaScript as well. And the verification process is very very important there and building solid decentralized applications. And finally we looked at the pipeline UI controls. Thank you very much.

Russell Fustino

Web3.js - Past, Present & Future

 Hi, everyone is another here and today we are gonna discuss the web 3GS one of the most famous and widely used library in the ethereum community. So we will be discussing some past aspects of the library and some future aspects as well as some present Milestones that we have achieved currently. So let's get started. So first of all, we're going to explore the past about the library. Most of you had been using this Library a lot, but maybe not aware of how this library was actually started. So this web 3GS library was started in 2014 by a solo contributor Jeffrey vehicle and in 2016, it was moved to another solo maintainer Samuel further and from 2018, ethereum GS from the ethereum foundation were maintaining it and since two years our company chain safe has been responsible to maintain this Library. and if you look on the facts that this library has been maintained for over eight years. It has over 100 contributors overall and have 17,000 more than 1700 pull requests. And so for 172 versions were released and of the which 90 were the previous release version that means this Library had very thorough investigation and the debugging and testing from the community during the private release versions. Ninety release version is a large number. And this library has 600,000 weekly downloads as well and it's all because of the community who is using interesting this Library. And there are some fun facts about the library passed so version 1 of the library web 3GS has been living in beta for two years and people helping using V1 beta in the production environment for many years because these three one was in extensive testing and thorough debugging process. And we started to have a V2 rewrite in past and it was a fail and abundant rewrite attempt because of some aspects. I will discuss in further slides. And we started V3 rewrite with some extensor features and which never lasted a lot. And since then V1 is the only version which whole Community has been using so far. This is quite an interesting aspect as well and considering that. Like two rewrite attempts or two version attempts have been failed so far, but it doesn't mean that the library V1 version has been unstable. So we won it's been maintained and support it so far and have been doing it. And if you look at the expected we even live for the two years in beta. I think this is the most longest time. After another project Express JS version 5 doing in the beta. It was almost more than two years. And there were some challenges. We are facing in the challenges. We were facing in the web3.js version 1 most of you can understand it because you already may have already reported some of the issues or have been also encountered or facing those issues. It was very good space. The code base was being maintained by over 100 contributors. I explained earlier. So the code base was not using some standard process or standard patterns the modules inside the code were very tightly covered. There were a lot of technical challenges to maintain this code and there was a lot of difficulties to introduce a new features particularly in the library. and most of the you guys already been using the typescript hopefully so there are a lot of decoupled types decoupled type sport in the web 3 version 1 the 3Gs version one and because of that. There were a lot of typescript issues been reported to the women by the community. And if I look on the laws, I can see around like 60 over 60 issues been reported of the mismatching or in accord types, which was one of the biggest challenge for us and from the community perspective the build size became around the portal neck and for the tab development because this library was bundled a huge single package file and package file has been bundled in every day. And this was causing a lot of problem during the day development by a lot of community as well and on a larger Spectrum JS community. And the tool chain has been Advanced a lot. A lot of new Frameworks new patterns and new tools have been introduced in the community in the ecosystem, but web3js could not get Way Forward because of those challenges I discussed earlier. So are we gonna stick with the version one or are we gonna do something about it? Despite the two attempts or failed attempts? We are still hopeful that we are going to present the current improvements in the library. And with that said this is the new era for the web 3GS the version 4 and this is Northern speculation. It's been under development for over a year now and we are almost ready to release. Hopefully it's been released this month and but you can already explore from directly from the GitHub. So version 4 is gonna be huge huge huge milestone for the 3Gs. Lifespan and it's gonna address a lot of stuff that will be discussing in the community and all those people been addressing those things. So version of four will come with the native typescript Sport and it will have a reduce wheel size a couple we are decoupled a lot of code and a complexity has been reduced since we are doing this rewrite completely from the scratch. So the code readability has been improved a lot. And we try to make it extensible so that with the future we can add more features very easily and even the community can extend the library for their own news and we focus on the test coverage for the version 4 and hopefully once right now we are working on writing the system test for the library and within a month when we will release the first Alpha for the V4. It will be having a lot higher test coverage compared to the version one and compared to any other competitive library in the ecosystems. So the question is does all these cores that we Define to rewrite for the version 4 are these good enough or we achieved it or not? Yes, we have achieved all these goals. And the most important thing is that we achieved all these goals with the V1. Parity API. So you don't need to be worried about that. Your projects are gonna break their would be slight changes that we will be documenting and sharing with the community in the change log or the migration guide, but those changes will not be a lot overall API over the version one Remains the Same we explicitly decided this architecture change so that or this pattern so that a lot of community does not break their projects and they can easily migrate to the version for which is more recent and The question is like does it just rewrite of the V1 with the same API or does include some new features as well or not? Yes it is. It contains a lot of new features. It's not just the rewrite rewrite was the first objective but during the rewrite we focused on creating more features within the library so that we can I'll be a future safe and we can extend the library very easily in the future and some of the features which I'm going to present here, which is very unique for the version one version 4 for the web 3GS library is unique in the ethereum ecosystem. No other package or the utility as of now, which I remember so far may have introduced such features and hopefully you guys will like them. So the first of thing the most important feature within our rewrite is this new introduction of the new validator because data is so important for any day particularly and data validation has been extensive job for the maintainers of the different apps and we decided to create a brand new layer of the declarative variation for the community and we use this validator within our Library as well and it is also available for you to use in your depth. So what is the ticket generative validator? So most of you know that Jason schema or Jason data is kind of a defective or data format for the GS Community. Jason schema is also defective data standard for validation and communities already adopted. So we use Both of these schemes are the Json data and adjacent schema and merge them together for the etherium community and you don't need to have no if else anymore and all of the validation that you're going to do using the Json schema will be directly coupled with the ethereum types. So you don't need to remember the ethereum native types or compared to the JavaScript native types. It will work seamlessly and this validator is also compatible with the ethereum ABS schema. So if you have such an API, it will also validate the data based on the API as well and let's jump to some example. So here you can see some example. So we have some data and which contains some addresses in an array and some balance and if I go with the imperative validation, which we had been doing in previous Library versions, you can see that we have Some Loops going on and then we are validating by using function calls and then throwing some errors any same for the balance field that we have. We are particularly validating by using some function call. But if we go with a declarative approach, you can see that we have schema defined for the data and this schema is gonna present the whole and not me of the data and if you notice that the data that we are going to present is very particular for the Italian. So we have an address array we have you into 50 60 days. And we can validate this data based on the schema and there are different formats of the schema and hope you can. explore further so there is another feature that we introduce in version 4 we write and this is going to change the way you look into your data. So the question is that every depth that you do well is not the same. So the need for every deaf is also different someone developing an app or using a library where he needs numbers in the beginning. Someone lost numbers number or someone more just numbers to be a number of things similarly for the buyers. So there can be different forms of the same data that you can use but previous version was very strict and very restrictive to the one data format which will not counter which was counterintuitive for the different depths which were using different data formats. So we try to cover this as well and we are creating a dynamic data format, which is quite easy. All of the ethereum web pages Library interfaces are gonna return I'm gonna support this custom data formatting and let's say we have this get balance and by default just get balanced return you are balanced in the hex string format. But if you want that the balance function should return the wellness into different formers. You can Define your own data format specifying the format for the numbers and specifying the format for the price and passing these formats to the every function call is the last parameter and you will get in the data in that particular format that you define and you can use this formatting logic in your own project as well. Our library between extensively using it. So one more important feature, maybe everyone should be relying it and I think this is one of the unique feature which a web 3.js version 4 is gonna introduce is a types of water contracts for but without any transpiling so you don't need to transfer anything you can all you need is your API declaration in the typescript project. So there is a no need for the transpiling of the apis or creating or doing some command line execution of any other third party tools. You just need to copy your Avi declare them into the typescript project and you will be ready to have a complete type sales contract instance. Let's say we have this API and all you need is to have this API declared and the trick is here that you have to declare them as a cost. So the types if there's not infer the most generic type rather have a strong time for each declaration. And once you have declared this API as a cost and you can create your contract, it's just and this contract instance will be completely type safe and there is no transpiling required and if you ever change the ABA or update your ABA your time automatically select those change and detect the validations on the compile time. unique features and I would love that which we will be sharing some feedback on it and There is another feature that we're going to introduce is easy extensibility for our API. So the web 3 modules have introduced a different or consistent API to support all module. So if when I'm referring to the modus you may be aware that we have different menus like contracts ethereum SSH ABI ens. So these are different modules. So we introduce a consistent API for all of the videos so that you don't have a different. Compatibility issues using them and you can also create your own modules if you want and the feature is very simple and like straightforward to introduce you just need to we have consistent object called web3 context and all you need is to declare your component or the module which is extended from the where three context and then you have a library instance web 3 you just call them I use and you will get an instance of the component which will have all of the main component of the library link. For example of Provider will be linked request manager or subscription manager and a lot more will link to your company and that will be so you can use your component easily with the same consistent API, which we had been using in the ethereum or contract or AVI or even as packages. So this is all from the version 4. So the question is like this is all the features that we're going to introduce. I think not there are a lot of future like a lot of feature improvements a lot of refactoring a lot of things going on. In the version 4 and I will left all those to you that you can explore in the version 4 and the version 4 will is in the alpha hopefully this month and but you don't need to wait it you can go to the GitHub and check out for DOT X branch and it will be all up. For you to install directly from the GitHub and use it. And yeah. So what is the future so after the V4 Alpha launch what we are going to do with the web 3GS Library what future aspects we have. So our main focus is to mature the V4 version 4 and release a production ready version this year with that set. We are not gonna deprecate the V1 right away. We will still be sporting V1 what we will encourage everyone in the community to use version 4 and share their feedback with us and in the future we are gonna introduce more flexible modularization in the library and we will be improving the tree shaking to minimize the DAP will size. So let's say your tab is gonna use one function from the library. So you don't need to rely on the whole Library package. You can just be using that one function and we will be improving tree checking to achieve this particular respect. And for the developer, I guess the login is most life-saving thing. So in the future after maturing the V4 Alpha We're going to introduce the comprehensive logging sport to the library and we will also support out of the paths integration for the different fronted tools, like react angular or vue.js. So this Library will be supporting all of these front-end tools out of the box. And once that is being done, then we will start supporting other ethereum projects as well. So we have three Gs will not just be the native ethereum client. It would also be available to connect to the other ethereum projects as well and use the same library that you have been using for years and lovely. Yeah, that's all for the future and If you have any question, I encourage everyone to join our community on the GitHub on the Discord. The QR codes are here you can scan them and login if you are having particular question, you can also reach to me on the Twitter and I will happy to answer those questions. I look forward to everyone to test version 4, which is on the GitHub and which will be Alpha released in this during this month, and I would like to get more feedback from you guys on the Discord and on the other community channels, and I'm happy to answer any questions after this presentation and hope to see you guys in person. Yeah. Thank you.

Nazar Hussain

Reacting to Web3

 Uh, 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 a 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 Tanners new tan stack. 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 to 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 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 where 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 initialized function like if you ever use stripe or off zero or anything like that, you just pick your blockchain you pick the network and any modules of the that you want to add in this case. We're using the ER 721 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 used 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 used 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 to centralize 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 buyers are more says 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 web 3 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 micro transactions, 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 any time I have a contracts where you just want to guarantee that both sides are sort of being honest. So a mediator type contract pattern is 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 latter-based engine, you know based on your data and you didn't have to build that the community can help, you know 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 off the 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, you know, booster open source with that. We have some documentation here you can visit and go to our Discord and thank you Amsterdam.

#web3