ORION: Trust the Identity, Not the Location
Why decentralized identity overlays matter for resilient systems — and how ORION uses Ed25519-signed records and P2P lookup to decouple trust from network location.
The problem with location-based trust
Most systems assume that if you reach the right IP or hostname, you can trust the response. That breaks under DNS hijacking, routing attacks, censored networks, and multi-region failover. ORION separates identity verification from where data is served — you validate cryptographic records, not server locations.
What ORION is
ORION (Open Resilient Identity Overlay Network) is a decentralized identity overlay built by Scraplay. Records are signed with Ed25519, replicated via P2P distributed lookup, and designed for high availability. The goal: trust the identity attached to data, regardless of which node serves it.
How it works in practice
Publishers sign identity records. Peers index and resolve those records across the overlay. Consumers verify signatures locally — no central authority required for lookup. If one node goes offline, others continue serving verified records. Location becomes an implementation detail, not a trust anchor.
Where it helps B2B systems
API endpoints that must survive infrastructure changes, federated services across regions, and any architecture where clients need to verify who they are talking to — not just where packets route. ORION complements TLS and PKI; it does not replace them, but adds an identity layer resilient to topology changes.
What's next
ORION is actively developed as Scraplay infrastructure. Explore the project at orion.scraplay.com or contact us if you are building systems that need location-independent identity verification.