This wasn’t a sudden decision. It was made after maintaining the Endurance network consensus layer explorer for nearly two years, considering both maintenance costs and economic benefits. The “Old Version” is Broken and the “New Version” is Unreachable The current open-source Beaconchain codebase is in an awkward state of neglect. The upstream development team’s energy has completely shifted to their “V2 version” development. The first problem: We can’t simply adopt this “new version”.

It sounds incredible even when I say it myself, but our Endurance network, a technical clone of Ethereum, has somehow developed self-awareness. Generally speaking, in the tech world, if Ethereum says something is right, we applaud with both hands. We don’t need to think, because Ethereum has already done the thinking for us. Ethereum is always more correct than we are, because truth comes from practice. With a scale thousands of times larger than ours, a single day of their operation yields more truth than a year of our practice.

Recently, two colleagues and I spent some time creating a website: Are We Fast Yet. The name and layout of the site are inspired by this site, which was set up 14 years ago by members of the Firefox team to track performance gaps between their browser and others1. Additionally, considering the Mozilla team’s tradition of sending a cake to the Internet Explorer team every time a new version was released2, I see this as a great cultural example of how teams can remain friendly and respectful even while competing.

This article is from my colleague @lyfsn. He just finished deploying Hyperlane on our Endurance chain with the Hyperlane team. Considering that Hyperlane CLI v4 is a significantly updated version and there aren’t many new tutorials available right now, I believe it offers valuable insights. Hyperlane is a permissionless cross-chain project that enables bridging any ERC-20, ERC-721, or similar assets to other chains. It also supports bridging native tokens and even non-EVM chains like Cosmos.

So far, Endurance’s development has been handled by our small in-house tech team, specifically a tiny blockchain crew —— including me, there are three coders. We carefully cherrypick necessary infrastructure without reinventing the wheel and wasting resources. For example, in the previous blog, we introduced the safewallet multisig wallet, which we consider one of those “MUST-HAVE SERVICES FOR A NEW BLOCKCHAIN.” Although it comes from a company, it has become an industry standard and offers an almost permissionless deployment method, we dig it.

Note: This tutorial is contributed by our colleague shelchin. Thanks for his efforts! Three weeks ago, just like you, I felt both excited and a bit uneasy about deploying Safe Wallet. After continuous attempts and learning, I have finally mastered the skills of deploying and managing Safe Wallet. I am ready to share this process with you in this tutorial. I will deploy Safe Wallet on the Endurance mainnet. The Endurance mainnet was successfully launched in January 2023, and it is a new Layer1 blockchain compatible with EVM.

Introduction A image from the community piqued my interest. One of the Validators on our Endurance network is running a set of Clients, including Beacon, Execution, and Validator Nodes, on a NAS with just 4GB of RAM. Moreover, the actual memory usage doesn’t even reach 1GB (738+181+25=944 MB), as seen in the image. This is significantly below our expectations. Initially, to simplify deployment complexity, we did not tailor the official Validator server hardware configuration of Endurance2.

When the Endurance network launched in late January, it started as just an application chain. Our team, experienced in traditional gaming, soon realized we had more to offer in the Web3 domain. Being just an application chain wasn’t maximizing our potential, so we shifted towards becoming a public chain to support more games. As a public chain, Endurance’s value extends beyond a single Dapp/GameFi to future developers. For example, its technical specs should meet mainstream developers’ needs over the next decade.

If you’ve read our previous articles, you should have a general idea of what our team has accomplished since its inception: We are developing the company’s first AAA Gamefi, named Fusionist1. Next, we established our own L1 chain called Endurance. We also gradually released our native currency, ACE, on our website through gamified methods, attracting early users. With the proliferation of L2 technology, we believe that the time is becoming ripe for a closer integration between the blockchain and games.

This article primarily introduces a specific technical branch in the evolutionary trajectory of Endurance 2.01: OP Endurance, which is based on the OP Stack (code-named Bedrock). OP Endurance We believe that Rollup, emerging as a de facto standard for Layer1 Scaling, will mature in the upcoming years. Nonetheless, with various solutions still undergoing rapid iterative development, there’s a long road ahead before they reach full maturity. At this juncture, we cannot predict which method will dominate the competition, and we’re not inclined to introduce “yet another Rollup” ourselves.