Skip to content

BiteRelay merges payment checks and sealed addresses for food delivery

@StateofIntent's Epistemic Resonance Protocol change refuses app-entry updates, and @TrevorWysong's BiteRelay merge checks payments and seals addresses.

The Epistemic Resonance Protocol is a Holochain app for discussing and checking claims, linked into graphs of claims, critiques and evidence. On 11 October 2026, @StateofIntent merged a change that makes the protocol refuse updates to its own app entries. On 10 October 2026, @TrevorWysong merged a hardening pass for BiteRelay, a food delivery app built on Holochain.
For a builder whose app keeps claims or records, the first change means an update to a protocol entry is refused rather than stored unchecked. The second changes how an order is paid and how a customer's details are kept: payments are checked against what the order owes, and the address stays private. Both pull requests are merged.

The protocol refuses app-entry updates instead of validating them

The gap came from validation: an update stored its new entry, but that entry reached a case the entry checks never matched, so no check ran on it at all. The result was an unvalidated write of any entry type, with any content and any claimed author, readable by hash.
The author chose refusal over validating updates. Every index, link and critique stays anchored on the original entry's hash, so a validated update would be readable only by a reader walking update chains, and nothing walks them. The refusal is scoped to the protocol's own entries, since a blanket refusal would make authorizeSigningCredentials fail. The protocol's remedies are additive: an author can publish a Retraction, and anyone can add an AntibodyPattern, each leaving the original readable with the objection attached.

BiteRelay checks each payment against what its order owes

@TrevorWysong's merged pull request validates payments against what each leg of a completed order owes and recomputes order totals during validation. Driver collateral is posted at pickup and returned on delivery.
The same change publishes an order's area and never its address, and it seals drop-off notes, saved addresses, recurring orders and phone numbers. Stores now answer every order within a response window, with validated cancellation reasons. Customers' conductors place scheduled orders and cancel unanswered ones, and stores' conductors settle fee shares with no app needed. Every order change is signalled to its parties, and polling runs as a backstop every 30 to 60 seconds.

What a builder has to change

The protocol runs on Holochain 0.7.0. The refusal covers the protocol's own entries; the test prober attempt_entry_update exists because nothing else in the code calls update_entry. BiteRelay's tests run as a sharded Tryorama suite with 4 CI jobs, and the author reports 51/51 Tryorama files passing locally.

By The hAppRadar Team. Written from the radar's measurements and reviewed before publication; corrections are welcome.