Okay, we are back. I think there are a little bit of trouble today with Twitter space because even in the beginning there was technical problem. I think now we are back on track and even Suzan is back. So we were speaking
about the importance of having this game on it. So if you can go, yeah, please. Oh, I'll just pick up from where I left off. Yeah. So what I was trying to explain is that the ICS 7 to 1 protocol is by nature more complex than
and ICS-20 because it has to pass more information, has to manage more information on all the participating chains, and it also has to pass more information between chains. Any NFT non-fungible token or token for short,
has off-chain metadata and on-chain metadata to manage. And the class to which NFTs belong to also has some meta class level metadata to manage. So when we design the I7 to I1 protocol,
We have to make sure that the necessary information is encoded in the packet data. So enough information is available to the receiving chase so that tokens can be constructed, can be minted correctly in the destination
For example, a lot of the digital arts oriented NFT collectibles, they for to support interoperability, usually they conform to some kind of off-chain metadata for
formats are very similar to what OpenC has specified. Usually it's a read only JSON file stored off-chain that has a spec predefined format. But for other NFT applications, not just digital art collectibles for
For example, like an NFT rental marketplace, we also need some on-chain metadata stored at either the class level or even the token level. For example, the rental rate, I mean, collect
to be collected by the original owner, things like that. So, and when you add in the complexity that some change in the customer network, use Coswasm virtual machines and other change use native
modules and they have different ways of managing these token level metadata and class level metadata. So how we make sure that the specification has enough details and the clarity to make sure that whoever implements
this specification using different language or different technologies will still have the can be can interact with each other correctly. So we spend a lot of time in a community to coordinate the creation and
the finalization of the specification actually took us almost 10 months, maybe 10 months, to have the first version of specification emerged by the IPC/IPC core team. And as we are gearing up for the game of NFTs,
As the GoLand implementation team, we had very frequent interaction with the other few teams in the community. They used Wassam smart contracts and we have to work out a lot of the issues about what I just mentioned the management and
communication of token level and class level metadata in a specification. So that's basically why we have this, we put a lot of effort into the specification and its implementation in different languages.
So that basically tells us the complexity of this standard. So that's why we need to have, we want to focus on the whole phase, the first phase on trying out the protocol is
in like a real world setting to make sure that the protocol is implemented correctly in the Golan and rust smart contracts and to make sure that these different chains using different implementations and settings can work together.
using the same protocol. And during the testing, hopefully we can find the nuances in implementations to maybe adjust either the specification or implementation and hopefully we can find some bugs in either implementation.
So that before we can put this, as I said, it's a very fundamental ICS standard, which enables the interaction of a whole set of tokens, it's a non-fungible tokens in our ecosystem, we have to be sure, we have to be doubly sure that it's protocol.
is implemented, is designed and implemented correctly. So that's why we need this game. I mean, because it's not just about one chain, it's about multiple chains and using different potentially different implementations of this new spec. So that's why we need this game.
Thank you, and I think you pointed out an important solution because this game on this will also solve problems that can be generated by having multiple specifications.
And if I'm correct, you also have been the DINN first NFT transfer, interaction NFT transfer on Iris Network. And it was using interchain accounts, right? You mean the
This ICS 721 doesn't really require or depend on the inner chain account, but of course you can use these two application level protocols that together. I mean, at the application layer, I'm user can choose to use them, combine them. And so basically once you have a distrust,
for the community to understand that you basically will be able, for example, to move an NFT's from Iris Network to Stargates or Omni-Clicks or whatever chain in the Cosmos ecosystem. And we also adopt
We actually also adopt or borrow this newly added feature of this memo field from SCS-21. In middle layer, I mean people can develop a middleware, I mean it's also an application layer ICS standard.
so that they can process this whatever people put into this memo field to enable some kind of application layer enhancement. For example, so automatically transfer an NFT from one chain to another and list it in the destination chains NFT marketplace, something like that.
I think this is absolutely a much needed feature in the interchain. I think this will also improve the security. Maybe Susanna can speak a bit about this because of having many
specification, we can lead them to security problems. So, do you think that in the inter-shane ecosystem, having this standard, we like to improve security, and maybe also create a new product opportunity?
Well, I think the interchange standard for NFT transfer, I mean, it's been specified and it is an interchange standard. That's clearly like a new product feature in itself. So, yes, definitely it's new opportunities there in terms of security.
Well, I think the point of the incentivized testnet is to make sure that this specification when implemented is as secure as possible and working correctly, as Highfeng already mentioned. So I guess the whole point of the incentivized testnet is to
ensure that we have the best security guarantees possible and any bugs or problems are picked up in this incentivized testnet phase. So I think in terms of security, that's kind of one of the factors for wanting to run an incentivized testnet.
I guess is the question a bit more around if having a standard improves the security of the application. And I mean, yes, it's just, it's a bit more of a solid engineering process to specify and then implement. So I'm not, is that, is that
Because it's the question. Yeah, I was running from the user perspective because it can be difficult for users to navigate to multiple wallets, multiple way to interact with NFTs. So I think a standard, especially this coming from the ABEC and
actually add the user and especially adoption because it is very important for adoption that we often have to use the most simple solution to interact with an episode that will be definitely one of the main features of the crypto ecosystem looking forward
of the end of it. So in terms of having a standard, it just means that everyone that's buying into a standard can use this application. And that's clearly much better for UX. And that's likely why this standard was also made with the ERC-721.
standard in mind as well, given that energies are, like we can't ignore, that energies are massive in Ethereum as well. So being able to interact with their standard and be compatible with that as well is clearly very important as well. And it's just better from a user perspective. You're likely not really going to be thinking
about the spec on that level, you're just going to be thinking about moving your NFTs around through your wallets and stuff. And so having a standard that multiple chains are buying into is just going to make that user experience way better for you as a user. Yeah. And also something I want to add is about the specification is
Actually, we borrowed a lot of the same principles from ICS-21, like some of the desired properties of this protocol like preservation of non-foundrability, which means that only one instance of any token is live across all the IVC-connected blockchains.
So we'll make sure that you cannot have two active instances of the same NFT living in two different chains. I mean, if the protocol, if all the chain's participates change implement the protocol correctly, and that is one thing that we'll test in the game, right? Make sure that
this property is maintained. And also like all the permission lists token transfer symmetric, symmetric property and fault containment, all these desired properties of ICS-20 will be maintained in ICS-71.
which of course we will also test in the game. So, yeah. And also there is some during the write-up of the specification, we have some discussions about metadata management, because I said this is one aspect that is much
that is more complex than I say it's 20. And I think the community reached an agreement at the early stage of the specification, which is for the first version of this specification, we want to make it simple.
enough so that implementation will be easy and less prone to error. So that we will assume that the off-chain metadata, the immutability of off-chain metadata will be guaranteed
by the source chain. But in terms of on-chain metadata, different applications change that interact with each other that depend on certain fields, certain properties in the on-chain metadata. They can decide on their own
whether they want the on-chain metadata to be updateable, I mean, down the stream. So these are some things that we will also test out in some of the games, competitions in this game of NFTs. So it's very flexible. So the assumptions are,
based on the community consensus at this moment. And in the future, we will hopefully we will upgrade this specification based on the experience and lessons learned during the actual use of the specification in real world scenarios.
And we may decide later to upgrade it, to make the off-chain metadata mutability management more complete or provide richer future capabilities in that aspect.
Thank you and I think there is also the right time if there is any community member that have questions I can jump on the call or make a question in the comment section and
And also, one thing is that I want to highlight about this demo and this piece is that the community will also be able to cover and follow the
event and participate and so understand better all the dynamics around the interchains and the how it is important that web is standard in the interchains ecosystem, IBC ecosystem.
Also, one thing that I want to look a bit deeper is with Susanna. When we will have this sort of standard and we will have more
testing and how it will coordinate with the change. It will be through documentation or basically we will raise awareness about this standard and push for adoption.
So, I mean just a preface, I've not personally been leading a development of this application at all, so it's been the responsibility of High Fang and Beyoncé and they've been coordinating with Juno, Stargate, Gravity, Bridge.
I'm probably ever changed, I'm sure as well. So we will of course support in their adoption efforts, but I'm not personally leading the project. I guess encouraging adoption, having more visibility of this
change standard is going to help adoption. That's one of the points of this incentivized testnet is to let people know that this functionality actually exists and that they can start using it and start developing their own products and features like using this standard and product. I mean there's a few NFT zones already
in the cosmos, which would clearly have a use case for the application, but then expanding upon that. I'm sure Hifeng probably has some more ideas. But yeah, I haven't personally planned the adoption rollout. I guess this is the first step.
Maybe Hi-Feng has more in silence. Yeah, so basically that's why I think we divide the game into phases. The first phase is to test out the correctness and robustness of the protocol implementation itself. And the second phase will be focusing on, it's a hackathon. It will be organized.
a Hikakata in the teams from the Cosmos ecosystem are welcome to join to take advantage of the existing connotations and build applications and tools on top of that. And we will have funding support from these
I mean, co-sponsoring teams like Iris Hub, I see, I know, Iris Hub, Gravity Bridge, Stargaze, Juno Arc Protocol, and maybe Arctic as well, right? So these co-sponsors will provide funding support.
And we have also in contact with some investment, crypto investment companies, teams who have shown so far strong interest in providing funding support for some of the winners of the second phase hackathon. So that that's part of the,
visit development and rollout plan. I mean we want to get that started, we have to get started in a second phase. So more teams, more developers will get to understand the protocol, how it works during the first
phase and we want to attract a lot of application builders to build creative, innovative applications and on top of that. I think we are very similar to the game of change. We are in the process of setting
up a website for the game of the FTES as well. I mean, that website hopefully we will make it a sort of a hub where different teams, development teams, interested in the NFTs, innovations, especially interchain NFTs, innovations can
use as a reference point for use development tools and information requirements and things like that. I think maybe the best thing is to, so one of the success criteria for this game of MFT is to make this new
I think this is a very important point and it can just do my research.
what will be this game on Netflix because it will basically attest of the ECS 7 to 1 and also it will open to new opportunity for ecosystem for more people to understand and use this customization and I think maybe it will also happen
that new project will burn from this kind of event because it happened in the past so it also helped the option of the inter chain ecosystem and also helped the Abit's help to kind of add this position of funding the main development around this specific
use case of an FT. So maybe I don't know I'm trying to imagine what will happen with this standard maybe NFTs aggregators specific wall at the round really many use cases that could burn from an event like this and it will be definitely very interesting to see to develop
So, Aiseng, thank you so much for your explanation. You really did a great job to explain all the facts of the event, the NFC standard, the white is important for the ecosystem. Do you have any last word that you want or any last talk about it?
Yeah, I think that's about it. If people have questions that I can answer, I'll be happy to answer to questions.
Sure, so let's wait a couple of minutes to see if there is any question coming. Maybe, Osteususana, do you have any last word that can sum our conversation?
Yeah, I mean, well, I would summarize that is saying NF cross chain NFT transfer is has similarities to non to fun to funge of all token transfer, but the packet data has many more fields. It's a bit more complicated.
So that's what the whole point of this proposal is is really to make sure we have higher security guarantees, find any bugs, make sure it's working as expected.
And it's kind of beneficial for the community to stress test the future, getting as many people involved in a centralized test net, generally always going to have positive outcomes. And it's really a useful primitive for the in-chain ecosystem.
Thank you Susanna and if there isn't any question coming I think we can close the conversation. Thank you Susanna, thank you A-Fanger. I think this has been extremely helpful to me.
to the community to understand that the upcoming event and the upcoming proposal on the ABBA. And I'm personally looking forward for it, and thank you everyone to participate. - Thanks. Thanks, Rob. - Thank you very much.