Milkomeda C1: Update on Current Work on Validator Software (Side note: we will continue posting more updates about different parts of the system every fews days including upcoming upgrades to A1! stay tuned) Milkomeda was launched around 10 months ago and it has been able to achieve multiple successes: - Smoothly “survive” the transition from Baggage - Process over 9.4M transactions and support over 110,000 wallet addresses - Pass 3 audits and get a formal verification with Certora (so far the only one in #Cardano) - Launch almost a year before IOG released the Sidechain Toolkit and with more features (multitoken support) One of the issues after launch and continuing worrying (a lot) about security is that you can’t rush some things because they are in production even if you really wish for them. Unfortunately a lot of the tooling wasn’t friendly enough for operators so this made us realize that we needed to start working on a V2 of the full-node right away because it wouldn’t be able to be simple enough. Also we had a lot of issues with cardano-db-sync (reliability and availability) so we had to create our own cardano indexer (carp) Full Node V1 - Cardano-db-sync (+ node + postgresql) - cardano-source - service formatting data from Cardano chain (fetched from db-sync) into specific format for the bridge - EVM node - m1-source - service fetching data from EVM and formatting data from EVM sidechain into specific format for the bridge - m1-executor - service responsible for performing actions (sending transactions to sign to ethsigner) - ethsigner - signing transactions that later are posted to the EVM node - cardano-executor Services to run: 9 Full Node V2 (already upgraded last week for Devnet and now in the process for Mainnet: - cardano-source - fetching data from Cardano chain (moved from being external service into the bridge core) - cardano-executor - m1-source - still separate service, but working towards moving it into the validator too Services to run: 2 + EVM node Full Node V2.1 - Decentralized chat system for validators (already in the smart contract so off-chain needs to be implemented) - Dashboard for validator coordination So, in the new version, we no longer need db-sync, ethsigner. Moreover, cardano-source and m1-executor are moved inside the bridge core code, so these are also 2 less services to run by the validator. Services to run: 3 Remember that decentralization is a very tricky process, Cardano took almost 4 years to move away from a 3 unique validators, the Sidechain toolkit just came out which only partially matches our Full node v1 (and we are moving towards v2) and once something goes bad it’s very difficult to go back and fix it so it’s going as fast as it can without compromising security or stability. Finally, the plan is to have everything ready for Milkomeda’s C1 anniversary. We are also going to share the research done (and finished) for the decentralization of the selection of validators and then start the work on the DAO and the implementation of more advance crypto primitives (already part of an internal group with IOG so we can propose a standard for Mamba, Milkomeda and Midnight). So things are looking good and we continue improving (with focus on security and stability). Let's go