CreditMesh

CreditMesh is a receivables financing protocol built on Hedera. A supplier creates an invoice pool, investors bid to fund it, and when the supplier accepts a bid, the settlement agent creates an HTS fungible claim token representing investor rights to future repayments from that invoice pool.

The project uses Hedera Token Service in two ways: one HTS claim token is created per invoice pool, and a demo CMUSDC HTS token is used for settlement transfers between investor, escrow, debtor, and claimant accounts. The lifecycle includes investor funding, debtor repayment, and investor claim settlement.

CreditMesh also logs lifecycle events to Hedera Consensus Service, creating an auditable trail for invoice creation, bid acceptance, tokenization, funding, repayment, and claim activity. The proof page shows HTS token configuration, HCS topic data, Mirror Node data, CMUSDC balances, and HashScan links on Hedera testnet.

CreditMesh is built with Next.js, TypeScript, React, and the Hedera JavaScript SDK. The app models a receivables financing protocol where suppliers create INR invoice pools, debtor agents confirm/repay obligations, investor agents bid, and settlement logic mints HTS claim tokens plus moves demo CMUSDC on Hedera testnet. Hedera is used in three places: HCS records lifecycle audit events, HTS creates invoice-pool claim tokens, and HTS token transfers simulate funding, debtor repayment, and investor claims. We also read Mirror Node data and surface HashScan links so judges can verify topic messages, token IDs, balances, and transfer transactions. For pricing, the protocol has a Chainlink-style FX layer: USD/INR quotes affect funding and repayment calculations, with support for an EVM sidecar/Chainlink feed path and deterministic fallback for demo reliability. World verification is modeled as the human-backing layer for supplier, debtor, and investor agents, with an MVP bypass for fast Hedera-only testing. The hacky-but-useful part: we generate disposable Hedera testnet actor accounts and a demo CMUSDC token, store their keys only in a gitignored local .creditmesh file, and let the server sign local demo transfers. That gives a smooth hackathon demo without pretending those keys are production custody.