Clinova — Real-World Healthcare Infrastructure for Telemedicine

Clinova is a DePIN/RWA infrastructure network that connects healthcare applications to verified real-world diagnostic capacity.

Telemedicine has made it possible to access healthcare digitally, but physical diagnostic services remain fragmented across independent laboratories and healthcare providers. Clinova creates an onchain coordination layer that allows healthcare applications to discover verified diagnostic providers, request their services, escrow payment, verify completion, and settle transactions.

Instead of putting medical records or patient data onchain, Clinova brings real-world healthcare capacity into a programmable infrastructure network.

How It Works

A healthcare application can:

Discover → Reserve → Escrow → Verify → Settle → Build Reputation

Discover — Find verified diagnostic providers with the required capabilities.
Reserve — Create a service request for a specific diagnostic service.
Escrow — Lock USDC in a smart-contract escrow until the service is resolved.
Verify — The provider submits a proof-of-service commitment that can be reviewed by an authorized verifier.
Settle — Once the service is approved, the smart contract releases payment to the provider.
Reputation — Provider performance is recorded at the protocol level.

What We Built

Clinova is backed by five Solidity smart contracts:

ProviderRegistry — provider registration, verification, capabilities, staking and eligibility.
ServiceMarketplace — service requests and the request lifecycle.
ClinovaEscrow — isolated USDC escrow and settlement accounting.
ProofOfService — proof submission, review and finalization.
ReputationRegistry — onchain provider performance and reputation.

The contracts use role-based access control, explicit state machines, SafeERC20, reentrancy protection, pausing controls, custom errors, pull-based payments and extensive invariant/fuzz testing.

What Has Been Tested

Clinova has been deployed to Arbitrum Sepolia and tested through real onchain flows using Circle USDC.

The working testnet flow includes:

Provider registration → staking → verification → activation → service request → USDC funding → provider acceptance → proof submission → verification → settlement → withdrawal → reputation update

We also tested:

Disputed services and buyer refunds
Protocol pause behavior
Unauthorized access attempts
Invalid state transitions
Duplicate actions
Escrow accounting
Provider stake accounting
Proof replay protection
Reputation consistency
Malicious-token behavior
Fork testing against Arbitrum Sepolia
Frontend integration and wallet flows

The protocol has undergone extensive fuzzing, invariant testing, adversarial testing and mutation testing, with the deployed system validated on Arbitrum Sepolia.

Why Blockchain?

Clinova uses blockchain specifically where a shared, programmable coordination layer is useful.

Independent healthcare businesses can interact through predefined rules for:

Escrow → Proof → Settlement → Reputation

Payment does not depend on a centralized database simply saying that a transaction happened. The protocol enforces the settlement rules through smart contracts, while sensitive healthcare information remains offchain.

The Bigger Vision

Clinova is starting with diagnostic capacity because physical healthcare infrastructure is fragmented and difficult for digital healthcare platforms to access programmatically.

The long-term vision is a broader decentralized healthcare infrastructure network where laboratories, diagnostic centers and other physical healthcare providers can contribute capacity that healthcare applications can discover and use through a common protocol.

Clinova turns fragmented real-world healthcare capacity into programmable infrastructure for the next generation of healthcare applications.

We built Clinova incrementally, starting from the protocol architecture and progressing through security testing, deployment, and the frontend application. Phase 1 — Architecture & Foundation Defined the protocol architecture, actors, service lifecycle, escrow model, provider eligibility, proof-of-service flow, and onchain/offchain data boundaries. Phase 2 — Provider Infrastructure Built and tested the `ProviderRegistry`, including provider registration, verification, staking, capabilities, eligibility checks, and job accounting. Phase 3 — Marketplace & Escrow Built the service marketplace and USDC escrow system with explicit state machines, payment accounting, cancellation, expiry, disputes, and settlement logic. Phase 4 — Proof & Reputation Added proof-of-service and protocol-level reputation. We also changed the settlement model so providers are only paid after an accepted or verified completion rather than simply submitting a completion claim. Phase 5 — Security & Adversarial Testing Performed extensive unit, fuzz, invariant, adversarial, boundary, authorization, malicious-token, mutation, and fork testing. We identified and fixed issues during this process before deployment. Phase 6 — Arbitrum Sepolia Deployment Deployed all five contracts to Arbitrum Sepolia and verified them on Arbiscan. We then executed real USDC flows including successful settlement, refunds, disputes, withdrawals, reputation updates, and pause behavior. Phase 7 — Frontend Built the Clinova web application with React, TypeScript, wagmi and viem. The frontend connects directly to the deployed contracts and provides buyer, provider, and verifier workflows. Phase 8 — Product Positioning & Demo Readiness Refined the product story around Clinova as a DePIN/RWA infrastructure layer for telemedicine, connecting digital healthcare applications to verified real-world diagnostic capacity. The result is a working end-to-end testnet prototype rather than a purely conceptual design: the smart contracts, frontend, wallet interactions, escrow, proof, settlement, and reputation layers have been implemented and tested together on Arbitrum Sepolia.

Clinova

ビデオ

テックスタック