Community Call

Recorded: Aug. 30, 2022 Duration: 0:08:06

Player

Snippets

Hey everyone.
Aevanisha
I don't know if you can hear you, Boris, but I can. How you doing?
I'm doing great, you know, are you done? Yeah, that's about it. I think we need to make a co-oper with Speaker as well. We need it in a minute.
- See ya, guys. - It's done. - Yeah, that was you.
Hello, everyone.
Yeah, go ahead. Right, I don't know if we're going to give it a minute or two for any more people to join. We've got quite a long list of questions to go through today. Some people really like asking those questions. So I think we're going to have to be quick to get all this done in an hour. Yeah, let's see how we go.
We can give them one more minute.
I'm looking at them now. We've probably got about 30 or 40 questions. Some of them are 5 or 6 or 7 from the same person. So we'll need to go a bit quicker there.
But yeah, we've got a decent range of people who have asked questions today. That's good. Some of the questions will be shorter than others. There's one we can do at the beginning while we're waiting for everyone else to arrive. From the voice.
when merge. When merge between not not merge with a G merge has emerged and dice. Oh when Merch and that's oh well well.
That's a good question. So we did get some t-shirts and apply some of the community members mostly from from Bergen did get a t-shirt I think three or four of them in total maybe but merch well
I would actually like to welcome some distance like. Probably, as soon as we start deploying the products, we're going to have some new brands of
you know, Kiwi and so forth. It might be a good opportunity for us to do a more likable, sliverless, techy and more kind of mainstream.
I'm a T-shirt guy. I would like to. What do you think John? I think that's a very gentle question to start off as right.
talking about merchandise. So yeah, we've seen some extra small ones. I would not fit the next small t-shirt. I'll be honest.
Yeah, let's get on with the big list then because there are plenty of questions to go through. Here to the right. What I would propose is maybe start with a general update. Sure. Come on, if you want to go first. Up to you. You can go. And then I will chip in. Okay. So the big news for us is, well, let's
Let's split it into a couple of different categories. We'll start with our highest profile customer in terms of Nougat's bank. We have a key deadline for the next round of work we're delivering for them. In the middle of September, that's some more advanced CBDC sandbox features that they've asked us to work on. That's on track.
also be making the code from the first round of development public and that will coincide with a joint blog post with Novice Bank for that one. So they seem to be happy the work we're doing is going well. The testing is opening up a bit wider. We're sure there'll be more for us to do with them.
in the near future. But the big deadline for us is mid September. That's the first point. We are very, very near on a side note to finally turning off the last part of Nami1. Everybody who has a balance on Nami1 will have the option if they choose to to take
whatever tokens are left in the system out. We need to publish the payloads. We have to do a couple of actual rounds of internal checks. We run a couple of simulators to make sure that everybody could withdraw and you can. So we'll publish the payloads and the guide on how to actually use those payloads to withdraw. It'll be a little bit technical.
hopefully it doesn't apply to too many accounts and that will be coming relatively soon. But maybe the biggest thing that we have been working on is the Nami 2 to Nami 3 upgrade. Now this will probably be a separate deployment. We'll need to confirm the details a little bit further down the line. But one of the questions that we can preempt
I think Jan asked us about this one is can we give you more information about Nami3, why are we upgrading the system, what are the benefits, what's the big story effectively? There are a number of different things we can talk about in terms of why we chose to do it. Those are you that know
in terms of Nome 2 and how it works today, it is EVM compatible. That means there are some small trade-offs when it comes to deploying code on Nome 2. We introduce a little bit of an overhead in terms of smart contract sizes so if you're trying to deploy a very large smart contract on Nome 2,
to the, you might run into this issue where it might just about fit on Ethereum, it might not fit on Nami2 without some refactoring. And that's been a problem for some of the products we've been looking to deploy. It's much easier to do it in the world that we're moving to with Nami3. So a couple, I might leave the

FAQ on Community Call | Twitter Space Recording

What is the big news for the company?
The big news for the company is that they have a key deadline for the next round of work they're delivering for Novus Bank in the middle of September, and they're very near to finally turning off the last part of Nami1.
What is the deadline for the next round of work for Novus Bank?
The deadline for the next round of work for Novus Bank is in the middle of September.
What are some advanced CBDC sandbox features that Nougat's bank has asked for?
Nougat's bank has asked for some more advanced CBDC sandbox features in the next round of work that the company is delivering.
What will coincide with the joint blog post with Novus Bank?
The code from the first round of development will coincide with the joint blog post with Novus Bank.
What is the status of testing with Novus Bank?
Testing with Novus Bank is opening up a bit wider, and the company seems to be happy with the work they've done so far.
What is the plan for turning off the last part of Nami1?
The company will be publishing payloads and a guide on how to use those payloads to withdraw any remaining tokens from Nami1 accounts. They also need to run a couple of simulators to make sure that everybody could withdraw before they turn off the last part of Nami1.
What is the upgrade the company is working on?
The company is working on the Nami2 to Nami3 upgrade.
What are some issues with deploying code on Nami2?
If you're trying to deploy a very large smart contract on Nami2, it might not fit without some refactoring because Nami2 is EVM compatible.
What is the benefit of the world that the company is moving to with Nami3?
It's much easier to deploy code on Nami3 because it is not EVM compatible and therefore, there are no trade-offs in smart contract size.
What is the ETA for the Nami2 to Nami3 upgrade?
The company is not ready to confirm the details of the Nami2 to Nami3 upgrade deployment yet.