3Jane Docs | Protocol Architecture
How onchain capital and offchain credit processes connect.
3Jane architecture spans onchain vault and token logic, protocol configuration, credit facilities, offchain underwriting and servicing, and external data or liquidity integrations. Understanding those boundaries is essential for audits, integrations and incident analysis.
Capital layer
USDC enters through supplier flows and is represented by the USD3 / sUSD3 tranche system. The capital layer tracks supplier claims, yield accrual and liquidity while routing deployable capital toward configured credit exposure.
Credit layer
CCL and FCC use different underwriting and servicing paths. Some credit decisions depend on offchain data and legal structures, while the resulting capital movements and supplier claims are represented onchain. Integrators should not assume every credit-state transition originates from a purely onchain oracle.
LCC and incentives
LCC adds contingent-capital state—margin, promises, calls and funding performance. JANE liquidity mining adds a separate reward-accounting layer that can reference eligible positions without changing the underlying credit risk of those positions.
Integration boundaries
External dependencies can include stablecoins, Ethereum RPC infrastructure, credit-data providers, idle-liquidity venues and wallet software. Architecture reviews should list what happens if each dependency becomes unavailable, stale or inconsistent.
| Boundary | Failure question |
|---|---|
| RPC / wallet | Can users read state and submit safely? |
| Stablecoin | What if peg or transfer behavior changes? |
| Credit data | What if data is missing or stale? |
| External venue | What if liquidity cannot be withdrawn? |
| Offchain servicing | How are delays or disputes handled? |
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.

