explaingit

alexanderdaly/neurofhe-relay

1JavaScriptAudience · researcherComplexity · 2/5ActiveLicenseSetup · easy

TLDR

Research package and pitch deck for a hybrid privacy gateway that combines neuromorphic spike preprocessing with homomorphic encryption, plus a small zero-dependency JavaScript prototype.

Mindmap

mindmap
  root((neurofhe-relay))
    Inputs
      Local sensor streams
      App logs
      Simulated events
    Outputs
      Encrypted features
      Safe local actions
      Recommendations
    Use Cases
      Pitch the concept to investors
      Run the JS demo
      Read the whitepaper
      Review risk register
    Tech Stack
      JavaScript
      Markdown
      PDF

Things people build with this

USE CASE 1

Read the one-pager, pitch deck, and whitepaper to understand the neuromorphic-plus-FHE thesis

USE CASE 2

Run the npm demo and benchmark scripts to see the gateway prototype in action

USE CASE 3

Reuse the risk register and post-quantum cryptography track as references for similar research

USE CASE 4

Adapt the gateway pattern doc for a privacy-preserving event pipeline of your own

Tech stack

JavaScriptMarkdownPDF

Getting it running

Difficulty · easy Time to first run · 30min

Most of the value is in the docs, deck, and whitepaper rather than code, so expect to read more than you run.

CC0 public domain, so you can copy, modify, and use it for any purpose with no attribution required.

In plain English

NeuroFHE Relay is a presentation and research package for an early-stage idea about privacy in event-driven AI. It is not a finished product. The repo combines two specialist areas: neuromorphic systems, which turn raw sensor or signal streams into sparse spike-like events instead of dense data, and homomorphic encryption, often shortened to FHE, which is a kind of cryptography that lets a server compute on data without ever decrypting it. The pitch is that those two ideas fit together at the boundary between local devices and cloud models. The design works in layers. Raw local signals from files, sensors, apps, logs, or simulated streams go through a spike sorter, then a local relay gateway that normalizes them and applies privacy policy. Only an approved, minimal event representation crosses the boundary. An encrypted compute service runs inference or verification on those features, and only a recommendation comes back, which the gateway then turns into safe local action. The raw payloads never leave the device. The author is careful about what to claim. The README says the project does not run FHE bootstrapping directly on neuromorphic chips, which would not be defensible today. The defensible near-term framing is a hybrid: neuromorphic preprocessing makes data sparse, and FHE protects the parts that need to stay private. The crypto target is described as quantum-resistant by design and cryptographically agile by default. Medical-device language is intentionally avoided since there is no clinical validation, dataset, or legal review behind the prototype. The package contents are mostly documents: a one-pager, a pitch deck, a technical architecture write-up, a demo roadmap, a risk register, evidence notes, a post-quantum cryptography track, a whitepaper on encrypted-thoughts architecture for brain-computer interfaces, and a gateway pattern doc. There is also a small JavaScript prototype with no dependencies that you can run with npm scripts: npm run demo, npm run benchmark, npm run gateway:demo, and others. Everything is released into the public domain under CC0.

Copy-paste prompts

Prompt 1
Summarize the neurofhe-relay architecture in plain English and explain why FHE bootstrapping on neuromorphic chips is not claimed
Prompt 2
Walk me through npm run demo, npm run benchmark, and npm run gateway:demo and what each one prints
Prompt 3
Read the encrypted-thoughts whitepaper and pull out the threat model for brain-computer interfaces
Prompt 4
Help me adapt the risk register template to my own early-stage privacy project
Prompt 5
Explain the layered design from raw signals to spike sorter to relay gateway to encrypted compute
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.