Skip to content

Epistemic Resonance v0.3.0 moves installed users to a new network

Epistemic Resonance Desktop v0.3.0 bundles its own Holochain conductor, so users skip the terminal, and it runs on a network apart from v0.2.x.

Epistemic Resonance Desktop published v0.3.0 on 24 October 2026. The desktop app packages the Epistemic Resonance Protocol, a platform for discussing and validating claims, with a Holochain conductor built in, so running it does not require Rust, Node, or a terminal.
For people who run the app, the release changes which network they join. v0.2.x installs and v0.3.x installs never gossip with each other, and auto-update will not offer v0.3.0 to anyone on v0.2.x. Everyone already installed downloads it by hand. Two other projects merged pull requests in the same week, and each is described below.

Epistemic Resonance v0.3.0 moves installed users to a separate network

A Holochain network is identified by its DNA hash, and the hash changes when the integrity rules change. This release bumps the minor version rather than the patch. The app installs its hApp only when its app id is absent, so a patch would have shown the new interface in front of the old protocol 9 cell. A minor bump gives the app a fresh conductor.
The author checked the artifact itself before shipping. The bundle's own dna.yaml declares protocol version 11, the .happ inside it is byte-identical to the one the app repository built, and all 101 checks of the attachment test script pass against a conductor generated from it.

Epistemic Resonance Protocol fixes a signal test that misread delivery

The Epistemic Resonance Protocol is a Holochain app for claims, critiques and evidence graphs. @StateofIntent merged pull request #318 on 23 October 2026. The test harness had reported that signals between 2 nodes did not arrive, but the signals did arrive. The harness's own reader could not parse them.
The old code made "nothing arrived" and "something arrived that I cannot read" the same observation. The change makes an arrival with no readable signal a setup failure that prints the envelope, never a verdict about delivery.

Social Production patches a memory leak that grew with each new account

Social Production is an open-source coordination platform for collective projects, with no central database and no server it depends on. @YMSVZ merged pull request #45 on 25 October 2026. The author measured the leak on a release build and profiled the heap, and found that each new account added about 350 MB and that disabling apps freed nothing.
The patch has 2 parts: no eviction at genesis, and no time-to-idle on the module cache. The author measured 3 more accounts at +8 MB after the patch, against +0.9–1.2 GB before it.

What a builder has to change

A builder packaging a Holochain app this way should expect a change to the integrity code to give a new DNA hash and a new network. The packaged webhapp is protocol_version 11, with DNA hash uhC0kb-i4w7LvWd-pzqG3Wmm76P0U4pFZ3yGXhWzp-aRCpinsVDdh. The desktop app installs through holochainManager only when the app id is absent. Social Production's patch vendors Holochain 0.7.1 at vendor/holochain and is applied with [patch.crates-io].

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