[Music] Hello everyone.
Yeah. Okay. We are live. Okay. Okay.
Okay. So I'm here too with Andre to talk with you about create crosschain tokens using the CCT standard. So I am solici you can come. So we are around and uh we are here to help you all the time. These are my contacts and
and yeah my name is Andre. I also work as a salange as a deer engineer. This is my Twitter handle but also I'll be at our boot to help you with debugging. I also write smart contract design newsletter patterns newsletter. I created a blockchain board game.
I did a lot of stuff. So you can find me if you need help with debugging to throughout this week. And this this is the most important uh slide for you because we have a lot of links over there. Everything is over there that you need to the hackathon.
Yeah. Amazing.
It's safe.
Yeah, you can trust this for sure.
Okay.
Yeah, I think you are fine. So, first of all, let's talk a bit about oracles and chaining. So oracles is the way that we can connect with all the information that's outside the blockchain or even in another blockchain. And we have different kind of oracles. For example, when we talk about data, we can talk about data streams or data feeds to get codes to get prices uh and all kind of numbers or you can have a proof of reservey of something that is in a bank or in another blockchain.
and uh CCIP we are talking later because this is the main focus we we could use functions in your hackathon if you'd like to use an external API any API create a JavaScript code and then use that JavaScript code inside your solidity smart contract and bring this information to your project. You can do that. This is so cool. I love to do that. And also you could use automation to automate any function that you'd like to call inside your smart content.
Can be a time based can be using a trigger that you define the conditions or can you can use even an log event in another contract to trigger something. This is the way that you can automate your smart contract. Also imagine that you'd like to have a random numbers can be a game. It can be some lottery but you need the random numbers. You can use VRF to have these random numbers.
Okay. And these are our bounties. We have two different tracks. One is related to the CCIP and the CCT that I'm talking a bit more today. And the other one is related to all the other chain link services.
So if you use CCT and another chain link service, you could win both tracks. I already saw in the past projects winning both um tracks. So it's a double chase for you and also this is all the other sponsors that are here and they uh you can use chain link with them. So you can see a lot of options that you can combine with chain link and increase your prices as well. So let's talk about interoperability.
So a blockchain is an isolated network like an Iceland and I'd like to connect this uh blockchain this Iceland this is the CCIP the crosschain interoperability protocol so in a high level archet of that you can see that a user in one size in in the Cersei blockchain can send messages or can send directly tokens to other blockchain and we have all the offchain part that uh this This is what the CCIP do. And uh also the communication is uh done between the houses over there. Okay. And then in the destination chain, you receive tokens or messages wherever you'd like to receive. So what can I do with CCIP?
Like I said before, tokens message or I could combine both. Imagine that I could send a message with a token and then I already read uh I'm telling what I'd like to do with that token and this is talking now about the CCT the crosschain token standard imagine that you can create your own token and this token can be crosschain using the CCT so your own token can go to one chain to another chain and can be any token that you would like to rate. How can we do this? The CCT is the standard to do that. So, it's uh a bit more of an ERC20 token.
You should have some extra capabilities to do that. And we have the the security here and all the capabilities over there. In the same way that we have the workflow of the CCT tokens, we normally have a pool in each of these chains. And this pool you can have the tokens that you are using in one chain and sending or receiving from from the other chain. And also it's important to you to know that we have the offchain part of this is totally secure because it's not only one decentralized oracle network but we have three different networks with a segregation of rules to be sure that this is not compromised like some bridges around.
So ways that you can use and create your uh token your CCT token. One of that is the CCIP token manager. So this is a UI this is an interface that you can go and uh uh click next next and choose your networks and do everything. You can deploy the token over there. You can enable the crosschain part and uh set the token pools that we must have in both blockchains.
and imagine how is the administration of that. Okay. Uh important to say what are these token pools as well. So these are the containers that uh we must have to enable the token transfers between the blockchains and would you like to say more about the token pools?
Yeah, sure. So the whole point of CCT is actually to add support for your own ERC20 token to be transferred coach training via CCIP because naturally or in the beginning you will you were able to transfer USDC go wrap it whatever but like for your own token you will need to find the workaround with transferring arbitrary data. Now with CCT as S told you you can just use the token manager in a few clicks to set up uh the to set up the support for your token to be transferred via CCI IP. And the whole point is how you can do that is by deploying one of these token pools. So you will either deploy lock or burn lock or burn token pools or unlock or mint and lock and unlock token pools which essentially does the handles the transfers of your tokens.
Now these pools are provided as a smart contracts by chain links. You literally just going to deploy them. That's what we are doing through the through the UI. just deploy one of these pools and it's up to you uh to choose which which uh token method for transferring you want you want to choose with these pools. For burn and mint, it's quite obvious you're going to burn the amount of tokens you want to transfer on a sort chain and mint the exact same amount of tokens on the other chain.
However, if your token does not have exposed burn and mint functions for whatever reasons, you can do lock and unlock, which will literally going to lock the amount of tokens you want to send on a source chain and it's going to stay in a token pool contract and then unlock the the same amount on the other side. Obviously, with this method, you will need to prefill those token pools as one of the steps. Now, how you can do that on test net and mainets like we have this UI. So, you can literally just going to click click click and that's it. However, if your use case is much more complex, you're you're dealing with rebasing tokens or stuff like that, you're you can also customize these pools because those smart contracts are open source.
You can just get clone and uh or npm install it via npm package and build on top of that like inherit those pool tokens and because of that you will need to then manually do the flow because now we don't have a UI support for that but these are essentially four steps that you will do. You will deploy your you will have your token already deployed deploy it on multiple chains deploys these pools and then you will just need your token will need to have either owner function or get CCP admin because that's how you prove to CCIP that that's your token after you accept this admin roles. The rest is just to uh to set up tokens and pools and you will see in our docs how you can do that manually as well if you want if you don't want to do it via UI which we recommend in the interest of time for this hackathon. Um you can also do this by using remix if you're a beginner. We have like multiple different guides in our docs.
So on docschain.linkccp you'll find multiple different guides and you can just uh you can just um add the support for this token by yourself of course. more links, more blog posts. You have the presentation already. So you can those all of these links are clickable.
If you don't want to scroll through the docs, just go through this links and you will find references.
We are sharing the presentation again. Don't worry yet.
Yeah. And finally, uh if you want to build with CCP much faster, you need a way to simulate these transactions locally so you can move much quicker in your foundry hardhead or remix environment. So that's why we created this tool called chaining local which is a CCP local simulator. So instead of like building directly on test nets then you need to go to faucets.chain.
link collect all tokens you need then deal with gas transactions whatever and then wait for finality times on test nets just to realize you have like a bug in your smart contract or a flow that needs to be uh fixed and then you need to redeploy contracts and again and again and again. much faster is to just install chain in local and instead of waiting for 10 plus minutes you just wait for less than a second and then in your again uh development environment of choice which is foundry hardhead and remix I saw a question where I'll do it afterwards you can just do these simulations locally so the first type of simulation is purely local with all the mock contracts the second one is in a fork environment you fork different chains and then you you you basically run a tests against the actual copies of the actual test nets which I think we think is uh uh is a way for you to build much faster avoiding these extra points of frictions and the most important thing about chaining local is the contract that you build with chaining local you can redeploy to test net or mainet without any change and it will just work as long as the config details are correct. Um so yeah what developers want is developers want chain local to bit build much more faster and uh CCP is the only protocol that has this local simulations that has the ability to combine both tokens and data transfers in a same message and that allows you to add support for crosschain transfers to your ERC20 token. Uh again, this is the the link to chain link local. And as you can see here, this is this literally works offline as well once you install it.
Like it's it's really cool. Um and yeah, these are the bounties. If you want to uh close it up, I'll give it to you also.
Yeah, this is really amazing. And you saw that we have the options to everyone. I know that my friend over there you use the token manager but that other friend over there for sure you uh he's using foundry because we are talking about that and this is the our goal to have this in a way that everyone can use and and to help everyone to build your projects in a way that you can really connect with the world and even connect your blockchains and don't have like any blocker with a blockchain. This is our goal. Okay, again this is our bounties.
I think you can see that we have one for CCIP or CCT and another one for all the other chaining services. And we are good on time. Yeah, we are so fast.
Yeah. And this is our developer hubby because sometimes uh if you'd like to know more about each of the services, the developer hubby has informations of all of them configuration, how to configurate uh tutorials and a lot of examples to be sure that you can be faster here in the hackathon. Also, this is the most important slides for you. Again, don't forget that uh you need this because this has everything that we talk about. This is the presentation.
I know that some of you arrived a bit late. So, this is the moment to get your slides to be with us. Yeah. And is this Thank you. Andor
bonar
bonor. Uh it's uh good luck in French for you. And do you have any question? We still have some minutes.
Yeah. Five minutes for questions if you like. Uh
one over there,
the gentleman. Yeah,
he was with Yeah.
Okay.
Um, so what I understood is um you're not expecting us to build uh sort of a framework or choose some problems and uh some finding some solutions but either way building on uh creating a CCT with the other project sort of we build do I understand right?
Yeah. Imagine that you are creating your project and uh you'd like to have a token for example. Why to have your token in only one chain you can have this token in multiple chains and using this crosschain solution for you. And when we talk about the other protocols and networks that they are here uh we talk about because they are here there are networks that you could use that we have CCIP implemented to you remember that chain link is not a blockchain it's a set of services that is deployed in other blockchains so we can use it us and then
sorry do you have like specific use cases or anything something
no surprises we'd like to use the best uses of uh us the best way and do you have your question over that?
I
I I had a question about chain link local and how it would um compare with Anvil or if you use them together or um can you tell a little bit more about that?
Compare with what?
How they compare with each other or if you can use them together? chain link local and what else compared with what
Enfield which is the local blockchain of of foundry. Yes.
Yeah. Cool. So yeah, chain link local has a native support for foundry. Uh it basically leverag node under the hood. Uh the one the design decision that we made is that we won't spin up any offchain components.
We in the local simulations will just assume that chain link will work. So there is no any offchain components. We have basically a set of smart contracts for local mode is just mock smart contracts and for fork mode we're literally forking the actual smart contracts. And the thing is that um what like the nice thing about anvil is that in foundry you have the way to switch between different forks. So what we do uh behind the scenes for you is that when you instance a new uh instance of uh TCP local simulator which is essentially just a giant smart contract with all of the test uh configurations in anvil we in first uh first u use case with mocks we just predeploy all of these mocks to our anvil node.
In a second example with forks we just uh switch between forks for you under the hood. So you just do CCP send and then we we can handle the rest under the hood without spinning out any of components or whatever. Um so that how it works and obviously in anvil you can see all the logs uh if you need um error messages etc. And if you still need help we're going to help with debugging at boot. You're welcome.
Um any final questions?
Yeah I think we have one more.
Yeah.
Okay cool. So again if you need any help with debugging with integrations whatever uh four of us will be at the training booth over there uh bounties you saw this is the link to the presentation which has a lot of different links that are clickable
it's for you
and yeah that'll be it I guess
yeah I know that there are more people getting the link now let's wait them okay
and good luck everyone
thank you Mercy Bonage Merci [Music]
Automatic transcript — names and jargon may be misspelled.
