3Jane Docs | Protocol Global Config
Shared controls that shape behavior across products.
Global configuration contains parameters that affect more than one page or facility. These values can include supply caps, supported assets, tranche constraints, fee settings, timing controls and other risk limits. Integrators should treat configuration as state, not documentation constants.
Why global config matters
A deposit page can look unchanged while a cap, fee or supported-asset list has changed. Reading the current config prevents integrations from assuming historical behavior and helps users distinguish product mechanics from temporary limits.
Configuration categories
Useful categories include capacity, asset eligibility, tranche relationships, economic fees, timing, access controls and emergency controls. The exact storage and governance path depends on the deployed contracts.
| Category | Examples |
|---|---|
| Capacity | Supply / facility caps |
| Assets | Supported tokens and margin assets |
| Tranches | Senior / junior constraints |
| Economics | Fees and allocation rules |
| Timing | Epochs, cooldowns, deadlines |
| Safety | Pauses, limits, emergency controls |
For users
Before a large action, verify live limits and fees. A transaction can fail because a cap was reached between page load and confirmation. If the interface and documentation disagree on a mutable value, the current deployed state controls the transaction.
For developers
Read configuration from contracts or official deployment data where possible. Avoid hardcoding mutable values into frontends, analytics or automation. When caching is necessary, use explicit refresh intervals and fail safely if the value cannot be refreshed.
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.

