zkFold

It’s not surprising you have decided to characterize our work this way. Anyone we’ve worked with in this community knows our intentions have always been genuine. We’ve never had any interest in "fooling" the people we operate alongside. ​That said, we believe in transparency and want to address the specific points being raised with facts: ​1. Scope vs. Expectations ​There is often a gap between personal expectations and a project's defined reality. Our project was completed strictly according to the signed-off scope of work, which has been publicly available from the start. We have in fact implemented the application that verifies arbitrary zkPass attestations on-chain on Cardano. ​While there is always room for improvement in any V1, the core technical requirements were met and approved. ​2. Addressing the "5 == 5" Code Oversight A specific line of code used for testing (5 == 5) has made it into the final milestone output. It is being taken out of proportion. In ZK development, we follow a standard process: - in Plutus scripts and off-chain code we first use basic circuits like identity or "always true" circuit instead of real ones to make sure these parts work - in parallel we develop and validate the actual ZK circuits used in a particular application That's how we normally debug ZK-powered apps. ​The Fix: We simply missed swapping the placeholder for the real zkPass verification circuit before the milestone submission. It was a few lines of boilerplate code. We’ve already corrected it, and we appreciate it being pointed out. The fact that it took hours to fix proves just how immaterial this was in the context of the total project timeline and scope. Comparing such a simple change to months of architecture and development and calling it a "scam" is your personal view. ​3. The "Capital Quiz" Bonus ​The quiz game was never a required milestone. We chose to include it as a "value-add" to help reviewers understand the project. However, the zkPass Transgate extension was unstable at the time of development. Rather than deliver a broken "extra" feature, we scaled it down to ensure a better user experience for the reviewers. ​4. R&D vs. Commercial Products ​Project Catalyst is an incredible launchpad for R&D and innovation. Not every funded project is a polished commercial product on day one. Our goal was to build the foundational infrastructure; once demand for this service grows, we (or others) can iterate and scale it into a full-scale product. ​5. Accountability Works Both Ways ​It is difficult to take these accusations at face value when the person making them is currently ignoring community questions about his own inactive or delayed projects. Those delays prevent other talented teams from getting the funding they need to deliver. ​We would have much preferred a professional "Raise a problem -> Address it" dialogue, but unfortunately, that wasn't the path chosen here. We remain committed to the Cardano community and will continue to focus on building and improving.

It’s not surprising you have decided to characterize our work this way. Anyone we’ve worked with in this community knows our intentions have always been genuine. We’ve never had any interest in "fooling" the people we operate alongside. ​That said, we believe in transparency and want to address the specific points being raised with facts: ​1. Scope vs. Expectations ​There is often a gap between personal expectations and a project's defined reality. Our project was completed strictly according to the signed-off scope of work, which has been publicly available from the start. We have in fact implemented the application that verifies arbitrary zkPass attestations on-chain on Cardano. ​While there is always room for improvement in any V1, the core technical requirements were met and approved. ​2. Addressing the "5 == 5" Code Oversight A specific line of code used for testing (5 == 5) has made it into the final milestone output. It is being taken out of proportion. In ZK development, we follow a standard process: - in Plutus scripts and off-chain code we first use basic circuits like identity or "always true" circuit instead of real ones to make sure these parts work - in parallel we develop and validate the actual ZK circuits used in a particular application That's how we normally debug ZK-powered apps. ​The Fix: We simply missed swapping the placeholder for the real zkPass verification circuit before the milestone submission. It was a few lines of boilerplate code. We’ve already corrected it, and we appreciate it being pointed out. The fact that it took hours to fix proves just how immaterial this was in the context of the total project timeline and scope. Comparing such a simple change to months of architecture and development and calling it a "scam" is your personal view. ​3. The "Capital Quiz" Bonus ​The quiz game was never a required milestone. We chose to include it as a "value-add" to help reviewers understand the project. However, the zkPass Transgate extension was unstable at the time of development. Rather than deliver a broken "extra" feature, we scaled it down to ensure a better user experience for the reviewers. ​4. R&D vs. Commercial Products ​Project Catalyst is an incredible launchpad for R&D and innovation. Not every funded project is a polished commercial product on day one. Our goal was to build the foundational infrastructure; once demand for this service grows, we (or others) can iterate and scale it into a full-scale product. ​5. Accountability Works Both Ways ​It is difficult to take these accusations at face value when the person making them is currently ignoring community questions about his own inactive or delayed projects. Those delays prevent other talented teams from getting the funding they need to deliver. ​We would have much preferred a professional "Raise a problem -> Address it" dialogue, but unfortunately, that wasn't the path chosen here. We remain committed to the Cardano community and will continue to focus on building and improving.

It’s not surprising you have decided to characterize our work this way. Anyone we’ve worked with in this community knows our intentions have always been genuine. We’ve never had any interest in "fooling" the people we operate alongside. ​That said, we believe in transparency and want to address the specific points being raised with facts: ​1. Scope vs. Expectations ​There is often a gap between personal expectations and a project's defined reality. Our project was completed strictly according to the signed-off scope of work, which has been publicly available from the start. We have in fact implemented the application that verifies arbitrary zkPass attestations on-chain on Cardano. ​While there is always room for improvement in any V1, the core technical requirements were met and approved. ​2. Addressing the "5 == 5" Code Oversight A specific line of code used for testing (5 == 5) has made it into the final milestone output. It is being taken out of proportion. In ZK development, we follow a standard process: - in Plutus scripts and off-chain code we first use basic circuits like identity or "always true" circuit instead of real ones to make sure these parts work - in parallel we develop and validate the actual ZK circuits used in a particular application That's how we normally debug ZK-powered apps. ​The Fix: We simply missed swapping the placeholder for the real zkPass verification circuit before the milestone submission. It was a few lines of boilerplate code. We’ve already corrected it, and we appreciate it being pointed out. The fact that it took hours to fix proves just how immaterial this was in the context of the total project timeline and scope. Comparing such a simple change to months of architecture and development and calling it a "scam" is your personal view. ​3. The "Capital Quiz" Bonus ​The quiz game was never a required milestone. We chose to include it as a "value-add" to help reviewers understand the project. However, the zkPass Transgate extension was unstable at the time of development. Rather than deliver a broken "extra" feature, we scaled it down to ensure a better user experience for the reviewers. ​4. R&D vs. Commercial Products ​Project Catalyst is an incredible launchpad for R&D and innovation. Not every funded project is a polished commercial product on day one. Our goal was to build the foundational infrastructure; once demand for this service grows, we (or others) can iterate and scale it into a full-scale product. ​5. Accountability Works Both Ways ​It is difficult to take these accusations at face value when the person making them is currently ignoring community questions about his own inactive or delayed projects. Those delays prevent other talented teams from getting the funding they need to deliver. ​We would have much preferred a professional "Raise a problem -> Address it" dialogue, but unfortunately, that wasn't the path chosen here. We remain committed to the Cardano community and will continue to focus on building and improving.

It’s not surprising you have decided to characterize our work this way. Anyone we’ve worked with in this community knows our intentions have always been genuine. We’ve never had any interest in "fooling" the people we operate alongside. ​That said, we believe in transparency and want to address the specific points being raised with facts: ​1. Scope vs. Expectations ​There is often a gap between personal expectations and a project's defined reality. Our project was completed strictly according to the signed-off scope of work, which has been publicly available from the start. We have in fact implemented the application that verifies arbitrary zkPass attestations on-chain on Cardano. ​While there is always room for improvement in any V1, the core technical requirements were met and approved. ​2. Addressing the "5 == 5" Code Oversight A specific line of code used for testing (5 == 5) has made it into the final milestone output. It is being taken out of proportion. In ZK development, we follow a standard process: - in Plutus scripts and off-chain code we first use basic circuits like identity or "always true" circuit instead of real ones to make sure these parts work - in parallel we develop and validate the actual ZK circuits used in a particular application That's how we normally debug ZK-powered apps. ​The Fix: We simply missed swapping the placeholder for the real zkPass verification circuit before the milestone submission. It was a few lines of boilerplate code. We’ve already corrected it, and we appreciate it being pointed out. The fact that it took hours to fix proves just how immaterial this was in the context of the total project timeline and scope. Comparing such a simple change to months of architecture and development and calling it a "scam" is your personal view. ​3. The "Capital Quiz" Bonus ​The quiz game was never a required milestone. We chose to include it as a "value-add" to help reviewers understand the project. However, the zkPass Transgate extension was unstable at the time of development. Rather than deliver a broken "extra" feature, we scaled it down to ensure a better user experience for the reviewers. ​4. R&D vs. Commercial Products ​Project Catalyst is an incredible launchpad for R&D and innovation. Not every funded project is a polished commercial product on day one. Our goal was to build the foundational infrastructure; once demand for this service grows, we (or others) can iterate and scale it into a full-scale product. ​5. Accountability Works Both Ways ​It is difficult to take these accusations at face value when the person making them is currently ignoring community questions about his own inactive or delayed projects. Those delays prevent other talented teams from getting the funding they need to deliver. ​We would have much preferred a professional "Raise a problem -> Address it" dialogue, but unfortunately, that wasn't the path chosen here. We remain committed to the Cardano community and will continue to focus on building and improving.

It’s not surprising you have decided to characterize our work this way. Anyone we’ve worked with in this community knows our intentions have always been genuine. We’ve never had any interest in "fooling" the people we operate alongside. ​That said, we believe in transparency and want to address the specific points being raised with facts: ​1. Scope vs. Expectations ​There is often a gap between personal expectations and a project's defined reality. Our project was completed strictly according to the signed-off scope of work, which has been publicly available from the start. We have in fact implemented the application that verifies arbitrary zkPass attestations on-chain on Cardano. ​While there is always room for improvement in any V1, the core technical requirements were met and approved. ​2. Addressing the "5 == 5" Code Oversight A specific line of code used for testing (5 == 5) has made it into the final milestone output. It is being taken out of proportion. In ZK development, we follow a standard process: - in Plutus scripts and off-chain code we first use basic circuits like identity or "always true" circuit instead of real ones to make sure these parts work - in parallel we develop and validate the actual ZK circuits used in a particular application That's how we normally debug ZK-powered apps. ​The Fix: We simply missed swapping the placeholder for the real zkPass verification circuit before the milestone submission. It was a few lines of boilerplate code. We’ve already corrected it, and we appreciate it being pointed out. The fact that it took hours to fix proves just how immaterial this was in the context of the total project timeline and scope. Comparing such a simple change to months of architecture and development and calling it a "scam" is your personal view. ​3. The "Capital Quiz" Bonus ​The quiz game was never a required milestone. We chose to include it as a "value-add" to help reviewers understand the project. However, the zkPass Transgate extension was unstable at the time of development. Rather than deliver a broken "extra" feature, we scaled it down to ensure a better user experience for the reviewers. ​4. R&D vs. Commercial Products ​Project Catalyst is an incredible launchpad for R&D and innovation. Not every funded project is a polished commercial product on day one. Our goal was to build the foundational infrastructure; once demand for this service grows, we (or others) can iterate and scale it into a full-scale product. ​5. Accountability Works Both Ways ​It is difficult to take these accusations at face value when the person making them is currently ignoring community questions about his own inactive or delayed projects. Those delays prevent other talented teams from getting the funding they need to deliver. ​We would have much preferred a professional "Raise a problem -> Address it" dialogue, but unfortunately, that wasn't the path chosen here. We remain committed to the Cardano community and will continue to focus on building and improving.