Skip to content
Page cover
3Jane Docs · Manifesto

3Jane Docs | Protocol Documentation

The credit-based money market, documented from first principles.

3Jane is built around a simple idea: internet-native finance needs credit that can price repayment capacity and future cash flows, not only existing crypto collateral. The documentation connects that thesis to the protocol's two-tranche supplier stack, its credit sleeves, Levered Callable Capital (LCC), JANE incentives and the operational controls that bind the system together.

Why credit expansion matters

Stablecoins solved a large part of the medium-of-exchange problem for onchain markets, while most DeFi lending still requires borrowers to pledge more collateral than they borrow. 3Jane extends the design space toward credit-based underwriting, where verifiable assets, cash flows and credit signals can contribute to a lending decision.

This changes the question from “what token can the borrower lock?” to “what repayment capacity can be verified, priced and monitored?” The rest of the docs explains how supplier capital is structured around that problem.

One capital stack, two credit sleeves

Suppliers deposit USDC into a tranched stack represented by USD3 and sUSD3. USD3 is the senior position; sUSD3 is the junior, first-loss position. That stack can fund Crypto Credit Lines (CCL) and Fintech Credit Conduits (FCC), which diversify exposure across borrower types and credit structures.

USDC suppliersUSD3 senior / sUSD3 juniorCCL + FCC credit sleevesInterest, recoveries and lossesTranche-level outcomes

How to use these docs

Start with Introduction for the system map. If you are supplying capital, continue through Suppliers, Supply USDC, Pool Interest Rates and Liquidity. If you are evaluating contingent capital, use the LCC section. Developers should use Architecture before Addresses so contract references are interpreted in system context.

GoalStart here
Deposit USDCSupply USDC
Compare risk layersSuppliers
Understand backingBacking Overview
Learn LCCLCC Introduction
Review securityRisks / Audits
IntegrateArchitecture / Addresses

Documentation principles

Parameters such as rates, caps, leverage, eligibility and emissions can change. Pages therefore separate durable protocol mechanics from values that should be read from the live interface or current protocol configuration. Never treat an example value in documentation as a guaranteed return or permanent risk parameter.

Use the live app for current rates and availability; use the docs for mechanics, risks and decision context.

Protocol mechanics are documented for education and integration context. Current rates, caps, emissions, eligibility and transaction parameters should be verified in the live 3Jane interface before acting.