Exploring the Differences Between Core and Mainsail

user avatar

by Giorgi Kostiuk

2 years ago

Made with AI

In the blog post, significant changes introduced by Mainsail are discussed along with how it distinguishes itself from the Core version. The focus is on understanding the differences between Core and Mainsail without delving into the EVM information.

Key Changes in Mainsail

Major changes in Mainsail compared to the latest Core version include:

  • Introducing a new BFT consensus mechanism with instant finality.
  • Increasing the number of active validators from 51 to 53.
  • Implementing state snapshots to speed up synchronization.
  • Eliminating the need for an external database configuration, except for the optional public API.
  • Separating the public API into a distinct process for better scalability.
  • Updating the codebase with the adoption of ES modules.
  • Switching to pnpm as the primary package manager for improved dependency management.
  • Changing the project’s license from MIT to GPLv3.

These changes collectively bolster the security, scalability, and performance of Mainsail, solidifying its position as a robust and innovative blockchain solution.

Technical Comparison

The technical variances between Mainsail and the latest Core version are outlined in a table format comparing features such as ledger database, API database, block finalization, validators, block time, and more.

Project Insights

Under this section, the technical, codebase, and general changes in Mainsail are discussed. The structure and packages of Mainsail, including crypto, transactions, and API details, are elaborated upon. For crypto transactions and API, significant changes have been made, resulting in the introduction of new packages and functionalities.

Toolchain

The blog details the toolchain used in Mainsail, including the transition from yarn to pnpm package manager, utilization of Lerna for monorepos, and the movement to ES modules for browser builds in most Mainsail packages. Recommendations for development in Visual Studio Code with specific extensions are also provided.

Tests

Uvu test runner replacing Jest in Mainsail is discussed in this section. Additional packages such as sinon, nock, esmock, and c8 used for testing are also mentioned. The rationale behind using Uvu, known for its performance, is presented.

Consensus

The consensus mechanism in Mainsail, inspired by Tendermint, and featuring block finality, block cycle, and BLS12-381 signatures, is explained in detail. The unique attributes of BLS12-381 signatures, including aggregation benefits, are highlighted.

Database

The choice of LMDB as the primary database, its performance advantages over PostgreSQL, and the state management process in Mainsail are discussed. The rationale behind utilizing LMDB and state snapshots for synchronization efficiency is outlined.

API (Optional)

The relocation of the Public API to a separate process, the synchronization process to a PostgreSQL database, and the specifics of data handling between the API and Mainsail node are described in this section.

Conclusion

The conclusion section summarizes the advancements Mainsail offers over Core V3, emphasizing improvements in consensus algorithms, database management, and modular architecture to enhance performance, scalability, and developer experience. Readers are encouraged to stay updated on ARK-related developments by following the provided link.

Tier I

Sector: #18291

Sealed Cache Room

Resource Cache

Resource Cache

Tier I

Requires 25% Tier Progress to Claim
Meme Cache

Meme Cache

Tier I

Requires 50% Tier Progress to Claim
Equipment Cache

Equipment Cache

Tier I

Requires 75% Tier Progress to Claim

After collecting, caches will be stored in your inventory and can be opened with Keys.

Other news

Trezor Implements New Security Measures After Data Breach

chest

Trezor is enhancing security measures, including anonymous delivery options, in response to a data breach affecting 67,000 customers.

user avatarFilippo Romano

Data Breach Affects 67,000 Trezor Customers

chest

A data breach at shipping provider ShipMonk has exposed personal information of 67,000 Trezor customers in the US.

user avatarEmily Carter

BAI Establishes Global Settlement Layer for AI Agents to Enhance Collaboration

chest

BAI is building a global settlement layer to enhance collaboration and efficiency among AI agents across various workflows.

user avatarTomas Novak

BAI Launches Free Access to Premium AI Models, Surpassing 133 Trillion Daily Tokens

chest

BAI has launched free access to its premium AI models, leading to a significant increase in platform activity and user adoption.

user avatarKaterina Papadopoulou

Axis Robotics Unveils Axis Sim Dataset V1 for Enhanced Robotic Manipulation

chest

Axis Robotics has released Axis Sim Dataset V1, one of the largest open-source simulation datasets for Franka arm manipulation, featuring over 50,000 human-teleoperated simulation trajectories.

user avatarMaya Lundqvist

ENS Proposes Migration to Layer 2 Registry Model

chest

Ethereum Name Service (ENS) has initiated discussions on a proposal to migrate domain registration and renewal to a Layer 2 registry model to reduce costs.

user avatarLeo van der Veen

Important disclaimer: The information presented on the Dapp.Expert portal is intended solely for informational purposes and does not constitute an investment recommendation or a guide to action in the field of cryptocurrencies. The Dapp.Expert team is not responsible for any potential losses or missed profits associated with the use of materials published on the site. Before making investment decisions in cryptocurrencies, we recommend consulting a qualified financial advisor.