Migration from EOSIO to Mandel

Dissatisfaction with Block One

In 2021, the EOS Community felt disappointed about the commitment of Block One with the them because of the lack of investment and action on behalf of B1 in supporting in the EOS blockchain. For these reasons, through a super-majority consensus of Block Producers, the community affirms that the company doesn't act in the interest of the community and were stop the payment that the company receives for the network maintenance.

After the fallout with B1, the EOS founder Daniel Larimer indicates that it’s necessary to restructure the EOSIO brand, its name, vision, and goals. Also, he says that is the beginning of a new era for EOS by firing B1 and no longer issuing tokens to them, as it allows the community to confront corporate interests that do not align with their interests.

Also, the EOS Network Foundation (ENF) emerged as a new alternative to direct network funds into furthering the development of the EOSIO protocol and EOS mainnet. The EOS Network Foundation's vision is to build a decentralized future where no sacrifice the community, cooperation, or consensus, making easy innovation through the union and empowerment of the developers around the world.

EOSIO vs Mandel

The EOS community didn't want to include all the code from the latest versions of the protocol because some of the added features didn't align with the interests of the community, so it was decided to start from EOSIO 2.0.13 using only some of the new features from EOSIO 2.1.0 and EOSIO 2.2.0.

For this reason, arises Mandel (abbreviation of Mandelbrot) which is a bifurcation of EOSIO source code, this was made by the team of ƒractally (previously known as Clarion OS) with the purpose of taking some of the most valuable improvements from EOSIO 2.1.0 and a few from EOSIO 2.2.0. In addition, to updating the protocol with Contract Pays and Enhanced Configurable Blockchain Params.

Also, it's important to know that Mandel is a provisional name. For more information visit Mandel to takeover EOSIO.

The previous features are concentrated in Mandel 3.0 which is derived from EOSIO 2.0.13, although some block producers updated to EOSIO 2.1.0, so there will be a Mandel 2.3 that derives from EOSIO 2.1.0 to ease the migration to Mandel 3.0 by avoiding downgrading the EOSIO version.

Mandel Changes

Among the changes included in Mandel 3.0, the following are worth mentioning:

• Is possible to configure the WASM limits, because for security reasons before was limited to several WASM parameters, but, thanks to the improvements in the performance now it’s secure to increment the limits and in looking for expanding limits are configurable.
• Include Pay contracts, where an account called provider is created with a certain amount of NET and CPU resources and the authorization private key is published so that anyone can sign a transaction, and if it's not cancelled the provider account will cover the NET and CPU expenses, the above in order to:
  • Implement transactions that are structured identically to Bitcoin transactions.
  • Delete the cost of creation of accounts for those who only want to use EOS as currency.
  • Incorporate privacy tokens without your privacy being compromised by the resource system.
• Enhanced configurable blockchain params to facilitate the add, elimination, and configuration of future objective features.

What is ƒractally doing with Mandel?

According to ƒractally in their page of frequently asked questions EOS community FAQ:

ƒractally is developing a suite of next-generation DeFi standards, including a token standard, nft standard, premium name system, premium token symbol system, and decentralized exchange. These standards are required for ƒractally to realize its vision.