3Jane Docs | Integrations
External systems that extend protocol functionality.
3Jane depends on more than core contracts. Wallets and Ethereum infrastructure carry transactions; USDC is the primary supplied asset; credit underwriting can use external data and scoring; and idle liquidity or market integrations can affect capital efficiency. Each dependency should be evaluated as its own risk boundary.
Wallet and network integration
Frontends should verify Ethereum chain context before enabling actions, display the exact asset being approved and avoid silently switching networks. RPC failures should degrade read-only features safely rather than produce stale transaction assumptions.
Credit-data integration
Underwriting can use onchain credit scoring and verified offchain financial information. Data provenance, freshness, user consent and failure handling matter because missing or stale data can change an underwriting result.
Liquidity integration
Idle USDC can be deployed to external liquidity venues under protocol rules. This adds counterparty and smart-contract dependencies beyond the credit facilities themselves, so integrations should be considered in both yield and risk analysis.
Integration checklist
For each dependency document the contract or API boundary, data freshness, failure mode, upgrade policy, permissions and fallback behavior. A feature is not truly integrated until the system has a defined response to the dependency failing.
| Integration | Key question |
|---|---|
| Wallet / RPC | Can state and chain ID be trusted? |
| USDC | Is the canonical token used? |
| Credit score | How fresh and explainable is the signal? |
| Offchain verification | What happens if data cannot be verified? |
| Liquidity venue | Can capital be withdrawn under stress? |
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.

