Hey everybody, we're just getting set up. Betty, do you mind testing your mic? A quick? Yeah sure. Good morning everyone. Sounds good.
Cool. Betty, I think as people start rolling in, we can go ahead and get started. We've got around 20 people in the call. So, yeah, so thanks everybody for hopping on and joining us. We're going to be talking
about mostly things around AUSD today. So, Daddy's going to get a given overview around this. Sounds somewhat technical, but when we explain it, it's not too difficult to understand, which is the AUSD fungibility palette.
We'll get into more detail around this, but a lot of this is mostly to kind of ensure that there's Economic infrastructure kind of spanning across both Polkadot and Kusama via AUSD and then Betty will get into a little bit more around how exactly that works some of the
risk mitigation tactics that are being kind of included in this and then kind of the roadmap for where we'll start with this and then how that will kind of start to scale and grow. So, buddy, if you want to go ahead and maybe quickly introduce yourself and then get into some details around
around this, that would be awesome. Sure, thanks Dan. Yeah, Betty here, good morning, good afternoon, good evening, depends on where you are. Thanks for coming along for the Twitter space today. I'm one of the co-founders at Akara and Karura.
So today is mostly to talk about a new feature that we are about to launch. And this is also one of the initiatives that we have to continue to improve liquidity and also infresidency of
the U.S.D. so that we can actually support as Polkadot Krasama ecosystem continue to grow. And then we can support them with this credit system or stable-con liquidity system to help all the ecosystem parachains or debts to actually grow.
along with it. And last week we introduced sort of IATs, folks can kind of look up probably the last recording. That's one of the initiatives for us to improve liquidity and also capital efficiency for AUSD
quite an issuance. And then this week, this is not too new because we've kind of proposed it quite a long time ago and went through some voting. Now it's mostly like implementation details for how we actually achieve making AUSD truly
multi-chain. Effectively what we are trying to achieve. So the current state is on the customer side we have a credit system on Corrura. So folks can actually collateralize your KSM, KR,
asset and probably very soon other type of assets that becomes available and also meets the risk and the quality requirements and can actually use those to actually create a USD credits. And also on the other side of the universe, on the polka dot side of the
the universe, folks can use dot, ACA, and also other, you know, dot derivatives like L dot, LC dot, to generate a USD credit. And right now, the two systems are completely separate, separate
by technically as well as economically as well. So if you hold DAW, you play in the world of DAW. If you hold KSM, you can only operate in the world of KSM, perishing ecosystem. You are only multi-chain within your own universe, I guess.
And the challenge there is these two credit systems actually operate under the same protocol provided by a car. And then it's the same sort of risk framework and then you know the same perishing structure.
And then there's no reason to actually fragment the liquidity, right? Because at the moment, the liquidity are fragmented, right? Because two economies are completely separate. So the goal that we want to achieve is be able to connect, poke it out and also
also, Kusama via connecting Akala and Karura and then making AUSD fungible across the two ecosystem. By fungible, I mean you can actually generate AUSD from Kusama side and then bring it over to the Pukodaksai and then use it within
any of the perishing depth that supports AUSD to access product services or do whatever you want or even actually pay down your AUSD desk on a color side and vice versa. So effectively, this will actually
making a union of the same economically. Effectively your KSM values can be crossed over to Polkadot and vice versa. So if you look at where the ecosystem are growing on the career side, we've
already connected to 20+ power chains and then many of them are operating and also integrating with the product and services on Correra. Whereas on the Pukodot side, it only started to launch two months ago and now we've connected to Havidesim.
So you probably see the swing as we go forward is there are a lot more faster activities happening on the summer side and then the pulpit outside will kind of like gradually catch up as things progress. So naturally while folks are waiting
There may be a need to actually bring dot based assets via a USD to the cruisame side and participate in many of the activities over there. And then those capital or liquidity can swing back to Pogodon as more activities happening on Pogodon site effectively
creating this synergy between the two ecosystems. So yeah, so this is sort of the high level goal that we're trying to achieve. And then of course, with the implementation of this vulnerability pattern, AUSD
can be multi-chain beyond the current two relay chains. So if you look at Polgodot's roadmap, where Polgodot's heading is, there will be multiple relay chains that can be trustlessly connected. Right? So right now, there are two relay chains, Polgodot and Kruzama, and they haven't been connected
And then the next sort of evolution for polgoda is you can actually actually spin up polgoda like red a chain or the current power chains can actually grow up to be a red a chain. And then that can be actually connected back to polgoda trustlessly. And then effectively,
giving the Polkadot ecosystem infinite scalability. Right? Because right now, you can effectively have 100 chains within Polkadot, 100 chains on Kusama. And then if they can all connect together and create multiple relay chains, then that will be tens of thousands of chains that are interconnected.
And then it will become more prominent than the liquidity needs to be unified and also be able to fundamentally transfer to each other. Because why vulnerability is important you might ask is right now there's like 10 different versions of bridges, right? Like go across to different places.
Each bridge will fragment the liquidity. Like if you bridge, say, die or USDC from one place to another using one bridge, that's, you know, X USDC. If you use another bridge, that's why USDC. Right. Those two are new
not interchangeable. So not interchangeable means they're not fundable. So that creates quite a bit of challenge for applications and also for users in terms of usability as well. And then with what we've done here, what will be possible is you can base
basically installed this pattern onto new relay chains, or probably the parachangs on those new relay chains, and then you can issue AUSD on those chains natively, but also make it fungible between
and Kusama, and then effectively connecting all those economies altogether. So this also gives AUSD, sort of unlimited scalability in the sense of where Pogodak is like scaling itself in a multi-relay chain ecosystem.
system. So yeah, so that is sort of where things are heading and then how we kind of like see it. Of course, that's a lot longer term. Right now, our focus is on making sure that Pogodakusama will have sufficient support of liquidity and
and also unify the liquidity. Yeah, so that's the context. Maybe we can go into a little bit more how we are achieving it. Let me start here at the real quick. If people are on the call, maybe you'd join a little bit
So we're discussing the AUSD Fundrability Palette, which allows AUSD to kind of seamlessly cross across from Pokerat to Kusama or from Kusama to Pokerat. The tweet that I have here pinned at the top is the kind of post about that if you want to read more.
And then if you scroll to the second tweet that's pended the top, there's a link in that tweet to Slido. So if anyone wants to ask questions via text, feel free to go to that Slido and ask to type your question out. And we'll go through those questions later on this
call. If you also have questions that you want to ask verbally on Twitter here, feel free to like whatever it's called, raise your hand or request to come up on the stage and you can also do that as soon as Betty's kind of finished with this next section here. So yeah, go ahead
buddy cool yeah awesome yeah do do ask questions if you have any yeah so the next thing is let's talk about how we actually made a USD fungible between Akala and Karura so there's a couple of pericuses
that we need to do before we get to this point. First is we've upgraded, we've created a token registry on both Correra side and a color side. It will enable this, but it can also do a whole bunch of other stuff. So effectively on the Correra side, the token registry
basically registers all the token ID as well as token symbol. So you can think about it equivalent as ERC 20 contract as well as the ERC 20 symbol. So if you think about let's say USDC, when it deployed on Ethereum,
is a contract address and then it also has a symbol called USDC. But of course the symbol is not on chain. You look it up on somewhere like EtherSket. Only the contract address is on chain and then they registered a symbol off chain. So on the correct side, so on the correct color, we
implemented the token registry where all of this information are on chain. So effectively anyone can query any of the token and they get the token ID as well as the symbol on chain. And of course all the details like decimal places and things like that. So that will just give any of the integrators like whether you are a DAB or whether
that you explore or exchange, making it a lot easier for those information. I think from a user perspective, you may not know a lot of the stuff that you read is actually not on chain. They actually run on a centralized server to tell you it's a USDC or it's a fake USDC, right?
You're actually trusting those parties to tell you that. But I think with the text that we have, we have a lot more customized ability and also ability to create this type of registry to make the tokens a lot more unified in terms of standards.
So, um, what was that then we're able to upgrade the KUSD symbol into AUSD on the carousel. So right now if you go on to carrura, it's already been a while, right? So, we've gone through this a few months ago. So you can already see AUSD is actually trading on carrura. Um,
And then the next thing that we require is a bridge between Carrera and Akala. So there is a one-hole bridge, a launch on Carrera as well as Akala. So we currently using that as a bridge between the two networks. And this can be quite easily upgraded.
to a substrate native bridge when it become available. And apparently that still sort of under development, but once it becomes available, we can actually switch to that and upgrade to it relatively easily and also similarly to to using that bridge instead. So those are the
two kind of prerequisites that we require to making AUSD a fungible between the two chains. So we check those off and then now today's topic is about the fungibility pattern. So the actual pattern that actually makes the two
tokens, but in the two sides, Fundrable. So we're going to a little bit more detail of how it works. So effectively, the Fundrable and the Palette is in store on the chain that's associated and needs to be made fundrable to the account.
AUSD. And that basically is, say, AUSD originated by Korea's on a caliside, secured by Pogodot is the AUSD standard for bridging to change outside of Pogodot ecosystem as well as across Pogodot and Krasama as well.
was within the Pugodot ecosystem. So AUSD, originally from Akala, is the standard. And then we installed a palette on the chains that are generating AUSD and needs to be made fungible to the AUSD on Akala. So and right now there's only one chain that
that's Carrura. So we're installing the vulnerability padded on Carrura and effectively making AUSD originated on Carrura, vulnerable to AUSD created on Akala. And how did it actually
works at a high level, you have two sides of transfers. So you can transfer AUSD from a color to Corrura or Corrura to a color and you want those coins exactly the same. So when you generate AUSD from a color side using DAW, you can actually
Senate across the Correra and use it to pay back the debt on Correra. But also using on any of the existing AUSD Daps, whether it's locally on Correra or across the Kusama-paraching ecosystem that have crossed AUSD to their chains and debts.
So the process kind of looks like this, when the AUSD Corrura gets sent from Corrura to Akala through this palette, it actually gets turned into the AUSD of Akala. And I'll go to
bit more detail right after this. And then vice versa. So effectively this pilot is kind of you can look at it as like exchange, but it's more of like a one to one to be able to change the AUSD originated from Corura.
to AUSD originated from Akala. And then this has another added benefit is doesn't matter which bridge you use, like to go to external. So right now we use one hole. So not only it connects Akala and Karura, it also connects all of these
these chains to external world like Ethereum, to Polygon, to any of the chains that it connects to, doesn't matter which one. And then regardless where you send AUSD from, like if you send AUSD from Corrura to Ethereum, it can come back to Akala, also vulnerable.
a vice versa. So it actually makes a USD kind of a fungible across all of these networks. So it doesn't matter whether you generated it across it to a color or from Corrura. And if you want to down the track of these use cases outside, you can send it across and then
take it back, they will all work the same. So there's one interesting use case there was, there's a team called Swim, and then they basically do multi-chain sort of liquidity provision for users. So if you come from say Ethereum, you are holding the Ethereum.
But you actually want to play or operate in the Akala ecosystem. So Swim basically will just like very smoothly one click to kind of convert your USDC from Ethereum into let's say a USD on Akala so you can pay fees, you can pay
participate in the pools or you can then hop over to other places, other depths to use it. So they provide the routing of the liquidity from different chains into the destination chain. And then in that scenario, they can effectively support both Akala and Guru Rao.
very much interchange the body. So if you come from an external ecosystem, it's very easy for you to convert your local currency to the currency of where you're heading. So that's what the pilot provides.
And then the next I will explain another part of the mechanics. So bear with me. I'll try to go slow and then the main thing is I understand the mechanics and also the risk that does actually imposes on both Akala and Korura. And understanding those will kind of help us to kind of
of management or predice going forward. So firstly, so as I mentioned, there's two sides, right? So firstly, it's transferred from Corrura and Akala. From a user perspective, it's actually quite similar. So you basically go on to the app and then, you know,
You put in a USD and you say I want to transfer from Karara to Akala, there will be like three set approach. So you have to sign a transaction for it to put into the vulnerability pattern, you know, kind of like in the pattern that makes it vulnerable. And then you have to sign another transaction to actually
allow it to go across the chain. So the crushing is provided by a wormhole currently but also be able to provide it by a substrates native bridge later on. So you need to sign a transaction for that. And then once it landed on the collar, you kind of sign another transaction that you have to claim that transferred a USD onto that
color style as AUSD and then be able to use it. So it's a three-step approach. We'll have another session to talk about the UI and probably demo that. That's like the next step. So once the padded a life, then it will be the front-ends that will
we will provide. But it's easy to actually imagine the process from a user perspective, it's like that. I think we'll be able to streamline that further to kind of batch a couple of the transactions. We only need like two clicks instead of like three or more clicks. But effectively, it's that simple from a user perspective to cross it over
over, but underlying is where the tricks are to making it fungible. So on either of the paddocks, you actually provide a quota for how much you can transfer to other trade. So for example, if you are transferring from karate to a color, there's
the quota of how much like the maximum amount of AUSD can be transferred from Kuruja to Akala. The reason for that being, this risk parameter is effectively limiting risk exposure to Akala from Kuruja. Because when you transfer AUSD from Kuruja to Akala, you
effectively there's Kusama's share security that you are taking into consideration and then you are crossing a bridge so the bridge risk you are also taking into consideration. So for example, I think right now the recommendation is the quota to
transfer from Karura to Akala is 450k. And that means the maximum amount of AUSD that can be transferred from Karura to Akala is 500k plus, you know, if there's already some Akala transferred to Karura, so that's sort of the maximum amount that can be transferred.
And then that also kind of determines the maximum exposure, like the risk that can be taken from that side. So I probably got it wrong. So the quota to a color, thanks for the 1.1 million. So that's how much the color start is taking on
as risk. And then when you actually configure those quota, you actually generate the AUST from a color as a quota in the palette, but it's not in circulation. And then you actually deposit that into one whole bridge
And within the Wompo Bridge, all the AUSDs from the Color Side is actually generated as WAUSD. So through any bridge, you will have the bridge version of the AUSD. It's effectively the same language or same standard that you are transferring the tokens.
Excuse me. So once you transfer AUSD from Karat to color is initiated, then effectively you are depositing.
say $100 USD that you are transferring from Karara to Akala, you are effectively firstly depositing that $100 USD into defundability pallet. Right?
So let me retract. So when you actually transfer AUSD from Corridor to color, you initiate the transaction and then effectively deposits the 100 AUSD into the vulnerability palette. And then the vulnerability palette can actually use that to actually mint one to one.
to WAUSD, which is the bridge version of the AUSD. And then through that, the WAUSD can then be automatically redeemed, one to one on the Arcada side as the Arcada AUSD, which you can be used for any operation.
on the Arcala side. And then the way that it's able to receive the AUSD in Corrura and then generate the AWS AUSD and how much can be generated is determined by the risk parameter the quota to Arcala. If the quota is being used up,
then there's no more WAUSD can be kind of swapped. Then the risk is kind of kept at the level. So, yeah, so that's how in the background, how everything works. Yeah, so
I think the reason we go into a lot of detail and you may think it's irrelevant is I guess that's the difference between like D5 and also kind of other type of you know C5 protocol is like you can actually understand the mechanics and then you understand how things work underneath and then also actually
because we expose all the risk parameters so you can also gouge how much risk each side is taking on and then also judge it in your own way. Yeah. So and then transfer from Akara to Karura is the other way around. So there's also a
second parameter that's been set called quota to Karura. So this is effectively how much Karura can take from the risk exposure from Akara as well as the bridge being used. And then and what you do is you initiate the transfer of AUSD
color and then that gets deposited into the bridge and then that generates the WA USD and then the WA USD gets deposited into defangibility pattern and then the fungibility pattern then can swap into the AUSD originated from
And then this AUSD from Corrura then can be received like redeemed on the Corrura side, which is effectively the same AUSD as everyone else is using on the Corrura side. So that's why you can actually use it to pay down your existing debt.
or do any of other product services that supporting the AUSD on the carousel. So effectively, this vulnerability pattern allows folks to, the swapping that it provides allows folks to actually use the real version of the local AWS
the USD that's been generated. So this is the magic behind the scene. But at the same time, I guess this also allows the same version of a USD across all the Parisian ecosystems via XAM.
the USD that crossed over to, I guess, other parachangs. You can easily cross them back and then can get sent to Polka.side or Kusama-side vice versa. Right? So, yeah. So that's effectively how the whole thing works. I know it's probably a little bit confusing.
as this quite a bit of technical detail is there. But hopefully, hopefully, hopefully, I'm looking at Sliders. Folks also asking questions. Hopefully, through the Q&A, we can also explain this a little bit further if you are sort of unclear or just mix it even more confusing as I
But overall, if I have to summarize it, is the functionality palette effectively allows you to send AUSD from Akala to Karura or Karura to Akala, and then be able to convert that USD to the local AUSD that being used
used on Akala or Kurura and then can use it to pay down the debt or using any of the product and services that supports a USD. And then the risk exposure is basically determined by the quota to Akala
and also quota to Karura, limiting how much each chain is taking on in terms of risk exposures. So, yeah, so that's about it. And then so far, we've had quite a bit of internal review, as well as a review from external partners like Ganglad and others have
looked at it. So right now the recommendation is setting the initial quota to transfer from a Carrura to a Cala is 1.1 million and then quota to transfer from a Cala to Carrura is 0.50K. The lower numbers because Carrura
can take on lesser risk compared to a color. So that's sort of the recommendation and the expectation of how much risk that we are introducing while introducing this new feature, new liquidity, new efficiency
combining the dot-samma ecosystem. And then overall, this will benefit a great deal for the users because so now that this bridge will be launched, there will be exchange support as well. So right now, AUSD is supporting
supported on the COCOIN only on the color side. So this will also allow exchange to support the AUSD on the color side. And then they are effectively one trading pair on the exchange, and then the exchange can manage the liquidity on
both trains. And obviously, when there's trading venues, your AUSD is as good. You can bridge it over and trade on any of the venues on either side. Either side don't just mean Akala and Karura, but also Tokudau and Kusama.
So this will hopefully will actually give a lot more room for liquidity growth and also using a market mechanism to drive the liquidity across the Hoku da Enkutsama ecosystem. And then for users, there's a lot more arbitrage opportunities as well for traders.
And because exchanges will support both, and then trading venues on both sides, whether it's locally on a car or carer, or remotely on other parachains, will give folks a lot of upper charge opportunities. And of course, effectively, there will also help stability of a USD.
And then another thing is if you are KR, KSM holder, you don't have to think you're kind of completely segregated from the dot ecosystem. Now there is an actual linkage, right? So effectively the credit that you generate, the AUSD that you generate, is as good as the
those are generated from the dot side. And then you can actually, if you don't hold any dot, right, then you can still participate in the dot ecosystem activity through using your KR or KSM asset and then to generate a USD and bridge it over and then to participate. And vice versa, because a lot
of the dog and a sayholders that may not necessarily, you know, also hold assets on the career or because I must die and this effectively allows them to bring their capital and the equity to the ecosystem where, you know, there's more activity or more attractive for them to participate.
identifying, I guess, economically the doc Samarit system. So, yeah, so that's kind of the whole thing. For this question, you kind of touched on this, but I think the questions someone asked on SIDO was around being able to bring KSM or KAR themselves over to Akala and Polkada, like
without minting a usd is that is that also possible? Yeah that's possible. So that's just a normal bridge function. So the one-hole bridge or later on the substrate bridge can do that out of the box. So effectively you just like you would be a wrap version, right? Wrap to
whatever the bridge provides. So yeah, so you can bring KSM over, bring KR over, there will be a money market launched on a car so you can't have to bridge those over and then you know land them borrow there. And then we can also do something that's fancy, it's like you can actually
deposit locally, KSM or KR on the career side and then it will automatically do a remote call onto the smart contract on a car or money market like Pike and then start to earn deposit you'd rent so you can do something like that. So this is real like sort of remote
cross-chain. Effectively your main store is setting up on a color but you can open those shops everywhere across the multi-chain ecosystem. Cool. We'll continue going through some questions.
questions if anyone else in the Twitter space here wants to come up on, we've got one question going on now. I'll invite them on.
Hey, go now, like I had a pv question. All right. Okay. Hello. Good morning here. So we just want to find out if there are technical documentation about everything that Bet has said.
because we are still building a making integration on our projects and of course anything that will promote the adoption of the dot-samma ecosystem, we are willing and ready to look at it.
there are documentation where do we find them because you've said quite a lot of things that are a little bit confusing so we would want to look at it from technical point of view and the integration and then see how easy it is to be able to integrate it on
and all that. Yeah, sure. So we can share the forum posts that already outlined the stuff that I set probably easier to read than actually listen to me in an abstract way. And then we can also provide the padded so you can look into the padded
And then another thing is we will be releasing SDK for doing all this operation. So you can also use the SDK to perform any actions as well. So those are probably the three things you can look at. OK, yeah. So is that any?
roadmap or timeframe to you know what you're like I mean SDK in terms of releasing the SDK the other roadmap we can keep track of and see oh yes so yeah so technically they're all
ready. So, and then the goal will be, you know, this palette and parameter setting can start first, and then the second, after this, then it will be the front end depth SDK, then it will be go live, right. So,
So they're all kind of like technically already ready and we can actually ready some so you'll probably looking at next week or so We can start looking at voting on these parameters and then the week after or two weeks after that maybe early August then all the front-end SDK stuff can be released
Okay, thank you very much. Yeah, by the way, we're building on the moon beam protocol. So yeah, both. Cool. Yeah, yeah. Thank you. Cool. Awesome. Thanks for the question.
Cool. We've got other questions on this slide, oh, maybe we can go through some of those. Yeah, sure. So the first one is you kind of touched on this, but how does the quota limit?
the risk and what would enable you to increase the quota? Yeah, so basically this is determined by the size and also revenue from each chain. And then when we say, let's say, from Correra to Akala,
the quota is 1.1 million and this effectively is saying if you actually transfer that much to a color, a color is exposed to that much risk. So let's just say everything failed. The whole Kutama failed and then the whole bridge failed. Then you effectively
If the maximum you will lose is 1.1 million. If you do lose that much AUSD and can you recover? The way to recover is multiple streams, not different from normally how we recover AUSD bad debt.
the AUSD Treasury, whether it has Treasury surplus, they can put it down or coming from auction off the ACA or KR Treasury or in the AUSD case there's also collected collateral that you can also auction off. So there's basically judging
the market cap of each chain as well as the ability for the treasury to be able to pay the down that way. So yeah, so that's why it's actually very very conservative because we're taking the whole risk as the potential exposure and then judging that to come up with the number of
And then to increase that number then you effectively work backwards on Understanding where each chain is currently at right how much surplus that you're generating and how much business that you're growing as well as how The market cap is growing as well as a chain so those factors will
kind of affects the quota as well. And also, need to bear in mind is this goes both ways. So effectively you have it goes, you know, because the AOS becomes one way and then also comes the other way.
way. So they may not be binding all the time. But this is like the sort of the constraint or the worst case scenario that we are setting ourselves so we don't go over.
Cool. Someone asked why are you deciding to use wormhole as a bridge and not XCM? There's no XCM yet. So we're kind of closely monitoring the substrate native bridge right now. And then yeah, so
So it's not quite ready yet and it's not going to be ready for the next three months, six months. So we kind of design it in a way that we can use an alternative bridge and then once the substrate native bridge for relay chain is ready, then we can upgrade to it.
One thing just to add to that is even though this is using wormhole, like Betty's mentioned a few times, there's no wrapped asset. So it is native USD that you are using on each respective network. So there's no
wrapping that's going on. Yep, and also for people who are maybe a little bit newer to XEM, so all the other chains that, let's say a collar on the polka-dead side are interacting with, like for example a collar and a
DX or Akala and ASTAR. That is all using XEM. But what can't be done with XEM right now is Akala Tikurura because that's Polkada Tikusama. So what Betty was referring to, there will be basically an XEM bridge between Polkada and Kusama but that's
at least six months out, most likely longer. So we don't have time to wait for that. So we're going forward with wormhole and then that'll get us, you know, that'll get all this up and running in the meantime and then we can use the XM bridge as well whenever that's ready.
Yeah, so the main thing was bridge is message passing. The fungibility is actually guarantees by the pilot that were installed on Kuruura. So that's why we're relatively, you know, comfortable with this approach.
And also knowing that we can actually seamlessly upgrade that also adds perspective on how this will pan out in a slightly longer term as to substrate native sort of bridge being developed.
Someone else asked, does this mean that I'll be able to send a USD from Correra to an exchange? Yeah, once, so the pilot wouldn't
in May, but there will be exchange announcement to actually support AUSD Correra. So you have to check with the exchange that you want to withdraw in deposit, AUSD from Correra. So right now,
only AUSD Akala I supported, but there will be additional support. But you have to make sure your chat was exchanged before you perform any actions. And then last question was, do I have to do anything to my AUSD?
So, all the effort that we put in like, you know, step one and then also the current palette is so that users are not affected. So, as the depth are not so much affected. Yeah. And then, yeah.
And then the user front, like for users, will be able to perform this actions will probably be early August or probably looking at that. Cool. So that's all the questions online. We've got 10
or 11 minutes or so. If anyone has any other questions about the AUSD fungibility palette or if you have any general questions really at all about Akala, Kaurura, Pokadat, feel free to raise your hand and
Any closing thoughts or comments, buddy? Yeah, so yeah, so this is my same technical but then I think ultimately this is like quite a huge
the user oriented solution is just this particular step that we're completing is a technical vulnerability pilot. And the step 4, if you look at the forum post that we had, is actually deploying the front end to support this. And yeah, so hopefully that's actually make it quite smoothly.
that you can do this operation. >> Cool. So, yeah, keep -- if you want to read more and haven't read the forum post that Buddy wrote, it's pinned right here in the Twitter space right here. And then keep
Just following our channels for updates on voting and then of course when this goes live we'll also be announcing that along with several other things that are about to go live along with this. So thanks for everyone's attention. This has been recorded so we'll go ahead and
download this and post it on YouTube in case you want to relisten to any of this or share. And other than that, thanks for everyone's time. And we'll definitely see you again sometime soon. Yeah, I appreciate everyone being here. Thanks. Great. Thank you. Bye.