Validator & RPC Infrastructure
Institutional Staking Infrastructure

“Validated for
Confident Decisions”

FP Validated is a blockchain infrastructure service provider that aims to enable the growth and maturation of digital asset networks.
Model
Validator · RPC
Footprint
5 providers
Posture
SOC 2 / ISO 27001
Version
2026.6
1
Rule above all — stop before restarting any active signer
0
Validator signing keys exposed on a server
2
Planes — control and workload, never co-located
100%
Changes reconciled & auditable through GitOps
↓ Scroll
01 — Vision
Validator as a Prepared & Trusted Partner for builders & institutions.

We believe validation should be boring in the best way — provably safe, fully auditable, and resilient across providers and regions. That is the infrastructure we are building, one clean separation at a time.

02 — Footprint

Live Today

Capacity is spread deliberately across independent providers
— no single vendor is a single point of failure.

Azure AKS · Management plane Argo CD · Vault · Observability GitOps fp:* summary OVH Cluster · k3s workload plane Encrypted private overlay OVH Worldstream Azure LA Cherry
14
Workload nodes — all Ready
5
Cloud providers
24
Chain networks operated
99.9%+
Effective uptime
How we're built differently
Signing Model
FP ValidatedThreshold Signing
Common SetupSingle Key File
Active Keys in K8s Secrets
FP ValidatedNever
Common SetupFrequently
Control vs Workload
FP ValidatedSeparated Planes
Common SetupCo-located
Provider Diversity
FP Validated5 Providers · Multi-region
Common SetupSingle Provider
Change Traceability
FP ValidatedGitOps + Audit Evidence
Common SetupManual / Ad-hoc

Comparison reflects architectural posture, not vendor benchmarks. “Common Setup” = a typical single-cluster, single-provider validator deployment.

03 — Team

Who We Are

FP Validated formally began scaling its team in 2026, but we are far from starting from scratch. Our team brings together leadership experience from one of Asia's largest validator companies, alongside veteran SREs who have operated hundreds of nodes under a SOC 2-compliant environment.

Our AUS is growing rapidly, and we are already working with institutions, VCs, and companies on white-label validator offerings and technical collaborations. With this foundation, FP Validated is positioned to become one of the most Prepared & Trusted validator partners for builders and institutions entering staking and blockchain infrastructure.

Node operations team · 5 members
Jay Jeong
Co-founder & Head of Validator.
Former Head of Governance at A41.
Hyuksoo Jang
Validator Advisor & Tech Researcher.
Former Head of Validator and Tech Lead at A41; former Cloud Architect Engineer at Samsung SDS Research / Cloud Business Division.
Hyunmin Kim
SRE.
Former SRE at A41; former node operator at Lambda 256.
Seokhyun Sim
SRE.
Former node operator at DSRV and Shinlabs.
Yeonghyun Sim
SRE.
Former node operator at Shinlabs.
Executive & research team · 8 members
Namwoong Kim
Co-founder & CEO.
Co-founder and former Head of Research at A41.
Heechang Kang
Co-founder & CSO.
Former researcher at Xangle.
Jinsol Bok
Co-founder & Head of Research.
Former researcher at A41.
+ team
Additional sector-specialized researchers and data engineers across the team.
04 — Networks

What We Operate

We build every network on one Kubernetes-based, institution-grade operating model — Cosmos-SDK chains, Sui & Walrus, Canton, Ethereum and Solana, and ten mainnet EVM / RPC networks, all reconciled by Argo CD.

Validators · 14 networks
Ethereum mainnet Ethereum testnet Solana testnet Canton Splice Sui mainnet Sui testnet Stable mainnet Stable testnet Sei mainnet LayerZero DVN · mainnet Walrus mainnet Walrus testnet Initia mainnet Initia testnet
RPC · 10 mainnet endpoints
More to come
Ethereum BSC Solana Hyperliquid Avalanche Polygon Arbitrum Optimism Base Tempo
05 — Principles

Four Pillars of FP Validated

When you delegate stake, you are handing over a signing key and a slashing risk. Most outages are survivable; a double-sign or a leaked key is not. We built an operator whose entire architecture is organised around that single truth — safety before uptime theater.

Pillar 01

Control / Workload

SEPARATE THE PLANES

A hardened management plane governs identity, secrets and policy. Chains run on a separate workload plane. A management outage can never restart a validator.

Pillar 02

Key Safety

PROTECT THE KEY

Threshold signing, keys outside Kubernetes Secrets, no signer failover on an alert. Any signer-state change is a SEV-1 procedure, not routine ops.

Pillar 03

Observability

SEE BEFORE YOU ACT

Raw detail at the edge, low-cardinality summary at the center. Alerts explain; they never execute dangerous actions on their own.

Pillar 04

Compliance

PROVE EVERYTHING

GitOps desired-state, tiered RBAC and audit evidence designed for SOC 2 / ISO 27001 from the first commit — verifiable, not just promised.

06 — Architecture

One Clean Seam

A managed control plane on Azure governs an external, multi-provider workload cluster — diff-only, with prune disabled. Two flows cross the seam, and nothing else.

MANAGEMENT PLANE · AKS Govern Argo CDGitOps Vault + ESOsecrets Grafana · Prometheus · Alertmanager SSO / RBAC · Kyverno · Audit WORKLOAD PLANE · k3s Execute Validators · threshold signers RPC endpoints10 chains Exporters · Edge Prometheus Encrypted private overlay GitOps · prune OFF fp:* summary Azure Key Vault · Workload Identity · 0 static secrets
Management never runs chain workloads. The workload plane never holds the keys to its own kingdom.
07 — Key Safety

Safety First

Signing keys are held in cloud KMS / HSM, sealed by HashiCorp Vault, and reached only through a Kubernetes-native key-management layer using short-lived workload identity — the raw key is never written to a pod or a Git repo.

KEY-MANAGEMENT FLOW Cloud KMS / HSM root key, sealed HashiCorp Vault seal · auto-unseal Workload Identity short-lived access Signer calls KMS to sign Validator / Chain one valid signature Raw key never exported · Git stores references, not values · no usable key on any single server
Layered key management — cloud KMS / HSM sealed by Vault, reached only through short-lived workload identity — no single node, and no single layer, ever holds a usable key.
01
KMS / HSM-backed signing

The raw key never leaves the vault

Validator signing keys are generated and held in cloud KMS / HSM. The signer calls KMS to sign — the key material is never exported to the node.
02
Vault-sealed, auto-unseal

Sealed, not stored

HashiCorp Vault seals every operational secret and auto-unseals against cloud KMS. Git holds references, never values; no long-lived credentials live in a pod.
03
Threshold signing

No single machine holds a usable key

Where the network supports it, validators sign through a threshold signer that splits signing across independent nodes — double-sign resistant by construction, already live on Initia and Stable.
04
Kubernetes-native boundaries

Key access is bounded & audited

Active keys are barred from Kubernetes Secrets; access is bounded by Workload Identity and network policy, and every use is audited. Signer failover never auto-runs on an alert.
08 — Observability

Raw at the Edge,
Summary at the Center

High-cardinality detail stays near the workload. Only low-cardinality fp:* summaries travel to the center — cheaper, and built for compliance evidence.

EDGE — RAW · SHORT RETENTION Exportersnode·chain·proc Edge Prometheusdrill-down, local remote_write fp:* only CENTER — SUMMARY Central Prometheus Grafana · Alertmanager FP Validated Guard Telegram · Slack · PagerDuty
Alerts are evaluated by PrometheusRule → Alertmanager. Grafana visualises only; the Guard explains and humans approve dangerous actions.
block height & lagpeer countsync status validator healthRPC latencyerror rate
09 — Operations

Explainable.
Reversible.

Every change is governed by its blast radius. The workload cluster runs diff-only, prune OFF — drift is reviewed, never blindly synced.

01
Tiered change classes

From Docs to Signer/Key

Documentation, monitoring, management apps, workload policy, chain runtime and signer/key each carry their own approval bar and rollback path.
02
Evidence-gated onboarding

Join ≠ Activate

A new worker is provisioned, joined, isolated by taint, observed, and recorded before any chain is scheduled to it — a seven-step gate.
03
Stop conditions

We Halt When Unsure

Unclear signer impact, ambiguous deploy target, prune touching runtime state, a monitoring blind spot, or no rollback path — any one stops the change.
04
Recovery order

Safety First, Always

Confirm no signer/key risk → freeze evidence → restore visibility → isolate workload → controlled recovery. Backups land in zone-redundant storage.
10 — Coverage

Value We Secure

Across the networks we validate and serve, this is the value riding on the infrastructure.

Asset Under Staked
FP Validated — total delegated value across chains
FP Validated dashboard — delegated value across 6 chains

*Note: On Ethereum, we actively participate in Lido's CSM and IDVTC modules and are preparing non-custodial white-label staking solutions through stVaults. Through these initiatives, we aim to provide institutions and ecosystem partners with secure, scalable, and battle-tested staking infrastructure.

11 — Live

Validator Node Performance

Not claims — evidence. Swipe through public explorers and dashboards across the networks we run.

Node performance · public explorers
FP Validated Guard · internal operations

Our in-house operations tool tracks upgrade readiness and live resources / logs — the backbone of safety-first change management.

12 — Roadmap

What's Next

2026 H1Live

Multi-Provider Platform

Two-plane architecture in production: validators across five providers, ten mainnet RPC endpoints, threshold signing on Cosmos-SDK chains.

2026 H2In Progress

Compliance Attestation

SOC 2 / ISO 27001 evidence packets, monthly access reviews, and continuous Azure inventory matured into formal audit readiness.

2027 H1Planned

Region & Provider Expansion

Additional independent regions and bare-metal providers, with dedicated per-chain capacity sets and tighter private-access controls.

2027Goal

SOC 2 Type II Certification

Complete an independent SOC 2 Type II audit on top of our ISO 27001-aligned controls — formal assurance for institutional clients.

FP Validated · Litepaper 2026
Validator & RPC Infrastructure · © 2026