MVP coverage
This page maps the Blockchain India Challenge guidelines for the Minimal Viable Product phase to the pages that address them.
Areas of the MVP phase
| Area | Expectation | Where |
|---|---|---|
| Functional product | An end-to-end working solution for the government use case | How a case moves, User manuals, Test report |
| Architecture | Modular, scalable, with API integration and the ability to replicate across States and UTs | System architecture, API overview, Adding a State |
| Blockchain implementation | A permissioned blockchain used meaningfully for multi-stakeholder workflows, transactions, auditability and tamper resistance | Network and nodes, Chaincode overview, Audit trail and verification |
| Demonstration and testing | Demonstrate the solution and test the MVP thoroughly | Demo and test data, Test report |
| Security and privacy | Security, privacy, access control and data protection | Security assessment, Data protection, Roles and privileges |
| Performance | Scalability, reliability and acceptable performance | Performance, Monitoring and logs |
| Innovation | Deep-tech capabilities where relevant | See below |
| Compliance | Applicable regulatory aspects | Legal basis, Regulatory aspects |
| Documentation | Design, development, testing, deployment and technical documentation | This site; Source code |
| Scalability plan | Proliferation to other States, UTs and departments | Adding a State, Performance, From MVP to pilot |
Deliverables and demonstrable outcomes
Deployment-ready modules and workflows
| Outcome | Where |
|---|---|
| End-to-end blockchain-based operational workflows | How a case moves |
| Core blockchain transactions | Signed actions, and the four chaincode pages |
| Roles and privileges of the stakeholders | Roles and privileges, Identity and access |
| Integration with existing systems through APIs | API overview, External systems |
| Realistic or approved synthetic test data | Demo and test data |
| What is stored on-chain and off-chain | On-chain and off-chain data |
| The audit trail and verification mechanism | Audit trail and verification |
Testing reports
| Report | Where |
|---|---|
| Functional testing | Test report |
| Integration testing | Test report |
| Security audit | Security reviews (internal reviews; an external audit is planned before go-live) |
| Performance and load testing | Performance |
Deployment readiness
| Item | Where |
|---|---|
| Production-oriented architecture | Deployment architecture |
| Infrastructure and deployment plan | Infrastructure plan, Deployment architecture |
| Backup and recovery plan | Backup and recovery |
| Monitoring and logs | Monitoring and logs |
| Security controls | Security assessment |
| API documentation | API overview and its pages |
| User and admin manuals | User manuals, Registrar, Officials' console |
Scalability
| Item | Where |
|---|---|
| Replication strategy for other departments and States | Adding a State |
| Roadmap from MVP to pilot | From MVP to pilot |
Documents and artefacts of the technical report
| Artefact | Where |
|---|---|
| System architecture and data flow | System architecture, Data flow |
| Blockchain network and node architecture | Network and nodes, Identity and access |
| Smart contract and chaincode documentation | Chaincode overview and the four contract pages |
| API and integration documentation | API and integration |
| Security and privacy assessment | Security assessment, Data protection, Security reviews |
| Performance and scalability test report | Performance |
| Source-code documentation | Repositories and the source pages |
| Open-source software and licence register | Open-source register |
| User and admin manuals | User manuals, Admin manuals |
| Deployment architecture | Deployment architecture |
Compliance points
| Point | Where |
|---|---|
| Detailed documentation maintained throughout the challenge | This site, and each repository's own documents listed in Repositories |
| A clear open-source register with components, licences, references and modifications | Open-source register |
Innovative components
- Every action is signed on the actor's own device, and the backend holds no authority, so a compromised server cannot forge a record. See System architecture.
- Private reads are signed requests whose answers are bound to the request and endorsed by peers of two institutions, so the phone need not trust the backend for a value.
- Statutory time limits of the BNSS run as clocks on the ledger, and a missed deadline cannot be erased by a later action. See fir-registry.
- Duplicate detection in two tiers: identical evidence hashes matched inside the chaincode, and attested text similarity from a registered, versioned model. Neither blocks anything, and a magistrate decides.
- Public verification of any police or court document by its SHA-256 fingerprint, without uploading the document.
- Erasure that destroys keys and keeps the proof, under a court order.
- Two-party custody hops for evidence, and laboratory notes kept from the police until the report is sealed.
- A purpose-built ledger explorer and integrity checker that each institution can run against its own peer.
Source: Blockchain India Challenge, "Guidelines to the Startups for the Minimal Viable Product (MVP) Phase".