About the Validator Introductions subcategory

Welcome to Validator Introductions

This is the place for Story Protocol validators to introduce themselves to the community.

For Delegators: Browse validator profiles to find operators that align with your values—whether that’s technical excellence, ecosystem contributions, or long-term commitment to Story’s IP mission.

For Validators: Introduce your operation using the template provided when you create a new topic. Keep it concise—delegators are busy and will scan for key info.


Posting Guidelines

  1. One post per validator operation — edit your existing post for updates

  2. Use the template — it pre-fills when you create a new topic

  3. Keep it scannable — short answers, no walls of text

  4. Update your mainnet uptime — delegators check this


Questions? Message on #validator-support in Discord

9 Likes

TEMPLATE

Validator introductions will use the following template


Overview

Validator Name: [ Your validator moniker ]
Operator ID(s):

  • storyvaloper... [ locked | unlocked ]

Website: [ https://… ]
Twitter: https://x.com/[ Twitter handle ]

Infrastructure

Type: [ Bare metal | Dedicated cloud | Hybrid ]
Regions: [ North America | South America | Europe | Asia | Africa ]
Security Certs: [ SOC2 | ISO27001 | None ]

Experience

Operating Since: [ Year ]
Networks Validated: [ number of networks, estimates are fine ]
Story Mainnet Uptime: [ ##.#% ]
Story Testnet (Iliad/Odyssey): [ Yes, uptime % | No ]

Story Ecosystem Contributions

  • [ How has your team contributed to the ecosystem beyond validation? ]
  • [ If your team has yet to do so, how does your team plan to contribute ]
  • [ Use of bullet points preferred ]

Why Delegate to Us?

[ Write 2-3 sentences: What makes you stand out? ]

Links

5 Likes