Leap software development

[chillsauce]

As an EOS node operator, I need to know what version of EOSIO I should be testing on testnets so that I can be prepared for the eventual upgrade on mainnet.

• or 3.1 for everyone
• Release candidate target mid-late June
• Final release about a month later
• aim to have BPs upgraded by end of August
• consensus upgrade can happen later (September 21)

Useful consensus features to consider activating by fall:

• configurable WASM limits (careful - incorrect config could brick the chain. test all configurations on testnets)

• get code hash

• return value from action

  • configure blockchain params

• Need to align on what consensus features we will activate

[chillsauce]

3.1 is the preferred option, waiting on costs and timelines. should have better sense in 1-2 weeks

[chillsauce]

Transaction lifecycle features may be ready to start testing in late May, or perhaps sooner

[chillsauce]

ENF will be sharing the acceptance criteria broadly for the transaction lifecycle features in the next week

[chillsauce]

Question from @matthewdarwin in Telegram:

I just want to make sure I understand what is in mandel 3.1. From what I heard, it has the following things:

• based on mandel 3.0rc1
• merge in b1 2.0 latest stuff Merge from 2.0.x eosnetworkfoundation/mandel#43
• port dfuse support from 2.1 Backport dfuse support eosnetworkfoundation/mandel#38
• port blocks.log rotation feature (strides) from 2.1 (clarification from @cc32d9: also includes state history logs)
• transaction lifecycle features (4 of them, as per API+ blue paper)

Anything else planned so far?

[chillsauce]

The following EOSIO 2.1 items added into Mandel 3.1 (alongside what is already built in
Mandel 3.0):

• Provide options for nodeos to automatically split the blocks log and state history logs
  (every X blocks).
• An eosio_blocklog utility that can read and split the logs.
• Merge the work of the dfuse team (deep-mind logger) that was included in the 2.1
  release.
• Remove deprecated features and modules listed at EOSIO Deprecations EOSIO/eos#7597

[chillsauce]

We're waiting for confirmation from Fractally team that they will commit to the 3.1 work

Dan's team confirmed they will be releasing 3.05 by early next week, which will include the following:

• Merge the work of the dfuse team (deep-mind logger) that was included in the 2.1

release.

ENF Engineers are all onboard by April 11

[chillsauce]

3.0.5 has been merged and is ready to be tested on Jungle
eosnetworkfoundation/mandel#38

There's no release yet, if you want to test you'll need to build your own binary.
ENF will release when new devs start in 3 weeks.
EOS Sweden is publishing their binaries. @cc32d9 will ask them to post this when it's ready.

Kevin will tag it as a release candidate 3.0.5 RC1
Fractally team will provide release notes for their changes.
Kevin will provide release notes for OCI changes.

From the Fractally team: "We have not tagged this work/commit because there are obviously OCI and numerous community contributions still to be included for 3.1. In lieu of a specific tag, this PR shows the merge where we included the dfuse changes. Let me know if you need any further details."

[chillsauce]

3.0.5.RC1 is now tagged with release notes

[chillsauce]

Bucky will be joining on April 18, Matt and Areg (new ENF devs) joining on April 11th

[chillsauce]

Transaction lifecycle features tracking for early June to be ready for testing on Jungle

[chillsauce]

Request for another feature to backport: eosnetworkfoundation/mandel#85

There are a number of additional features that would be good candidates to backport. Stan and Kevin will work on compiling a list.

Stan has already started a list: https://github.com/cc32d9/code_reviews

[chillsauce]

From @matthewdarwin :

Hello all,

As part of mandel 3.1 plans, it has been previously discussed that the "blocks.log splitting feature" is a necessary requirement for the release to be acceptable to the community. Recently, a question arose, as to what is the actual requirements necessary for 3.1 related to this feature.

It is my (and a few other people's view) that the desirable list of features for mandel 3.1 is as follows:

1. keep all the blogs.log, in a single file, as per nodeos 2.0 (no change). Starts from beginning or based on a snapshot.

2. keep some recent blocks, in one file (or optionally more files at the discretion of the developers), and remove old blocks when the configured number of blocks passes

• this is less features than is in 2.1 where it can split files, move them to archive directory, and other things

3. don't store any blocks at all (this is a new feature, not in 2.1)

If you have opinions one way or another, please add thoughts to the github issues:
eosnetworkfoundation/mandel#100
eosnetworkfoundation/mandel#92

Above also applies to "ship" (state history)

[chillsauce]

• 2 items have been prioritized for 3.1
• 7 items have been identified as candidates to be prioritized for 3.1
• Otherwise, 3.1 feature set has been frozen

https://github.com/orgs/eosnetworkfoundation/projects/3

[chillsauce]

• Leap 3.1 Final release is out: https://github.com/AntelopeIO/leap/releases/tag/v3.1.0
• DUNE RC3 and CDT RC3 is expected within the next week or so

[chillsauce]

• CDT RC3 was released yesterday
• The current release of DUNE is not compatible with CDT RC3 and will require a minor update.

[stephenpdeos]

DUNE RC3 has been released to support CDT RC3 and Leap 3.1.0 Stable https://github.com/AntelopeIO/DUNE/releases/tag/v1.0.0-rc3

[chillsauce]

• EOS system contracts, DUNE and CDT will likely go to Final by the end of the week. No changes expected, just a version bump.

[chillsauce]

• Patch release of 3.1.2 expected later today or by end of week
• 3.2.0 RC1 also expected by end of week

[chillsauce]

• Leap 3.2 RC1 is out
  • This should include all the best of 2.1 plus some improvements in particular for performance issues experienced on WAX
• CDT release 3.1 by end of this week or early next week
• Possibility we'll get EOS system contract release in the next 1-2 weeks

[stephenpdeos]

We are actively addressing the msig issue mentioned in the last two calls within this issue. We do not have a definitive timeline for eos-system-contracts v3.2.0 but this will be part of it AntelopeIO/reference-contracts#7. Please note this issue is for reference contracts but the change will be in both places.

[chillsauce]

• Expecting Leap 3.2 RC2 with some bug fixes by the end of this week or early next week
• CDT release 3.1 by end of this week or early next week
• EOS System contracts and reference contracts to be updated shortly after to make it more user friendly
• ENF is still working towards a possible March/April timeline for next consensus upgrade to Leap 4.0

[chillsauce]

On the way:

• Leap 3.1.3 patch release
• Leap 3.2.0 RC2
• CDT 3.1.0 RC1 for CDT
• System contract updates
• Release of DUNE in the next month

[chillsauce]

• Antelope software updates just released:
  • Leap 3.1.3 patch release
  • Leap 3.2.0 RC2
• Antelope software updates on the way:
  • CDT 3.1.0 RC1
  • System contract updates
  • Release of DUNE in the next month