Milkomeda SPO validator training

https://drive.google.com/open?id=1spchuE5FzgVmlSM8MAIJO1yegGNhQ0jX https://drive.google.com/open?id=1xHkjk5ucMfslgoPS1Ocd_eBwr77eBxK_

We have reached a crucial stage in our project, as we are now actively testing the management of validators' sets on the live devnet network. This phase marks a significant milestone as we focus on introducing enhancements and fine-tuning various aspects of our system to ensure it is primed and ready for production (c1-main).

https://drive.google.com/open?id=193grULgZrBbWvLGEEK0pI5RQplgoU4gA https://drive.google.com/open?id=1YuOUaHYbPjaAE9RnRlFHqZfoE2KxYvsK https://drive.google.com/open?id=1f3Pa1gvTr_qIF30DAlmebZB4IldA_blo

We are at the stage of the project where we are starting testing validators set management locally on our machines, simulating live-network environments. Validators Coordination has been successfully finished and prepared for production deployments.

https://drive.google.com/open?id=1IVa5sc_-uDqhHc0_yDbmjN7O8vKGcriI https://drive.google.com/open?id=1lEOdQWMDfmQFO4uYVAKcSLT734F-ws-D https://drive.google.com/open?id=1HqUkCxOS-9HaBfE27Y8Op3GquAH4E7fi https://drive.google.com/open?id=1VDwn87Opk1ogK2xlvXDjXeuBYOkn9Y2N

We are making progress on multiple fields in regards to the Milkomeda Validator. Since last time, we introduced in production environment Deterministic UTxOs, rotation of validators & Liquid Staking. We are preparing for deployments of Validators Coordination on devnet too. Bridge code, backend indexer (with API), smart contract changes as well as the dApp are ready.

https://drive.google.com/open?id=1uIm1iCYfHQjZEl2kHif--iXi82O3Uflj https://drive.google.com/open?id=184qjKLhB8v9x2DBnXE89rc7QX5g1p1lm https://drive.google.com/open?id=1i0HIi4zmk_VxD_4Oocvvbmd7KuUiyxzK https://drive.google.com/open?id=1cnTiBmgKYPyLKZmptl_W32rbHtiCAzgU

We are making progress on multiple fields in regards to the Milkomeda Validator. Since last time, we implemented all the scenarios for coordinating validators in the automatic manner through Validators Channel contract. Additionally to the Validators Coordination, we are wrapping up the backend part (api, indexing mechanics and database) as well as UI interface which will allow us to communicate with validators channel contract. Those pieces are going to be soon introduced on devnet, so we can perform QA on the live network. Moreover, we successfully finished QA of deterministic utxos and leadership rotation on devnet and will be proceeding with mainnet deployments.

https://drive.google.com/open?id=1DltQ1N4IrfFnY6XC113dFkqzW0Hztt4h https://drive.google.com/open?id=13ItKUKRvYLBNrRAhwJFqO9e9KJq-Nr-d https://drive.google.com/open?id=11fzZAxBtf-x-_Qwm77rrs8MSF0d_k3Dw https://drive.google.com/open?id=1Uz76zvblCYb92QoPa7rfwrcTlc7S48aJ https://drive.google.com/open?id=13YihF05yl-JEuckqS4Z3RACpbKNXcA2G

We are making progress on multiple fields in regards to the Milkomeda Validator. Since last time, we implemented the first scenarios for coordinating validators in the automatic manner through Validators Channel contract. Moreover, we introduced a mechanism that allows to rotate transaction submitters smoothly in the automatic manner (Milkomeda V1 allows that already but it’s a complex process). This will improve the network efficiency and adds additional assurance that everyone contributes an equal amount of work and shares the responsibility. This part is already deployed and being tested on devnet C1 network.

https://drive.google.com/open?id=1Okk8COfSkp9QxEoiSdFWuxKuWGcZB-CY https://drive.google.com/open?id=1K0D5cd-GwVOXvZsFZBH9bojHDZIMxRaU https://drive.google.com/open?id=1gkTNBuA8Y17OYeDHke60CDHJV7WYGCCA

Since last report, smart contract has been upgraded and its newest version was deployed on mainnet C1. Additionally, we introduce Mixed UTxO handling improvement for the UTxO selection algorithm that is used by Milkomeda bridge. This is also introduced in the production environment and tested with Cardano Mainnet network. Now, we are at the stage of testing basic interfaces of the Validators Channel work that will allow us to sync events from the Validators Channel smart contract, which is the first step to introducing all the necessary scenarios for Validators Coordination. Moreover, we are making progress on deterministic UTxO handling, to be able to introduce validators rotation mechanics.

In the previous report we stated that the new infrastructure was moved onto mainnet but without m1-source. In this update we can say that the latest changes are now deployed on mainnet C1 connected to Cardano Mainnet. The next stage is going to be C1 smart contract upgrade which will allow us to apply all latest improvements to the currently deployed smart contract. In the next set of stages, we are going to introduce a few more features for the bridge, to make validators coordination much smoother

In the previous report we stated that the new infrastructure was moved onto mainnet. However, this new infrastructure didn’t yet have all the pieces ready in place. The remaining piece was the service responsible for synchronization of events from the EVM side. Between last report and the current one, this service was finished, deployed and tested on devnet C1 and will soon be deployed on mainnet C1. So, now the architecture will change in the following way. From (having 3 services): The bridge: cardano-source - fetching data from Cardano chain (moved from being external service into the bridge core) Cardano-executor m1-executor - moved from being external service into the bridge core EVM side: EVM node - as mentioned above m1-source - still separate service, but working towards moving it into the bridge too To (having 2 services): The bridge contains now all the services inside: cardano-source cardano-executor m1-executo m1-source EVM side: EVM node - as mentioned above Now, each operator running validator needs to provide proper configuration to the Cardnao node & run EVM node (which is also optional, because they can also use the external provider. Another step that was unblocked with the new infrastructure that was performed, was the upgrade of the smart contract on devnet C1. Newest audited bridge smart contract is in place and gives necessary pieces to implement further steps for multistargate address management for the validators set changes.

Link - Newest version of the smart contract deployed on Mainnet C1 Upload - Release containing newest infrastructure for the bridge & handling for smart contract upgrade

This proposal has progressed on several fronts in the past month. Because of this, we have written an extended PDF written report with evidence. Please view the attached file to learn about proposal "Milkomeda SPO Validator Training" progress.

"As the formal verification of the audit (accessible from Milkomeda.com

https://drive.google.com/open?id=1-TXrRjpcOwvLaKPP3fJZrpvjWHe_3-K4 https://drive.google.com/open?id=1fH2zHkUp7koMzRQqQz_wARBQV4N2yBCB https://drive.google.com/open?id=1z7E82arEFbRIfyq4MiOaVNcdDY0y9fKT

We finishes the formal verification audit (accessible from Milkomeda.com

The importance of security in the blockchain world cannot be understated. At Milkomeda, we place a high emphasis on ensuring the security of our systems and processes. In recent months, we have seen an increase in attempts by hackers to target blockchain interoperability systems, specifically blockchain bridges. In response to this trend, we made the decision to conduct a thorough security audit of the Bridge contracts before moving forward with our plans. This decision was made in order to ensure the safety and integrity of our systems and to protect our users from potential security breaches. We are pleased to report that we have recently completed a formal verification of the Solidity smart contracts on the Milkomeda side of the bridge. This extensive security review has allowed us to identify and address any potential vulnerabilities, ensuring that our systems are secure and ready for use. With the security audit now complete, we are excited to move forward with our plans and continue working on this grant early next year.

During the Formal Verification Audit, we conduct weekly meetings and troubleshoot issues (such as TokenRegistry) with the auditors. We are also working on a new blog on what the Formal Verification Audit is and why it matters. We hope to publish it in the coming weeks.

We are still in the process of development of for improvements to Milkomeda's bridge smart contracts. Until then, we are unable to implement the grant. In the near future, after updating the bridge contracts, we will resume work on the project.

-

We are still in the process of development of for improvements to Milkomeda's bridge smart contracts. Until then, we are unable to implement the grant. In the near future, after updating the bridge contracts, we will resume work on the project. To ensure maximum security, we cannot release the results of the bridge sc improvements for the time being until the review phase is completed.

The project is currently in a slowdown phase. We are waiting for important changes to Milkomeda's bridge smart contracts. Until then, we are unable to implement the grant. In the near future, after updating the bridge contracts, we will resume work on the project.

We finished JP translations (https://dcspark.gitbook.io/milkomeda-jp/

We want to onboard new validators soon, but we always work to provide best solutions. Therefore, we will ask for additional time to implement this project in accordance with our standards.