[topher-the-geek]

Having Jepsen tests would be a good thing. The community trusts them, and it's wise to have tests from someone other than the author of the main-line code. If I'm so lucky as to find funding--my savings will only go so far--then I or someone I hire will eventually apply Jepsen to Treode. In the meantime, there are already tests a bit like Jepsen in the repository. They simulate dropping and reordering messages, and crashing and recovering nodes. They have proven their value as they have flushed out lots of early bugs.

My immediate concerns are finding help and finding a sponsor (investor or adventurous customer). To that end, I'm less coding right now and more promoting. Getting the word out will help me find developers interested in improving or trying it.

When I do get to code, I may focus on load and performance testing. I have not done enough work along those lines yet. Or, I may focus on an example that sketches how the read/write side of the API integrates easily with Etags, CDNs and web-clients, and how the scan API integrates with Spark or Map-Reduce.

[fasteo]

Maybe you can try to contact aphyr. Some of his "call me maybe" articles have been funded (by Comcast if I remember well)