Four-person university project

Honorablockchain evidence management

2025 to 2026. Repository.

What I ownedBlockchain, backend and testing: the EvidenceRegistry contract, the Express API, the integrity pipeline and their tests.

  • Diya AI layer
  • Abhijith A Frontend and testing
  • Meghna Cross-case linkage and frontend
Deployed and source-verified on Ethereum Sepolia0xf4e1c0179acC2A54C195e8687621ee070be06B3CEvidenceRegistry.sol, Solidity 0.8.24Open on Etherscan

Architecture, drawn

Honora: every request passes an Express gate for a cheap 403 and then the contract's own role check, which is the authority. Evidence hashes and custody transfers live on Ethereum Sepolia; files go to IPFS and metadata to MongoDB; AI indexing never blocks an evidence operation.Source of truthhashfails closedappend-only custody chainfilemetadataClientPolice, Forensic, Lawyer, JudgeExpress APIJWT HS256, bcrypt 12 roundsMiddleware RBACcheap 403 at the edgeEvidenceRegistry.solSepolia, verified, Solidity 0.8.24Modifier RBACauthoritative gate, on-chainIPFS via Pinataevidence filesMongoDB Atlasoff-chain metadata onlyAI indexingfire-and-forgetduplicate hashes rejected globallyevery action emits an eventSHA-256 of the evidence fileone signer wallet per rolean application-layer bypass still cannot act on-chain
Honora: every request passes an Express gate for a cheap 403 and then the contract's own role check, which is the authority. Evidence hashes and custody transfers live on Ethereum Sepolia; files go to IPFS and metadata to MongoDB; AI indexing never blocks an evidence operation.

Problem

Digital evidence is only useful in court if nobody could have altered it between collection and trial. Honora records a hash of every piece of evidence and every custody transfer on Ethereum, and treats the on-chain record as the only source of truth.

Architecture

EvidenceRegistry.sol, Solidity 0.8.24, built with Hardhat v3 and ethers.js v6. An on-chain role enum (None, Police, Forensic, Lawyer, Judge), gas-efficient custom-error reverts, an append-only custody chain, global duplicate-hash prevention and full event emission.

Access control is dual-layer. Express middleware gives a cheap 403 at the edge; Solidity modifiers are the authoritative gate. An application-layer bypass still cannot act on-chain.

The backend is Node 22, Express, TypeScript ESM, JWT HS256, bcrypt at 12 rounds, MongoDB Atlas for off-chain metadata only, IPFS via Pinata, and a SHA-256 integrity pipeline. Role-specific signer wallets fail closed when unconfigured. AI indexing is fire-and-forget, so evidence operations never depend on a non-critical service.

Decisions

Two gates, one authority
The middleware exists for speed and error messages. The contract exists for truth. If they ever disagree, the contract wins, because it is the only one an attacker cannot route around.
Fail closed on missing signers
A role whose wallet is not configured cannot act at all. Silently falling back to a default signer would make the audit trail lie about who did what.
AI indexing never blocks evidence
Indexing is useful and non-critical. It is dispatched and forgotten, so an outage in the AI layer cannot stall a custody transfer.

Measured, not asserted

Contract
EvidenceRegistry.sol, verified on Sepolia
Duplicate evidence hashes
rejected globally, on-chain

Honest limits

  • University-caliber proof of concept, not a production deployment.
  • CI/CD is in progress, not yet complete.

Stack

  • TypeScript
  • Node.js
  • Express
  • MongoDB
  • Solidity
  • Hardhat
  • ethers.js
  • IPFS