The CHC feature of Holochain is a "Chain Head Coordinator". The basic idea is to push all ops that an agent is creating to a remote service. If that agent switches machine to another machine with a CHC enabled conductor then they should be able to restore their source chain from the CHC.

Holo uses this feature to allow Holoports to be treated as transient. An agent is assigned to use a Holoport when they access an app through the browser. Any data they create is stored on the CHC service. When that user logs at another time, they can be allocated to a different Holoport and still see all the data they created last time.

• We need Holochain to have CHC enabled, that will require changing the flake.nix in this repository and also tweaking our deploy to the Holoports
• Where will we run the CHC service when the tests are deployed? Don't need to do this for the tests to get written, but we should have an answer to how.
• We need a CHC service. If we can't make Holo's public then we should consider building our own reference implementation to be used with Holochain. I seem to remember that Holo are using some technology that we can't run locally, so we may not be able to use theirs.
• We already have some TryCP tests that do read/write. We want to create another one of those but have CHC enabled and check that the content the test creates actually makes it to the CHC service.

Part of the performance testing should be to move agents between conductors but I think the above is enough for one issue. We can create a second issue for this if want to complete the coverage of the CHC feature.