Please describe your proposed solution.
The cardano-ledger can be seen as a set of rules that specifies how data on Cardano is expected to be stored and or used;
A Zig implementation would allow for one of the most efficient implementations of these rules; it would be the core dependency for any upcoming Zig project that wants to interact with the blockchain; especially through the creation of transactions.
Why Zig?
The choice of Zig as a language is mostly due to the incredible performances it can achieve (often comparable to C) with a strong focus on memory safety and best practices (errors as values, no hidden control flow, etc.);
Despite being a relatively young language (Zig development started in 2017) the characteristics of the language are allowing it to easily be adopted by the industry with lots of exciting projects, including the blazingly fast javascript runtme "Bun" with over 42k stars on GitHub.
TL;DR: adopting Zig means making sure that Cardano stays at the forefront of industry standards.
How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?
In the challange description, one of the "possible directions" specified is;
> Developing common tools, frameworks, core infrastructures, or proof of concepts
which matches the idea of the proposal to create a tool that can work as a base for any other project who intends to use the library.
How do you intend to measure the success of your project?
The final goal is to have an open-source library to be reused across the ecosystem.
As an open-source project, the most direct way would be the number of stars the project will receive on GitHub; indicative of the people interested in it.
As a library, the number of dependent projects (directly or indirectly) will be an incredibly useful metric.
Please describe your plans to share the outputs and results of your project?
So far Twitter has been mainly used to communicate the progress of the various projects.
Mainly the (personal) MicheleHarmonic account will be alongside the HarmonicLabs account where appropriate.
Twitter has proven itself a useful tool to share the progress and it will still be used.
for any unreported progress, the project itself has always been open source, and anyone interested should be able to use GitHub to stay updated; the repository can be found at: ( TODO insert link of repo )