Evidences of Expert Feedback Outreach
| Name | Expertise | Work Experience | Feedback Given | Feedback Addressed | Feedback Yet to be Addressed | How We Intend to Address It |
|---|---|---|---|---|---|---|
| Björn Kihlberg | Haskell/Scheme Developer, Blockchain Expert | - Haskell/Scheme Developer at IOHK (Sep 2022 – Jun 2024) - Haskell Developer at CarbonCloud (Aug 2019 – Aug 2022) | - Tech Stack Complexity: Warned about hiring challenges due to complex tech stack. - Nix vs. Guix: Recommended using Nix over Guix. | - Nix has been adopted instead of Guix. | - Developer onboarding and tooling not yet addressed. | - We plan to introduce SDKs, onboarding guides, and training programs to make the tech stack more accessible. - We will host hackathons and developer workshops to attract and educate more developers. |
| Adithya Obilisetty | Haskell Developer, System Performance Expert | - Haskell Developer at JUSPAY (Contract) (Oct 2019 – Dec 2019) - Developer at Haskell.Org (Google Summer of Code) (May 2019 – Aug 2019) - Software Engineer at Composewell (Dec 2019 – Present) | - Tech Stack Complexity: Acknowledged challenges with RISC-V, NuttX-OS, unikernels, Haskell, Rust, Racket, Guix. - Unikernel Suitability: Supported unikernels but was unsure about Haskell's support. - Replacing Racket: Suggested Haskell for DSLs instead of Racket. | - Replaced Racket with Haskell for DSLs. - Confirmed unikernels for security. | N/A | N/A |
| Claudio Hermida | Researcher in Formal Semantics, Categorical Logic | - Honorary Research Fellow at University of Birmingham (Sep 2021 – Present) - Research Associate at Queen’s University (Nov 2002 – Mar 2011) | - Project Scale: Warned about feasibility within Catalyst scope. - Formal Verification for ISAs: Emphasized need for formal semantics for ISAs. - Complexity and Specifics: Noted difficulty assessing large-scale projects without more details. | - Formal verification methods (symbolic execution) are included. | - Formal verification for ISA not detailed. | - We will define how ISAs are formally verified using symbolic execution. - Our goal is to include more detailed formal semantics explanations in the technical documentation. |
| Kapil Shyam | RISC-V and System Software Engineer | - System Software Engineer at Mindgrove Technologies (Aug 2023 – Present) - Project/Research Intern at Mindgrove Technologies (Mar 2022 – Aug 2023) | - RISC-V Benefits: Supported RISC-V but warned about limited talent pool. - Security: Recommended Rust due to memory safety. - Scalability: Mentioned reproducibility as key for large-scale adoption. | - RISC-V and Rust have been fully integrated. - Reproducibility with Nix is implemented. | - No clear strategy for addressing the RISC-V talent shortage. | - We plan to develop a training program and community partnerships to increase RISC-V adoption. - We will host developer-focused training sessions and create learning materials to attract more engineers into the RISC-V ecosystem. |
| Intersect MBO | Tech and Research Organization | N/A | Create educational resources to simplify HaskLedger’s complex tech stack and improve accessibility. As HaskLedger is designed for integration and scalability, clear documentation will help other projects adopt it. | Simplified design documentation has been created. Structured educational resources/ campaign underway | N/A | N/A |
| Sebastian Pereira | Economist and freelance writer | - Content Writer at EMURGO (Nov 2023 – Present, 1 yr 4 mos) Creates blockchain-related content, focusing on Cardano ecosystem updates, education, and technical insights. -Member at 3ken (Aug 2023 – Present, 1 yr 7 mos)Contributes to blockchain research and content creation. | Appreciated the Hardware Level scalability and security we are addressing with HaskLedger. | N/A | N/A | N/A |
| Duncan Coutts | Haskell Expert, Well-Typed | - Well-Typed LLP (Haskell Consultancy) | Suggested two approaches for HaskLedger integration:Fork Cardano and modify it, though this requires extensive research and validation.Run a standard Cardano node on RISC-V SoC, leveraging its existing stability and security. | |||
| The importance of leveraging Cardano’s existing research-backed architecture has been acknowledged. |
| A final decision on whether to fork Cardano or run it as is on RISC-V SoC has not been made. | - We will assess feasibility, resource requirements, and long-term sustainability of both approaches. - A technical analysis will be conducted to determine the most efficient path forward. |