Solana Development With Anchor: A Complete Introduction

[00:00:12]hey hey what is up everyone we should now be live okay can everyone hear me okay hey hey how's it going welcome welcome we'll give some people a couple minutes to join the stream and then we'll get started [Music] how's everyone doing today let's get some gms in the chat awesome i'm excited to give this talk hope everyone's having a a great and productive changing hackathon really excited to see what everyone builds all right we'll give it one more minute uh everyone and then we're going to get started yes it is a great day to learn chaining [Music] yeah we're going to be going for about an hour today do we start directly from rust um there is going to be some rust involved here today however if you're not too familiar with it um don't fret too much um you'll still be able to follow along it's it's just a matter of the syntax but i'll be kind of explaining everything as best i can cool all right i think we might get started welcome everyone i hope everyone's having an amazing 2022 spring hackathon today we are going to be talking about all things anchor solana and using chain ink on solana right so i'm just going to share my screen here hopefully you guys can see that i might switch my view there we go gm so my name is harry pepper chris you and i'm a developer advocate for changing clubs and today like i said we're going to be talking about building on solana how to use uh anchor on solana how to use chain ink on solana so first we're going to go through just a quick introduction of what solana is and the architecture and programming model because it's quite different from other chains such as ethereum then we're going to give you an introduction to what anchor is and how it increases your productivity and then we're going to just do a quick demo workshop using anchor to create just a simple program and deploy it and get it working and then we're going to do another demo um with anchor and solana that uses chaining price feeds in your solana smart contract and then we'll wrap things up by talking about where you can learn more so let's go intro to solana so solana is a open source uh public blockchain and um the unit of account is a soul or a fraction of a soul is a lan port right so it's about 1500 nodes and there's a number of um real enhancements under the hood to kind of um achieve the the higher tps and bandwidth that it has right so if you're interested in that kind of real low level stuff um i recommend checking out this article that i'll paste in the chat here now we'll move on but celina has multiple clusters so they call a networker cluster right so their mainnet is called mainnet beta um they have a devnet uh which is like a a test network for developers they have a test net which is a another non mainnet network that's mainly for infrastructure type things and deployments and testing things like that and you can run a local cluster or a local solano instance on your local machine which you'll be doing today as well right so um celine uses a byzantine fault tolerant proof-of-stake consensus mechanism and this thing called proof of history to maintain its state now the biggest thing i want to talk about before we go into anything else with solana is the programming account model right so in the case of ethereum and other chains the smart contract also holds the state it has the logic which is the code that says do this do that but then it also has the state that says um that stores all the variables the arrays and all those types of things in that same place on solano it's different right a program is um essentially just an unchained smart contract that is just code right um it doesn't store anything it just gets executed right um and it has a program id which is basically the address or public key address that the smart contract is deployed to just like ethereum however there is no state stored in that program right so the way solana works is data for programs is actually stored in these things called accounts right and an account is basically just like a buffer but you can kind of think of it as like a file in an operating system right um and so it just has a bunch of data just like a file and has a bunch of metadata as well that says you know who can access the data in here um and it's held in validated memory right so the biggest difference to know with solana is you have programs which is just the smart contract code and then you have accounts that store the actual data for smart contracts so um in an erc 20 example or a token example in a theory we have one contract that stores the token details as well as the um the uh balances of each person that holds the token all in that same contract in salon you'd have a deploy program which is like a token program that has the token information um or it has all the functions to like send tokens min tokens et cetera and then you have multiple accounts for each person that holds the token right because once again you do not have um the logic stored together with the state in solana so here's basically what an account looks like on solana you've got a public key which is like a just the identifier for the account you've got a bunch of metadata that says um is a signer is it writable um who owns this account um is it an executable is it a smart contract this account or not because smart contracts are also accounts weekly enough um and most importantly it's got a data section where it stores a buy array of data so that's how data is stored and it's got lan ports which says how much um solana is in that account right and we'll get into that um very soon so in terms of how you interact with blockchain to call smart contract programs and things like that but part of me um you basically have to generate what are called uh instructions right so you can think of an instruction as like a function call right an instruction basically has three parts to it has a program id what program you're interacting with um it's got like an array of accounts that you send it to say here are all the accounts that i want you to interact with um with this program id and it's got this um a buy array of instruction data which is like input parameters right so if you have a function that takes in the price for ethereum or something you need to send that in any instruction data section right so that's kind of the three things that an instruction is comprised of and then a transaction is basically just a list of instructions right so you can have first do this function call then do this then do this etc so um here's just a small example here where you have instruction one interacts with you know this program id here so we want to call this program under here we want to um pass in these two accounts to basically have data modified or stored um and these are our input parameters for interacting with this program here and then similarly for instruction two it's the same thing but slightly different uh data or slightly different same program id different accounts different instruction data and then we bundle those up into a transaction that contains both of them right um so basically this is very important that you understand this if you're going to be playing around and building on salon because this underpins the whole programming model right you have an on-chain program that's just code no logical state um and you build up these instructions off-chain that you use to interact with the on-chain programs and you submit these instructions via a json rpc api to to the solano um cluster and and then basically they get executed right and you also pass in all the accounts to the program that you want to have data um modified for right and any instruction data you pass it in the instruction data by array so very different you can't just call a function and pass in a string or an input parameter and then it's just everything's in that function um once again it's very different you say you have a program id which is just the logic the accounts get passed in so that program id knows which uh where to basically modify data um and then it takes in input parameters in the form of that instruction data by array so once again the instruction data is just a buy array of an arbitrary size that's used for sending input data to on-chain programs right so there's just an example of some instruction data i think it's like a string of like a glass tube or something like that um so let's talk about the flow of uh developing and interacting with programs just quickly again so you compile the programs you can build solana programs in rust clc plus plus you compile them they get deployed in as bytecode 2 solana and then to interact with them you have an adjacent rpc api that's exposed and then you build your clients which could be a front-end or web app or whatever and then they can submit via that json rpc api um to to basically call programs on the solana network um yeah just to reiterate the um the the program itself is stateless it doesn't store anything so when we call programs we need to pass in accounts to what to say here use this account for doing um the first thing that you're going to do with accounts then this account for the second and and so on so let's just talk quickly about rent now um so solana's similar to a theorem and other chains where um you basically validators get paid transaction fees and things like that um however because we have these things called accounts that store data um we also have this thing called rent because validators need to get paid to store this data as well right so basically storage room basically covers the cost of storing data in accounts over time and there's two methods that are used for this with this one called set and forget and there's one called paper buy it so set and forget is basically where if you have two years worth of sold in the account um you never have to pay rent again so you just have to prepay like a large amount otherwise if you don't have two years worth you can pay per bite and in terms of how much is two years worth it depends on how much how big is the account how much data is in there and there's also a cell amount per kilobyte which uh is set somewhere um i'll grab it from the solana docks and paste it when we get to our first exercise generally most people go with option one they just put two years worth of rent in an account and then that way they just don't ever have to pay rent again however you have to be careful with that because if you add more data to your account over time um you need to make sure that two years worth is still true because the more the bigger the account is um the more that two years worth of rent is going to be so you need to be careful about that too seeing a couple questions in the chat companies select versions of solidity in solana um yeah so you can't program with solidity in solana in solana you can only use uh with native celina anyway you can only use rust c or c plus plus there are some projects that are dealing with trying to get evm compatibility going with solana however i haven't played around with them yet um and yet and arsenal programs are mutable like ethereum uh great question um just to reiterate from earlier um the solana programs do not store any data they're just the logic right so in terms of the smart contract getting deployed and the logic yes it's immutable that can never be changed but there's no data in in that smart contract right it's just the logic all right let's move on um so just you know a quick recap on instructions uh that we send to the solana network you have a program id a list of accounts and data instruction data that the client sends through as an instruction right um however if you need to send some input parameter to a celina program you need to let's say it's a string you can't just send it as a string like you do in ethereum um you need to basically serialize it into a buy array because once again the um instruction data that we send is in by array form so if you need to send the string harry as an input parameter program you basically need to turn it into a byte array right so that's what serialization is converting an object in memory into a stream of bias and then when that buy array gets accepted onto the in the solana program um via via the program to basically do stuff with it you don't need to deserialize it you need to turn it back into a string right so it's a bit finicky salama in raw salan anyway where you need to basically serialize and deserialize this instruction data um if you want to use it on chain however when we get to anchor soon you'll see that um you can that kind of stuff kind of gets attracted away so um just a quick visualization here so examples of serializing and deserializing um you may want to you'll be serializing instruction data sent from a client via the json rpc api onto a celina program where it's then deserialized and turned back into its original form or it could even be the other way around you could be serializing account info data that's going to be stored in the accounts via the program as well um but enough about that let's let's start talking about anchor so in the web 2 world you have things like rails uh right um and in ethereum world you have things like hard hat truffle and web3 js and basically these are all tools designed to increase your productivity right and they do that by abstracting away some of the more low-level details of the underlying platform so in solana we have this thing called anchor that basically does that for you right so anchor is a framework built by project serum um which is a decentralized exchange exchange and d5 ecosystem built on solana um and anchor basically is a framework for quickly building secure solana programs right and it basically does this by reducing uh coding efforts um and and by generating various boilerplate code for you so i'm just going to paste a link to the anchor docs in the chat before i continue for those that want to read more so anker basically uses a number of tools so once can we we build smart contracts in this workshop we're going to build them in rust um it generates these files called idl files interface description language files which is very similar to an abi file um in the ethereum world if you're coming from a solidity point of view and we're going to go through that in a minute and then you generate your clients or off chain kind of programs use using you know javascript or typescript etc and anchor has its own cli for interacting with programs and deploying them and things like that as well so in terms of how the workflow of anchor works right first we have our smart contracts which in this case we're going to write in rust and then with those smart contracts you know we build them which basically compiles the program into byte code just as if just like if we're not using anchor um however also with anchor it generates this idl file as well that says how to interact with the program and from that idea we can then generate clients and with the clients we can then talk to our program and then test them and things like that so an anchor program basically consists of three parts so it's just a rust program with with like some little hooks and macros added to it which you'll see in a minute right so we have a a program module that defines you know this is all the logic in the program and we have these things called accounts structs which is where all the accounts that are passed in are validated um and we have this thing called a declare id macro that stores the address of the program that's been deployed right so the actual program that um you're in we actually store the address of the the public key address of it in there um so that when the solana accounts get validated and stuff it knows who owns them and things like that um so here's just a basic example of an anchor program basically so all the bits in red are the anchor hooks or macros that are added in right so this is basically saying this program is located at this address here this is the public key address this little program macro basically says this is where all the logic of the program is so in this case we have a module called hello anchor and we have a function called initialize um and then in the account struct here we basically define a struct called initialize right so these are like the the anchor hooks or macros that you basically put into your program and we'll go through them in more detail right now so in terms of these accounts macros here basically this is where you define which accounts your instructional function call expects and and what constraints these accounts should follow right so uh in this example here we have um this set data function here and this with anchor programs you always have this thing called a context that's passed in and and you need to define in the context what the cons context is right so we're saying the context for this function call is set data basically what that means is it's going to look down here in the account structs and look for one called set data so it says okay when this function call gets called the accounts that we're expecting to be passed in are going to be specified here in this set data struct here so in this case we're saying we're expecting one mutable account so mutable means it can be modified and we're expecting one account to be passed in called my account and it's of a type my account which hasn't been defined yet oh no sorry my account is here um so that's basically saying this is the account the work data we're expecting and we're also expecting uh unsigned integer 64-bit parameter here um and yeah over here in that account definition we're saying we're expecting this one account called my account it's of type this so then in your account little macro here you can then define what this is you say public strike my account this is just a struct that has one um unsigned into just 64-bit uh called data right so that's how we can kind of combine the logic um the account that defines um what kind of how the data is stored and stuff and then the accounts that defines um what accounts we expect to be passed in within this context here um so the program module as i said before is where the business logic is defined um you can then call them from from off chain clients and things like that so they're just kind of like where your functions go and as i said before each define endpoint takes a context type as an argument that provides access to the accounts of the executing program and the program id that we specified up here [Music] yeah so in this example here we've got this uh we've got this set data function that we define here and like i said earlier we where we in the context we're saying we're looking for a set data thing down here in this section here that's going to define what kind of accounts you're expecting and where and it can take one um input parameter here as well so just like earlier i said you need to serialize and deserialize when using solana when you use anchor you can actually take in input parameters directly on the function definitions just like i have here so that abstracts away all of that serializing and deserializing for you so that's one of the cool things about anchor yeah and the instruction data can be added by adding arguments to the function after the context argument um and anchor will automatically deserialize the instruction data so as i said earlier um you don't need to serialize things into bioarrays pass them in and then deserialize them back with anchor you can literally just pass in you know integers strings etc on your pro um function definitions here and then just deal with them directly and and anchor will automatically do all of the serializing and deserializing required um so the idl file is generated very similar to the uh abr file in um the solidity world and it's basically used by clients to be able to interact with the deployed anchor programs right so it just defines you know what are all the function definitions what kind of um accounts are they expecting what kind of arguments are they expecting and things like that so here's just a simple example of one here cool let's do a quick demo now so um what we'll do is we'll just build a single simple anchor program that just takes in a string parameter like a name and and it can just basically say gm to that name right so you know something very simple so the first thing i'm going to do is bring out my vs code here um here we go so i've got my console here um what we're going to do the first thing we're going to do is we're going to go so i've got anchor installed and um i've sent you guys the link to the docs there it's got all the um info on how to install anchor so i got version.0242 installed so the first thing we're going to do is we're going to use the cli and go anchor a net m anchor it's going to initialize a new project for us with some boilerplate code right and then we're going to just build upon that that project give that a minute to complete um in this example i'm going to be deploying things and using things on a local anchor uh cluster so i'm going to start a local um anchor validator and we're going to do everything locally also as you can see we've got a whole bunch of stuff that's been generated including some boilerplate rustcode here and yeah we can get going now so we have a function called initialize here that takes in that has a context of initialize here um and it just returns nothing right so the first thing that we're going to do is we're going to change this to execute and context as execute change that to execute as well and in this case we're going to take a string parameter in name string um and then what are we going to do so we want to take the string that's passed in and just you know store it in an account that's passed in maybe right so we're going to say let gm account equals mutable context accounts count right so what does this mean this is basically taking in um looking in this execute context for something called gm account right now but there's nothing in here yet so let's define that next so what we want to do is we want to specify uh using our anchor tags one account that we're expecting to be passed in maybe a new account that's initialized um the person who's going to pay for that initialization of the account is going to be the person generating this transaction and the initial space we're going to allocate for the account is eight plus 32 bytes so there's always like an eight-bit discriminator at the beginning um and then we're just going to say we're going to install 32 bytes worth of data that should be enough for a name so once we've specified this little um anchor hook here we can then define the account so pub gm account it's of type account and beta that we're going to be storing use of type greeting account oops [Music] and next we're going to be expecting another account passed in which is the account that's um signing the transaction um and that's going to be the we're going to call it user and they're going to be who's signing the transaction i think that's syntax there um and then one more thing when you create accounts which is what's going to happen here you need to pass in the solana system program so we need to basically specify that to the system program is the 18 program into the protocol that does a whole bunch of protocol type things such as creating accounts and things like that [Music] this is all pretty standard boilerplate anchor type things there's nothing that's very different yet so once that's defined um the next thing we need to do is define what is this data look like that we're storing this gm account so we're going to have our account okay kind of hook here we're going to create a struct called greeting account and we're going to store a name here cool i think that is okay for now account info greeting account accounts let's see what's wrong here execute info there we go so basically we're taking in um when this function gets called uh we're saying from the context here um get this account here that's the create this account here which stores data using this kind of structure here um and then once we've done that all we want to do is say gm account dot name equals name which basically says grab this name that's passed in here and store it in this newly created account which is of this type psa store in this part here right and we might as well print it out to the program logs why not and then we'll end now are there anything else ah my anchor directory here so there's my anchor project we're on anchor build start compiling my program now now this um program id here that i talked about before anchor's a bit weird in that you you need to kind of specify the program id that you're gonna that gets deployed right um however you don't know what the program id is going to be until you actually build it for the first time because it generates it randomly so this is kind of double building thing that you just have to do in anchor for the time being until they find a solution so you need to then you need to build it and then you need to extract the generated program id which is stored in the idl file i think and then you can then paste that generated program id in here and then you actually need to build it again because you've changed the source code and once you've built it once it will reuse the same program id as long as you don't blow away your target folder here which contains all the metadata um so that you need to kind of build it get the program id paste it in there and then build it twice so it's a bit weird like that so um to extract the address i'm going to run [Music] selena address from selena cli and we can kind of get it here i'm going to paste it in there and i'm going do anchor build one more time and it should be quicker this time cool now before we deploy i'm going to tell solana that i'm going to be using my local validator so solana config set and then in another terminal session i'm going to go to lana test to spin up my local solana instance and once that's running uh we're nearly ready to go so first we're going to generate a new wallet address using the solana qli it's a line of cli sorry so i'm going to call it um id.json password so as you can see i've got an id dot json here um the first thing i want to do is just air drop some solano tokens to it so with salon you don't need to go to a faucet um you can use the airdrop program if you're on a test net um however there's no airdrop program for mainnet for obvious reasons and id.json let's try that oh we got to sell on our account um i think we're ready to deploy now to deploy to our local cluster let's give it a shot um actually one more thing so anchor we're gonna we need to specify an environment variable actually i think that's for the client let's try hit deploy to deploy it and we specified earlier that we're working with a local cluster and it's deployed and as you can see the program id here matches the one over there right so now that we've deployed it the next step is to kind of get a client going so just quickly though when using a client uh in this case we're going to generate such a javascript script to run to simulate a front-end you need to export um this anchor wallet environment variable for because we're going to be using the anco javascript library it uses it to know what wallet should be used to kind of generate transactions so in this case we want to specify the id.json public key or wallet that we generated here um so we're going to basically say set that environment variable to that we're doing double dots because i'm going to create my client file in this app folder here cool so let's go to the app folder and let's create a new file called client.js i'm going to open here now in the anchor in the anchor docs um there is a simple example that i've pasted in the chat um and i see there's a bunch of questions i'll get to them at the end of this exercise um so we're going to basically go to that minimal example and we're going to start with the boilerplate code that's there right so i'm going to paste it in here um so basically the first thing it does is it grabs the generated idl file right because it needs it to interact with that deploy program we're going to get our deployed program id which was this one here and we're going to paste it in here to say this is the program id we want to interact with and basically all the anchorworkprepackage does is it gets connection to that deployed program using the idl and the program id and then you can go program.rpc.functionname right um so the first thing we're going to do is go anchor equals require serum anchor use the anchor web3 library for javascript and provider is a way to get a connection to work in that case it's the local network so we're going to call that provider um and then we're going to have everything in a main function right and then um all we're going to do is call our main function and then just say done cool so we don't need that no we do need that let's fix the syntax issue here so let's see what in our uh program so in our case our idl generated idl file is um is going to be called audiel gm anchor dot json so we're going to change this to gm anchor right and what we're going to do next is we have a connection to our program id here so um we need to basically generate a new um account address to pass in as that account that we want to initialize so we're going to say m account equals anchor.web3.keypair all right so it's going to generate a new uh account address for us and now [Music] that under here and um now we're ready to interact with our program so we're going to say uh let transaction equals await program dot ipc dot execute because execute was our function name here and it takes in a string parameter here the context you don't need to specify um so we're going to say and then we're going to pass in a name oh we need to set the name actually so let's go um const name equals harry we're going to part in a name and we also need to specify the accounts so accounts that we want to pass in the gm account is the gm account that we specified just further up um the user the person that's signing for the transaction is our id.json one that we generated just before which he gets from the provider because we set that environment variable and then finally the system program so system program anchor dot web3 file like this there we go um and then once we pass in the accounts i think you don't need to do this but i'm just going to say our starting point for for this instruction call is on all um confirmed transactions right and signers who's signing this transaction we also want to include the gm account um that we created just so that um it knows that we have access to that to basically store stuff in that okay so that should be it for that let's see i've got a name here we go uh accounts means a colon cool so once we've called that function call um then we basically um that's going to store that uh name in the account that we're passing so we basically just need to double check that it's been stored so we go hunts store name equals awaits program.accounts.greeting account dot fetch so we're basically calling this um [Music] in our deployed uh program we're saying get the greeting account which is this here dot fetch and we want to get the name right um so gm account dot public key and then we're just going to go console.log store name dot name all right so it's going to basically just for this gm account that we created here and passed into our call it's going to basically look up the account data and fetch the green account dot name value okay i think that's it um so one other thing we just need to do quickly is set the anchor provider url so um when working off chain uh in these javascript libraries or typescript or whatever um anchor doesn't anchor needs to know uh you can't access the anchor cli to know that we're working with a local host so we just need to specify it um using this environment variable here so i'm just going to set it to my local host and then we're going to see up up we're already in app sorry um so i'm just going to run node client.js to run it and we have an error let's see where we're going uh we need to go back one extra folder because we're in the context of the app folder here and let's see what the next issue is um value arguments system program not defined think it's program.program id oh how are you done so um you did a console it basically with our name here it basically called this execute function it passed in this gm account to get initialized and we passed in the the string harry so the program executed it took the harry parameter it took the account that was passed in and created as a new account to store this type of data in it and it basically just stored the um it set the name here to the name that was passed in here and then off chain once the program completed all we did is just read the data from the account right so just a very simple example of using anchor how we're doing for time we've got 15 minutes do you need to install do you need do you need curl to install rust and salina cli i think you can download pre-built binaries depending on what system you have a great question um but definitely check out the the celina docks which i'll paste in the chat here and the um anchor docs which i pasted already i think but yeah great question now um i see a few other questions i'll try to get to them at the end but for now i just want to go on to the the chaining stuff um because we are running uh a bit over time so let's go back to the presentation cool so now let's talk about changing price feeds so um chaining price feeds are live on the slanted devnet for anyone to use they will be available on mainnet for anyone to use very soon um but for now they're live on devnet so if you want high quality uh accurate price data um celina price sorry chaining price feeds is the way to go so if you go to docs.chain.link there's a solana tab at the top here and and all the info about our price feeds is here so we have i think a few on devnet right now btc eath link soul and a couple stable coins um so if you need any uh if you need price data for your chaining hackathon submission and you want to build on solana uh this is where you go to basically to do that right and um what we're going to do next is um we have a yeah we're going to go straight into a demo so if you go to our github repository [Music] i'll um in the chat once again we have this thing called a solana starter kit right so if you need to build something on solana that uses price feeds this is the one place to go so it's pinned to our repo here selana starter kit and it is a pre-packaged repository that contains an anchor example program that uses chaining price feeds so you can just use it to kind of work out how to do it you can use it as a starting point for your project um you can use it um to just you know see how to do it basically so what we're going to do is we're just going to run this starter kit and i'll just kind of walk everyone through it and then hopefully i'll have time to answer some questions so i'm in my group folder here so we're going to get clone i'm going to paste the url of the starter kit here and as you can see i have a whole bunch of stuff here now so salona cool so the first thing you want to do is just install all the npm stuff that needs to get installed while that's going i'll i'll basically walk everyone through everything so here is the the deploy program uh it uses anchor just like we we saw um not too much in here um [Music] we have a declared id we have we define the way in which we're storing the price data here so this example program just literally takes in a price feed account uh address such as you know your sole usd account and basically looks up the latest price and then stores that data in another account that's passed in so there's a function for just formatting price data um and the thing to note here is we're using the chaining solana anchor library uh channing salana library here sorry and then using that library we can call functions such as latest round data you know description is that soul usd link usd et cetera and decimals how many decimal places is there in the what's the precision of the price feed data so we can basically call those functions and all that it's doing is it's basically just calling those functions and it's just setting the latest round data for a price feed into a variable and it's basically storing it into an account that's passed in right so we've passed we're taking in a new account to store the price data in this boilerplate code we're taking the specified chaining feed which we grab from here on devnet they're just accounts we're taking the deploy chaining program so there's one deployed chaining program on devnet that has all the functions and everything that defines how to interact with price feeds so it's a static value um and we're passing the system program because we're initializing accounts here so that's the um [Music] program let's see if we can get this built now so firstly i'm just gonna once again generate a new id.json wallet now the difference is this time we're going to be dealing with devnet the public devnet network instead of the our local validator and as you can see i'm doing an airdrop here uh i'm doing it twice actually uh to our id.json generated wallet address and i'm specifying the uh devnet rpc endpoint here api dot devnet.cellana.com so i'm just going to kill my local validator here because we don't need it anymore um so we're going to air drop ourselves some soul and then we're going to try build the anchor program so while that's building i'll go through the the client so we have a client called client.js here we actually have two clients we have client.js and readdata.ts so client.js is very similar to the example that we just went through um in our first workshop um in this case where we have the stored program id that's just a static value of the chaining program on on devnet uh we have a price feed specified here which i think is the sole usd thing is that w6 yep um but you can pass in another um feed address on the command line when you're on the script if you want and all it's doing is it's getting a connection to our deployed celina program um it's generating a new account just like we did before and then it's calling the execute function like we did before passing in all the account information so passing in the the new um account that we that we're creating uh our id.json wallet address for signing the transaction paying for it the chaining price feed uh which we're getting from here that we want to get the latest price for the chain program um is this one here that static value and then the system program because we're going to be generating new new counts so once that's done we've built it once once again we need to run the we need to extract the [Music] the generated id for this program we need to go back to our anchor program and put it in the declare id section up and then do that build one more time to build it with that in place and once that's done we should be able to deploy to devnet so we say anchor deploy provider.cluster equals devnet here so that might on devnet it usually takes um a little bit of time maybe a minute or so uh hopefully not um so what i'll do is uh i'll go through the rest of the client so once we call that program uh it will basically store the latest price for the feed that we specify in that account and then we're just printing out the the contents of the logs here and it looks like the end point is down that is not good using a free public um endpoint here so let's try to do that again um and once we uh once we have called that function um once again we're just reading the value of that account that we passed in um to get that latest price information so very similar to our last um example that we ran now we also have this read data script as well that you can use so if you're building an app that you just want to use price feed data in your front end if you're building a cfl application or something um you don't need to generate transactions on solana if you want to read price data you don't need to pay sol and lan ports and things like that you can just read the price for data off chain as well and that's exactly what this read data script does is right we specify a chaining feed address and a program id and we basically just we get a connection to that uh deployed feed and it basically just looks at the logs for that feed and it just basically keeps printing the latest price so you can do this off chain in your web app or whatever it is you don't need to pay sold land ports or generate any transactions and you can use it just to read the price data off chain so that's what this read data script does as well so um hopefully we can deploy to devnet um i'll just give it a minute to complete i'll have a look at some questions while we're waiting this anchor kind of like docker but for rust ankle's kind of like more of like a hard hat sort of for for solano i'd say than the docker um yeah will the default celina ross template run with cargo run i think so i think it does yeah can we access system program idl files the system program that's baked into solana i don't know if it's got an ideal file because i don't know if it was built using anchor can a program access data created by another in your account great question so you specify in when you specify your um [Music] accounts here you can specify uh you can specify who owns them and things like that um and in this case we're saying um whoever pays for owns it so you need to basically have access to the account to be able to access it on chain right um so because this program's doing it here uh the program has access to it right however once again it's just by data stored um so if you know the address of an account that you want to access from off chain and you know the structure of that data because you know the source code or something of the program that uses it you can theoretically off change it to read the by array and then like deserialize it into something meaningful um so there's nothing stopping anyone from doing that but yeah great question cool so that's deployed now uh the next thing we want to try and do is run the the client now so um so i'm just following the steps here in our solana starter kit repo which uh i'll paste here again in case anyone hasn't seen it um so once again we need to set some environment variables so we're saying the anchor provider url is the the local devnet rpc endpoint and the wallet that we want to generate uh account that we want to generate transactions with is our id.json that we created so once that's done we should be able to run our client script so um in this case we would say node climb.js uh the program we're passing in dynamically using the chain link um cli but it's essentially just going to return this program id here and the feed that we're passing in is i think it's the the eth usd feed so we're going to see what the latest price for ethereum is so we run that client cool there we go so we see a bunch of um program log data um ethersd price there and then price is that's our client.js here um just reading the account info from off chain um and then basically just stripping out the value so so there you go we deployed a selana program that basically looked up price data on a chaining price feed the latest price for ethereum and then stored it in a passed in account right and then you can do stuff with that data in your hackathon submission so the last thing i want to show everyone is the read data script so once again it's a great use case if you're building something where you just need high quality price data off chain and it's actually really really easy to run really easy to run so you don't need to change the program id you just basically say what is the feed address you want to look up data for right in this case we have an eth usd as well and you basically just run npm run read data to just run the script and it'll basically go in it will read the price data from the uh account it will look at the events generated and it will basically just um keep printing out the the latest price as it gets stored right so i think the um around time is set to one second or a couple seconds or something like that um so as you can see there's the price of ethereum and it basically just keeps printing it out so you can just use this as a means to kind of know how to do it and then you can basically just incorporate this into your off chain web app or front end or whatever it is you're building well so that's it really as you can see quite easy to use price feeds on solana there's a perfect boilerplate project to show you exactly how it's done and then you can just use this as a starting point or just as a reference point to using your own submission so i'll get to a couple more questions in a minute i just want to talk about where you can learn more about celina and chaining quickly so uh where you can learn more um a really good place to go is the salina cookbook i can't recommend this site enough and i'm going to paste all of these in the chat so it's a really good developer resource it's got tutorials and guides for doing all kinds of things on salina and it's very popular with with salina developers so i highly recommend i check that out if you're interested another place is sol deaf this is like a content aggregator for solana so whenever people build published tutorials or blog posts or guides on how to do things um they usually end up in this install dev here so you can search for things really easily once again really great resource so the solana labs have a solana developers page as well with a bunch of more resources videos uh content uh starting how-to guides et cetera so i definitely recommend checking that out as well uh anchor anchor's got this thing called the anchor book which is awesome um so if you're using anchor definitely recommend checking this out it's got a reference information on how anchor works it's got example projects like tic-tac-toe projects and stuff so you can follow along and just you know see how everything works uh we discussed the solana starter kit i pasted it in the chat earlier so that's our pre-packaged boilerplate repo for interacting with solana programs and um yeah docs so you go to docs.chain.link click on solana and it's got information on how to use data feeds and and the reference information for the data feeds on our devnet and and soon to be mainnet as well cool um we are time so i just want to say thanks everyone for tuning in i will answer a couple questions now um but yeah really excited to see what everyone builds uh if you are building something for the hackathon on solana um awesome really happy to see can't wait to see how you use our price feeds um and i think yeah there might be some really interesting projects so once again thank you if you have any questions or issues hit us up in our disc in our discord um or if you have solana specific errors or issues um definitely recommend checking out the uh solana discord which is uh here as well and asking questions there they're very active there as well but thank you for tuning in and looking forward to see what everyone builds i will spend a couple minutes just checking out a couple more questions here why there isn't why isn't there a bigger market blockchain cyber security i'm not sure um can we select versions of solidity and solana yeah so once again i don't think you can use solution yet however i do know that there are some people trying to bring evm compatibility to solana and but i haven't played around with a um myself do you recommend us learning rust yes if you're gonna if you're if you want to spend time building on solana uh rust is definitely the way to go i think personally um it's not hugely hard if you've if you know any other programming language you can pick up rust fairly easily um there's not a huge amount of rust used on solana as well it's just like a subset of rust kind of like the basics um so yeah if you want to get in the salina ecosystem um getting up to speed on rust is the way to go and there's this thing called the rust book rust book which is a good online language uh reference that i'll paste in the chat um however if you want to hide something a hard copy let me see if i got it here this is what i have this is what i've been using here i'll see if i can throw it up here programming rust um this is a really great resource um for for learning rust so probably the first six or seven chapters is applicable for solana so i can highly recommend that one as well does celina have prizes in the hackathon um i'm not 100 sure i don't know if there is yet however um you can build on any chain with chaining and be applicable for any of the major prizes so if you're building a d5 um you can um build it on solana you can build on violent smart chain you can put it on ethereum and and you're still um applicable for you know the the main prices because as long as you use chain link in some way um so you can build on solana for the hackathon uh you can definitely get prizes with it i'm not sure if solana has a um has a sponsor prize at this stage though what is anchor so just yeah definitely watch the replay of this um workshop but anchor is basically a um a library for making building celina smart contracts a lot more pain-free definitely um okay but definitely over time here so i think i'm gonna end the stream but once again thanks to everyone for tuning in and really look forward to seeing what everyone builds um sorry just one more thing i want to plug my boot camp i forgot uh if you want to build more um if you want to learn more about solana if you go to chain.link uh forward slash boot camp we do have a celina bootcamp that we recently ran i'll paste it in the chat uh you can sign up and do this boot camp on demand so it goes for about eight hours so you learn all about solana um and current building um selana programs and stuff like that um you can just do it by watching the pre-recorded sessions and i think it's about five exercises so um if you want to get more into solana definitely recommend checking that out as well but for now i will stop sharing um and cool all right thank you everyone um yeah really looking forward to seeing what everyone builds and yes the bootcamp is free it's it's 100 free