Immutable Contract
A smart contract whose code and parameters can never be changed after deployment: no admin key, no upgrades, no one who can alter the rules.
An immutable contract is a smart contract whose code and parameters cannot be changed by anyone after deployment. There is no admin key, no upgrade mechanism, and no governance process that can alter how it behaves. The verified code you can read onchain at launch is exactly what will run for as long as the chain exists.
Immutability matters because many DeFi losses are not hacks at all: they are insiders using legitimate admin powers. An upgradeable proxy lets a deployer swap in new logic, a pausable contract lets someone freeze withdrawals, and an owner-settable fee can be raised to confiscatory levels. An immutable contract removes this entire class of risk, since there is no privileged role to abuse, sell, or compromise. Before trusting any contract, it is worth checking the verified source for owner functions, proxy patterns, and upgrade hooks, because a project can claim decentralization while keeping a master key.
The trade-off is that the lock applies to everyone, including the developers. If a bug ships, it cannot be patched, and if conditions change, the contract cannot adapt, which is why immutable designs suit simple, well-audited primitives with fixed rules rather than complex evolving strategies. Tessera sits at the immutable end of the spectrum: each index vault's basket and parameters are fixed at creation, so no admin can swap assets, change weights, or block redemptions. Immutability shifts the question from whether you trust the team to whether you trust the code. That is a meaningful improvement in verifiability, but it is not a guarantee of safety, and audited code can still contain flaws.