3Jane

3jane.xyz3JaneA New Era of Capital Efficiencyhttps://www.3jane.xyz/

The loan book is the product

Most DeFi lending stays clean by avoiding the borrower.

Aave, Morpho, Spark, and the rest of the overcollateralized stack do not really underwrite credit. They underwrite liquidation. The borrower can be anonymous because the collateral is meant to speak for them. If the trade goes wrong, the protocol sells the collateral and moves on.

That is why DeFi lending scales so neatly: it removes the ugliest part of lending. 3Jane is trying to bring that part back.

The current 3Jane site frames USD3 as a credit-backed yieldcoin for fintech lenders. The older introduction docs were broader: proofs of assets and cash flows, credit data, collections, and even non-performing-loan auctions. The May 2026 evolution post narrows the thesis into warehouse loans, participations, and forward-flow programs for fintech originators.

That transition is still visible in the public materials. The docs manifesto and introduction layer still read like a general-purpose crypto credit primitive. The operating focus the team is now pointing to is much narrower: asset-backed credit facilities for fintech lenders. That narrowing is healthy. It also means the public narrative is still catching up with the product they seem to actually want to build.

What matters is the direction of travel. 3Jane moved from "unsecured crypto credit for users" toward stablecoin capital funding real-world receivables through a crypto-native liability stack. Risk moved closer to the assets. That makes the project more serious, and harder to evaluate.

3Jane can clearly ship contracts. The harder part is whether the assets behind them become legible enough for capital to stay when repayment stops being theoretical.

The borrower comes back

Aave is the easy comparison, and also the wrong stopping point.

Aave is a collateral machine. 3Jane is trying to become a credit conduit. In overcollateralized lending, the system can ignore a lot of human mess because collateral liquidation is the enforcement layer. In credit, the enforcement layer is repayment, servicing, reporting, loss allocation, and recovery. That changes the underwriting standard.

3Jane's earlier V1 framing looked more crypto-native and more expansive. Users could borrow against proofs of assets, future cash flows, or credit data. That idea is powerful, but it runs straight into adverse selection. The users most eager to borrow against fuzzy proofs are not automatically the borrowers a protocol wants to fund.

The evolution post gives V1 one useful credit mark: 3Jane says it originated about $8 million to 60 U.S.-based prime and superprime yield farmers, with 100% monthly payments, zero defaults, and zero principal impairment after seven months. That matters, but it is not enough to underwrite the new system. It is project-reported, still lightly seasoned, and different from proving performance across fintech receivables, warehouse lines, and redemption pressure.

The V2 path is narrower and probably stronger. Fintech originators already produce receivables. They need capital and they understand warehouse lines, forward-flow buyers, repayment data, servicing, and portfolio reporting. 3Jane's job becomes less magical: give those originators a new funding interface and give crypto capital a tokenized liability it can hold, trade, and route through DeFi. Less magical is often where the real business starts.

The useful clarification is that 3Jane is no longer speaking about "credit" as one blob. The ABF risk primer splits the product into two real structures: warehouse loans and forward-flow programs. That matters because it moves the discussion from abstract credit expansion to specific conduits with specific failure modes.

Proof of plumbing

3Jane has deployed USD3, sUSD3, and JANE addresses. The public repo, moneymarket-contracts, is Solidity-heavy, active into June 2026, and has shipped releases through v1.1.4. Veridise lists 3Jane audit work.

Paradigm lists 3Jane on its portfolio page, The Block reported a $5.2 million seed led by Paradigm, and Wintermute Ventures publicly backed 3Jane and Jacob Chudnovsky.

The repo and release surface are useful because they point at real operating problems: withdrawal liquidity, stale NAV handling, sUSD3 loss absorption, shutdown reporting, operational roles, credit-vault logic, borrower reserves, and withdrawal queues. Those are not cosmetic features. They are the parts that get tested when credit meets liquid tokens.

Still, code is only plumbing. NAV freshness, withdrawal queues, loss absorption, and shutdown behavior matter because credit products usually fail slowly: delays, partial recoveries, stale marks, unclear waterfalls. The repo raises conviction that the team understands the machinery. It does not answer whether the assets perform.

The strongest new bridge between "plumbing exists" and "credit conduit exists" is the LendSwift senior warehouse facility report. This is more than a generic partner mention. 3Jane says it executed a $10 million senior warehouse facility funding roughly 15,000 short-duration consumer receivables, with a ~124-day weighted-average life, a 15% facility coupon, a 75% advance rate, a 25% first-loss layer retained by LendSwift, a bankruptcy-remote SPV, a DACA-controlled collections account, weekly surveillance, a revolving period through May 26, 2027, and final maturity on November 26, 2027.

Performance is still open. What this does show is that the project has crossed an important line: there is now a named facility with a stated structure, waterfall, and collateral pool.

Two interfaces, one hard part

3Jane has two interfaces. The crypto interface is clean: deposit, receive USD3 or sUSD3, earn yield, move through DeFi integrations, maybe later participate in JANE-driven incentives or governance. Crypto users understand this part.

The credit interface is not clean. Originators need capital. Facilities need terms. Cash flows need servicing. Losses need a waterfall. Redemptions need liquidity. Someone has to decide how much risk sits in USD3, how much sits in sUSD3, and how much value leaks out before users ever see it.

The product becomes real in the second interface. This is why 3Jane cannot be judged only by its token contracts, repo, or headline yield. The onchain layer makes the liability programmable, but the credit still has to perform.

A high APY is a credit question before it is a marketing line. The question is what risk is paying for it.

USD3 is rehearsing

The most important detail in the docs is the staging. The FAQ says USD3 is intended to be fully backed by Aave USDC for the first three-plus months, with only JANE incentives during that risk-off phase.

That is a sensible launch design: users get a familiar backing profile while the protocol builds distribution, liquidity, integrations, and habit. It also means early USD3 supply should not be read as proof that the credit machine is working.

At this stage, USD3 is partly a rehearsal. It tests whether users will hold the liability, whether venues will route it, whether liquidity can form, and whether incentives can create enough attention for the system to matter. The harder product starts when USD3 and sUSD3 carry more of the credit exposure they are meant to represent.

sUSD3 is closer to the real risk. Public docs describe it as having full exposure to the credit-line pool, a one-month lockup, liquidity-limited redemptions, and an initial utilization target around 85%. That is the cleaner bargain: extra yield in exchange for being closer to the credit.

The split makes sense, but the market still needs to watch it through stress. The first real test is not launch. It is a month where repayments are late, redemptions are requested, NAV has to be updated, and the protocol has to explain who takes the loss without turning the answer into fog.

Slope is a rung

Slope is the strongest credit-side signal in the pack.

There are project-side claims around Slope and later facility growth, but the useful evidence is counterparty-side. Ashish Jain posted on LinkedIn about 3Jane executing an $8.5 million whole-loan purchase with Slope, and another Slope-side post points in the same direction.

That is meaningfully better than a partner logo. It says a named transaction happened.

It is not performance history.

LendSwift pushes the same point one step further. Slope showed that a counterparty-side transaction happened. LendSwift adds facility structure, tranche logic, collateral composition, and cash-control detail. Useful progress, but still not the same thing as a seasoned credit record.

The ladder from here is simple: project-side claim, counterparty-side transaction, observable facility behavior, repeated repayment performance, then stress-tested capital retention. Slope gets 3Jane above the first rung. The rest still has to be earned.

The next evidence layer is what happens after the loans season: repayment behavior, delinquencies, recoveries, and whether USD3/sUSD3 holders are actually being paid for the risk.

Credit buyers do not stop at "did a transaction happen?" They ask what happened the first time it got ugly.

Evidence quality

The evidence stack is good, but uneven. Credit research gets dangerous when every signal is treated as the same kind of proof.

The boring competition

3Jane competes against different stacks depending on who is looking.

For stablecoin suppliers, the substitute set is Aave, Morpho, Spark, Sky/sUSDS, Ethena/sUSDe, T-bill wrappers, CEX yield accounts, and other products that already package yield behind a simple interface. Users are not waking up wanting fintech receivables. They want liquidity, clarity, and a reason not to feel like exit liquidity for someone else's credit book.

There is also the onchain private-credit lane: Maple, Goldfinch, Centrifuge, Credix-style rails, and the broader RWA yield wrapper set. 3Jane is not identical to those projects, but it competes for the same question: can crypto capital fund offchain credit without turning the risk into a black box?

For originators, the substitute set is bank warehouse lines, private credit funds, forward-flow buyers, ABS and securitization channels, balance-sheet capital, and relationship lenders. Those markets are slower and less composable, but they already know how to evaluate credit.

So 3Jane's edge cannot just be "onchain." Onchain is useful only if it improves the liability side enough to matter: faster capital formation, broader stablecoin distribution, programmable tranching, transparent positions, DeFi routing, maybe more liquid funding.

The wrapper changed, but the credit question stayed the same. If the assets are good, 3Jane can become an onchain conduit for productive private credit. If that answer stays hidden behind APY, the product is still asking users to hold risk they cannot evaluate.

JANE comes after the credit

JANE should not lead the analysis. The liquidity mining article, JANE docs, and current farm surface show where bootstrapping spend is being directed. Weekly emissions go to supplier and LP behavior, with transferability expected in 2026 and supply still ranging widely from 1.111 billion to 6.667 billion. Eligible activity includes USD3/sUSD3 deposits, Pendle/Curve-style liquidity, YT/PT positions, and credit-line withdrawal.

Those mechanics can bootstrap attention. They can also blur demand.

Users holding USD3 for JANE is different from users holding USD3 because they trust the credit. LP depth paid for by emissions is different from durable funding. Incentives are useful early, but they are not proof of credit-market fit.

The token becomes interesting only after the credit machine deserves a token. JANE's eventual value case depends on a few concrete things: governance that matters, fees that accrue, and useful activity that actually reaches token holders instead of leaking away elsewhere.

Disclosure as collateral

The most important product 3Jane can ship may be a dull dashboard.

A serious credit interface needs to show enough performance data for users to understand what they own: facility size, originator exposure, utilization, delinquencies, reserve coverage, and how those numbers change over time.

For a product like this, disclosure is part of what users are underwriting.

That sounds strange only if credit is treated like an offchain appendix. The onchain contracts can show supply, balances, transfers, and protocol mechanics. They cannot tell users whether a fintech-originated loan pool is improving or deteriorating. That information has to enter the system with enough discipline that the return stops looking like a number floating above a black box.

This is where 3Jane could separate itself from generic RWA yield wrappers. Many products sell users a yield number and a story. A better credit protocol gives users a way to notice when the story is getting worse.

What changes the view

The next real proof is regular reporting. Not another facility announcement, but numbers that keep showing up after the announcement is old.

If LendSwift starts producing regular facility-level reporting and Slope turns from a transaction headline into a performance record, the thesis gets stronger. If USD3/sUSD3 capital stays after JANE rewards normalize, stronger still. If reporting stays thin, the product remains harder to underwrite no matter how clean the liability layer looks.

Final take

3Jane is not a better Aave. It is a bet that private credit can be funded through crypto-native liabilities without hiding the loan book behind yield.

The liability side is already programmable enough to take seriously: USD3, sUSD3, JANE, contracts, liquidity incentives, DeFi routes, live funding surfaces. The unresolved part is the asset side: repayments, losses, redemptions, and reporting when emissions stop doing the talking.

The decision-grade read is straightforward: 3Jane has built enough infrastructure to make the credit thesis worth taking seriously, but not enough public credit history to make the loan book underwritable yet.

The liability is programmable already. What still has to become readable is the credit behind it.