Crust status and new redesign

Could, a Dev, give us some information about the current status of Crust?

Are you going to use the current design or will be modified based on the design of Andrew Cann?

Can we get to use the current Crust implementation, if the bugs are fixed, to test the network or we will have to wait for the new design?

How long could lead this change?



Agile is all about iteration, so I hope this is considered.

1 Like

We are moving to use MIO which allows a huge amount of async connections in rust as opposed to the thread model we currently have. There will be some API changes but not too many. Andrew is spending time spec’ing the tasks and RFC’s for this move. If you check MIO you will see why this is happening. Also moving several modules out of crust to their own crate. Just more simplicity, reduced resource usage and significant performance improvements. atm Rust async IO is young and MIO makes great use of epoll etc. So we let the OS handle 10’s of thousands of messages per second as opposed to a more blocking threading module with a centralised state object.


Yes and we are :slight_smile:


will we see jira done before next dev update?(in 2 days)

Crust had an update today to version 0.5.1.

Routing had an update to 0.4.2