Show HN: ERPC – encrypted, typed RPC over any bidirectional channel
eRPC is a new framework for encrypted, typed remote procedure calls over various bidirectional channels. It offers end-to-end encryption and supports multiple authentication modes, making it versatile for different environments. The framework is designed to be transport-agnostic and is compatible with various platforms including Node.js and modern browsers.
- ▪eRPC uses XSalsa20-Poly1305 AEAD for end-to-end encryption.
- ▪It supports multiple authentication modes including pre-shared secrets and asymmetric methods.
- ▪The framework is compatible with Node.js, browsers, Service Workers, and more.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/dotexorg/erpc |
| Publication time | Wed, 27 May 2026 11:31:17 +0000 |
| Retrieval time | 2026-05-27T11:37:59.142Z |
| Last seen | 2026-05-27T11:37:59.142Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 93lEGQ9xrBbd |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
eRPC Encrypted, typed RPC over any bidirectional channel. Two peers, one shared secret (or one keypair). Every call is end-to-end encrypted with XSalsa20-Poly1305 AEAD. WebSocket, postMessage, MessagePort, chrome.runtime, BroadcastChannel, WebRTC — if a channel can carry bytes, eRPC encrypts and types what flows through it. Think tRPC, but transport-agnostic and encrypted by default. npm install @dotex/erpc Full docs and rationale: https://dotex.org/epic/erpc Quickstart · API · Wire Protocol · Security · Transports Highlights Typed procedures with Zod input/output validation End-to-end encryption. X25519 ECDH, XSalsa20-Poly1305 AEAD, HKDF-SHA-256, with forward secrecy by design Lazy handshake on the first call.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.