Why

Hiding your IP (Tor, mixnets) doesn't hide what you asked for. A shielded wallet still hands the RPC server a leaf index or commitment hash on every read, and that pointer is enough to reconstruct who you are.

Raven closes that gap on the query layer. The wallet sends an encrypted query, the server runs computation over the database without ever decrypting which row is the target, and the wallet recovers the record locally. Same proofs, same chain, blind reads.

Scope of the blindness is bounded and documented: PIR hides which row inside a shard, but the shard identifier travels in the clear today. Read SECURITY.md for the open items before serving real value.

How it works

• Encoders turn a logical store (Merkle tree, key-value map) into a flat array of fixed-width rows that the PIR server can answer queries over. The same engine handles per-leaf, per-path, per-node, or per-key layouts depending on what the workload needs.
• Sharding maps every entry to one shard at one offset. Updates re-encode only the affected shards, not the whole database.
• Blue-green rebuilds keep a second engine warm. It absorbs new chain events in the background and atomically swaps in when ready, so live queries never block on indexing.

PIR schemes

Scheme	Status
InsPIRe	Integrated.
iSimplePIR	WIP

Adapters

Currently one: Railgun.

• Uses InsPIRe for both static and dynamic state.
• Blue-green rebuild pattern keeps PPOI status, PPOI paths, and commit-tree paths fresh against live chain head.
• Drop-in POINodeInterface for the Railgun wallet stack.

Live demo: https://demo.railgun.hisoka.io/

Build

crates/inspire is a git submodule and the root workspace does not resolve without it:

git clone --recursive https://github.com/hisoka-io/raven.git
# already cloned without --recursive:
git submodule update --init --recursive

cargo test --workspace
cargo check -p raven-client --target wasm32-unknown-unknown

--workspace covers the root members only. Several trees are detached workspaces (crates/inspire, crates/isimplepir, crates/binary-fuse-filter, adapters/railgun, examples/eth-state); build each with its own --manifest-path. The wasm target applies to the client path (raven-client), not to every crate: server-side crates pull in native-only dependencies.

License

Apache-2.0 © Hisoka.io