VIX Wallet Identity
Users are identified by VIX wallet keys instead of phone numbers. A VIX identity can register trusted devices, public encryption keys, and contact relationships.
ValkNet is being designed as a secure communications network powered by VIX. It uses VIX wallet identities, local device encryption, onion-routed relay paths, decentralized message swarms, and blockchain-anchored proofs.
hash(ciphertext) → anchored, not plaintext
ValkNet is not designed around a normal centralized chat database. The long-term architecture is a VIX message protocol where private keys stay on user devices, messages are sealed before transport, and VIX nodes relay encrypted envelopes.
Users are identified by VIX wallet keys instead of phone numbers. A VIX identity can register trusted devices, public encryption keys, and contact relationships.
Each device generates its own private key locally. The private key stays on the device. Only the public device key is published to VIX for contact encryption.
Messages are encrypted before they leave the sender’s device. VIX relay nodes only handle sealed encrypted payloads and routing metadata.
Messages can be wrapped in multiple routing layers so each VIX relay only knows the previous hop and the next hop, not the full path.
Offline messages are stored temporarily by a decentralized swarm assigned to the recipient’s VIX identity. Swarms store encrypted envelopes only.
VIX Chain provides node registration, node trust, device-key proof, message hash anchoring, emergency broadcast proof, and future staking or reputation controls.
This page shows the intended flow. The live version will connect to VIX-MSG APIs for device registration, encrypted envelope submission, swarm inbox polling, and message proof anchoring.
A centralized chat app sends everything through one server. ValkNet is designed around a VIX node network. The app builds a sealed message envelope, wraps it for relay hops, and sends it through VIX relay nodes toward the recipient swarm.
{
"protocol": "VIX-MSG",
"identity": "VIX wallet key",
"device_key": "local private key",
"transport": "onion-routed relay path",
"storage": "recipient swarm",
"chain_use": [
"node registry",
"device key proof",
"swarm assignment",
"message hash anchor"
],
"plaintext_on_chain": false
}
ValkNet must be clear: blockchain is used for trust, identity, routing infrastructure, and proofs — not for exposing private messages.
Plaintext exists only on the sender and recipient devices. The network receives encrypted envelopes, not readable chat content.
Relay routing is designed so individual nodes forward traffic without knowing the full sender-to-recipient path.
Recipient swarms provide temporary encrypted mailbox storage so users can receive messages even when offline.
ValkNet is being designed so the VIX blockchain secures the network, not the private content. VIX can prove identity, node participation, device registration, route trust, and message integrity while keeping message text off-chain.
The website explains the protocol and previews the user experience. The real product direction is standalone mobile apps using the same VIX-MSG encrypted transport.
Public trust site explaining VIX wallet identity, encryption, relays, swarms, and proofs.
Current phaseDevice registry, relay node registry, message submit, swarm inbox, receipt, and proof APIs.
Next buildNative ValkNet Android app with local keys, encrypted messages, VIX routing, and offline inbox.
App buildNative iOS release after Android and VIX-MSG protocol are stable.
PlannedVIX wallet identities, local encryption, onion-routed relays, decentralized message swarms, and blockchain proof — built to become a real alternative to centralized messaging.
Review VIX-MSG Protocol