Saito Tech Team Update #1

Although Saito’s codebase has always been open source, the amount of interest in contributing from the public has never been higher.

Going forward, the Tech Team will be publishing bi-weekly updates to keep the public aware of our progress and to help orient anyone who wishes to contribute to the project.

With a growing team and a more engaged community, we’ve been thinking hard about how to support a bigger and more decentralized effort. In that spirit, Team Saito would like to formally invite the community to begin contributing by writing to us at or by joining one of our new dev channels on Discord.

We’d also like to point the community to our new Rust codebase which we’ve added on GitHub. This project will apply the lessons learned from Saito-lite, our Node.js implementation, to design the consensus and architecture. This codebase will support our next testnet and should eventually produce peta-byte-per-day transaction throughput. We will be redesigning the network APIs and applying best practices to help also support more seamless integration with other projects in the Saito ecosystem.

Milestone 1 for the Rust project will be a stripped-down version that can be used to benchmark the Rust implementation and give us some perspective on the tooling we’ll need to support development. We’re looking forward to sharing more on this next time.

We’ll be practicing Design By Contract and Test-Driven Development, which we believe will enable the team to produce both high-quality code quickly while also keeping the codebase clean and flexible enough to support changes later as we discover bottlenecks and approach the peta-byte-per-day level.

A significant amount of code has already been ported from our old Rust codebase. Architectural targets for our first few milestones are nearly complete and will be shared with the community very soon. Expect to see more Documentation, Roadmap/Milestones, Architectural Diagrams, Code Review Process, Bug Tracking, and Style Guides in the coming weeks.

GitHub link:

Leave a Reply

Your email address will not be published. Required fields are marked *