Antelope Node Operator Roundtable

Antelope Node Operators, community members and Antelope core developers meet every Wednesday at 14:00 UTC to discuss opportunities to improve the Antelope protocol for node operators.

💬 Join us in Telegram 🗂 See all meeting summaries

🗓 April 12 - 14:00 UTC

🎥 Watch the recording

Passcode: 3+D4%sB$

Summary

🟢 Leap Software Status

Leap 4.0.0-rc3 has been released:
- https://github.com/AntelopeIO/leap/releases/tag/v4.0.0-rc3
CDT RC1 expected next week
New developer office hours meeting hosted by ENF - Thursdays 9am eastern, every 2 weeks
- There'll be a CDT demo at the next developer office hours call
- Reach out to Stephen Diesel @stephenpdiesel on Telegram to get an invite

Technical roundtable for Antelope Node Operators

We discussed a proposal for custom port/ip configurations in a future release of Leap 5.0:

https://github.com/eosnetworkfoundation/product/pull/143/files
- This plan defines a proposed configuration format to let node operators set different addresses for HTTP endpoints provided by nodes.
- Instead of setting a different address for every single endpoint, endpoints are grouped together into categories. The high level categories proposed are get_info, chain_ro, chain_rw, net_ro, net_rw, producer_ro, poroducer_rw, snapshot, trace_api, prometheus, and node.
- The full list of endpoints for each category are defined in the plan.

Next week's topic: feedback from community and node operators around dreams for 5.0

Things that cause us pain
Things we could reinforce that make Antelope special

Participants (17)

Shaq
Brian Hazzard
Kevin Heifner
Max_Cho :: KOREOS Owner-South Korea
Daniel Keyes
EOSUSA Michael
Ross (EOSphere)
Stephen Diesel
Aaron Cox
Denis Carriere
MachnBird Sparo
J.P. | wakeupjohnny | Detroit Ledger Tech
Virginia Glass
'@I_Seth |Boid|Animus BlockBase
Tony Licavoli
Zach Butler - ENF Automation
Matthew Darwin

EOS-Nation / leap

April 12 - Proposal for custom port/ip configurations in Leap 5.0 #123