DAVC Network issues verifiable asset certificates for crypto-backed institutional lending. Custody attestations, privacy proofs, and an audit trail from application to funding.
Operating flow
One path operators actually run. Not a feature matrix, a sequence.
Open a loan. Attach MISMO packages. Status only advances when docs, custody, and certificate checks clear.
Request balance attestations from qualified custodians. Offline APIs block certificate issuance on purpose.
Issue a DAVC with subject DID, asset summary, ZK proof hash, expiry, and a tx/block receipt.
Compliance disposes risk and KYC, then approves or funds. Everything lands in the audit pack.
What the product is
The work is certificates tied to custody attestations and loan state. Brokers complete checklists. Compliance closes exceptions. Admins export the pack when someone asks for evidence.
Broker, compliance, admin. Each login gets a work queue from live product state: pending KYC, offline custodians, expiring certs, applications stuck mid-checklist.
Issue, attest, approve, fund. Each mutation records actor, timestamp, and a chain receipt (live gateway or local simulation for demos). Public verify resolves certificates from the shared store.
Chain modules
Cosmos SDK modules that map 1:1 to operator work. If it isn’t in the dashboard, it doesn’t belong in the pitch.
davc custody zkverifier loanescrow loantoken frauddetection lenderportal anchoring Stack
Cosmos SDK chain, CometBFT consensus, IBC-ready. An API gateway returns receipts when available; the dashboard falls back cleanly for demos. The point of the stack is not TPS theater. It’s a durable record that a specific collateral was attested and certified.
Contact
Technical briefings, custody integrations, and lender onboarding. We reply within one business day.
hello@davcnetwork.com