Welcome to the next crypto level
← Nexorena

protocols

A Zcash web wallet tests encrypted OHTTP streams in Chromium

An experiment published on November 15 routed test funds through OHTTP for both receipt and sending. It also checked that the browser rejected truncated streams.

Nexorena Editorial Team

A Zcash web wallet tests encrypted OHTTP streams in Chromium

The browser encrypts requests before sending them

On November 15, contributor Crackdevs published a web wallet experiment on the Zcash forum. It ran in Chromium using a modified version of WebZjs. The wallet received and sent funds on the Zcash test network through a version of Oblivious HTTP designed for responses sent in multiple chunks. A public repository contains the patch, steps for reproducing the experiment, and the saved results.

The setup routes browser requests through a relay, then a gateway and a gRPC-web proxy before reaching the test network. The relay carries encrypted requests. The gateway opens them to forward them to the responding service. The separation is designed to prevent any one intermediary from reading a request and also knowing its originating network address. The tested code encrypts requests in the browser, including in workers dedicated to syncing the wallet.

A confirmed transfer and deliberately interrupted responses

The authors report passing 22 checks in Chromium. At height 4,606,479, a direct scan and a scan over OHTTP produced the same block identifier, history, and balance, including a confirmed receipt of 0.1 TAZ, the test unit. A separate transaction lookup returned the same response along both paths. The wallet then sent 0.01 TAZ once over OHTTP, and the transaction was included in block 4,606,481.

A response containing 100 blocks let the client begin processing data before the stream ended. The authors also tested cancellation, relay interruption, and missing or corrupted stream endings. The client was expected to reject a response without an authenticated ending even after receiving usable data. During the funded test, the relay received 70 requests, and the authors observed no attempts to fall back to a direct connection while OHTTP was enabled.

Conditions for a public service still need testing

The authors operated both the relay and the gateway locally. The identifying markers inserted for the test did not reach the gateway, but that measurement does not show how two remote, independent operators would behave. The archive validates neither real-world key distribution nor resistance to traffic analysis. The authors tested Chromium, and reproducing the funded workflow still depends on the availability of test network services.

In the same thread, a Konclave contributor shared a separate prototype for its web application and servers on November 15. The contributor said the experimental implementation did not yet handle streaming responses. The WebZjs test therefore offers a documented example of that function in a browser. Integration with Konclave, support for other browsers, and interoperability with other projects’ gateways remain to be established.

Article sources

Written with love byRyan MitchellMeet this editorial pen name ↗

Explorer Nexorena