3Jane USD3

3Jane USD3: A Credit-Backed Yieldcoin Built Around Unsecured USDC Lending

USD3 is the senior supplier token in 3Jane’s Ethereum-based credit market. Its yield depends on a pool of credit lines, idle-capital deployment through Aave, and the protocol’s ability to assess and recover unsecured loans.

What 3Jane is trying to build

3Jane describes itself as a credit-based money market for Ethereum rather than a conventional overcollateralized lending pool. Its stated aim is to extend USDC credit against a borrower’s verifiable crypto assets, bank and brokerage information, credit data, and future cash flows. The protocol is designed for traders, yield farmers, fintech lenders, businesses, and other cryptonative users that may have repayment capacity without wanting to lock equivalent onchain collateral.

The project’s own materials frame this as a peer-to-pool model. Suppliers provide the capital, while approved merchants draw variable USDC credit lines. The core product therefore combines an onchain market with offchain underwriting and repayment enforcement. That combination is central to understanding USD3: the token is not simply backed by a reserve of short-term government securities or by excess crypto collateral.

USD3’s role in the system

USD3 is described in the whitepaper as a stablecoin-denominated ERC-4626 yieldcoin minted when users deposit USDC. It represents the senior supplier position in the pool and has a senior claim on payments generated by outstanding credit lines. The project says USD3 is intended to have withdrawal liquidity based on available market reserves, but that is a protocol design objective rather than a guarantee that every holder can exit immediately during stress.

Users may also stake USD3 to receive sUSD3, a separate ERC-4626 position that receives levered exposure to pool returns while absorbing first losses from defaults after recoveries. The whitepaper assigns an 85 percent pool weight to USD3 and 15 percent to sUSD3 in its illustrated rate framework. This makes USD3 the more senior tranche, but seniority does not eliminate credit, liquidity, smart-contract, or recovery risk.

How the credit market works

The protocol’s stated merchant flow begins with wallet ownership verification and the connection of bank or other financial accounts. 3Jane’s credit underwriting algorithm, called 3CA, uses a combination of onchain activity, DeFi and exchange positions, bank information, cash flows, and external credit scores to determine a credit-line size, a default-risk premium, and a repayment rate. The resulting terms are posted to contracts alongside proofs and signatures described by the project as zkTLS-backed evidence.

A borrower can draw USDC up to the approved line and must make periodic repayments. The whitepaper describes the facility as a purchase of future receivables, with repayment requirements linked to principal, interest components, and the borrower’s measured appreciation or cash-flow profile. If a borrower becomes delinquent, the protocol can apply a late premium, reduce the borrower’s future credit score, and trigger a non-performing credit-line auction.

Default handling is an offchain dependency

Because the model is unsecured or lightly secured, recovery is a practical dependency rather than a secondary detail. 3Jane’s proposed process uses an onchain Dutch auction in which licensed United States collections agencies may bid for the right to pursue a delinquent account on a contingency basis. The project also describes a write-down model for non-performing credit lines that estimates both loss probability and possible recovery over time.

This design means protocol solvency depends on more than smart-contract accounting. It also depends on the quality of underwriting, the accuracy and availability of external financial data, the willingness and legal ability of collection partners to pursue debts, and the recoverability of loans after default. The whitepaper presents these mechanisms as part of the protocol architecture; the reviewed materials do not independently establish their historical recovery performance.

The Ethereum and Aave components

The whitepaper says the core money market is based on a single-market deployment of Morpho Blue with modifications that replace conventional collateral positions with a credit-line contract and credit-slashing logic. It also says idle USDC is deposited into Aave V3’s USDC market, with the resulting aUSDC position redeposited into the core market until borrowers draw funds. A USD3 holder is therefore exposed to both 3Jane’s contracts and the external money-market infrastructure used for idle liquidity.

The public contract repository is presented as a fork or deployment codebase associated with Morpho Blue and contains source, documentation, audit-scope material, and testing directories. Repository visibility is useful for review, but code availability alone does not prove that deployed contracts match the latest source, that all components have been audited, or that operational permissions are minimized.

Governance, control, and token boundaries

USD3’s documented function is economic rather than governance-oriented: it is the senior yield-bearing supplier claim. The reviewed whitepaper does not describe USD3 as a voting token or identify a separate governance process that gives USD3 holders control over upgrades. It does state that several risk parameters, including elements of the interest-rate model, may be adjusted as credit conditions change. The precise authority, timelock structure, emergency controls, and upgrade process should therefore be checked directly in deployed contracts and current documentation before treating the system as governance-minimized.

The project website currently presents USD3 as a credit-backed yieldcoin and distinguishes it from sUSD3, while also marketing capital access for fintech lenders and cryptonative borrowers. Those descriptions explain the intended market, but they should not be read as independent evidence of adoption, repayment quality, or realized yield.

What users should verify

Before relying on USD3, users should verify the Ethereum contract address, the current mint and withdrawal rules, the composition and concentration of outstanding credit lines, the treatment of delinquent loans, and the permissions held by administrators or underwriters. They should also confirm how much capital is idle in Aave, how much is drawn by borrowers, and whether withdrawals are limited by reserves or cooldowns.

The main analytical distinction is between the token’s accounting seniority and actual economic safety. USD3 may stand ahead of sUSD3 in the tranche structure, but losses can still arise from borrower defaults, weak recoveries, valuation errors, contract exploits, Aave dependency, data-provider failures, or a rush to withdraw. The reviewed sources provide a detailed proposed mechanism, but not enough independently verified history to establish how the design performs across a full credit cycle.

Key takeaways

• USD3 is the senior supplier-side ERC-4626 yieldcoin in 3Jane’s credit market.
• Its intended return comes from borrower credit lines and, for idle capital, Aave V3 USDC exposure.
• sUSD3 is the subordinate position described as absorbing first losses in exchange for levered pool exposure.
• 3Jane’s underwriting depends on onchain data, financial-account information, external credit data, and project-operated risk models.
• Default recovery depends partly on offchain collections agencies and legal enforcement, not only on smart contracts.
• The reviewed materials do not clearly document a USD3 voting role or a complete public description of upgrade and emergency-control authority.

Risks and open questions

• Unsecured and undercollateralized borrower defaults could reduce the value or liquidity of the supplier pool.
• The accuracy, availability, and privacy handling of bank, exchange, credit-score, and other offchain data are material dependencies.
• Recovery assumptions may fail if collections agencies cannot recover delinquent balances or if legal enforcement is slow or unavailable.
• Aave, Morpho-derived contracts, 3Jane-specific modules, oracle or proof systems, and administrative permissions create layered smart-contract and operational risk.
• The public materials reviewed do not establish a long, independently verified history of realized yield, defaults, recoveries, or withdrawal performance.
• The exact governance, upgrade, and emergency-control structure should be verified against deployed contracts and current documentation.