The Tonk team has been very busy since our technical release! Here are the big headlines:
- We continue to build out Tonk core which is even more performant and stable!
- We have a working internal product that is built on Tonk core.
- We had a team offsite to dream up what is in Tonk's future.
- We sent Goblin to represent Tonk at the Digital Commons Policy Summit in Brussels.
- We are hiring a Brand and Ecosystem Associate.
Engineering
Tonk is committed to building within an open technology ecosystem. All of the following changes you can see in the GitHub Repository.
We have opened an RFC system to discuss ongoing design work.
New Features
- We have written our relay server in Rust. This improves both the servers memory footprint as well as overall performance. Stress testing and performance benchmarks were used to harden the server. A single instance is currently able to support up to 1000 simultaneous sync connections with very little overhead, more than enough for personal use.
Bugfixes and Improvements
- Our WASM builds are now deterministic
- The Tonk Core zustand middleware is now much more efficient in how it transacts data changes.
- A full re-write of the Virtual FileSystem metadata was necessary to fix a critical initialization bug.
Works in Progress
- We are laying the foundations for our identity and permissioning system. This system will make use of DIDs and OCAP model.
Product
Yes, Tonk is building interesting new technology, but we're also crafting a user-facing product that makes it easy to put that technology to work.
That product is now starting to take shape and we believe that we've found a form factor that does this effectively.
We are now continuing to iterate on it with internal testers. If you would like to be an internal tester please come talk to us!