Conversation
| - **Geographic distribution**: Nodes run across multiple regions for redundancy. | ||
| - **Technical teams**: In-house engineering teams managing the infrastructure. | ||
| - **24/7 operations**: Dedicated teams monitoring and maintaining infrastructure around the clock. | ||
| - **Multi-client capability**: Ability to run different client implementations for network diversity. |
There was a problem hiding this comment.
Should we leave this out for now? There is only one client implementation right now.
There was a problem hiding this comment.
Yes, agree we should leave it out for now.
| - Active engagement with the XMTP community and willingness to contribute to protocol development and governance. | ||
| - **Technical and operational excellence** | ||
| - **Infrastructure ownership**: Own hardware or maintain control over infrastructure for maximum censorship resistance. Operators are ranked by resilience: | ||
| 1. **Own bare metal in friendly jurisdiction** (most resistant) |
There was a problem hiding this comment.
@jhaaaa should we replace "friendly" with what we mean by that.. like maybe "censorship-resistant"?
| 3. **Hybrid bare metal + cloud** | ||
| 4. **Multi-cloud providers** | ||
| 5. **Single cloud provider** (least resistant) | ||
| - **Performance**: Capability to run an XMTP node with reliable uptime and sufficient network and hardware resources to handle messaging throughput at scale. |
There was a problem hiding this comment.
Love this yes! Right now, we have some min requirements documented https://github.com/xmtp/xmtpd-infrastructure?tab=readme-ov-file#minimum-system-requirements -- but I'll check with the D14N team to see if it needs any updates. Once updated -- I'll add a link!
| 4. **Multi-cloud providers** | ||
| 5. **Single cloud provider** (least resistant) | ||
| - **Performance**: Capability to run an XMTP node with reliable uptime and sufficient network and hardware resources to handle messaging throughput at scale. | ||
| - **Security focus**: Implementation of robust security protocols and slashing protection. |
There was a problem hiding this comment.
could we be more descriptive of what type of security protocols are required?
remove slashing protection - unclear what this means in our current system
There was a problem hiding this comment.
Fantastic callout - let me check in with the D14N team about specific security protocols as well! I will add info/a link once available.
2 participants
Refine XIP-54 node operator qualifications and set XMTP Mainnet initial operator cap to 7 in xip-54-node-operator-qualifications.md
Update the XIP-54 document to introduce an initial cap of 7 node operators, generalize references to operator count, and expand qualification criteria across trust, governance alignment, and technical/operational excellence.
📍Where to Start
Start with the Abstract and Selection Process sections in xip-54-node-operator-qualifications.md.
Changes since #129 opened
Macroscope summarized c281ae4.