Week 12 - December 14

[chillsauce]

The EOS Node Operator Roundtable meets every Wednesday at 14:00 UTC to prepare for the next EOS consensus upgrade and share feedback on opportunities to improve the Antelope protocol for node operators.

💬 Join us in Telegram 🗂 See all meeting summaries

🗓 December 14 - 14:00 UTC

🎥 Watch the recording

• Passcode: mGH6Ec?8

Summary

🟢 Leap Software Status

41

• Antelope software/documentation updates on the way:
  • CDT 3.1 targeted for Today
  • DUNE release sometime soon
  • No longer plans for 3.2.1 patch release
  • Document on how crypto extensions inside CDT to utilize crypto primitive host functions
  • System contract updates

Technical roundtable for EOS Node Operators

• This week we wrapped up last week's discussion on what statistics should be added to the prometheus exporter in Leap 4.0 and discussed opportunities for node operators to address the WAX congestion issues currently being experienced.

Additional requests and feedback for monitoring at the Node level (low hanging fruit):

• head block drift
• LIB offset (current time - LIB time)
• Feedback from the group: monitoring doesn't need to be every block, once or twice per round is probably enough
• Would be nice if it could also be available in JSON in get info 2

WAX Network Congestion

The problem

• Seeing lots of failed transactions due to what seem to be some incentive in the network to push lots of transactions
  • Blocks are missed
  • Blocks are empty
  • Transactions expire

Possible solutions

• Proposed changes to LEAP:
  • Pass the blocks along without doing transaction level validation
    • Easy to add, but would not help with current WAX congestion
    • What would help: Interrupt the execution of the current block to pass the block faster
  • Apply 3 strikes rule to all transactions
    • In 3.2
    • Could have a 3 strike rule according to contract or action (risk of DDoS - probably not a good solution)
  • Validating failed transactions
  • cap to the unapplied queue
  • logging framework (on a new thread)
  • subjective billing plugin or service (not at the node level)
  • Ability for a user to see the subjective billing status for their account (in 3.2)

Future opportunities

• Resource model discussion opportunity
  • Should we bill failed transactions?

Advice for WAX node operators:

• Upgrade to 3.2
• Make sure you have subjective billing turned on for all nodes

In the new year

• Gather feedback on the challenges we're looking to address with a potential resource model change (not public)
  • Brian to lead? Daniel, Stephen and Brian to coordinate to set up this conversation
• For a future discussion in the new year, Matthew has proposed a conversation on the Antelope resource model
  • As can be seen with the current congestion issues on WAX, there are opportunities to improve the resource model on Antelope chains
  • Who do we need to participate:
    • Areg - document some of the initial thoughts and direction - some options for proposals that we can provide feedback on
    • Gather your thoughts in advance

Participants (15)

• Max_Cho :: KOREOS Owner-South Korea
• Kevin Heifner
• Randall Roland
• john@boid.com
• Stephen Diesel
• Daniel Keyes | EOS Nation
• EOSUSA Michael
• Matthew Darwin
• Bart Wyatt
• Dario | EOSsupport.io
• Ted Cahall
• @I_Seth |Boid|Animus BlockBase
• Jeff Werner
• Ross (EOSphere)
• Denis Carriere