82 posts tagged with "mithril"

High level overview​

The Mithril team has released a new distribution 2335.0 which brings enhancements to the client: support for simultaneous downloading and unpacking of the snapshot archives, support for one line command restoration of the latest snapshot, and availability of machine readable progress information.

They have also worked on snapshots enhancements: implementation of the zstandard compression to produce smaller archives, and providing the version of the Cardano node used to create the archive in the snapshot artifacts. They have completed the second phase of the implementation of the stress test tool to benchamrk the aggregator. Additionally, they have kept working on refactoring and standardizing errors in the Mithril nodes.

Finally, they have worked on adding Cloudflare protection to the infrastructure, and they have fixed some bugs that occurred during restoration of a snapshot by a client.

Low level overview​

• Completed the issue Use 'zstandard' compression for snapshot archives #876
• Completed the issue Design & implement stress test tool for aggregator - phase 2 #1155
• Completed the issue Provide progress information with '--json' option in Client #1095
• Completed the issue Make client download and extract the archive simultaneously #1115
• Completed the issue Add aggregator Cardano node version in snapshot artifact #948
• Completed the issue Make Cardano node version part of the Mithril network configuration #947
• Completed the issue Post deployment 'mainnet' infrastructure #1091
• Worked on the issue Errors refactoring #798
• Worked on the issue Add Cloudflare protection of infrastructure #986
• Completed the issue Failed to restore recent snapshot with strange error #1160
• Completed the issue Update 'ed25519-dalek' to '2.0.0' #1188
• Completed the issue Add target networks blocks in release notes #1151
• Completed the issue Fix end to end 'wait_for_the_expected_time' test #1191
• Completed the issue Fix docs 'git checkout' command #1174

High level overview​

The Mithril team created an explorer page with the registered signers to give recognition to the SPOs already running on mainnet. They also worked on refactoring and standardizing errors in the Mithril nodes, and they enhanced the clarity and reduced verbosity of the logs for the signer and aggregator nodes. Additionally, they started working on the implementation of zstandard compression of the snapshot archive, and streaming its download and decompression in the client.

Finally, they implemented machine readable progress information in the client, and streamlined the process of verifying the registration status of a signer.

Low level overview​

• Completed the issue Create explorer page with registered signers #1097
• Completed the issue Simplify logs on the Signer/Aggregator #1106
• Completed the issue Refactor (de)serialization of crypto entities #668
• Completed the issue Mithril client last snapshot download #1078
• Completed the issue Use the '/signers/registered' route to verify if a signer is registered #1152
• Worked on the issue Provide progress information with '--json' option in Client #1095
• Worked on the issue Use 'zstandard' compression for snapshot archives #876
• Worked on the issue Make client download and extract the archive simultaneously #1115

High level overview​

The Mithril team completed the Mithril protocol’s mainnet beta launch: the release-mainnet network is now consistently producing new certificates and snapshots! The team has released a new distribution 2331.1 which includes some optimizations and bug fixes: the bootstrap time of a Cardano node restored from a Mithril snapshot has been significantly reduced, and a bug that made the aggregator produce corrupted archives has been fixed. They also kept working on the implementation of the stress test tool for benchmarking the aggregator: the first phase has been implemented, as well as a monitoring feature. Additionally, they kept implementing the refactoring of the serialization/deserialization of the entities of the cryptographic library, and working on the post deployment of the mainnet infrastructure.

Finally, they completed the rewriting and enhancements of the documentation website, and they completed the runbook for operating a production Mithril network.

Low level overview​

• Released the new distribution 2331.1
• Completed the epic Release 'mainnet' Mithril network #918
• Worked on the epic Benchmark performances of Mithril Aggregator #904:
  • Completed the issue Design & implement basic stress test tool for aggregator - phase 1 #991
• Worked on the epic Post deployment 'mainnet' infrastructure #1091:
  • Completed the issue Create Production Infrastructure Runbook #1085
  • Completed the issue Ingest 'mainnet' metrics/logs in Grafana #1122
• Worked on optimizations:
  • Completed the issue Add a 'clean' file to extracted database in client #1131
  • Worked on the issue Create explorer page with registered signers #1097
• Worked on refactoring:
  • Worked on the issue Refactor (de)serialization of crypto entities #668
• Worked on bugs:
  • Completed the issue Client fails to unpack some snapshot archive #1137
  • Completed the issue The 'release-preprod' network stopped producing certificates #1114
  • Completed the issue The 'release-mainnet' network does not show up in the explorer #1111
• Worked on dependencies:
  • Completed the issue Upgrade Cardano node to '8.1.2' #1090
• Worked on troubleshooting:
  • Completed the issue Signer can't sign with 'Invalid signature for party' error #1125

High level overview​

The Mithril team launched Mithril protocol’s mainnet beta: the release-mainnet network is now open for signer registrations, and its genesis certificate has been created. The team is monitoring the network, and expects it to start producing certificates during the next Cardano epoch.

They have released a new distribution 2329.0, which is running on the release-mainnet network. They also kept working on the implementation of the stress test tool for benchmarking the aggregator. The team kept working on the refactoring of the serialization/deserialization of the entities of the cryptographic library. Additionally, they completed the cleanup of the legacy store adapters in the aggregator.

Finally, they have worked on enhancing the documentation for onboarding SPOs and setting up a Mithril signer, and fixing installation bugs of the binary artifacts produced in the CI.

Low level overview​

• Created the dev blog post Mithril Protocol’s Mainnet Beta Launch
• Released the new distribution 2329.0
• Closed the epic that prepares the Mithril infrastructure for mainnet #767:
  • Completed the issue Deploy 'mainnet' infrastructure #988
  • Completed the issue Handle Secrets management #989
• Worked on the epic Release 'mainnet' Mithril network #918
  • Completed the issue Prepare SPO on-boarding guide #1049
• Worked on the epic Benchmark performances of Mithril Aggregator #904:
  • Worked on the issue Design & implement basic stress test tool for aggregator #991
• Worked on optimizations:
  • Completed the issue Enhance the configuration of Mithril relay #1080
  • Completed the issue Remove legacy store adapters from aggregator #1053
  • Completed the issue Add a 'sign' sub-command to 'genesis' command in aggregator #1081
• Worked on refactoring:
  • Worked on the issue Refactor (de)serialization of crypto entities #668
• Worked on documentation:
  • Completed the issue Enhance 'Run a Mithril Signer node (SPO)' guide #1055
• Worked on bugs:
  • Completed the issue Shared library error in CI binaries #1073
  • Completed the issue Debian package does not install cleanly on older ubuntu versions #834
  • Completed the issue Aggregator panics with new (de)serialization of 'ProtocolVerificationKey' #1083

High level overview​

The Mithril team created a new 2327.0 distribution. They focused on preparing the beta launch on the mainnet: they tested the new production signer deployment model with the pioneer SPOs, they prepared an SPO on-boarding guide, and they kept working on the deployment and monitoring of the mainnet infrastructure. The team also worked on the implementation of a simple stress test tool for benchmarking the aggregator. Additionally, they completed the refactoring of the interface to the cryptographic library.

Finally, they fixed a bug that sporadically prevented the latest signer registration of a SPO to be used in the associated signing epoch, they fixed a bug in the epoch gap detection of the certificate chain in the aggregator, and worked on multiple other optimizations and bugs.

Low level overview​

• Released the new distribution 2327.0
• Worked on the epic that prepares the Mithril infrastructure for mainnet #767:
  • Completed the issue Add infrastructure monitoring #987
  • Worked on the issue Deploy 'mainnet' infrastructure #988
  • Worked on the issue Handle Secrets management #989
• Worked on the epic Benchmark performances of Mithril Aggregator #904:
  • Worked on the issue Design & implement basic stress test tool for aggregator #991
• Worked on optimizations:
  • Completed the issue Remove certificate hash from Artifact #932
  • Completed the issue Check vulnerabilities in CI #1037
  • Completed the issue Add 'created_at' in Mithril Stake Distribution messages #1030
  • Completed the issue Add a 'run-only' option in end to end test #1048
• Worked on refactoring:
  • Completed the issue Factorize protocol crypto operations #669
  • Completed the issue Refactor aggregator dependency injection and services #1058
  • Completed the issue Build static binaries in CI #874
• Worked on documentation:
  • Completed the issue Prepare SPO on-boarding guide #1049
  • Completed the issue Add instructions to set firewall using iptables #1040
  • Completed the issue Update ufw command to set firewall on Mithril Signer installation instructions #1041
• Worked on bugs:
  • Completed the issue Aggregator does not detect certificate chain epoch gap #952
  • Completed the issue 'testing-preview' network does not create certificates #1015
  • Completed the issue SQLite compatibility in aggregator #837
  • Completed the issue Q&A followup fixes #1035
  • Completed the issue E2E tests are flaky in CI #1023