Test Leap on Jungle 4

[chillsauce]

Action items:

• [x] confirm if we can proceed with launching Jungle 4 on B1's 2.0 @ansigroup
• [x] Launch jungle 4 with B1's 2.0 (latest release)
• [x] BPs registered on Jungle 4
• [x] 15/21 BPs (ideally more) upgrade to 3.1 (June 15 - June 21)
• [x] Release CDT for Jungle4 (June 17-21)
• [x] go/no-go during next Mandel weekly call to activate EVM features (June 22)
• [x] MSIG to activate EVM features (June 22-23)
• [ ] MSIG to update system contract using new CDT (June 23-24)

Resources

Mandel

• Mandel GitHub repo
• Mandel release notes
  • Binary is available under Assets

Jungle 4

Monitor: https://monitor4.jungletestnet.io/ Info: https://github.com/EOS-Jungle-Testnet/Node-Manual-Installation

API: https://jungle4.cryptolions.io/ P2P: jungle4.cryptolions.io:9870

Validator: https://validate.eosnation.io/jungle4/reports/api_versions.html

[chillsauce]

Action item: confirm if we can proceed with launching Jungle 4 on B1's 2.0 (Sudip)

[ansigroup]

Yes, we can do, will prepare boot scripts for J4

[chillsauce]

Jungle 4 Monitor: https://monitor4.jungletestnet.io/ Info: https://github.com/EOS-Jungle-Testnet/Node-Manual-Installation

API: https://jungle4.cryptolions.io/ P2P: jungle4.cryptolions.io:9870

[chillsauce]

BPs will register to Jungle 4:

• [x] Cryptolions @ansigroup
• [x] EOS USA @eosusa
• [x] NodeOne @nodeoneio
• [x] EOS Nation @eos-nation
• [x] EOSeoul @letspesl
• [x] Aloha EOS @NatPDeveloper
• [x] Amsterdam @cc32d9
• [ ] Costa Rica @eoscostarica
• [x] EOS Argentina Telegram and GitHub: @elmato
• [x] EOS Sphere
• [x] AtticLab

[chillsauce]

EOS Nation has upgraded about half of our nodes to 3.0.5.RC1

[chillsauce]

EOS Nation upgraded Jungle4 API nodes to Mandel 3.0.5-rc1. The validator can process this version information as well: https://validate.eosnation.io/jungle4/reports/api_versions.html

[chillsauce]

Can Aloha add Jungle 4 to their benchmarks? @NatPDeveloper

[chillsauce]

EOSphere is running 3.05 RC1 on Jungle 4, public API and seed peer. BP coming soon

[chillsauce]

There have been reports that Jungle 4 was forking and losing LIB.

@matthewdarwin has confirmed that this is not due to any issue with the Mandel software and not unexpected for Jungle4 given the testing happening on unstable releases. Jungle4 is meant to be the testnet for breaking stuff. ENF may want to consider funding a stable testnet for dApp developers, along the lines of the B1 testnet, which is no longer stable.

[chillsauce]

• EOSphere is now producing on 3.05
• Micheal is looking forward to testing 3.1 features
• Matthew has been testing new 3.1 features as they become available and reports all is good
• Think about what role Kylin plays in testing - does it mirror EOS current state or future state?

[chillsauce]

• EOS Nation and EOSphere are now running Mandel 3.1 RC1 on Jungle 4
• CDT needs to be upgraded on Jungle4 - crypto lions will see if they can upgrade themselves or if it requires coordination with Jungle BPs

Next steps

• Heads up to Jungle BPs (June 15) @chillsauce
• 15/21 BPs (ideally more) 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)
• MSIG to update system contract using new CDT (June 23-24)

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.

[chillsauce]

Go/no-go outcome:

• No go for June 22 activation
• Need to wait for Mandel 3.1 RC2 (1-2 weeks)
• Need more BPs to upgrade (21 ideally, no less than 15)

[chillsauce]

• Daniel will engage with CryptoLions to get their Jungle4 nodes upgraded to Mandel 3.1 RC2 and post MSIG to activate features on Jungle4
• Kevin will confirm and document activation procedure
• We'd like an update from Michael (EOS USA) on the status of Hyperion on Mandel 3.1 with features activated

[chillsauce]

• Consensus features are activated 🥳
• Hyperion is working 🥳
• dfuse stopped working upon activation, but a fix is underway. dfuse will be needed for UX's IBC solution
• Need to look into activating BLOCKCHAIN_PARAMETERS consensus feature, which has not yet been activated

[chillsauce]

• Opportunity to do more testing on system contracts and CDT.
• Get Jungle to confirm we're running latest version of contracts and CDT

Stephen Diesel from ENF has suggested the following areas to focus on:

Re: testing for contracts and CDT, I have received the following feedback thus far:

For CDT:

Baseline able to compile mandel-contracts. But, would be good to see others trying to build their own contract projects.

For Contracts: Baseline is to set mandel-contracts as the system contract. But, it would be good to exercise any new functionality explicitly.

[chillsauce]

• BLOCKCHAIN_PARAMETERS has been activated
• 15/15 BPs have signed MSIG to deploy updated system contracts on Jungle4. Pending execution.
• Focus for testing on Jungle4 this week:
  • deploy system contracts
  • BPs should upgrade to Mandel 3.1 RC3
• Other EOSIO chains will be participating in testing soon too

[chillsauce]

EOS USA has noted that older versions of Hyperion have issues on Jungle with Mandel (3.1.4). Use latest version of Hyperion (3.3.5 or later).

[chillsauce]

This week we'll work to deploy updated system contracts to Jungle and Kylin: https://github.com/eosnetworkfoundation/eos-system-contracts/releases/tag/v3.1.0-rc2

[chillsauce]

CryptoLions is reporting that they're getting the same hashes for RC2 as RC1. ENF will look into it.