| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | https://github.com/chainaim3003/ZK-PRET-DEV-V2 | |||||||||||||||||||||||||||||
2 | ITERATION:1 | Deliverable | SCOPE Notes | HOW TO TEST ? REVIEW / ADJUST | ProgressNotes:March 16,,2025 | ProgressNotes:March 4,2025 | ProgressNotes:Feb22,2025 | ProgressNotes:Feb4,2025 | Test Case Documentation | Test Case to Run ( Node command to run from CLI from \ZK-PRET-DEV-V2\zkapps\ZK-PRET-DEV\PRET-ZK-RWA-SCF> dir.. please run npm run build, and then, run | ||||||||||||||||||||
3 | End of Week 4 | 1 | ZK- DEEP COMPOSITION ENGINE | 1 | Identity and Compliance Proofs for Individual Identities Global Legal Entity Identifier, Examples ( Ministry of Corp Affairs/ India) / Director General of Foreign Trade API Specs With MOCK data | Example JSONs based on Mock Data, Check for signatures and Proofs generated. | Identty/Compliance Proof for CorporationRegistration Compliance Completed. and tested on MOCK DATA - Example Ministry of Corporate Affairs. ExportImport Compliance / GLEIF compliance on MOCK DATA - COMPLETED | Identty/Compliance Proof for CorporationRegistration Compliance Completed. and tested on MOCK DATA - Example Ministry of Corporate Affairs. ExportImport Compliance / GLEIF compliance on MOCK DATA - COMPLETED | Identty/Compliance Proof for CorporationRegistration Compliance Completed. and tested on MOCK DATA - Example Ministry of Corporate Affairs. ExportImport Compliance / GLEIF compliance on MOCK DATA - COMPLETED | Identty/Compliance Proof for CorporationRegistration Compliance Completed. and tested on MOCK DATA - Example Ministry of Corporate Affairs. ExportImport Compliance / GLEIF compliance on MOCK DATA - in Progress. | In progress | node ./build/src/CorporateRegistrationVerificationTestWithSign.js node ./build/src/EXIMVerificationTestWithSign.js node ./build/src/GLEIFVerificationTestWithSign.js node ./build/src/ComposedRecurrsiveSCF3LevelProofs.js node ./build/src/ComposedRecursive3LevelVerificationTestWithSign.js | ||||||||||||||||||
4 | 2 | Recursive Identity and Compliance Proofs for Individual Identities Global Legal Entity Identifier, Example ( Ministry of Corp Affairs/ India) / Director General of Foreign Trade API Specs With MOCK data | Out of Scope: Other KYC/ Sanctions Providers | Example JSONs based on Mock Data, Check for signatures and Proofs generated. Proofs verified for positive and negative test cases for Recursion. | The design is complete. First-cut Check Completed. Full Implementation in Progress.(50%) | The design is complete. First-cut Check Completed. Full Implementation in Progress.(50%) | The design is in progress | The design is complete. Will follow #1. | test Case Documentation | |||||||||||||||||||||
5 | 3 | First Cut Implementation: For DCSA Bill of Lading ( Transfer Records Document ) Standards Schema, Check and Proofs of Deep Integrity ( For Required fields / Individual Fields / Patterns ) | Example JSONs based on Mock Data, Check for signatures and Proofs generated. Proofs verified for positive and negative test cases for Deep Integrity of Supply Chain Finance document content. | Design is complete. Implementation in progress. First-cut backend implementation is avaiable, and documented in the test script. Included in the Mid Point Review Demo / Documentation. Please note that this is the key document , the title document for all financing for Supply Chain Finance. This is a deep data verfication and aligment to the evolving business standard ( V 3) | Design is complete. Implementation in progress. First-cut backend implementation is avaiable, and documented in the test script | Design is complete. Implementation in progress. First-cut backend implementation is expected to be available as part of the mid-point review | Design is complete. Implementation in progress. | To be done | node ./build/src/BusinessStandardDataIntegrityVerificationTest.js | |||||||||||||||||||||
6 | 4 | Template - For Financiers to choose from / customize - Research | Design Review | In Progress - Most of the research and design here will eventually fit in to all 5 components. Based on the funcational components completed, these templates will extend the functionality by parameterizing the different business processes and ACTUS risk factors. | In Progress - Most of the research and design here will eventually fit in to all 5 components. Based on the funcational components completed, these templates will extend the functionality by parameterizing the different business processes and ACTUS risk factors. | This is still in research with the quant team. We realized there is dependency on the SCF Reference Impl Risk Model. - This is back-loaded a bit. | The design is complete. Will follow #1. | Artifact Links | ||||||||||||||||||||||
7 | ||||||||||||||||||||||||||||||
8 | ||||||||||||||||||||||||||||||
9 | ||||||||||||||||||||||||||||||
10 | 2 | ZK - BUSINESS PROCESS PROVER | ||||||||||||||||||||||||||||
11 | 1 | Complete First Cut of the Backend - ZK APP provers for taking in BPMN 2.0 formats of ANY business process ( Expected versus Actuals ). | Example test scripts, data and checks - review | The First-Cut Implmentation is Completed. and tested for tjhe basic model. Many other business process models are being templated for testing. The on-chain smart contract verifier is complete and avaiiable at https://zk-pret-bpmn-prover-test.vercel.app/ | Completed. and tested for tjhe basic model. Many other business process models are being templated for testing. | Completed. and progressing to Testing. | In progress | node ./build/src/BusinessProcessIntegrityVerificationFileTest.js 'bpmn-SCF-Example-Process-Expected.bpmn' 'bpmn-SCF-Example-Execution-Actual-Accepted-1.bpmn' node ./build/src/BusinessProcessIntegrityVerificationTest.js 'a(cb|bc)d(ef|f)g' 'abcdefg' | ||||||||||||||||||||||
12 | 2 | Generate example models and convert them in to test cases for processes involved in Supply-Chain Finance: | Design / Artifact Review | https://zk-pret-bpmn-prover-dev.vercel.app/ | A sample example is completed. Further examples are researched. Testing on the samples started | A sample example is completed. Further examples are researched. Testing on the samples started | A sample example is completed. Further examples are researched. | |||||||||||||||||||||||
13 | 3 | Uploading / Sourcing models from bpmn.io.- UI/UX Review. | Scope revision to using as a .bpmn extension import. | Design / Artifact Review | In progress. For the samples, testing underway. | In progress. For the samples, testing underway. | In progress. For the samples, testing underway. | In progress | Artifact Links | |||||||||||||||||||||
14 | 4 | Complete First Cut of the FrontEnd- ZK APP provers for taking in BPMN 2.0 formats of ANY business process ( Expected versus Actuals ). | Demo | An issue in the UI prototype implementation. Working and consuliting with MINA team. The UI fix has been verified. Thanks Aytunc. For the mid-point review, the bankend implemenation is ready to demo. while the ui will continuously evolve. will try to show the evolving ui. The midpoint review inlcuded the following: 1. A On-chain MINA Smart Cotnract verifier of the BusinessProcessIntegrity data in the smartcontract. at https://zk-pret-bpmn-prover-test.vercel.app/. The codebase for this is available at bpmn-bussiness-procers-prover 2. A version where the MINA L1 smart contract verifies the Proof produced from a ZKProgram . The steps are indicated in the readme, in a separatde code base in dir bpmn-bussiness-procers-prover-local. The wallet / ZKapp integration is work in progress for iteration 2 | An issue in the UI prototype implementation. Working and consuliting with MINA team. The UI fix has been verified. Thanks Aytunc. For the mid-point review, the bankend implemenation is ready to demo. while the ui will continuously evolve. will try to show the evolving ui. | An issue in the UI prototype implementation. Working and consuliting with MINA team. Thers was an inssue in the foundational ui - reported to MINA Issue - When a deployed smart contract is compiled using web-pack it gave invalid proofs, as the verfiication keys were different. Aytunc, helped with a fix / trunaround. We will incorporate. We tested and it seems to work in the tutorials and sample test rigs. Now we will incorporate in our broader code, test and notify. For the mid-point review, we will be able to show the backend Implementation, while the ui will continuously evolve. | An issue in the UI prototype implementation. Working and consuliting with MINA team. | We have seen ( and not able yet able to confirm if it just a timelag / race condition issue) or truly, there is an intermittent problem. This might be user error on our side., but also seeing other prople reporting such issues. https://github.com/o1-labs/o1js/issues/1287. However , when we dig in to this, we understand this is all about MINA internals on actually deploying the smart contract itself , and hence we are thinking this could just be some kind of timing / race condition issue. we are trying to set up a simple rig to isolate the problem, with just MINA tutorials without any of our code. Already connected in discord, where we got this link. However, we might need help in the next 1-2 days. | ||||||||||||||||||||||
15 | ||||||||||||||||||||||||||||||
16 | ||||||||||||||||||||||||||||||
17 | ||||||||||||||||||||||||||||||
18 | 3 | ZK-RISK MODEL PROVER | 1 | Complete Initial Roundtrip with an Implementor Sandbox for ACTUS unified Financial Contracts ForSimple Contract Types.. PAM / ANNUITY ( Principal At Maturity / ANNUITY ) | Example test scripts and PASS/FAIL health checks. | COMPLETED. AND SUCCESSFUL FOR KEY CONTRACT TYPES. Test scipts done | COMPLETED. AND SUCCESSFUL FOR KEY CONTRACT TYPES. Test scipts done | COMPLETED. AND SUCCESSFUL FOR KEY CONTRACT TYPES. | COMPLETED. AND SUCCESSFUL FOR KEY CONTRACT TYPES. | node ./build/src/RiskLiquidityACTUSVerifierTest_adv_zk_WithSign.js 8 | This is going very well, in terms of connecting to live ACTUS servers, and using ZK for compliance use-cases. | |||||||||||||||||||
19 | 2 | Design for CashFlowIn/Out Models for Liquidity Risk for Financial Portfolios and ZK PROOFS | Design / Artifact Review | Design in progress. Initial roundtrip also completed. COMPLETED. Inital models will be demod. But realisitic portfolios are being constructed. | Design in progress. Initial roundtrip also completed. COMPLETED. Inital models will be demod. But realisitic portfolios are being constructed. | Design in progress. Initial roundtrip also completed. COMPLETED. | Design in progress. Initial roundtrip also completed. | node ./build/src/RiskLiquidityACTUSVerifierTest_adv_zk_WithSign.js 8 "node build/src/RiskLiquidityACTUSVerifierTest_basel3_Withsign.js 0.5 - PASS node build/src/RiskLiquidityACTUSVerifierTest_basel3_Withsign.js 1 - PASS node build/src/RiskLiquidityACTUSVerifierTest_basel3_Withsign.js 2 - FAIL" | ||||||||||||||||||||||
20 | 3 | UI/UX Design complete for a demo app: For Financiers and Borrowers - Based on Data Integrity Analysis on Schemas and Privacy Aspects. | Design / Artifact Review | Design in progress.. First cut prototype in progress. | Design in progress.. First cut prototype in progress. | Design in progress.. Implementation in progess. | Design in progress. | |||||||||||||||||||||||
21 | ||||||||||||||||||||||||||||||
22 | ||||||||||||||||||||||||||||||
23 | ||||||||||||||||||||||||||||||
24 | 4 | STANDARDS-REGISTRY | 1 | Based on all above work, abstract the requirements for standards-registry | Design / Artifact Review | In progress. First-cut simple registry is evovling. Test scripts attached. | In progress. First-cut simple registry is evovling. Test scripts attached. | In progress | In progress | OracleRegistry.ts | ||||||||||||||||||||
25 | 2 | First cut Design Review for meta-data to be stored in an extensible way. | Design / Artifact Review | In progress on first-cut design | In progress on first-cut design | In progress on first-cut design | In progress | |||||||||||||||||||||||
26 | ||||||||||||||||||||||||||||||
27 | ||||||||||||||||||||||||||||||
28 | ITERATION:2 | Deliverable | ||||||||||||||||||||||||||||
29 | End of Week 8 | 1 | ZK- DEEP COMPOSITION ENGINE | 1 | Complete Identity and Compliance Proofs for Individual Identities Global Legal Entity Identifier, Examples ( Ministry of Corp Affairs/ India) / Director General of Foreign Trade API Specs With MOCK data | Example JSON and test scripts , , from mock data c harvested from the sand-box. | Started, and pulled forward in to the Mid-Point review. ( as above ) | Started | Started | |||||||||||||||||||||
30 | 2 | Complete Sand-Box Integrations With: Recursive Identity and Compliance Proofs for Individual Identities Global Legal Entity Identifier, Example ( Ministry of Corp Affairs/ India) / Director General of Foreign Trade API Specs With MOCK data | Example JSON and test scripts, for recursive modeling for layered identity based on sand-box data. ( This step will need collaboration with LEI - might need MINA Foundation support ). | Started conversations with ACTUS for sandbox, ir an implementor runtime ( chainaim) | Started conversations with ACTUS for sandbox, ir an implementor runtime ( chainaim) | Started conversations with ACTUS for sandbox, ir an implementor runtime ( chainaim) | ||||||||||||||||||||||||
31 | 3 | First Cut Implementation: For any given Standards Schema, Check and Proofs of Deep Integrity - abstracted for different schemas as a generic utility. ( For Required fields / Individual Fields ) | For example, JSON and test scripts are based on MOCK data. The assumption is that the user attestation of the data they are signing or relaying from other attestors will be used. All aspects of alignment to the standards for what financiers need ( ranges, thresholds etc ) will be proved without Borrowers having a need to expose un-necessary information . | Started the design. | ||||||||||||||||||||||||||
32 | 4 | Templates - For Financiers to choose from / customize - Research | Started design. | |||||||||||||||||||||||||||
33 | ||||||||||||||||||||||||||||||
34 | ||||||||||||||||||||||||||||||
35 | ||||||||||||||||||||||||||||||
36 | 2 | ZK - BUSINESS PROCESS PROVER | 1 | Completed BackEnd ( circuits generation ) and FrontEnd ( For importing files created in bpmn.io) | Test scripts, and Execution health checks. | Completed for SmartContract _verification . The ZKApp implementation is 60% done. | In progress | |||||||||||||||||||||||
37 | 2 | A usable demo-app: that takes in the expected and actual models , and produces the ZKPs for Business Execution Accuracy. | Demo. I | Started work on a demo for Business Process Prover. Implementation started. Can demo WIP. This was pulled-in and fast forwarded, because of issues with other parts of UI. The test demo app is running at https://zk-pret-bpmn-prover-test.vercel.app/ | Started work on a demo for Business Process Prover. Implementation started. Can demo WIP | Started some work on a demo for Business Process Prover. | backend - node server.js Server is running on http://localhost:4000 frontend - npm start browser running on http://localhost:3000/ BUSINESS PROCESS - EXPECTED = bpmn-SCF-Example-Process-Expected.bpmn BUSINESS PROCESS - ACTUAL -> Accepted --> bpmn-SCF-Example-Execution-Actual-Accepted-1.bpmn Rejected --> bpmn-SCF-Example-Execution-Actual-Rejected-2.bpmn | |||||||||||||||||||||||
38 | 3 | Finalize template models in : Finance / Supply-Chain Finance: Templates for Mortgage Loan, BL Process, Working Capital Loan | Artifact Review | In progress | In progress | |||||||||||||||||||||||||
39 | 4 | For SCF Ref Impl : Finalized ( Standards Alignment - For templates / customization for needed information ) | Artifact Review | Started. | ||||||||||||||||||||||||||
40 | ||||||||||||||||||||||||||||||
41 | ||||||||||||||||||||||||||||||
42 | 3 | ZK-RISK MODEL PROVER | 1 | Complete Initial Roundtrip with an Implementor Sandbox for ACTUS unified Financial Contracts For a Simple Contract Types. | Test scripts, and Execution health checks. | Started and In-progress. For Basel 3 compliance. | ||||||||||||||||||||||||
43 | 2 | CashFlowIn/Out Models and Common Metrics Proofs for ValueAtRisk, LiquidityAtRisk for common contract types : PAM( Principal At Maturity , ANN, Flavors of ANN( Annuity ), - Covering Tradfi / Defi and Institutional defi. | Design/Artifact Review | Started and In-progress. For Basel 3 compliance. | ||||||||||||||||||||||||||
44 | 3 | First cut demo app: For Financiers and Borrowers | Demo | |||||||||||||||||||||||||||
45 | ||||||||||||||||||||||||||||||
46 | 4 | STANDARDS-REGISTRY | 1 | First cut Schema - definition for the registry | Design/Artifact Review | |||||||||||||||||||||||||
47 | 2 | First cut Implementation of the standards registry | Design/Artifact Review | |||||||||||||||||||||||||||
48 | ||||||||||||||||||||||||||||||
49 | END2END SCF Assembly | First cut implementation of information flowing end2end. | Demo | This demo will be from the backend. Included in the mid point demo ( conceptual ) . The overall implementation is evolving. | This demo will be from the backend | This demo will be from teh backend | ||||||||||||||||||||||||
50 | ||||||||||||||||||||||||||||||
51 | ||||||||||||||||||||||||||||||
52 | ITERATION:3 | Deliverable | ||||||||||||||||||||||||||||
53 | End of Week 12 | 1 | ZK PRET - Deep Composition | 1 | Staging Both TEST and PROD environments | Test scripts Execution / Health checks | ||||||||||||||||||||||||
54 | 2 | Complete assembly of all kinds of proofs | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
55 | 3 | Test of membership of proofs - feeding to risk models for risk mapping | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
56 | 4 | end2end SCF flow testing | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
57 | ||||||||||||||||||||||||||||||
58 | ||||||||||||||||||||||||||||||
59 | 2 | ZK - BUSINESS PROCESS PROVER | ||||||||||||||||||||||||||||
60 | 1 | Business Process Provers for Example Templates completed. | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
61 | 2 | Business Process Provers for Standards Alignment completed -For any standards / Schema | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
62 | 3 | Business Process Provers - Completed , and tested in TEST env. | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
63 | 4 | Component stood up for use - ( For any model that is BPMN 2.0 compliant ) . | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||||||
66 | 3 | ZK-RISK MODEL PROVER | 1 | Complete testing for Proof s for risk metrics for common contract types for a variety of tokenization usecases. - Commodiites, Forex, UMP ( Non Maturity ) | Test scripts Execution / Health checks | |||||||||||||||||||||||||
67 | 2 | end2end SCF flow testing | Demo | |||||||||||||||||||||||||||
68 | 3 | Validations of Risk Model behavior - for different risk conditions | Test scripts Execution / Health checks | |||||||||||||||||||||||||||
69 | 4 | Future enhancements - of the highly vetted data for ACTUS to be run on financier AI models . | Research | |||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||||||
71 | ||||||||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||||||
73 | ||||||||||||||||||||||||||||||
74 | 4 | STANDARDS-REGISTRY | 1 | Onboarding early participant(s) - LEI, ACTUS | Relationships | |||||||||||||||||||||||||
75 | 2 | Chart out plans for interoperability with any other registry efforts, or promote this schema along with marketing efforts from ACTUS/ other universities / MINA etc. | Multi-level Ecosystem Dev. The standards organizations are offering support. | |||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||||||
77 | ||||||||||||||||||||||||||||||
78 | Summary | |||||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||||||
80 | Mar 16, 2025 | |||||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||||||
83 | Finished the Iteration-1 items The UI to be plumbed with the Wallet was facing issues, and hence pulled-in work planned for iteration #2 | |||||||||||||||||||||||||||||
84 | All founcational items connected to the right standards / data sources and generated Deep verification and compliance proofs | |||||||||||||||||||||||||||||
85 | For Deep compliance( Jurisdictional registration, Export Import compliance,Global legal Identifier, ) and composed proofs , Biil of Lading Invoice, BPMN 2.0 standard and ACTUS Risk standard adn simulation. | |||||||||||||||||||||||||||||
86 | Focus was on connectivity and the business infrastructure layer to produce these standards based proofs | |||||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||||||
88 | In further weeks in iteration # 2 focus will be on things like end2end encryption, UI impl with zkappworker, optimization for latency, and tightening trust assumptions- checkz and working closely with o1labs / MINA experts. | |||||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||||||
100 |