jakiro
Source: funblocks
“In this special DEVS On DEVS, we invited TDOT [2] of the core protocol developer of Plasma Mode [1] (also the developer of Redstone [3]), and the co -founder of Optimism [4].Jones [5] Optimism is the core promoter of OP Stack.And improve scalability. In this dialogue, they discussed the origin of the cooperation between Redstone and Optimism, the importance of Fuxing Plasma, the necessity of introducing experimental agreements into the production environment, PLASMA MODE and OP STACK’s future roadmap, andTheir excitement of the development of the full -chain game. “
01. How to use Plasma mode to improve OP Stack
Ben:What is the process of starting to improve OP Stack?
TDOT:I joined Lattice about a year ago and was responsible for Plasma Mode.The goal is very clear: we have many MUD [6] applications that consume a lot of GAS. At the same time, we try to put a lot of data on the chain, so we need a solution that supports these needs and cheap.The Lattice team has conducted some experiments on OP Stack, such as the prototype of some chain world and deployed on OP Stack.We found that OP STACK has been very easy to use.
So we asked ourselves, “How can it make it cheaper?” The basic assumption is, “We think OP STACK is the framework that is most consistent with Ethereum and is completely compatible with EVM.”Run, this is an ideal solution.But we want it to be cheaper.
At that time, CallData was still the source of data availability (DA) of the OP Stack chain, which was very expensive.So we obviously cannot start a L2 with CALLDATA, because our full -chain game and MUD world need higher throughput.Therefore, we decided to start trying other data usability (Alt DA) solutions.In fact, it has been mentioned in the initial OP Stack documentation that it needs to explore Alt DA.
So we asked ourselves, “What would happen from the DA from the chain?” We hope that the entire security model and all content can rely on L1 Ethereum.Therefore, we avoided other Alt DA solutions, decided to store data in centralized DA storage, and then found an effective security model on L1.
This is why we use some old Plasma concepts and put them on Rollup.There are some differences here.The biggest question is, how to achieve data challenges on DA and chain on the existing OP Stack?Our goal is to change the OP Stack as little as possible, which has no effect on the Rollup path because we don’t want to affect the security of other Rollup chains using OP Stack.
When designing ROLLUP, you won’t think about, “If anyone changes the data generation process to store data from other places?” Even if there are these changes, OP Stack is still very powerful, and the effect is very effective.This is the first change we have made.
After that, we need to write contracts to create these challenges.It is used to force DA challenges to the chain of data.This is the second step to integrate the contract into the process.We must build the entire integrated system in the process of derivation, so that you can derive data from a DA source outside a chain and a L1 DA challenge contract to prevent data from submitting to the chain during the challenge solution.
This is the main point of things.Very complicated, because we want to maintain the elegance and stability of things.At the same time, this is a relatively simple concept.We did not try to re -invent everything or change the entire OP Stack, but try to keep things simple in a complex environment.So in general, this is a very cool journey.
Ben:I can talk from the perspective of OP.You mentioned some early work of Lattice.It happened that at the same time, we Optimism rewritten the entire OP Stack. This time we published it we call BEDROCK.
Basically, after two years of building RollUP, we took a step back and reflected: “Well, if we want to use all the experience we have learned to the extreme, what will it look like?”The code library for BEDROCK, this is our biggest upgrade to the network.
At that time, we cooperated with you a project called OPCRAFT [7]. I think Biomes [8] was its spiritual successor. This is the happiest time we have played in the chain.At the same time, we were relieved because others could also use OP Stack for development.I think that in the past few years, another important turning point of expansion is that many people can run the chain.
Karl from Optimism Observes OPCRAFT Gameplay
It is not only those who have developed huge and complex code libraries to do this.When we start cooperating, seeing others can take over this code library and do something very remarkable, this is a great affirmation.Then it was so cool to see this situation expand to Plasma in practical applications.I can even talk about that history a little.
Before Optimism became Optimism, we were actually studying a technology called Plasma.At that time, the tasks we assumed far exceeded the ability of the expansion community at that time.You see the design in the early Plasma design may not have a direct relationship with today’s Plasma.
Today’s Plasma is much simpler.We look at the proof and challenges of status verification and challenges.In the end, we realized a few years ago that Rollups is much simpler than Plasma.I think the conclusion of the community at that time was “Plasma was dead.”This was a stalk in the history of Ethereum expanded at that time.
But we have always thought that “Plasma has not died, but we can try a simpler task first.”Now we use different terms.For example, there were concepts such as exit (exits). Now you can look back and say, “Oh, that is a data availability challenge with some additional steps.”So seeing not only OP Stack was used by others, it was also evolved into what we first tried but in a very chaotic and immature abstraction. It was really amazing.We have completed a complete cycle, and you have made a great abstraction around them and make it work in a reasonable and rational way.This is really cool.
Coindesk Coverage from When Plasma Became Optimism
02. The most important thing is to enter the production environment as soon as possible
TDOT:There are still some challenges and unresolved problems in the Plasma model, and we are still trying to solve it.The key is how to avoid spending up to ten years?Do you understand what I mean?We need to reach the stage where the results can be delivered as soon as possible.
This is our thoughts.We already have many applications developed based on MUD to go online immediately.We need to prepare a main network for these games as soon as possible.People are waiting and ready.You need a chain that can be launched quickly and can run to run all these applications, so that these applications can develop parallel development in parallel in our solution to the problem.It takes a long time to achieve production stability.
It takes a lot of time to launch something online to make it without permission, stability and security.Seeing that the entire process of achieving this goal is already amazing.This is why we need to maintain high degree of agility, because there are too many things.The entire ecosystem develops very quickly.I think everyone is delivering a lot of innovation.That's why you must keep up, but you can't compromise with safety and performance, otherwise the system will not run.
Ben:Or technical burden.The minimum change principle you mentioned is one of the core ideas for us to rewrite Bedrol.I talked about the rewriting of the entire end -to -end, but more importantly, we reduced about 50,000 lines of code, which is very powerful in itself.Because you are right, these things are really difficult.
Each additional line of code will make you farther from the production environment, making it more difficult for things to go through actual combat testing and introduce more wrong opportunities.Therefore, we are very grateful for your efforts in the process of promoting this process, especially for the new operation mode of OP Stack.
TDOT:OP Stack has indeed created a way that you can quickly advance such things.It is very difficult to coordinate everyone because we are obviously two different companies.In Lattice, we are building a game, a game engine, and a chain.
And you are building a hundred thousand things and delivering all these products regularly.From the perspective of coordination, this is really difficult.
Ben:Yes, there is really a long way to go.But this is the core charm of modularity.For me, from the perspective of OP Stack, this is one of the most exciting things. For the time being, the amazing games and virtual worlds that are now built on Redstone.From the perspective of OP Stack, this is a very powerful example that proves that many excellent core developers have joined in and improved this stack. This is very amazing.
This is the first time that you can significantly change the attributes of the system through a key Boolean value.To do this thoroughly, as you say, there is indeed a long way to go.But even if you are close to effectively, you need modular support, right?For us, seeing you realized this, without the need to rewrite L2 Geth, it was really relieved.For me, this proves that modularization is playing.
TDOT:Now the situation has become better.Judging from this example, you turn everything into a small module that can adjust and change the attributes.So I am looking forward to seeing which new features will be integrated.I remember we were worried that we had a bifurcation that included all changes to OP Stack and needed to merge it into the backbone.We thought, "Oh my God, it will be crazy to review everything."
We have to decompose it into a smaller part, but the whole process is very smooth.The atmosphere of our cooperation with the team is very good, so the review process is also very happy.This feels very natural.And I think this process is very fast in reviewing and solving some potential problems.Everything was unexpectedly smooth.
Ben:This is really good.One of our focus this year is to contribute to OP Stack.So I am very grateful to you to participate in the test and promote these processes.I am glad that these processes are not unbearable and we have achieved some results.Speaking of which, I am curious. From your perspective, how will this work develop next?What are you looking forward to development next?
TDOT:There are many different job directions.It is mainly integrated with the fault certificate mechanism.We adopt a gradual method to decentralize the entire technology stack and increase its unique features. The ultimate goal is to achieve functions such as no license and forced exit.
We have this ultimate goal and gradually realize while maintaining safety.One challenge is that it is easier to not be on the main network, because it does not need to make a hard fork.You may think, "Oh, as long as I wait until everything is completely ready to release it, so that there is no need to do hard fork or technical burden." However, if you want to go online quickly, you must deal with these complex ones.Upgrade and frequently release.It is always a challenge to achieve this and maintain high availability.
I think that after the failure mechanism and all these parts are ready, there will be many upgrades in the PLASMA model.I think there is still some optimization space in terms of commissioning commission in batches.Now we do it very simple, each transaction is a communitynt.Commission is just the hash value of the input data stored under the chain.
We are temporarily as simple as possible, so that it can be simple and fast to review, and there is no big difference in OP Stack.But now there are some optimization that can make it cheaper, such as batching the Community or submitting them to Blob, or using other different methods.So we will definitely study this to reduce the cost of L1.
This is what we are very excited.Of course, we are also looking forward to all interoperability -related contents that are coming and can interact between all chains.It is clear that this will be a huge progress for users.
Many of these tasks must be implemented by you.But we hope to figure out what these are in the Plasma mode and have different security assumptions.
Ben:Speaking of this, this will be another test of OP Stack modularization.You mentioned the Fault Proofs, we are very looking forward to its launch in the Plasma mode.This is also an important feature of the Roll-up in the main network in the next few months.
A exciting place we build this code library is that although there are some precautions, relatively speaking, as long as you click the re -compilation button, you can run a fault certificate in the new environment.So seeing this is very exciting in practice, because this will be another example of "normal functioning".As one of the first teams to make large -scale changes, I am convinced that this will not be completely friction, but for the community, it is definitely exciting to try and publish a fault proof on a large change code library.Advantages.
TDOT:Its design is very good. You can insert your input like "Oracle" and change these data sources in the fault proof process.This should not be too difficult.Obviously, you need to ensure that it can work normally throughout the end -to -end process, but I think it should not be too difficult to release it.This may also be the focus of the next roadmap.
Overall, we are very interested in making a lot of performance improvement and optimization.There is no puzzle, and every small problem needs to be gradually solved.If the entire community is studying these issues, like an army of continuous efforts, we can gradually realize a high -performance chain and build on amazing stability.
The Mud logo
03.mud, redstone, and cooperation with Optimism
Ben:I am looking forward to seeing your progress in the integration of MUD and OP Stack.I think there are many very cool potentials here.One of the most exciting things we will do in the next one or two years is to continue to promote many major improvements in performance and throughput discussed by L1 Ethereum.
The Ethereum Research Community has made a lot of efforts in this regard, but this is also a high -risk field.Some major changes require a test platform.An example I think of is the issue of expired state.There is no doubt that your work is amazing because it promotes the limit of how much amazing content can accommodate on the chain.I think one of the results we will see is the true manifestation of the problem of "status growth".This basically means that the more games are playing, the more content that needs to be tracked, and the more difficult it is to implement the transaction.
The Ethereum community has been studying this issue for many years and proposed a solution.I think these solutions are tricky because they fundamentally changed the structure of state management.Basically, you need to provide these proofs at a certain time so that you can discard the state unless anyone wants to restore it.
I am very excited because I think MUD is the perfect environment that you actually implement these changes and make it take effect.You have done very well in status management, and you already have a framework and model that everyone follows.I am also looking forward to it, because I think you focus on how to build a framework of an application on Redstone, which will be able to experiment under this framework and try these very difficult improvements. These improvements will bring huge performance improvement, but you need to updateParadigm.I think you have the potential to make breakthroughs in this field, so I am very excited about it.
TDOT:This is a good point of view.I like MUD to abstract developers to deal with various basic functions.Basically, OP Stack is the basic layer, and you are just dealing with the original and similar things.The use of MUD development is to simplify these processes.When we enter the world of multi -chain interoperability, we will consider how to abstract on multiple chains.This is definitely an important issue that we think of when considering the combination of MUD and Redstone.
So we also need to figure out what the ideal developer experience should look like.When you deal with all these chains, these problems become difficult to clear, and your users will be tired of constantly switch between them.If you have a lot of L2, it will only make people feel confused.I recently saw someone saying, "I don't remember which chain I am on." The balance of tracking each chain is very complicated.We definitely need some abstraction to simplify this problem.Otherwise, this will be very complicated.MUD is undoubtedly a very good opportunity to solve this problem.
Ben:Looking forward to your help.The workload is very large, but it is super cool.
TDOT:I think working with you is definitely a huge help for us, because we are a very small team with only about 15 people.Therefore, it is clear that it is really difficult to deal with all these things.When you develop and cooperate on Superchain, suddenly you have a huge company and get all the engineering resources you may need.I am basically the only engineer Lattice who works on the Plasma model, but cooperates with Optimism and uses the power of all other core developers to greatly improve our productivity, so that we can complete some jobs that are often difficult to complete independently.This flywheel effect is really great.
When I experience this, it feels very powerful.I think, "Wow, I can't believe that we have just completed these." This makes me think everything is possible.
Ben:My heart is really warm.Thanks.
Is there some philosophical foundation about the safety design of Plasma and the working principle of Layer 2?When some amazing things happen, the community will cause debate on security models, which is often a sign that indicates that the technical boundary has been advanced.When there are subtle and discussing and education, it usually means exciting progress.
I think we have not really discussed the design structure of Plasma as the Layer 2 security model.I am curious about your views on this.I have some thoughts on the early Plasma era, and I also want to hear your views on this.
04. Define the PLASMA mode
TDOT:I want to introduce what PLASMA mode is, and its specific meaning.This is a new OP Stack function developed by our core. It is currently in the experimental stage and contains one aspect of Plasma, that is, the availability of the under -chain data.
We call it Plasma because it promotes the concept of storing the input data under the chain.You do not use L1 DA, but store data on any storage service, such as AWS or IPFS.Then you need to monitor whether the data is available.At least one person needs to check whether the data submitted is available.
If the data becomes unavailable for some reason, the agreement allows users to withdraw forced withdrawal within seven days.There are still lack of some parts that are still under development, such as Fault Proofs that are about to be launched and not allowed.Users can automatically verify the availability of data [9].If the data becomes unavailable, you must challenge on L1.
If the data is not available, you have to challenge, basically to force the data to go online or re -organize data, so that you can withdraw funds and exit the chain.So at this stage, these components have not been fully deployed.Therefore, we hope to emphasize that there is still a certain distance to go to the goal completely without permission and accessible, but it is gradually advancing.
There are some assumptions about the cost of using user challenges to extract funds.These things are still defined, and we are optimizing these projects so that they will eventually become cheaper and easier to obtain.We are developing a related roadmap.This is different from the planning of Fraud Proofs and decentralized sorters in the OP Stack router.
One problem in this agreement is the fisherman's dilemma [10]. This means that you need an honest "fisherman" to always be online, because if no one is online, you don’t know if the data becomes unavailable.During this period, the chain may be attacked by an operator.
The Fisherman's Dilemma
You have many ways to solve this problem.You can inspire people to maintain online through a reward mechanism and create a powerful community to ensure that those who have greater investment in the chain, such as users or liquidity providers running by bridge, keep online and ensure the integrity of the chain and operatorsEssenceThese users should keep online and challenge when they occur.Obviously, this topic is very interesting, because there are many ways to solve this dilemma, and there are many jobs to do so that this system is easy to access anyone and ensure that users continue to pay attention to the maintenance of chain.
Ben:What is layer 2?It is a more efficient use of Layer 1 blockchain.The classic analogy is, "You will not go to the court to fulfill the check, but go to the court when you check the ticket." This is exactly the basic design concept behind these optimistic systems, and it is also our thinking about roll-up: moreUse the blockchain efficiently.By using L1 only when there is controversy, it can increase the total throughput of the blockchain.I think this is also a good analogy of the Plasma model.The Plasma mode basically expands the concept of roll-up. It not only solves the withdrawal of withdrawals, but also requires the availability of the transaction data itself.
I think this will be a very powerful tool, because by implementing this, we can use Layer 1 more efficiently, and processing more data in the Layer 2 system, and the cost is much lower than using only Roll-Up.So this is very exciting.More importantly, it enables you to improve the existing state without the PLASMA mode, these cannot be achieved.
Of course it is not perfect.There is a fisherman ’s Dilemma, which put forward some basic requirements for the entire system.The most fundamental thing is that Plasma's most exciting compared to other Alt DA systems is that it transforms security balances into active balance.
In other systems, you cannot go to court to solve data problems.Data defaults to exist.This means that if the data does not exist, you do not have enough evidence to prove the status quo in the court, and you will fall into trouble.In contrast, the PLASMA model has made a good trade -off. By adding a new form of challenge to avoid data loss, the community payment fee is released to L1.
During the resolution of the dispute, you may not know the state of the chain, but it is much better to make active trade -offs than security, because active balance means that you may not know the chain status for a while, and security balances are when youIt means that you don't know if the withdrawal of the chain's withdrawal is effective, and may allow someone to make invalid withdrawal.This is my view of the PLASMA mode.
It expands the concept of "don't go to court to the court in order to fulfill the check, but go to the court when the check is jumped" and use it to improve the weighing when the use of Alt DA.In this way, even if the funds may be lost, you will only encounter the state of the chain temporarily unknown and the user pays the data release cost.I think this is a very exciting balance.
TDOT:We really have some risks when we use the word "Plasma" because it has a lot of historical burdens.The problem is definition.When we announce the Plasma model and deploy it to the main network, many people may think it is almost the same as it described as Vitalik and others.
In fact, this is still OP Stack.When we introduced these features similar to Plasma into OP Stack, we did not redesign OP Stack.We still maintain the security assumptions of OP Stack, and increased the linked data availability (DA) on this basis.What we learn from Plasma is that users can challenge data and verify its availability. If the data is not available, we can force the DA provider to submit it to the chain, or re -organize the data to exit.Our security assumptions are that no matter what happens, users can force exit or withdraw funds, even if chain operators or DA providers are malicious nodes.
In order to ensure this situation, many steps are required.Our ideas are to ensure the most basic part first, and gradually develop on the basis of some guarantees of OP Stack, gradually realize decentralization, and gradually introduce these guarantees.We already have many frameworks for evaluating Rollup security, which are established by L2Beat, which is very useful for the community.
But Plasma itself is not entirely suitable for this model.The problem is that if you try to fully adapt to the framework of the Plasma mode, it does not fully match at all stage.
We still need to implement some of them.Therefore, it is clear that the specific roadmap and implementation methods need to be clear.I think these things are constantly defined and improved.Let's discuss these issues together, find out their meaning and propose definition together, which is very meaningful.
Ben:Yes, I fully agree with this.It is really important to progress about fault proof, but you are right. Plasma's security model requires a new framework that is unique to Rollup.If you are optimistic about the expansion of Ethereum, in fact, there is no other choice, you need to replace the data availability (DA) solution.
The reality is that rollup has obvious weighing.They are easier to build, which is why the expansion community starts to build them first.But if you want a truly horizontal scalable blockchain system, you cannot be limited by the data throughput of L1.And if you only use rollup, you will be limited.Therefore, once you understand that the goal is to push the blockchain to the global scale, a replacement data availability solution is required.
I mentioned earlier that Plasma is the best choice we can do for the layer 2 of Alt Da, but it also has a weighing.We need to clearly convey these -if this data usability provider is down, funds will be lost.But for Plasma, we actually need to convey, "If this data is available, users need to pay the L1 release fee, and these costs will not be recovered." To understand the security model of Plasma, you will say, ""This is a DA provider, this provider may be down, and it needs X dollar to keep the community safe every day. "
Then you may take this cost to exit the window and say, "If a malicious DA provider occurs, the net cost will be X dollar, which is basically the cost of these challenges until people can take out their funds from their funds"This is a very subtle question, which will inevitably cause a lot of discussions on weighing.You can obviously have a more complex source of DA, which will increase the cost of attack and reduce the possibility of burning money.
At the same time, this will increase the cost of the system.So in the end, as the manager of this technology, we need to make these weighing very clearly.I think your point of view is correct. DA providers will naturally have motivation, which will not make us fall into the fisherman's predicament, because they can't withdraw funds in the end, and can only burn money.This may be one of my favorite Layer 2 expansion debates.It is one of the most primitive debates -before we realize that "we may eventually need to do this, but we can bypass this problem by publishing data to L1".So I am glad to see this topic and return to the public vision again.
I think that in the next year, we will see the community's understanding of this issue greatly.
Coming Full-Circle, from OPCRAFT to Biomes on Redstone
05. Standardization of the chain and moving towards the future
TDOT:We need better tools to verify the chain and ensure the availability of data, ensure the correctness of the output, and conduct a comprehensive inspection to ensure that at least one person is verified by default.
The more people verify, the greater the value of the chain.Therefore, if we can make people run cheaper and easily run these authenticants, then we can bring together community resources to ensure that there are always people challenging and verifying.This is one of the important steps to improve safety and decentralization.
It is great to cooperate together in these things.This allows the agreement to get more attention, more ideas, more discussions and more tests.I think the Plasma model will be run by more people, and more people will find and experience it.In this way, running your agreement and knowing that more people are also running it, it will add more review and combat tests to the agreement.In the end, we will find some very reliable solutions.So I am also looking forward to this.If we just develop this agreement in the corner, the experience will be completely different.
Ben:So this is why this method is very good, which can help us find out the problem.We realize that standardization is essential for OP Stack.We need to provide a unified and easy -to -understand way to allow people to run these chains while ensuring the security characteristics they declare.Because a challenge is that the external team may make seemingly harmless changes, but it may actually have a huge impact on the security, performance or overall behavior of the system.From our perspective, standardization is a powerful tool.Through community discussions, we can not only obtain extensive opinions, but also form a set of standards, so that everyone can operate and communicate responsible.
The security model provided by L2Beat is a very valuable public resource.At present, it is still very customized and scattered.What we need is to place it in the Plasma mode when compiling or deploying the OP Stack version, and the system can output the security assumptions you bear.Therefore, standardization is crucial.You are right, if everyone is developed in their respective small environments, and there is no unified standard implementation, these problems will be magnified.
TDOT:There are already stakeholders and applications running it, which is really great.After entering the production environment, you can understand the needs of users more deeply.Do you know who is using this chain, who is deploying, and then can communicate with them, asking, "What do you expect? What do you need? How much do you want to spend? Is this price appropriate?" In this way, you can get trueFeedback, not in the endless discussion, cannot really understand the problem.
The significance of game theory is that it must be tested in the real world.Otherwise, you can never know the real effect.Although it can be speculated, there are always accidents.Therefore, I think it is necessary to iterate and test the experiments in a relatively secure environment.This is also very interesting.Just like to have different levels of security; some chains have high security standards, and some chains are at the forefront of technology, which can perform bold experiments.
These chains may be cheaper and better performance, but risks are greater.You can perform experiments and promote innovation from it.Therefore, it is risky and reward to these batch of users on these chains.This is also a question we spend a lot of time this year.
Ben:Collective is also exploring the path of contribution.I think you say very well.You need to weigh between new improvements and operations in the real environment.We regard OP STACK as an open source promoter in this process. People have developed amazing technologies at the forefront to prove their effectiveness, and then return to the standard to make everyone benefit.
This is fully in line with the concept of positive and game, open source, and growth.You are right.To promote the development of cutting -edge technology, weighing must be made.The process that can benefit us in an important moment (such as the release of Redstone) is very critical. At the same time, it solves the problem of flexible improvement in the field of Ethereum. There may be ten years of development space in this field.We need to consolidate these verified experiments and clearly define it into the standard.
We are very happy to embark on this journey with everyone.
TDOT:In my opinion, despite these differences, it can still become part of Superchain, which is very interesting to share income and inspire people to experiment and deploy new chains. At the same time, it can also benefit the entire community and various realities.
This model is very good, unlike people running forks in their respective corners, it is difficult to track and prone to safety problems.Here, you have a framework that can verify and check people's operations.This is undoubtedly a huge advantage.I think this is naturally formed.It is fascinating to see its development in the past year.
Ben:We must continue to break through the limit.In the end, in the long run, these should be regarded as an extension of Ethereum.In the past year, Rollup Improvement Process has been launched. This is a very cool thing, which basically connects the core developers of Layer 1 and Layer 2.
In the future, we will see that Layer 2 will gradually adopt some important EIP that everyone is very eager to achieve on Layer 1.Layer 2 is a good test platform that improves from some random forks, and then merged to OP Stack, and finally released.
In the end, these improvements will land to Layer 1, and everyone will cheer.This will be very cool.This is a bit like turning Ethereum into an organism, and Ethereum code library is its DNA.
TDOT:This is also very meaningful.
Ben:Yes, it's great.Speaking of the amazing Redstone chain, TDOT, are you excited about what happened on Redstone now?
TDOT:Yes, we have the best applications.Honestly, I was always shocked.I have been playing This Cursed Machine [11], which is the most crazy application currently running on Redstone.This is really great, especially when people release their creativity and create something that has never been done before.
Ben:Is this the first horror game on the chain?I am not sure if I saw something like This Cursed Machine.
TDOT:I have no idea.This is a good question.I think putting these experiences on the chain really promotes your development.I really like people to make these new games, not just transplanted the existing games to the chain.
Ben:I don't want to use classic venture capital to compare the early Internet era, but I do feel that the autonomous world on Redstone is indeed leading the trend.As the analogy, when the Internet first appeared, people's intuition was to move existing things to the Internet, such as turning newspapers into a digital version.
Real innovation appears in the function of how you realize how to use the new system.In fact, newspapers on the Internet are not as valuable as everyone has their own 240 -character small newspapers.For me, this is very similar to the innovative space on Redstone.The current community is breaking through the boundaries of all -chain games and the world, and exploring how to promote their development.
TDOT:Yes, we are very excited.This environment really attracts a super active community, and everyone can push the ideas to the limit here.This has greatly improved than the simple speculative mentality.I think the idea of playing games with friends is also very warm, attracting many very good people.
It's time to enjoy fun now, guys.I think we have not fully prepared to welcome all the new things that are coming, so we look forward to it.
Ben:Plasma is back.Long live Plasma.
TDOT:We are very excited, and construction has just begun.
Reference information
[1] Plasma Mode: https://specs.optimism.io/experimental/plasma.html
[2] tdot: https://twitter.com/unsaFetdotdot
[3] Redstone: https://redstone.xyz/
[4] Optimism: https://optimism.io/
[5] ben jones: https://twitter.com/ben_chain
[6] MUD: https://mud.dev/
[7] OPCRAFT: https://lattice.xyz/blog/making-OPCRAFT-PAN
[8] biomes: https://biomes.aw/
[9] Sentinel: https://github.com/latticexyz/Sentinel
[10] Fisherman Dilemma: https://github.com/ethereum/research/wiki/a-n-data-availability
[11] This cursed machine: https://thiscursedmachine.fun/
