DeFi Lender Onboarding

1. DeFi capital — your vault / treasury sits on idle stablecoin or asset reserves looking for diversified, non-synthetic yield.
2. The trust fabric — droplinked’s on-chain attestation layer (EAS Schema v2 — see Trust Fabric) lets you publish your underwriting methodology in a cryptographically verifiable way and issue per-merchant credit-risk attestations regulators can independently audit.
3. Real-world commerce — droplinked merchants (physical goods, digital, POD, in-store retail) generating actual sales — actual cash flow — and therefore actual repayments back to your wallet.

​

Architecture at a glance

​

Why droplinked?

• Real-world yield, not synthetic. Every repayment is anchored to a real merchant order on a real PSP (Stripe, PayPal, Telr, Bonum, PayMob). No rehypothecation, no second-order DeFi exposure.
• Cryptographic verifiability. Every credit-risk decision you issue is an on-chain attestation (Schema B) pinning a SHA-256 of the underwriting methodology you published. Verifiers re-hash and refuse on divergence.
• Per-merchant credit-risk granularity. Underwrite one merchant or one thousand; each gets its own Schema B attestation with its own creditTier + maxCreditLineUsdCents + expiresAt lifecycle. No portfolio-level smearing.
• Methodology hash pinning. You can’t silently swap underwriting basis. If you publish v2 of your scorecard, old attestations stay pinned to the v1 hash they cited at mint time; new mints cite v2. Every divergence is auditable.
• Audit trail for regulators. Every registry mutation — lender registration, status change, methodology supersession, methodology revocation — lands in an append-only audit log preserved by droplinked. Regulators querying the operator console can reconstruct any state at any past timestamp.
• Routing surfaces. Verified merchants in matching jurisdictions can discover you via GET /v2/lender-routing/recommend — exact-jurisdiction first, GLOBAL fallback. Your jurisdiction is your first-mover moat.
• MCP surface for consumer agents. ChatGPT / Claude / Cursor / OpenAI Agents SDK can discover and recommend you to onboarding merchants directly via the droplinked-mcp server. No partner BD required.

​

The 4-step onboarding flow

curl -X POST https://apiv3.droplinked.com/admin/lenders \
  -H "Authorization: Bearer $SUPER_ADMIN_JWT" \
  -H "Content-Type: application/json" \
  -d '{
    "lenderId": "your-lender-slug",
    "displayName": "Your Lender (Jurisdiction)",
    "archetype": "defi-vault",
    "jurisdiction": "GLOBAL",
    "signingWallet": "0x0000000000000000000000000000000000000000",
    "regulatorReference": null
  }'

HASH=$(shasum -a 256 ./methodology-v1.pdf | awk '{print $1}')

curl -X POST https://apiv3.droplinked.com/admin/methodologies \
  -H "Authorization: Bearer $SUPER_ADMIN_JWT" \
  -H "Content-Type: application/json" \
  -d "{
    \"lenderId\": \"your-lender-slug\",
    \"version\": \"1.0.0\",
    \"methodologyHash\": \"$HASH\",
    \"documentUrl\": \"https://yourdomain.example/methodology-v1.pdf\",
    \"displayName\": \"Your Lender — Working-Capital Methodology v1.0\"
  }"

curl -X POST https://apiv3.droplinked.com/admin/lenders/your-lender-slug/status \
  -H "Authorization: Bearer $SUPER_ADMIN_JWT" \
  -H "Content-Type: application/json" \
  -d '{ "newStatus": "ACTIVE", "reason": "KYB verified" }'

curl -X POST https://apiv3.droplinked.com/v2/attestations/credit-risk \
  -H "Authorization: Bearer $LENDER_JWT" \
  -H "Content-Type: application/json" \
  -d '{
    "merchantId": "6a207db0d29923bffaa983ca",
    "lenderId": "your-lender-slug",
    "creditTier": "T2",
    "maxCreditLineUsdCents": 5000000,
    "methodologyHash": "0xabc123...",
    "expiresAt": "2026-12-31T23:59:59Z"
  }'

​

What verifiers see

​

Agent surface (MCP)

​

Audit-trail commitment

​

Status semantics

​

LenderRegistry status

​

MethodologyRegistry status

​

Reference dashboard

​

Verifier integrity recipe

1. Read the on-chain Schema B attestation — GET /v2/attestations/credit-risk/:merchantId. Pin attestationUid, lenderId, issuerWallet, methodologyHash, occurredAt.
2. Resolve the methodology hash — GET /v2/methodologies/:lenderId/:methodologyHash. Pull documentUrl + status + effectiveAt.
3. Re-hash the document — curl -sLo /tmp/methodology.pdf $DOC_URL && shasum -a 256 /tmp/methodology.pdf. Compare against the on-chain methodologyHash. Any divergence is methodology tampering and the attestation must be refused.

​

Operator gates

​

Related

• Trust Fabric (EAS Schema v2) — 4-axis architecture overview
• Forensic Chain Workflow — end-to-end verifier walkthrough
• Lender Registry Lookup — /v2/lenders/* reference
• Methodology Registry Lookup — /v2/methodologies/* reference
• Trust-Fabric Stats — /v2/trust-fabric/stats reference
• Lender Trinity MCP Tools — agent-callable wrappers
• Trust-Fabric Dashboard Template — drop-in HTML + JS reference