v1.1.0 - The Pre-Hash Protocol: A Major Architectural Upgrade

[focusjordan]

The Pre-Hash Protocol: A Major Architectural Upgrade

This release fundamentally revamps the cryptographic handshake of the ORBIT protocol to permanently eliminate Node.js Event Loop Blocking during high-throughput media ingestions.

⚠️ BREAKING API CHANGE FOR CLIENTS ⚠️

Because the server no longer verifies signatures against the raw audio buffer, all client-side upload scripts must be updated to match the new mathematical contract.

If you are building custom uploading scripts:
You MUST update your client to calculate the SHA-256 hash of your audio file, and sign the lightweight metadata + hash payload, rather than signing the 50MB raw binary. (Note: if you are using the official ORBIT SDK, this is handled automatically).

The core challenge of atomic binary transmission is that Ed25519 cryptographic validation is heavily CPU-bound. In previous versions, the ORBIT API node would verify signatures against the entire raw 50MB audio payload in pure JavaScript. This caused an ~800ms computation delay per upload that completely locked the V8 JavaScript thread. During this ~800ms window, the server could not accept any other incoming HTTP requests or execute database callbacks. If 10 clients uploaded concurrently, the 10th client would have had to wait 8 full seconds just to connect—exposing the infrastructure to devastating Denial of Service (DoS) and server overload vulnerabilities.

To mathematically guarantee non-blocking, high-throughput verification, ORBIT v1.1.0 introduces the Pre-Hash Protocol.

When an incoming CBOR payload contains a large audio buffer, the ORBIT API node will now bypass pure-JavaScript Ed25519 validation on the raw buffer. Instead, the server leverages native C++ (OpenSSL) bindings to calculate a lightning-fast SHA-256 hash of the binary asynchronously in the OS thread pool, and then verifies the Ed25519 signature against the lightweight metadata + hash.

Cryptographic Latency Benchmarks (50MB Audio Payload)

By isolating the heavy binary scanning to the native C++ layer via the Pre-Hash Protocol, we observed massive, provable latency reductions:

• Signature Generation (Client-Side): Dropped from 1450.9 ms to 26.4 ms
• Signature Validation (ORBIT Middleware): Dropped from 837.8 ms to 26.5 ms

Under heavy concurrent load (20 simultaneous 50MB payloads), the ORBIT ingest server now parses 1GB of incoming binary data 4.69x faster than legacy JSON/Base64 APIs while peaking at roughly a quarter of the memory footprint. The event loop remains entirely unblocked, allowing ORBIT to seamlessly scale to enterprise-level ingestion demands.

---

This discussion was created from the release v1.1.0 - The Pre-Hash Protocol: A Major Architectural Upgrade.