Safrochain Mainnet Validator onboarding form

Use this form to submit and update your validator onboarding application for Safrochain. Submissions are reviewed by the Foundation team; you will be contacted using the email address you provide if further information or next steps are required. Completing the form does not guarantee selection or delegation.

Application window closes: Saturday, May 30, 2026

For questions about this form or eligibility, contact [email protected] or the Safrochain Discord #validator channel.

Application

Complete the form below. Fields marked with * are required. Your submission is stored securely and used solely for Foundation review and communication related to this onboarding process.

Applicant details

Entity, team, or individual name *

Use your company or team name when applicable. If you are a solo operator, use your legal name or the name you use publicly for validator work (it does not have to be a registered organisation).

Country / region *

Where you are based or where your validator operations are primarily run (country is enough; add region if helpful).

Primary contact name *

For individuals, this is usually you; for teams, the main point of contact.

Planned mainnet

Planned mainnet moniker *

The validator name you plan to use on mainnet (as it would appear on explorers). Use 2-70 characters. Do not use your email, full legal name as sole identifier, or your wallet address here.

Validator wallet address (Safro testnet) *

Use Trust Wallet on Safro testnet. This must be the same wallet you will use on mainnet. We store both the testnet and mainnet address formats below.

Paste your addr_safro1… address only. It must differ from your email and planned mainnet moniker (do not paste the same text into multiple fields).

Mainnet (same wallet)

Derived automatically from your addr_safro address and is not editable.

Contact & social

Email *

Work or personal email you check regularly. Do not reuse your planned mainnet moniker or testnet wallet address here.

City / region

Optional. City and country or region (helps with time zones and local community context).

Optional. @username or t.me link, whichever you use for validator / team contact.

Discord

Optional. Username or server invite you are comfortable sharing.

Twitter / X handle

Optional. @handle for your validator or team account.

GitHub profile URL

Optional. Full URL to your user or org (e.g. contributions or open-source work).

Website / blog URL

Optional. Validator site, blog, or landing page (https://…).

Keybase / on-chain identity

Optional. Keybase username or proof string if you use it for validator identity on other chains.

Applicant type *

Individual if you apply alone; organisation if a registered entity; team for an informal group of operators.

If organisation or team: name, legal form, and country of registration

Required when you are not “Individual”. At least a short legal name, entity type, and country.

Testnet validator

Did you operate a validator on the Safrochain testnet? *

Choose Yes only if you ran a validator node on Safro testnet; extra testnet fields appear below.

Technical experience & infrastructure

Years operating validator nodes *

Total experience across chains as a validator operator (not relayer-only unless you also validate).

Networks validated, other chains, and profile links *

List chains, roles (validator / relayer / contributor), and links to profiles or explorers where reviewers can verify your history.

Mainnet server infrastructure setup *

Regions, providers, redundancy (e.g. multi-AZ), monitoring, and how you isolate signing from sentry / public nodes.

Anticipated Mainnet uptime SLA *

Realistic target for signing availability (choices span from 99.9%+ down to 80%); the Foundation may use public uptime signals at review time.

Disaster recovery plan *

How you would recover from datacenter loss, key compromise suspicion, or chain halt. Pick the option that best matches today.

Disaster recovery summary (optional)

Optional: RTO/RPO if you track them, backups, runbooks, and last time you tested a restore or failover.

IBC relayer experience *

If you run or have run IBC relayers (e.g. Hermes, Go relayer), say so here; otherwise choose No.

Intended Mainnet commission *

Planned commission rate at launch (e.g. 5% or 0.05; be consistent with how you express it).

Intended self-stake (SAF) on Mainnet

Optional rough plan (amount or range). Mainnet is not live yet; this is indicative only.

SF validator maintainer

Are you interested in joining Safrochain as an SF Validator Maintainer (volunteer or compensated)? *

Maintainers help with docs, tooling, testnet support, and governance. Choose No if you are only applying as a validator operator.

Optional pre-stake (USDC on Noble)

Deposit between $100 and $1,000 USDC as a sign of good faith.
You will receive 100% of your deposit back in SAF tokens on Mainnet launch day.
In addition, you will receive an automatic delegation bonus from the Foundation to boost your voting power from day 1.
This is completely optional. Testnet active validators will also receive a retroactive delegation even without deposit.

Noble treasury address, Safrochain Foundation (SF) multisig (100-1000 USDC, whole units, optional):

noble1vpvsxfr462xldafy5luj6gtafftj3vx0cpau67

View on explorer

Denom: uusdc

Amount (USDC)

Leave empty to skip payment. If you set an amount or broadcast a tx, it must be a whole number between 100 and 1000.

Custom amount (optional)

After a successful broadcast, the transaction hash is filled in automatically. You do not paste it manually.

Declarations

I confirm the information in this application is accurate and complete to the best of my knowledge. *I have read and understand the Foundation delegation policy for testnet activity and eligibility. *I agree to the processing of this data for onboarding and compliance. *

Submit sends the complete application (all required fields, declarations, and security check when enabled). You get a reference ID after success.

Save draft uploads the full form as a work-in-progress. You need a valid email; the draft is tied to this browser tab (session token).

Loading form…