feat: integrate COS Blockchain Compliance Tracker into DKG Edge Node fork#4063
feat: integrate COS Blockchain Compliance Tracker into DKG Edge Node fork#4063cmacademyconsulting wants to merge 3 commits intoOriginTrail:v8/developfrom
Conversation
There was a problem hiding this comment.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| cd dkg-edge-node-cos-compliance-tracker/apps/cos-compliance-tracker | ||
| npm install | ||
| cp .env.example .env # add Infura Project ID + PRIVATE_KEY | ||
| node demo.js |
There was a problem hiding this comment.
Bug: Referenced demo files missing from commit
Documentation instructs users to run node demo.js and npm run demo, but neither demo.js nor package.json defining the npm scripts are included in this commit. The judge instructions emphasize reproducibility as a core requirement, yet the primary demo script needed to verify the submission is missing, making it impossible for judges to execute the Quick Judge Path or verify the compliance tracker functionality.
Additional Locations (1)
| - Governance events (e.g., safety inspections, carbon permits, gender inclusion reports) are hashed using SHA‑256. | ||
| - Hashes are committed to Polkadot Westend/Paseo testnets. | ||
| - TxIDs, block numbers, and timestamps are logged in `/appendix/audit_table.csv`. | ||
| - **Verification:** Judges and researchers can cross‑check TxIDs via Polkadot.js Apps explorer. |
There was a problem hiding this comment.
Bug: Conflicting blockchain networks across documentation
The methodology document claims transactions are committed to Polkadot Westend/Paseo testnets and verified via Polkadot.js Apps, while all other documentation (READMEs, audit table, judge instructions) references Ethereum Sepolia testnet and Etherscan verification. The audit table contains Ethereum transaction IDs starting with 0x that are incompatible with Polkadot. This fundamental inconsistency makes it impossible to verify the blockchain records, breaking the core reproducibility requirement of the submission.
Additional Locations (2)
| @@ -0,0 +1,4 @@ | |||
| # Example environment configuration | |||
| RPC_URL=https://sepolia.infura.io/v3/YOUR_PROJECT_ID | |||
There was a problem hiding this comment.
Bug: Environment variable name mismatch breaks configuration
The .env.example file defines the variable as RPC_URL, but the judge instructions document shows the example as RPC_URL_SEPOLIA. This mismatch means judges following the instructions will configure a variable name that differs from what the example file provides, potentially causing the demo scripts to fail when they attempt to read the RPC endpoint configuration.
Description
This PR integrates the full COS Blockchain Compliance Tracker into the DKG Edge Node fork under
apps/cos-compliance-tracker.It demonstrates Agent–Knowledge–Trust architecture:
Motivation & Context
This integration is part of the NASA/OriginTrail hackathon submission. It ensures reproducibility, transparency, and judge‑friendly onboarding by embedding the COS tracker directly into the Edge Node repo.
Type of change
How Has This Been Tested?
apps/cos-compliance-trackerappendix/Checklist
Note
Adds the COS Blockchain Compliance Tracker under
apps/cos-compliance-trackerwith comprehensive docs, judge resources, proofs, and setup, and overhauls the rootREADME.mdwith a polished hackathon-focused guide.apps/cos-compliance-tracker/:README.md, judge instructions, checklist, and screenshot guide underdocs/andappendix/.appendix/audit_table.csv,proofs/demo_run.json..env.exampleand project-specific.gitignore.LICENSE(Apache-2.0) and references/bibliography.README.md: Replaced with a hackathon-oriented overview, Quick Judge Path, demo output example, judge resources, impact, references, repo structure, and license section.Written by Cursor Bugbot for commit 4903785. This will update automatically on new commits. Configure here.