SPHERE is a decentralized network that provides secure identity authentication, encrypted communication, peer-to-peer content hosting, and verifiable randomness — all without relying on blockchains or central servers.
Identity in SPHERE is based on fragmented private keys. Each key is split into encrypted segments, and reassembled during authentication using chained decryption — meaning users prove identity without revealing sensitive data or relying on any central authority.
Yes. SPHERE lets you publish content via ContentIDs stored in a decentralized hash table (DHT). Users can register a familiar web-style alias (like 'www.yoursite') which is converted into a secure reference on the network. These sites are tamper-resistant, censorship-proof, and served directly through peer nodes.
SPHERE uses elliptic curve cryptography (ECC) for key generation and hybrid symmetric encryption (AES-256) for storing content and message payloads. Each interaction is authenticated using HMAC verification.
SPHERE aliases map human-readable names to encrypted ContentIDs or identities. These are stored in the DHT with access controlled via signed BRACE tokens. Users query aliases to locate content, websites, or users without needing DNS or third-party directories.
Yes. You can wrap SPHERE endpoints into Web2 frontends or expose encrypted services via public APIs. Identity and content hosting can also be integrated into traditional websites with minimal setup.
Absolutely. SPHERE is designed to run on lightweight devices like Raspberry Pi. Nodes validate requests, store encrypted fragments, and power the network. You remain in control of what services you offer.
Unlike blockchains, SPHERE doesn’t rely on mining, consensus, or global state. It’s faster, lighter, and easier to scale. While it uses tokens internally for permission control and resource validation, there are no public tokenomics, transaction fees, or mining overhead — just verifiable logic and encrypted data exchange.
No one — and that’s the point. With SPHERE, governance handled at the node and protocol level. There are no gatekeepers or centralized authorities.