Validator Onboarding Guide

Step-by-step process to become a Pilier validator: from application to full activation.

Reading time: 15 minutes

---

Overview

Timeline

Total duration: ~90 days

Week 1-2:   Submit EOI → Initial review
Week 3-6:   Technical review → Testnet trial (30 days)
Week 7-8:   Governance proposal → Voting (14 days)
Week 9-12:  Onboarding → Sign Charter → Generate keys → Activate

Prerequisites

Before applying, ensure you:

• ✅ Are an eligible entity (university, NGO, public body, chamber, standards body)
• ✅ Have reviewed Eligibility
• ✅ Understand Responsibilities
• ✅ Can cover operational costs (~€500/month or apply for grants)
• ✅ Have technical capacity (sysadmin, 24/7 emergency contact)

---

Phase 1: Expression of Interest (Week 1-2)

Step 1: Self-Assessment

Complete the Eligibility Checklist:

Question	Your Answer
Is your entity non-commercial?	☐ Yes ☐ No
Legally registered in EU?	☐ Yes ☐ No
Mission aligned with Pilier values?	☐ Yes ☐ No
Can cover €500/month operational costs?	☐ Yes ☐ No
Have technical staff?	☐ Yes ☐ No
Can provide 24/7 emergency contact?	☐ Yes ☐ No
Commit to 99% uptime target?	☐ Yes ☐ No
Can respond to incidents <2 hours?	☐ Yes ☐ No

If all ✅ Yes: Proceed to Step 2

If any ❌ No: Review eligibility requirements or contact validators@pilier.org for guidance

---

Step 2: Submit Expression of Interest (EOI)

Send email to: validators@pilier.org

Subject: Validator Application - [Entity Name]

Email template:

Hello Pilier Team,

We are interested in becoming a Pilier validator.

## Entity Information

**Legal name:** [Full legal name]
**Entity type:** [University / NGO / Public Body / Chamber / Standards Body]
**Country:** [EU member state]
**Registration number:** [Company/org registration #]
**Website:** [URL]

## Contact Information

**Primary contact:**
├─ Name: [Full name]
├─ Title: [Job title]
├─ Email: [email]
├─ Phone: [phone with country code]
└─ Telegram: [@username] (optional)

**Technical contact:**
├─ Name: [Sysadmin name]
├─ Email: [tech email]
├─ Phone: [emergency phone, 24/7]
└─ Availability: [on-call schedule]

**Emergency backup contact:**
├─ Name: [Backup person]
└─ Phone: [backup emergency phone]

## Mission Alignment

**Our organization's mission:**
[Brief description, 2-3 sentences]

**Why we want to become a validator:**
[Explain alignment with Pilier values: transparency, sustainability, EU sovereignty, etc.]

**How we will contribute to Pilier ecosystem:**
[Research collaboration? NGO partnerships? Public sector pilots?]

## Technical Capacity

**Infrastructure:**
├─ Hosting: [Self-hosted / Cloud (OVH, Hetzner, AWS, etc.)]
├─ Hardware: [Specs: CPU cores, RAM, disk, network]
├─ Location: [City, country, datacenter if applicable]
└─ Redundancy: [Backup server? Yes/No]

**Team:**
├─ Sysadmin experience: [Years, relevant skills]
├─ Blockchain experience: [Yes/No, details if yes]
├─ Security practices: [Firewall, monitoring, backups, etc.]
└─ On-call coverage: [How we handle 24/7 emergency response]

## Budget

**Operational costs (monthly estimate):**
├─ Server hosting: €[X]
├─ Monitoring tools: €[X]
├─ Staff time: €[X]
├─ Insurance: €[X]
└─ Total: €[X]

**Funding source:**
[Internal IT budget / Grant / Institutional support / Need infrastructure grant]

**Infrastructure grant needed?**
☐ Yes, requesting: [Hardware subsidy / Hosting subsidy / Training budget]
☐ No, self-funded

## Availability

**When can we start testnet trial?**
[Date or "Immediately"]

**Estimated time to prepare infrastructure:**
[X weeks]

## Attachments

Please find attached:
├─ Certificate of incorporation (PDF)
├─ Statute/bylaws (proving non-profit status)
├─ Most recent annual report (if applicable)
└─ Proof of address (utility bill or lease)

## Confirmation

I confirm that:
☐ We have read the Validator Charter documentation
☐ We understand the responsibilities and commitments
☐ We are prepared for a 30-day testnet trial
☐ Our legal team will review the Charter before signing

---

Best regards,
[Name]
[Title]
[Entity]
[Email]
[Phone]

---

Step 3: Initial Review (3-5 Business Days)

Pilier core team reviews your EOI:

Review checklist:
├─ Entity eligibility (matches criteria?)
├─ Mission alignment (values match?)
├─ Technical capacity (can they run a validator?)
├─ Budget feasibility (can they afford it or need grant?)
└─ Documentation completeness (all attachments provided?)

Possible outcomes:

✅ Approved for technical review:

Email response:
"Welcome! You've passed initial review. Next steps:
1. Technical review + testnet trial (30 days)
2. Timeline: Start [date]
3. Instructions attached"

⚠️ Request for more information:

Email response:
"Thank you for your application. We need additional information:
- [Question 1]
- [Question 2]
Please provide by [date]."

❌ Not eligible:

Email response:
"Thank you for your interest. Unfortunately, [reason].
Alternative: [Suggestion, e.g., become a client instead of validator]"

---

Phase 2: Technical Review (Week 3-6)

Step 4: Hardware Audit

Pilier provides detailed hardware requirements:

Minimum specifications:
├─ CPU: 4 cores (8 recommended)
├─ RAM: 16GB (32GB recommended)
├─ Disk: 500GB NVMe SSD (1TB recommended)
├─ Network: 100 Mbps symmetrical (1 Gbps recommended)
└─ Uptime: 99.5% SLA from hosting provider

Software stack:
├─ OS: Ubuntu 24.04 LTS (or compatible)
├─ Pilier node binary: Latest stable release
├─ Monitoring: Prometheus + Grafana (or equivalent)
└─ Backup: Daily snapshots (off-site storage)

You provide:

Infrastructure details:
├─ Server specs (screenshot of `lscpu`, `free -h`, `df -h`)
├─ Network test (bandwidth test results)
├─ Hosting provider SLA (uptime guarantee document)
└─ Backup strategy (documented procedure)

Security measures:
├─ Firewall config (only necessary ports open)
├─ SSH hardening (key-based auth, no password login)
├─ Monitoring setup (Prometheus endpoints, alert rules)
└─ Access control (who has SSH access? MFA enabled?)

Pilier reviews and provides feedback:

Common issues:
├─ Insufficient disk space → Upgrade to 1TB
├─ No monitoring → Set up Prometheus/Grafana
├─ Weak SSH config → Disable password auth, enforce keys
└─ Missing backup plan → Document daily snapshot procedure

---

Step 5: Testnet Trial (30 Days)

Purpose: Prove you can run a validator reliably before mainnet.

What you'll do:

Day 1: Setup
├─ Receive testnet bootnodes list
├─ Sync testnet blockchain (~2-4 hours)
├─ Generate session keys (testnet)
└─ Submit session keys to Pilier (for validation)

Day 2-7: Shadow validator
├─ Observe-only mode (not producing blocks yet)
├─ Monitor sync status, peer connections
├─ Familiarize yourself with telemetry dashboard
└─ Test monitoring alerts (simulate failure)

Day 8-30: Active validator
├─ Added to testnet validator set
├─ Produce blocks and finality votes
├─ Target: 99.5%+ uptime
└─ Weekly check-ins with Pilier team

Day 30: Final evaluation
├─ Review performance metrics
├─ Discuss any issues encountered
└─ Decision: Ready for mainnet? or extend trial?

Performance targets:

Metric	Target	Your Result
Uptime	≥99.5%	_%
Block production	~20% (if 5 validators)	_%
Finality participation	100%	_%
Peer connections	≥10	_
Average block import time	<500ms	_ms

Common issues during trial:

Issue: Node won't sync
├─ Check bootnodes (are they correct?)
├─ Check firewall (P2P port 30333 open?)
└─ Check disk space (enough room for blockchain?)

Issue: Missing blocks
├─ Check session keys (correctly submitted?)
├─ Check system time (NTP synchronized?)
└─ Check CPU usage (not overloaded?)

Issue: Low peer count (<10)
├─ Check firewall (incoming connections allowed?)
├─ Check network (NAT issues? Port forwarding?)
└─ Add more bootnodes (request list from Pilier)

Weekly check-in template:

To: validators@pilier.org
Subject: Testnet Trial Week [N] - validator-{id}

Hello,

Here's our weekly testnet trial update:

**Performance (Week [N]):**
├─ Uptime: X.XX%
├─ Blocks produced: X / Y (Z%)
├─ Finality votes: X / Y (Z%)
└─ Issues: [None / List any issues]

**Issues Resolved:**
├─ [Issue 1]: [How we fixed it]
└─ [Issue 2]: [How we fixed it]

**Learnings:**
├─ [Lesson 1]
└─ [Lesson 2]

**Questions:**
├─ [Question 1]
└─ [Question 2]

Next week's goals:
├─ [Goal 1]
└─ [Goal 2]

---
[Your name]
[Entity]

---

Step 6: Security Audit (During Testnet Trial)

Pilier conducts lightweight security review:

Audit scope:
├─ Penetration test (automated scan for common vulnerabilities)
├─ Configuration review (SSH, firewall, node config)
├─ Access control review (who has access? MFA enforced?)
└─ Monitoring review (alerts configured? tested?)

Typical findings:
├─ SSH password auth enabled → Disable, keys only
├─ Root login allowed → Disable, use sudo
├─ Firewall too permissive → Close unnecessary ports
├─ No monitoring alerts → Set up email/SMS alerts
└─ Weak session key backup → Encrypt backup, store off-site

You fix issues within 7 days, re-audit if needed.

---

Step 7: Testnet Trial Evaluation

After 30 days, Pilier evaluates your performance:

Pass criteria:
├─ Uptime: ≥99.5% ✅
├─ Block production: ≥95% of expected ✅
├─ Finality participation: ≥99% ✅
├─ Security audit: No critical issues ✅
└─ Responsiveness: Timely weekly check-ins ✅

If PASS:
└─ Proceed to governance proposal (Phase 3)

If FAIL (rare):
├─ Option 1: Extend trial by 14-30 days (address issues)
├─ Option 2: Defer to next cohort (need more prep time)
└─ Option 3: Withdraw application (not ready)

---

Phase 3: Governance Proposal (Week 7-8)

Step 8: Governance Proposal Submitted

Pilier submits proposal on your behalf:

Proposal title: "Add validator-{id} ([Entity Name])"

Proposal content:

# Proposal: Add validator-amsterdam-01 (University of Amsterdam)

## Summary

Onboard University of Amsterdam as institutional validator to strengthen
EU academic network and geographic diversity.

## Entity Information

**Name:** Universiteit van Amsterdam
**Type:** Public research university
**Country:** Netherlands
**Website:** uva.nl

**Mission alignment:**

- Research focus: Digital rights, privacy, open science
- Values: Transparency, academic freedom, EU sovereignty
- Contribution: Research collaboration, student projects

## Technical Review

**Hardware:**
├─ CPU: 8 cores (AMD EPYC)
├─ RAM: 32GB
├─ Disk: 1TB NVMe SSD
├─ Network: 1 Gbps symmetrical
└─ Location: Amsterdam, Netherlands (university datacenter)

**Testnet trial results (30 days):**
├─ Uptime: 99.7% ✅
├─ Blocks produced: 2,156 / 2,160 (99.8%) ✅
├─ Finality votes: 43,200 / 43,200 (100%) ✅
├─ Peer connections: 15 average ✅
└─ Issues: None (smooth operation)

**Security audit:** PASSED
├─ No critical vulnerabilities
├─ Configuration compliant with Validator Charter
└─ Monitoring and alerting properly configured

## Impact Analysis

**Benefits:**
├─ Geographic diversity (first Netherlands validator)
├─ Academic credibility (top-tier research university)
├─ Civic trust narrative (public institution)
└─ Research collaboration (Pilier as academic testbed)

**Risks:**
├─ University funding cycles (potential budget cuts)
├─ Academic calendar (summer break, holidays)
└─ Mitigation: 24/7 on-call coverage, backup operators

## Charter Compliance

- [x] Signed Validator Charter (pending governance approval)
- [x] Insurance coverage (cyber liability €50k, professional indemnity €100k)
- [x] 24/7 monitoring and emergency contact
- [x] Disaster recovery plan documented

## Timeline

If approved:
├─ Week 1-2: Mainnet sync
├─ Week 3: Shadow validator (observe-only)
└─ Week 4: Full validator activation

## Budget

No treasury allocation required (validator self-funded).

## Voting

**Threshold:** 75% approval + 20% quorum
**Duration:** 14 days
**Start:** [Date]
**End:** [Date]

---

**Submitted by:** Pilier Core Team
**Contact:** validators@pilier.org
**Applicant contact:** validator-ops@uva.nl

---

Step 9: Community Discussion (14 Days)

During voting period, you should:

1. Introduce yourself on forum
   └─ forum.pilier.net/governance/proposal-XXX
   └─ Share your story, answer questions

2. Engage with community feedback
   ├─ Technical questions: Answer promptly
   ├─ Mission questions: Explain your values
   └─ Concerns: Address transparently

3. Reach out to other validators
   └─ Telegram: @pilier_validators
   └─ Build relationships (you'll be peers soon)

4. Participate in Q&A sessions (if scheduled)
   └─ Video call or forum AMA
   └─ Show your team's competence and commitment

Example forum post:

Hello Pilier community!

I'm Jean Dupont, validator operator for University of Amsterdam's
proposed validator node.

**About us:**
We're a public research university with a strong focus on digital rights
and open science. We see Pilier as aligned with our mission: creating
open, transparent infrastructure for the public good.

**Why we want to join:**
- Contribute to EU digital sovereignty
- Use Pilier as research testbed (with community input)
- Support SME adoption in Netherlands
- Strengthen academic validator network

**Our commitment:**
- 24/7 operations (we run critical university services)
- 99.5%+ uptime target (backed by institutional SLA)
- Active governance participation (we'll vote on proposals)
- Transparency (we'll publish quarterly reports)

**Questions?**
Happy to answer anything. You can reach me:
├─ Forum: @uva_validator
├─ Email: validator-ops@uva.nl
└─ Telegram: @jean_dupont_uva

Thank you for considering our application!

---
Jean Dupont
University of Amsterdam

---

Step 10: Governance Vote

Voting mechanics:

Eligible voters: All tPIL holders
Voting period: 14 days
Threshold: 75% approval + 20% quorum (high bar for validator additions)

Example tally:
├─ Total eligible: 920,000 tPIL
├─ Voted: 485,000 tPIL (52.7% turnout) ✅ >20% quorum
├─ Aye: 395,000 tPIL (81.4%) ✅ >75% approval
├─ Nay: 75,000 tPIL (15.5%)
├─ Abstain: 15,000 tPIL (3.1%)
└─ Result: PASSED ✅

If approved: Proceed to Phase 4 (Onboarding)

If rejected: Rare, but possible reasons:

├─ Technical concerns (testnet performance)
├─ Mission misalignment (community doesn't see fit)
├─ Timing (too many validators added recently)
└─ Unresolved questions (lack of transparency)

Next steps:
├─ Option 1: Address concerns, re-apply in 3-6 months
├─ Option 2: Withdraw application
└─ Option 3: Engage with community to understand objections

---

Phase 4: Onboarding (Week 9-12)

Step 11: Sign Validator Charter

Legal agreement between validator entity and Pilier SAS:

Process:
1. Pilier sends Charter via DocuSign (or wet signature if required)
2. Your legal representative reviews (3-5 business days)
3. Sign and return
4. Counter-signed by Pilier
5. Both parties retain signed copy

Key clauses to review:

Responsibilities:
├─ 99% uptime target
├─ <2 hour incident response
├─ Governance participation
└─ Security best practices

Compensation:
├─ Target: €500/month (best effort, not guaranteed)
├─ Source: Transaction fees + inflation subsidy
└─ Exchange: 1 PIL = €1.00 via Treasury

Liability:
├─ Limited to 12 months compensation (€6,000 cap)
├─ Not liable: Network downtime with due diligence
└─ Liable: Gross negligence, willful misconduct

Term & Termination:
├─ Indefinite duration
├─ Voluntary exit: 90-day notice recommended
└─ Involuntary removal: Via governance vote (75% approval)

Your legal team's common questions:

Q: Can we negotiate terms?
A: Charter is standard (all validators sign same document).
   But: Concerns can be raised via governance amendment process.

Q: What if French law conflicts with our local law?
A: Both apply (hierarchy: mandatory local law > French law > Charter).
   Conflicts are rare; Pilier can clarify if issues arise.

Q: What's our liability cap?
A: €6,000 (12 months × €500 compensation).
   Exception: Gross negligence, willful misconduct (no cap).

Q: Can we exit anytime?
A: Yes, no financial penalties. 90-day notice recommended (graceful handover).

---

Step 12: Generate Session Keys (Secure Ceremony)

Session keys = cryptographic keys used for block production and finality voting.

Security requirements:

Generate on:
├─ Offline machine (air-gapped, no network)
├─ Or secure VM (encrypted disk, no internet after generation)
└─ NOT on validator server itself (defense in depth)

Backup:
├─ Encrypted with strong passphrase
├─ Stored off-site (separate physical location)
└─ At least 2 copies (primary + backup)

Access control:
├─ Only authorized operators can access keys
├─ MFA required for key storage access
└─ Audit log (who accessed keys, when?)

Step-by-step key generation:

# On secure, offline machine:

# 1. Download Pilier binary (verify checksum)
wget https://releases.pilier.net/v1.x.x/pilier-node
sha256sum pilier-node
# Compare to official checksum: https://releases.pilier.net/checksums.txt

# 2. Generate session keys
./pilier-node key generate \
  --scheme sr25519 \
  --output-type json \
  > session-keys.json

# 3. Backup keys (encrypt with GPG)
gpg --symmetric --cipher-algo AES256 session-keys.json
# Enter strong passphrase (min 20 chars, mix of symbols/numbers/letters)
# Output: session-keys.json.gpg

# 4. Store encrypted backup off-site
# - USB drive in safe
# - Encrypted cloud storage (with separate password manager entry)
# - Physical printout in sealed envelope (bank vault)

# 5. Securely transfer public keys to validator server
# Do NOT transfer private keys over network
# Option A: Physical USB (sneakernet)
# Option B: QR code (scan with phone, type manually)
# Option C: Short-lived SSH with key destruction after transfer

# 6. Wipe offline machine
shred -vfz -n 10 session-keys.json
# Reboot machine, verify file deleted

Submit public keys to Pilier:

Email: validators@pilier.org
Subject: Session Keys - validator-amsterdam-01

Body:
Please find our session keys (public portion only):

{
  "babe": "0x1234abcd...",
  "grandpa": "0x5678ef01...",
  "im_online": "0x9012ab34..."
}

Generated on: [Date]
Backup verified: [Date]
Authorized by: [Name, Title]

We confirm:
☐ Keys generated on offline machine
☐ Backup encrypted and stored off-site
☐ Private keys NOT transmitted over network
☐ Only authorized operators have access

---
[Your name]
[Entity]

---

Step 13: Shadow Validator (7 Days)

Purpose: Observe mainnet before actively validating.

What you'll do:

Day 1-2: Sync mainnet
├─ Download latest snapshot (faster than full sync)
├─ Start node: pilier-node --validator --name validator-amsterdam-01
├─ Monitor sync progress: tail -f /var/log/pilier/node.log
└─ Wait for full sync (~6-24 hours depending on snapshot age)

Day 3-4: Observe-only mode
├─ Watch telemetry: https://telemetry.pilier.net
├─ Monitor peer connections (should be 10+)
├─ Check block import times (\<500ms)
├─ Familiarize with mainnet traffic patterns

Day 5-6: Dry-run session keys
├─ Load session keys (without announcing to network)
├─ Test key rotation procedure (simulate emergency)
├─ Verify monitoring alerts fire correctly

Day 7: Final readiness check
├─ Review all monitoring dashboards (Prometheus, Grafana)
├─ Test emergency contact procedure (24/7 phone)
├─ Confirm backup restoration (can you restore from backup?)
└─ Sign-off: "Ready for full validator activation"

Checklist before activation:

☐ Node fully synced (block height matches explorer)
☐ Peer connections stable (10+)
☐ Session keys loaded and tested
☐ Monitoring alerts configured and tested
☐ Backup restoration tested (successfully restored from snapshot)
☐ Emergency contacts tested (Pilier called your 24/7 number)
☐ Insurance policy active (cyber liability + professional indemnity)
☐ Disaster recovery plan documented
☐ Team trained on incident response procedures

---

Step 14: Full Validator Activation

Coordinated activation with other validators:

Timeline:
├─ T-48h: Pilier announces activation date/time
├─ T-24h: Confirm readiness (final check-in)
├─ T-0: Activation (governance extrinsic executed)
├─ T+1h: Monitor first blocks produced
└─ T+24h: First era complete, performance review

Governance extrinsic (executed by sudo or validator multisig):
└─ session.setKeys(validator_account, session_keys_public, proof)

What happens:

Block N (activation block):
├─ Your validator added to session keys pallet
├─ BABE selects you for block production (random)
├─ GRANDPA includes you in finality voting
└─ You're now a full validator ✅

Within first hour:
├─ Expected: Produce ~3-5 blocks (depends on BABE randomness)
├─ Expected: Participate in all finality rounds
└─ Monitor: No errors in logs

Within first 24 hours (first era):
├─ Expected: Produce ~17-20% of blocks (if 5 validators)
├─ Expected: 100% finality participation
└─ Review: Telemetry dashboard, peer feedback

Activation day checklist:

☐ All team members on standby (no vacations during activation)
☐ Backup operator available (in case primary unavailable)
☐ Monitoring dashboards open (telemetry + Prometheus)
☐ Telegram notifications enabled (@pilier_validators)
☐ Emergency phone charged and nearby
☐ Backup server ready (in case primary fails)
☐ Incident response playbook printed (physical copy)

---

Step 15: First Week Post-Activation

Monitor closely during first week:

Day 1:
├─ Check every 2 hours (blocks produced, finality votes)
├─ Verify no errors in logs
└─ Respond to any alerts within 15 minutes

Day 2-7:
├─ Check twice daily (morning, evening)
├─ Weekly performance review (see template below)
└─ Engage with other validators (Telegram)

Day 7:
└─ Submit first weekly report to validators@pilier.org

First week report template:

To: validators@pilier.org
Subject: First Week Report - validator-amsterdam-01

Hello,

We've completed our first week as a Pilier validator. Here's our summary:

## Performance Metrics

**Uptime:** 99.9% (1 hour planned maintenance on Day 3)
**Blocks produced:** 1,215 / 1,220 (99.6%)
**Finality participation:** 10,080 / 10,080 (100%)
**Peer connections:** 12-15 (average)

## Issues Encountered

**Day 3 - Planned maintenance:**
├─ Duration: 1 hour
├─ Reason: Kernel security patch (required reboot)
├─ Impact: Missed 10 blocks, no finality disruption (4/5 validators active)
└─ Resolution: Back online, validated patch didn't affect node

**No other issues.**

## Learnings

├─ BABE randomness: Lower variance than expected (good distribution)
├─ Monitoring: Grafana dashboards are excellent
├─ Community: Helpful feedback from validator-lyon-01 on firewall tuning
└─ Governance: Voted on Proposal #043 (fee adjustment) - first vote!

## Plans for Next Week

├─ Set up automated backup verification (daily restoration test)
├─ Tune monitoring alert thresholds (reduce false positives)
└─ Attend validator sync call (if scheduled)

## Feedback

The onboarding process was smooth. Thank you to the Pilier team and
fellow validators for their support!

---
Jean Dupont
University of Amsterdam
validator-amsterdam-01

---

Post-Onboarding: Ongoing Responsibilities

Monthly Activities

☐ Claim PIL rewards (monthly)
☐ Exchange PIL for EUR via Treasury (if needed)
☐ Review performance metrics (telemetry dashboard)
☐ Vote on governance proposals (≥80% participation expected)
☐ Check insurance renewal (if annual policy)

Quarterly Activities

☐ Security checklist review (access controls, passwords, firewall)
☐ Test emergency contact (Pilier sends test alert)
☐ Disaster recovery drill (restore from backup)
☐ Lock PIL for tPIL (if not already done, build governance power)

Annual Activities

☐ Review Validator Charter (any amendments?)
☐ Renew insurance policies (cyber liability, professional indemnity)
☐ Annual report (publish performance summary on forum)
☐ Validator summit (if organized, attend in person)

---

Frequently Asked Questions

Application Process

Q: How long does the entire process take?

A: ~90 days (2 weeks application + 4 weeks testnet + 2 weeks governance + 4 weeks onboarding)

---

Q: Can we fast-track the process?

A: Not really. Testnet trial (30 days) and governance vote (14 days) are fixed durations. These ensure you're ready and community has time to evaluate.

---

Q: What if we fail the testnet trial?

A: Rare, but you can extend the trial (14-30 days) to address issues, or defer to next cohort.

---

Q: Can we withdraw our application?

A: Yes, at any stage. No penalties. Just notify validators@pilier.org.

---

Technical

Q: Do we need blockchain experience?

A: Helpful but not required. Strong sysadmin skills are more important (Linux, networking, monitoring). We provide documentation and support.

---

Q: Can we use cloud hosting (AWS, GCP, Azure)?

A: Yes. OVH, Hetzner, and Scaleway are more common (EU-based, cheaper), but AWS/GCP are acceptable.

---

Q: What if our hardware doesn't meet minimum specs?

A: Upgrade before testnet trial. Infrastructure grants available (up to €1,000 hardware subsidy).

---

Q: Can we run validator on university/office network?

A: Yes, but ensure:

• Firewall allows P2P port (30333)
• Static IP or dynamic DNS
• No NAT issues (test port forwarding)
• University IT department approves

---

Financial

Q: When do we start earning PIL?

A: Immediately upon activation (first era). Rewards paid per era (~24 hours).

---

Q: Can we cash out PIL rewards immediately?

A: Yes, but monthly exchange recommended (aligns with typical expense cycles). Strongly encouraged to lock 10-20% for tPIL (governance power).

---

Q: What if we can't afford operational costs?

A: Apply for infrastructure grant (hosting subsidy €200/month for 12 months). See Compensation Guide.

---

Governance

Q: Are we required to vote on proposals?

A: Yes, Charter expects ≥80% governance participation. Validators are infrastructure operators—your votes matter.

---

Q: Can we vote "No" on proposals we disagree with?

A: Absolutely. Voting "Nay" is encouraged if you have concerns. Explain reasoning in forum (transparency).

---

Q: What if we don't have time to analyze complex proposals?

A: Ask questions in forum. Other validators and community members provide analysis. Abstain if truly uncertain (but don't abstain frequently).

---

Support & Next Steps

During Application

Questions about eligibility? 📧 validators@pilier.org

Technical setup help? 📧 tech-support@pilier.org 📖 Node Setup Guide

Infrastructure grants? 📧 validators@pilier.org (mention "grant" in subject)

---

During Testnet Trial

Weekly check-ins: 📧 validators@pilier.org (use weekly template above)

Technical issues: 💬 Telegram: @pilier_validators (other validators can help)

Emergency: 📞 +33 X XX XX XX XX (24/7 hotline)

---

After Activation

Performance monitoring: 📊 https://telemetry.pilier.net

Governance portal: 🗳️ https://governance.pilier.net

Validator community: 💬 Telegram: @pilier_validators 🌐 Forum: forum.pilier.net/validators

---

Summary Checklist

Phase 1: Application (Week 1-2)

• ☐ Complete self-assessment
• ☐ Submit EOI email with attachments
• ☐ Respond to initial review feedback

Phase 2: Technical Review (Week 3-6)

• ☐ Pass hardware audit
• ☐ Complete 30-day testnet trial (≥99.5% uptime)
• ☐ Pass security audit
• ☐ Weekly check-ins submitted

Phase 3: Governance (Week 7-8)

• ☐ Governance proposal submitted by Pilier
• ☐ Introduce yourself on forum
• ☐ Answer community questions
• ☐ Wait for vote result (14 days)

Phase 4: Onboarding (Week 9-12)

• ☐ Sign Validator Charter
• ☐ Generate session keys (secure ceremony)
• ☐ Submit public keys to Pilier
• ☐ Shadow validator (7 days)
• ☐ Full activation coordinated
• ☐ First week report submitted

You're now a Pilier validator! 🎉

---

Appendix: Common Timelines

Fast Track (Minimum: 60 Days)

Week 1: Application + immediate approval
Week 2-5: Testnet trial (30 days, perfect performance)
Week 6-7: Governance proposal (14 days, passes quickly)
Week 8-9: Onboarding (sign Charter, generate keys, activate)

Rare: Only for highly qualified entities (existing blockchain validators, recognized institutions).

---

Standard Track (Typical: 90 Days)

Week 1-2: Application + initial review
Week 3-6: Testnet trial (30 days)
Week 7-8: Governance proposal (14 days)
Week 9-12: Onboarding

Most common: Expected timeline for typical applicant.

---

Extended Track (120+ Days)

Week 1-4: Application + multiple rounds of clarification
Week 5-8: Testnet trial (30 days)
Week 9-10: Testnet extension (14 days, address issues)
Week 11-12: Governance proposal (14 days)
Week 13-16: Onboarding

Occurs when: Technical issues during testnet, governance discussion requires more time, or infrastructure delays.

---

Ready to apply? Email validators@pilier.org with your EOI! 🚀