Voices on the call were aligned with the results of the survey with a few exceptions. In general:
There is a need for a chunked blocks.log file, but the way it was implemented in EOSIO v2.1 was no useful because the archived blocks aren't easily accessible.
There is value in having the ability to store some blocks in different locations, such as in slower disk storage.
BPs would appreciate another way to share blocks between nodeos instances (in particular, similarly to how Ethereum supports automatic peer discovery and automatically downloads and backfills the history over BitTorrent.)
For nodes that serve API queries, BPs would appreciate a way for nodeos instances with partial blocks to retrieve blocks from another nodeos instance to fill API requests for blocks it does not have locally.
As a result of the technical discussion, a few new features were added to the ENF's development backlog.
Next week, the ENF will be providing a demo of their public program management system to provide more transparency into the Antelope development roadmap and give the community an opportunity to influence it.
The Antelope Leap upgrade working group meets every Wednesday at 13:00 UTC to prepare for the next EOS consensus upgrade.
✅ Track project progress 💬 Join us in Telegram 🗂 See all meeting summaries
🗓 October 26 - 13:00 UTC
🎥 Watch the recording
Summary
🟢 In progress action items are on track:
41
Participants (11)