Previously I was hashing a statebox by its value, but that just didn't sit well. There was a chance of having two stateboxes with the same content and different local mutation histories collide. So now we hash every unique statebox which makes any space savings by Content Addressed Systems absolutely useless (since each statebox has a last modified timestamp). The plan should be to have end-user statebox values point to permanodes (another state box) that points to a blob. We shouldn't be storing graphics, movies, audio, posts, etc, in a statebox. A statebox should *point* to a permanode that *points to* the blob itself. Get statebox -> get permanode -> get current contents. If you care about static contents, you could have your statebox point to the blob directly, but then you lose any future updates (unless you follow a chain of REPLACES indexes). Oh, also the tests have been updated to work with the adjusted hash digest scheme. All 10 tests pass.