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.
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
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
Summary
🟢 Leap Software Status
@stephenpdiesel
on Telegram to get an inviteTechnical roundtable for Antelope Node Operators
We discussed a proposal for custom port/ip configurations in a future release of Leap 5.0:
Next week's topic: feedback from community and node operators around dreams for 5.0
Participants (17)