Mandel 19 Meeting Highlights

Further updates on platform support as Mandel hits a historic landmark.

Credit: Bywire News, Canva
Credit: Bywire News, Canva
Bywire - Claim your free account nowBywire - Claim your free account now

LONDON (Bywire News) - It’s been a great week for Mandel, as the first release candidate for Mandel 3.1 has been released on Jungle 4. With EOS celebrating its anniversary on the same day, it feels like a symbolic declaration for the whole of the network. 

For more details on this and some of the other highlights from meeting number 19, read on. 

Mandel Code 

After development teams worked overtime, Mandel RC1 was released on Jungle4 on June 14th. Already people have deployed it and started using it on Jungle. The release coincides with the anniversary of the EOS chain being activated. Four years later the first independent release from the EOS community is now available on Jungle. 

Jungle Activation 

EOS Nation and EOSphere have both upgraded to Mandel 3.1 RC1 Jungle 4. The Working group has proposed the following timeline for continued Jungle 4 testing: 

  • An MSIG will be needed to upgrade the CDT. 
  • CDT needs to be upgraded on Jungle 4. They will aim to have at least 15 of 21 block producers upgraded to 3.1 between June 15th to June 21st).
  • Next week’s Mandel meeting will be a go/no go on the decision to activate EVM features. An MSIG will be needed to activate EVM features on June 22nd/23rd.
  • MSIG to update system contract using new CDT.

Platform Support 

After feedback from a developer, they had identified some new unit testing tools which could be added. They will soon have support for unit testing tools for smart contracts available on D.U.N.E.

Testing strategy

There are a number of things which need to be done to make Kylin ready for testing. To speed things up EOS Nation will propose an MSIG on Kylin to update EOSIO permissions granting them and EOS USA permissions to accelerate the process of preparing updates for testing. 

After the call, a risk was raised that history solutions such as Hyperion and Dfuse need time to test with Mandel 3.1 RC1. Dfuse still needs a great deal of testing before it is ready to run on Mandel 3.1. The status of Hyperion will need to be checked with the EOS Rio team.

(Writing by Tom Cropper, editing by Klaudia Fior)

Bywire will email you from time to time with news digests, stories & opportunities to get involved. Privacy

Bywire - Claim your free account nowBywire - Claim your free account now