You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EOS Nation and EOSphere have upgraded to Mandel 3.1 RC1 on Jungle4
The working group proposed the following timeline for continued testing on Jungle4:
15/21 BPs (ideally 21/21) upgrade to 3.1 (June 15 - June 21)
Release CDT for Jungle4 (crypto lions will need to prepare for the MSIG to activate it) (June 17-21)
go/no-go during next Mandel weekly call to activate EVM features (June 22)
MSIG to activate EVM features (June 22-23)
Note - the following risk was raised after the call: history solutions like Hyperion and dfuse need time to test with mandel 3.1-rc1. dfuse still needs a lot more testing before it is ready to run on Mandel 3.1. Hyperion status should be checked with EOS Rio team. There would be no working block explorer if no history solutions are ready at the time of feature activation.
MSIG to update system contract using new CDT (June 23-24)
EOS Nation will propose an MSIG on Kylin to update EOSIO permissions granting authority to EOS Nation and EOS USA to facilitate more rapid updates in preparation for testing.
Participants (21)
Host: Daniel Keyes | EOS Nation
Max_Cho EdenOnEOS Member-South Korea
g
Matt Witherspoon
Kevin Heifner
Andriy Cryptolions (Andriu Bobrovych)
Bucky Kittinger
Stephen Diesel
Yves La Rose
Genie Kim - EOSeoul# NEOPLY
Lovejoy
Alysha Mims
Hahn Ryu (@luckyhahnryu)
Ted Cahall
Jeff Werner
EOSUSA Michael
junhank | NodeONE
Johnsonb - Object Computing# Inc.
Ross (EOSphere)
Vlad
Denis Carriere
The text was updated successfully, but these errors were encountered:
The Mandel upgrade working group meets every Wednesday at 13:00 UTC to check in on progress towards action items.
β Track project progress
π¬ Join us in Telegram
π See all meeting summaries
π June 15 - 13:00 UTC
π₯ Watch the recording
Summary
π’ In progress action items are on track:
Participants (21)
The text was updated successfully, but these errors were encountered: