It's also an opportunity to simplify some of the blueprints of Cardano because for example there's been a lot of conversations about retiring some or all of the logic of Byron and to massively simplify the design and reduce the complexity of the code which would mean there's a much faster time to market for the Rust and TypeScript clients and there shouldn't be any consequences to the users of Cardano because those are legacy concerns.

Then there's the actual rollover of what we have today - the Byron system - to where we'd like to go, Shelley. Now, this means that we're going to have to issue series of updates to the Cardano Client. At least two updates will be required. One is that the current implementation of Ouroboros, this Ouroboros classic is a very old implementation. It's based on the ideas we had back in 2017, but...

What's really nice is we've actually managed to take the ledgers back which defines all the rules for validating what is legitimate Ledger and what is not legitimate leisure and create almost like a DSL to describe different Ledger rules and so it's very easy for us to describe the old ledger, which is the Byron Ledger and what the new Shelley Ledger is going to look like...

So, when we released the client Byron back in late September of 2017, there were a few goals that we had. Number one, Due to the nature of how ADA was sold. The buyers had to redeem vouchers to get their ADA. So it was a high priority that the buyers redeem into the system. This is more than 80% of ADA in the circulation. So, to us it was very important that that group understand how to install Daedalus, use Daedalus, redeem their vouchers and learn how to safely use exchanges. So, they can have liquidity if they so choose, and then ADA could also get more broadly distributed from the initial distribution.

Where are we going? There's January and February and many months coming. And then there's the Shelley release. So, the immediate priority is that there is some technical debt in our architecture and our code from the Byron release. And we've been working towards reducing that debt in parallel to finishing the specifications for Shelley and starting new code work for Shelley.

For example, easy submission of logs is something that slipped the Byron release. It was something I really wanted to get in, but unfortunately software is software and occasionally you have to cut it somewhere.

So, there's a few other things that we're working on under the hood to try to make the Daedalus experience better, few other things we're working on to make the code much more concise and clean in certain areas that just didn't get where they needed to be during the Byron release and our hope is that in the coming weeks we're going to be able to chip away...

OK, so that's Byron and that's Byron for the next two months, expect things to gradually get faster. Expect the connecting to network issues to start receding. Expect patches coming in February and in March, which will dramatically improve things. Expect more exchanges coming and we're certainly going to work really hard.