Live configuration

Contract addresses and lending settings depend on the network and deployment. Use deployed contract views and the lending app to check values before a transaction. Read values on the same network as the intended transaction. Documentation explains the rules and labels illustrative examples.

​

Where to find values

​

Configuration is not deployment proof

A configuration file can contain disabled markets or listings that have no usable market on-chain. Check both the deployed market and the account’s spoke listing before treating an asset as available. This distinction matters for Spiko entries in the mainnet configuration: the files contain disabled market definitions. Their presence in configuration does not establish available collateral. Follow the deployed views for availability. Market presence alone is insufficient for new supply or borrowing: the hub must be active, and the account’s spoke listing must allow the action. Pause flags, caps, prices, and liquidity can still prevent it. Withdrawal and repayment follow their own exit rules. Spoke configuration keys are also not necessarily deployed spoke IDs. Use the published deployment registry or contract views when identifying a spoke.

​

Before confirming a transaction

Confirm the wallet network, account, spoke, and asset. Review the projected balances and limits in the lending app. Rates, prices, and available liquidity can change between that review and execution; the transaction must pass the contract’s checks at execution. If a balance, price, or risk value is unavailable, keep it unresolved. A missing value is not zero, and a maximum displayed health factor alone does not prove that no debt remains.