The Antelope Node Operator Roundtable meets every Wednesday to share and discuss feedback to improve the Antelope.io protocol.
This first topic of discussion involved a status update on Leap 5.0. The team has worked on fixes for issues found in the testing of the release candidates and aims to have Leap 5.0 RC3 available in early December.
Following this, Kevin Heifner led a discussion on a proposed change to P2P to support arbitrary labeling of peers. They also, discussed the need for a more structured configuration format in adding more options to this configuration and reviewed issue #1870, which involves long wait times when stopping nodeos due to the need to flush state files.
Matthew of EOSNation and Ross of EOSphere shared their reasons for using ZFS, in relation to performance. Ross highlighted a blog about how ZFS helps to run nodes on WAX:
In an informal poll, 3 out of 7 were using ZFS, others were using BTRFS and ext4. The team then reviewed issue #1861 which involves long log lines caused by non-default options and Matthew expressed concerns about the readability of the log files due to many lines from non-default options. Kevin then pointed out the value of fewer lines for receiving debug information from node operators.
Finally, those in attendance Reviewed issue #1763, involving a request for a new –is-state-compatible check and the general consensus that this would be valuable. The options identified include the proposed flag or more explicit exit codes.
The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// EOS Network Foundation //
info@eosnetwork.com
#EOS #Web3
[ad_2]
source
