OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Infrastructure

EVID-DGC

EVID-DGC is a JavaScript digital evidence-management application that hashes files on intake, pins them to IPFS, and can anchor their digests on Polygon Amoy for later integrity verification.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

EVID-DGC — OpenViST project profile in Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it to evaluate or configure a testnet evidence-integrity workflow where file hashing, IPFS storage, and on-chain digest anchoring are relevant.

Who it is for

  • Teams evaluating digital evidence intake and file-integrity workflows
  • Developers configuring an evidence-management application with IPFS and Polygon Amoy

Documented uses

  • Calculate a SHA-256 digest for an evidence file at intake
  • Pin evidence files to IPFS and record their content identifier
  • Compare a retrieved file's hash with its recorded digest
  • Anchor a digest on Polygon Amoy when an authorized signer is configured
Before you choose

Requirements & limits

  • The documented chain target is Polygon Amoy testnet, not an economically final network.
  • Anchoring requires an authorized signer; otherwise anchor transactions revert and uploads may save with a warning.
  • IPFS or chain failures do not necessarily stop an upload from saving.
  • The README says public hash verification uses a database lookup rather than checking the ledger.
  • The base row-level security policy is permissive until security-hardening.sql is applied.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare a local EVID-DGC installation

Set up the documented application and database prerequisites for local use.

Before you start

  • Node.js ^20.19.0 or >=22.0.0
  • A Supabase project using Postgres
  • Supabase URL, Supabase key, and JWT secret

Steps

  1. Clone the public repository and change into its directory.

  2. Install dependencies with npm install.

  3. Copy .env.example to .env and fill in the required configuration.

  4. Set up the Supabase base schema and apply the listed additive migrations in order; apply security-hardening.sql to replace the permissive base row-level security policy.

  5. Start the server with npm start.

Expected outcome

The documented local server is configured to run at http://localhost:3000.

Guide limitations

  • The base SQL setup drops tables and is documented for an empty project only.
  • Seeded demo users cannot log in; the README instructs users to register a real account.
  • This setup does not establish production readiness or successful operation.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
17 October 2026
Original website title
Gooichand/blockchain-evidence · Official homepage title · retained in its source language
How we review sourcesSuggest a correction