Open-source DeFi infrastructure on Stellar. Our flagship project is InvoFi — an on-chain invoice financing protocol built on Soroban, Stark Vault Link's answer to a working-capital market that still leaves small businesses waiting 30–90 days on unpaid invoices.
- Businesses tokenize outstanding invoices on-chain and raise working capital against them.
- Lenders browse verified invoices, offer financing in USDC or XLM, and earn interest — holding POSI position tokens that make their exposure transferable.
- Trustless Work escrows gate disbursements: financed funds are released against delivery milestones, not blind trust.
- Insurance + reputation: an on-chain insurance pool covers lenders on defaults, and repayment history feeds on-chain reputation scores.
The full lifecycle — register → offer → accept → escrow disbursement → repay or reclaim — happens on Stellar testnet today, with mainnet on the roadmap.
| Repo | What lives there |
|---|---|
invofi |
The application: Next.js frontend, wallet-first auth (SEP-10, no passwords), marketplace, portfolio, stats, Trustless Work escrow integration, @invofi/sdk |
invofi-contracts |
The protocol: five Soroban contracts (registry, financing, repayment, insurance, reputation) plus a shared common library |
- Register — a business tokenizes an invoice in the registry contract.
- Finance — lenders submit offers; on acceptance funds move and POSI position tokens mint natively.
- Disburse — the financed amount flows through a Trustless Work escrow tied to delivery milestones.
- Repay or reclaim — the business repays principal + interest; on default, the insurance pool settles lenders' outstanding claims.
- Reputation — every repayment updates the participant's on-chain score.
- Live app: https://invofi-five.vercel.app
- Telegram: https://t.me/+K56Xkd2pfPM4NDE0
- LinkedIn: https://www.linkedin.com/company/stellar-vaultlink
Both repos accept external contributions. Issues are scoped and labeled by
complexity (good first issue, trivial, medium, high) — pick one,
request assignment, and open a PR against it. PRs from contributors must map
to an assigned issue.
Security: private vulnerability reporting is enabled on both repos — see
each repo's SECURITY.md for contact channels and response expectations.
Everything here is MIT licensed.