Dialogue with the founder of Sui: Sui means water, and I hope that the network performance will be as free and sufficient as water

22-08-23 12:40
Read this article in 53 Minutes
总结 AI summary
View the summary 收起
Original source: Mynft Twitter Space
Original compilation: Chain catcher


On August 18th, the Mynft team and Mysten Labs co-founded Sam Blackshear, the creator of the Move language, conducted an in-depth interview on Twitter Space to discuss the characteristics of the Move language and the development plan of the Sui blockchain developed by Mysten Labs. The following is the chain catcher's summary of the conversation:



Mynft Team: Hello everyone, I am Millet from Mynft, and I am the host of today’s conversation. Thank you for accepting the invitation to join us for this AMA.


First of all congratulations to you and MystenLabs on your success. So we've sent you a list of questions before, is there anything that needs to be adjusted?


Sam Blackshear: Nice to meet you and thank you for the invitation. No, I think it's a good list of questions and I'd be happy to answer them all.


Mynft Team: There has been a lot of talk about the Move project lately. For example, what is the difference between Move and other languages, such as Solidity, and what are the advantages of Move. How can other programmers learn Move, because it is said that Move programmers are paid very well, and of course they work a lot. Then everyone is also very curious about how Sui won the attention and support of top venture capital in the case of a bearish market, and now the competition in Layer 1 is also very fierce. To know the answers to these questions, of course, we need Sam to help us reveal it. He is one of the founders and CTO of MystenLabs.


We have two main parts today, first Sam will answer the previous list of questions from our community and media partners and then Q&A session.


List of Questions


Mynft Team: Then we start AMA . Sam, can you introduce yourself and the project?


Sam Blackshear: I'm Sam from Mysten Labs Founder and CTO, founder of Move. I mainly work on static analysis, I have also worked on Diem and Libra projects. At the beginning of my career, I was doing programming language research, and I was also a Ph. D. I made some audit tools that can automatically find bugs.


Then let me tell you how I switched from language research to the encryption industry. I was a doctoral student at the University of Colorado before, doing research on programming languages, doing static analysis, and doing some automatic bug-finding tools. This is very interesting and very mathematical. All you have to do is to find the problem and answer the project implementation questions. In this process, you can always find more problems and more alternative solutions (semantic solutions), and sometimes report "false positive" behaviors. Actually none of these behaviors happen.


So you can always improve, but there is never a definite answer. By designing very smart models, you can predict program behavior, find bugs and understand how the code works. I spent many years doing these academic research before, I would make some bug finding tools, let it run, and then I would feel quite fulfilled after I found the bug.


At the end of my Ph.D., I had an internship opportunity at Facebook, which should have been in early 2013 or 14, when Facebook was moving from web-first to Mobile-first transformation. When it was released on the mobile terminal, there were actually some problems at that time. At that time, they had a bug on the mobile side, and that problem existed for two weeks. The same problem can actually be fixed in a day or an hour on the web side, so they invested a lot to solve the bug on the mobile side.


When I was an intern, I did the same kind of work, finding and fixing problems. At that time, I also had the opportunity to communicate with many programmers. They gave me a lot of real-time feedback and told me how to make things better and different. At that time, I had an idea, hoping to do cross work between R&D and research. So I joined Facebook after graduating, and I have done static program analysis for many years, which is to make a tool for automatically finding bugs, and then look at some empty references, find some buffers for overload, look at data requisition, and look at some security issues. Look at the new applications of static program analysis other than finding bugs, such as how to better keep the code, or how to port the code to a new framework, how to help security engineers be more productive, and so on.


This job is very interesting, but you will find that in the end you will know how to design languages, design frameworks, how to ensure security, etc., and you will hate it a bit For problems brought by others, we will consider whether we can do more things, such as how to design the language from the beginning to make it safer and more bug-proof, and then support some work, such as verification. You'll consider how you can help programmers write code that is safer and easier to assemble with other software.


Then I was very lucky. In 2018, I had the opportunity to do this at Facebook. In fact, it was the Libra project, which was a highly confidential project at the time , And then I found a lot of experts to do research such as distributed systems, cryptography, databases, etc. Then what I was asked to do at the time was to look at the language, which is why I came up with Move later, because at that time I became interested in distributed systems and cryptography, so I started to look at the field of encryption. Friends of the founders, we also built a very harmonious working relationship at that time.


At that time, we had a lot of interesting ideas about how to build the next generation of blockchain. These things may be more ambitious, which could not be done with Libra before arrived. Then we founded Mysten Labs, and we followed Libra for a long time, but later found that it was unable to go online, so we decided to go to the vast world of Web3.


So in November last year, we jumped out and studied the design of Sui from scratch, thinking about how to adapt it to Move and what advantages it has , and it's exciting to think of what new things can be built on top of it. So basically this is my career, how I went from research to crypto and became a CTO of a startup.


Mynft Team: Your experience is very interesting, because you are actually moving from Web2 to Web3. You have a compound background of academics and industry research, and you are also deeply involved in the fields of bug finding, static analysis and so on. Just now you mentioned composability, which is very important for the next generation of blockchain, and we will discuss this in detail later.


You also talked about the construction of the next generation blockchain, and the Sui you are now admiring. So we actually want to know why you and your partners founded Mysten Labs? Or, for example, how did you choose the name first?


Sam Blackshear: About Mysten Labs, its name doesn’t mean much. We had other ideas at the time as well, but I thought it would be a good fit because I ended up signing some legal documents with that name, so I chose that.


Sui actually thought a lot at the time and consulted some professionals. I ended up with Sui, which means water in Japanese and other languages. Then I hope that the block space, transactions, throughput, etc. on our platform are free to flow and sufficient, just like water. At the same time, water is everywhere and is good for us, so I think this brand name is good. From a technical point of view, because our founders have been studying the Libra project for several years, they have spent a lot of effort, learned a lot, and have a lot of good inspiration.


At the same time, Libra was also ambitious at the time. In 2018, everyone said that they hoped that it would become an "Ethereum killer", that is, to draw some designs from Ethereum, but do better. Libra was originally designed as a general-purpose smart contract platform, but considering the regulatory requirements and wanting to push it to the market quickly, we finally think it should be a payment and settlement system, and we don’t have to consider processing a large number of transactions. Orders, because most orders will be carried out between off-chain virtual asset service providers for privacy reasons. We also don't need to consider the issue of expansion, because payments and accounts basically don't take up too much space. We also don’t plan to make those fancy things, such as NFT, etc., which will take up more space.


As for the program, in fact, we are more concerned about how to make it run compliance policies and how to prevent assets from disappearing or being sent to the wrong place. So we did a lot of this kind of work in the early days, and then we thought about how to reduce the defects of the Libra project and build the next generation of blockchain. For example, my colleague George is a senior system expert. When he was in Libra, he participated in projects such as fast payment.


So we basically have two major projects, one is Narwhal and Tusk (consensus protocol), one is fast payment. Then we also started to contact customers, especially in the game field, to understand their needs. Basically, they will have a demand for TPS.


In fact, it is very important to take something out of a system and then make adaptive modifications to it so that it can handle various throughputs and transactions. Difficult, of course, does not mean impossible. But that said, you're starting from scratch, so there are a lot of difficulties and differences. So basically this is what we do. At the beginning, we did fast payments, and then we considered what else to do besides payments, whether we can do other transactions that can be paid quickly. For example, if they don't need to place an order, they can pay directly and quickly, and if they need to place an order, they can go through a normal process.


So basically we drew some resources from Facebook, and then built such a system and Move, we are confident that it can be expanded and adapted to any throughput or storage requirements. Then you can do it in a Web2 way, where the verifier can be a single machine or a group of machines. (If you have more needs, you can distribute them across machines). You know that users and companies will have greater needs, so in order to meet this demand, we created Mysten Labs and want to build a new layer of blockchain. We hope that this system can be expanded to meet any demand without facing bottlenecks in cost, storage, and throughput.


Mynft Team: Yes, Sui actually means water in Chinese. You also talked about the shortcomings of Libra, and the increase of TPS in order to be able to build on the Libra fast payment system, and some limitations of payment or blockchain that you hope to solve. The things you mentioned, such as payment, are actually still managed by some centralized organizations. This brings us to another problem that has plagued the blockchain field for many years, that is, the impossible triangle, how to balance scalability, security and decentralization. How do you understand this question? Is there a solution?


Sam Blackshear: That's an interesting question, with trade-offs and so on. I think there is actually a "fourth fulcrum" that can be considered, and that is its utility. Because no matter which one you choose, it must be valid for the protocol and for the developers. If in the end your solution is "not useful", then maybe you solved the technical problem, but you didn't solve the business problem.


I think first of all, if you need utility, it must consider its scalability, and of course security must also be considered. Of course, decentralization should also be considered, but different people have different definitions of decentralization. In contrast, if you ask someone what security or scalability is like, I think these questions will be more absolute, or the correct answer will be less, then this actually implies a little bit, that is, there will actually be greater design space.


So, regarding Sui, when it comes to decentralization, there are actually different aspects to consider, you can consider the number of verifiers, you can consider the internal state distribution. You might think about the number of full nodes, you might think about the threshold in terms of cost to run a validator, or the threshold in terms of hardware required, all of these factors are important.


Sometimes we pick out precise definitions for these things. So for me, if I'm going to do something different on the trilemma, if we want to have more throughput and more storage, we're going to need more hardware resources. This is not something that can be done casually, if you need to do more work, you will need more hardware.


Many people are now splitting the state by sharding at the protocol level, and I don't agree with that. We think what's useful about the blockchain or the blockchain vision is that you have all the assets in the world, like all the smart contracts, and they're all sitting together and they're able to talk to each other. You can send a transaction and it will involve all transactions. All the finance-related components come together, and then you only need one function to call out, and everything is done.


You can add friction between different assets, different smart contracts, and different use cases. Then you basically hand the problem over to the programmers and users to figure it out and figure out how to bridge the gap. I think blockchain is supposed to remove friction.


What Sui does is, if validators need to take on more throughput, I ask them to use more hardware, more storage. But we're not going to compromise and say it's going to be very expensive to make the work validators do. Otherwise, then I think you'll end up with an oligopoly where validators are the two giants on the network and no one can afford to check the work they're doing.


So one of the things we're doing to help with this is our data model allows for an alternative, which is non-voting validation server node, called a Sparse node. It works the same as being a validator, just without voting.


Sparse node starts with a set of basic data, such as some objects you care about, some addresses you care about, it can re-do and check the work of the validator, Only for these specific routes. For example, if you are a wallet, you can become a Sparse node and only track specific coins, such as NFTs, or game items that are unique to you. You can replay all transactions and check that validators are honest.


If you're running a game, you can run game servers and see what validators are doing to your game state and your players' game state, but only Care about yourself, don't care about others. So this is better and cheaper than running a full node.


Because considering storage and transactions, if you run a full node, it will be more expensive. But if you only think about one part of the network, only your own part, it's actually pretty cheap. This is all thanks to Sui's data model, which can clarify the connection between transactions and the objects you care about. So I think that's how we can solve the trilemma, of course you need to have stronger validators, but that doesn't mean you should compromise on the 3rd party that checks on the validators. Therefore, although there will be higher requirements for verifiers, their integrity can still be guaranteed because of the existence of Sparse nodes.


Mynft Team: It was really full of dry goods just now, and the brain was running at high speed, so you did not do partitioning or sharding in the blockchain field Trendy things, but use Sui to allocate tasks on demand, such as running validator nodes, etc., which are equivalent to the rewards you receive, which can help us interpret the abstract perspective of.


You also mentioned that you think the way of the trilemma is a kind of trade-off, and you think that to solve the basic The above is a trade-off. Is this an approach you agree with? Because in your twitter, you talked about blockchain as a service that can be used by large companies. I can understand, is this how you think Sui is coming to Web2? It is for use by large companies, but without sacrificing decentralization.


Sam Blackshear: Yeah, that's right. I think if you're going to tap into an audience outside of the current cryptocurrency space, you really need to have scalability beyond the current blockchain. So that's what we're trying to provide. Moreover, Sui is carrying the torch on the important journey of decentralization and security.


Sui is very concerned about user use cases and things that already exist on the blockchain, such as DeFi is a liquidity engine that drives a lot of value on the blockchain , For example, NFT is also very important for branding and game building. For example, there are also many local use cases for cryptocurrencies. So what we're really concerned about is the mix of old and new, and we think we're going to be able to do old stuff with better programs, say safer programs, lower fees.


I think we will be able to have the developer experience, scalability, necessary superstructure, etc. to get into web2 well and attract mainstream and enterprise use cases. So we really care about those two things. We need old parts that are also interesting things, and then we need new things that can benefit from that. I don't think it's really an alternative, I think you really need a combination of both to make this thing work.


Mynft Team: Interesting point is that Sui claims to be the next generation Layer1. So compared with other L1 public chains such as Ethereum and Avalanche, what do you think is your uniqueness or advantage?


Sam Blackshear: I think these are all different projects. One of our differences is that we have a data model that reflects the transaction and final results. This makes the relationship between a transaction and what it does so explicit that you don't even have to run the transaction to see it. This makes it easy to tell how transactions are related, and also makes it easy to tell, for example, who was the last transaction touched when you look at an object. Or if you look at traders, you want to look at related transactions, what is the object of its operation, and what is it going to do. This is the basis of all our progress in scalability, and then in usability as well.


If you look at the traditional blockchain architecture, it has a lot of sequential models, which makes it very difficult to scale. First, there are a bunch of transactions coming in, and your computer starts working on these transactions, based on the global consensus of course. We have to sort them all, and then execute the transaction, and many systems need to be in order, even though there may be no relationship between them. You just need to do the trades sequentially, because that's the easiest and most obvious way to do it right.


There is another bottleneck. These transactions will eventually have a result that needs to be written back to the database. This database exists in the form of a tree, where your accounts, balances, user accounts and other information are displayed, at the root, and then you have to update these changes all the way to the top, forming a new tree, with The state is getting bigger and bigger, and the tree is getting bigger and bigger. When this thing gets too big to fit in memory, it becomes very difficult to run it in a faster and more efficient manner.


So basically you have these different, big, sequential bottlenecks, and then that makes the throughput and storage of the blockchain difficult expand. We are trying to remove or mitigate these sequential bottlenecks as much as possible.


So, as far as the consensus part is concerned, because we can tell if consensus is needed just by looking at the transaction, sometimes we can just skip the consensus and use the faster payment Ways to do transactions, such as Token transfer or NFT casting.


If you need to place an order, we use Narwhal, which separates the sequential parts, such as the actual calculation, sorting in transaction propagation, to ensure that the verifier The transaction is agreed upon. This gives you a big speed boost because you can do some consensus parts in parallel.


In terms of execution, when you know these relationships, when you know which transactions will be touched, you can easily come up with the most efficient way to execute transactions schedule, so you can have maximum parallelism on the workload. Finally, since we know the circumstances of each transaction, we don't need a notion of a large global state, and we can perform authenticated credit upgrades on transactions without computing data structures.


So we work on the sequential bottleneck that is responsible for many of the things that make commercial blockchains difficult to scale. We then either try to get around these problems with fast payments, or get rid of them entirely, or find ways to find ways to operate in parallel. I think that's what's unique about what we might be doing right now.


This is not to say that there are no other systems doing similar things. For example, many blockchains are now exploring parallel execution of similar things, using similar technologies, A structure such as a Merkle tree is also used.


But I think we've really bonded. We provide a complete data model that allows us to have more post-optimization. The other thing I would say is that I was also exposed to these things earlier than other people.


Many expansion strategies nowadays are to abandon the combination of smart contracts and assets, and put things into multiple shards. Basically scaling at the expense of user experience and developer experience, so I think that's where we're different.


We are committed to maintaining the developer and user experience by keeping all assets and smart contracts in one place. Eliminate friction, which is the value of blockchain. Then we have a scalable architecture without some trade-offs and compromises.


Mynft Team: It is really important to be able to see transactions before they are even executed, and then you The idea of parallelism was also brought up, which is very interesting and very important.


But we have talked so much about technical issues, maybe we can change the angle and talk about the ecosystem and applications The problem. Because we know that when it comes to the development of the ecosystem, the smart language and various applications of smart contracts are very important, such as the recent Defi summer and the recent NFT boom. So can you tell us what type of apps you think are most promising in general and hopefully built on Sui in particular. How do you plan to invest in these dapps in the future?


Sam Blackshear: I think some of the use cases you mentioned are interesting. We talked to people who work on games and learned that they had a lot of creative ideas about how to use the blockchain, how to make the game more engaging, how to move part of the game economy to the chain.


The other is to cooperate with brands to establish interesting relationships between games, so that people's gaming experience is not limited to a certain game. And that's something we take very seriously.

We are also very concerned about the monetization of creators, whether this can be through NFT, it can be through micropayments, or anything related to finance.


We are also very concerned about traditional finance and how to develop connections with Defi. Basically we think we're building a base layer. We talk to interested cryptocurrency and blockchain users who have great ideas, who are stuck with other systems, and we help them figure out if Sui can help them solve those problems.


We invest in different ways. We work with partners, give grants, help people develop, brainstorm with them about how best to use blockchain or how to use a platform like Sui. Hopefully I can finally get answers, do something general and practical, and help people do something non-speculative and generally interesting.


Mynft Team: You talked about gaming and GameFi. Games need composability, because they hope that the assets in the game can be migrated in different games, and users want to have assets that can be controlled independently and can be migrated on different platforms. This is also a point that Sui values, and it is also part of the architectural design.

Other chains to bridge? Considering that you want to use some of the existing web3 native encryption, how do you bring the users of these applications to your ecosystem through some "bridges"?


Sam Blackshear: Yeah, we think it's critical. Now there is a lot of liquidity and some interesting Tokens and interesting NFTs in other blockchains, so we hope people can bring these over. To do that, we need to build a better app ecosystem to attract people.


For example, you can add new functions or use the functions of sui, even lower costs, safer and so on. We'll be rolling out two different bridges later. We will spend more time thinking about how to connect with existing blockchains and ecosystems.


Mynft Team: When it comes to the ecosystem, the ecosystem is a very important point in the blockchain. So tell us, what kind of ecosystem do you want to build? and how are you going to build it? How will you support the builders of the ecosystem? What specific support and grants will there be? What kind of support will you have for developers? Especially developers from Asia, if they see the prospects in this direction and want to join it, what should they do?


Sam Blackshear: Yeah, so we want to build an ecosystem to drive cryptocurrency use cases the limits of what you can do, and the limits of what you can do. We want to keep what is, we want to make it better, we want to be creative, to think of new ways of doing things, to do things that will blow your mind, that’s our vision.


Because we are not dedicated developers ourselves, we are not professionals. So I think, like from a philosophical point of view, that's what we want to do.


In terms of support, I think the most important support is to encourage them (developers) and help them see more possibilities. Of course, as you mentioned, grants are a very important form of support.


We want to form communities where people can discuss, create standards, share code and ideas. This is another thing we want to do in terms of specifically supporting Asian Chinese developers. Regarding the support for Asian developers, we think that funding projects is also a good kind of support. In the field of blockchain, we have deep ties with South Korea and China.


For the last part of the question, what is the best way for people to participate? They should participate in conversations, ask questions, and find out what happened. Study the documentation and start learning how to program, move and build apps. Based on this, it is also possible to understand the details of Sui's work and make it unique. Then you can also go to Github, see what's going on, and see if you can make some contributions. I think it all depends on your interests, how you want to contribute, and how we can help you. But I think those are some of the best ways to get involved as a developer.


Mynft Team: As a developer, will it be difficult to learn Move? You also mentioned that Move has borrowed from Rust, can you talk about the difference between the two? Would past development experience be of some help in building on Sui?


Sam Blackshear: I think learning to write smart contracts is hard. But I think Move simplifies it. I think smart contracts are fundamentally very different from traditional programming, basically like it's a very narrow set of tasks, say you have some assets, you want to transfer them, you want to update, you want to do some tracking, etc. You don't write a compiler, an operating system, a web or mobile application in a smart contract language, so this is a very narrow requirement, and at the same time, programming with scarcity is not something traditional languages do, so This is going to be a bit of a struggle, especially for someone from a traditional language background. So, we use Move because we want it to simplify things so that people can get up and running quickly.


Solidity is actually a good background. Because it was designed to explicitly address many performance and security issues. So what we've found is that people who can use the language feel they're up to speed with Move because it's designed for them to do what they've been doing with Solidity, but in a more intuitive, more intuitive way. Safer and more efficient way. Some of the feedback we've heard from our partners is. If you give them some guidance, it only takes four or five days and they can pick it up very quickly. So I think this is an ideal background.


Secondly, I think knowing Rust is also a good background. The biggest similarity between Rust and Move is the so-called borrow checker, which analyzes safety. If you already know Rust, I think your transition will be easier. Because you have to choose something as your language syntax, our syntax is also similar to Rust, so if you're used to reading Rust, this will be very familiar to you.


But Move is a smaller, simpler language than Rust. For example, some things in Rust are difficult to use, such as the lifetime of references, but in Move you don't have to worry about this problem.


So we think that people with these backgrounds will get started better. But we also want to make it accessible to people who don't have a web background, don't know Solidity, Rust. I think the most important thing is to find a compiler to guide you to do the right thing and write efficient and safe code. Then combine a large number of examples and file learning, and constantly read these error messages that pop up.


If anyone wants to learn Move, but doesn't know how to do it. Then try to write code, read and compile constantly, this is an effective language teaching method, applicable to the general public.


Q&A session


< p>Q: Move is a relatively difficult language. Our developers also encountered some problems during the development process, that is, its return and search functions are a bit simple. Currently, the corresponding content information such as row The number and function are also relatively simple, and some functions are not supported. Will there be future updates for Move?


A: Yes, there will definitely be some updates in the future. For example, if you do a certain test, you will get a complete trace result to understand where the failure occurred, including source information, etc. Then you also said that some basic functions are relatively simple, of course we will also make improvements. But in general, we spent the first three years working hard on the design of the basic language, because this is a part that we cannot change in the future. Once a smart contract is released, this place can no longer be changed, and errors will remain there forever. So we worked really hard to get it right.


It all takes focused time and needs feedback so I think you can expect more improvements because we get feedback and we see the biggest pain points what, and figure out what our priorities should be, figure out how to improve the tools and the language.


Q: Because we know that token standards in different ecosystems are different and have different functions, so we want to know about you What is the standard of Token?


A: Because we know that there are standards such as ERC20 and ERC721, some homogenization and non-homogeneity tokens will be specification. For example, the standard of coinage, supply, how to transfer, how to divide, etc. will be stipulated.


For NFT, it already exists standard. From one point of view, NFT is like a metadata, every NFT can be transferred, if you want a restrictive transfer policy, it is also possible. These functions are all native to Sui, and there is no clear standard.


Then I think the question is, besides our existing standards, what else needs to be standardized?


I think there are too many answers. Like showing an NFT, or a way to show something like an explorer? And the way we do it is by standardizing some of the name and type fields. For example, a named URL or image, when I show you my URL, I will not only show you the text, but also render the image to you.


We did some standardization attempts like this. We want to build blocks for NFTs and other things like that that people can mix and match in any way they want. It's not like there's only one standard that defines these things, or that creators have to cater to rental companies and operators and so on.


So we're trying to figure out which standardized block builds make sense, and how to combine them. This is a high-level angle. Of course, everyone also said that we may also create a standard similar to NFT. For example, on Sui, there will be Ethereum-style rappers, or Netflix-style rappers, etc.


All these ideas will be realized in the future. I think we're going to do it in a variety of ways, and we've made a lot of progress, and I think a lot of the progress going forward will be determined by what people want, what they want to create.


Q: Do we have a tool chain? Is it possible for developers to use this tool chain? To implement Move, compile it, integrate it with smart contracts, and run it on Aptos or Sui at the same time. Is it possible now, is it going to be done?


A: There is currently no toolchain. It's actually all related to Move, so the migration burden is pretty low. For example, if you look at some repositories on the Internet, many projects are built on both Aptos and Sui.


You can go to GitHub to search for Pentagon, and you can see relevant information. In fact, there are many cases. They maintain a set of directly accessible directories that look very similar. I think automatic translation between them is also possible in some cases. Especially if you know Move, and you're using the same compiler. Of course, in other cases, we have many differences, such as expansion, operation, etc., and these points may not be compatible.


Q: Which narratives or areas do you think you will pay more attention to and give more priority to? Because the entire ecology is actually quite rich at present, and there are all kinds of things in the market, so what will your focus be in the future? For example, which projects will you focus on?


A: I am actually more interested in what I just said, such as the game industry, the monetization of creators, and traditional web3 finance etc. I am looking forward to seeing these things, but I am more concerned about technology than technology, because these things are not only stored on the blockchain, how does this thing reflect the founder's philosophy, etc. This is what I am more interested in. concerned.


Q: Regarding the name "Sui", the pronunciation seems to be weird, a bit uncomfortable, and a bit negative a feeling of. It is possible to say that we changed the name later or why did we choose this name?


A: Actually, I answered it just now. Because Sui represents water, constantly flowing, full of life, everywhere. It's important to your life, so that's why we chose the name. We are also unlikely to make changes, because there are many meanings behind this name, and our founders are actually more enthusiastic about this name. You have to know that it is not easy to find a name that is popular all over the world. Everyone will have different interpretations. Then we tried our best to find such a name, which represents water. Of course, this name may also have shortcomings in other aspects.


Q: I noticed that Move has a collection activity recently, which aspects are you more interested in? For example, what functions or aspects do you want to add/collect?


A: I think these things will go into Sui's library later, or other libraries, activities. For example, the data structure of Bloom filter is a good structure. Or when it comes to features, like if you want to check membership without dealing with a lot of data, this feature is useful. We also have a built in map which I think is quite useful. I think there are many good data structures to look at, and then to see what people's basic needs are, such as putting off-chain data on the chain, writing code, decoding, etc.


Q: Sui has taken a very novel approach to prioritizing scalability. This allows for near-instant finality for simple transactions. I'm curious how you would describe the trade sequence, especially given that it helps us narrow our focus down to financial markets. For example, how is the transaction order determined? On the traditional blockchain, it is in the form of auction, or in the form of first-in-first-out. I'm wondering how you describe this at a high level, how transaction ordering is determined, especially given some issues with sharding, scalability, and parallelism.


A: This is actually considering that when transactions need to be sorted, how do you decide which one is placed? How do you determine which transactions are processed first? What we're trying to do is something really interesting and novel, where we offer our clients an object-based free marketplace.


Because normally there is a unified price on the platform, for example, there is a popular NFT, the value is very high, everyone is going to grab it. Then even if you are smart and can operate in parallel, because fundamentally this thing is sequential, the cost will eventually rise for everyone.


What we want to do at Sui is that when something like this happens, the app's cost goes up, but other unrelated apps don't .


This means that we have a way inside the protocol to quantify the difficulty of such a shared object by looking at how many times it has been touched in blocks in the past, and then we It will be included in the mass priority mechanism. If many people are touching this thing, we will ask for a relatively high fee, so that we can ensure that all transactions will not be affected by this hot transaction. If you are in contact with other shared objects, such as just doing token transfers, your fees will not be affected.


So we're not going to have a single global price, the fee basically depends on how much competition you create in the system and how much you're going to Slow down our transactions.


We actually haven't made the idea public yet. We're really excited about that because it's a way to provide a great user experience while prioritizing deals and you're not stuck on every issue. If you interact directly with an object, the only thing you need to worry about is a "neighbor" touching the object. Also it would be great for validators to make sure they are using their resources most efficiently and collecting fees as much as possible.


Original link


欢迎加入律动 BlockBeats 官方社群:

Telegram 订阅群:https://t.me/theblockbeats

Telegram 交流群:https://t.me/BlockBeats_App

Twitter 官方账号:https://twitter.com/BlockBeatsAsia

举报 Correction/Report
Choose Library
Add Library
Cancel
Finish
Add Library
Visible to myself only
Public
Save
Correction/Report
Submit