What Sponsors Must Include

• Operator Identity: organisational name and intended deployment scope
• Use Case: infrastructure alignment and tunnel purpose
• Jurisdiction Bias: preferred regional zones
• Sponsor Assurance: reason for vouching, prior lineage performance
• Voice Contact Metadata: operator’s encrypted call alias or number

Voice Channel Activation

• EcoVPN initiates contact with the prospective operator using sponsor-supplied voice metadata
• There is no public phone number or direct contact portal, access is granted outbound only
• Voice validation confirms operational intent and Tier eligibility

Review Process

• Signals are manually vetted by Infrastructure Ops including entropy scoring and lineage audit
• Unqualified signals are ignored silently; sponsors may be notified of Tier impact
• Approved applicants receive tunnel configuration and Tier metadata via secure channel

Common Issues

• Missing voice contact info in sponsor glyph submission
• Vague operational scope or ambiguous region intent
• Attempting personal use or bypassing sponsor validation flow

Best Practices for Sponsors

• Pre-validate your invitee’s deployment logic before issuing a glyph
• Use consistent jurisdiction bias to align with your node stewardship
• Monitor signal response time after voice contact initiation

“Glyph access begins with the sponsor and ends with signal trust.”