<h1>Smart Contract Upgradability</h1>
Smart contract upgradability는 배포된 contract의 behavior를 full redeploy 없이 발전시킬 수 있게 하여, state와 external interactions를 보존합니다. 이는 proxy-based architecture와 rigorous governance에 의존합니다.
Smart contract upgradability는 배포된 contract가 저장된 state를 잃거나 진행 중인 interactions를 중단하지 않고 underlying logic의 변경 사항을 받을 수 있는 capability입니다. 이는 일반적으로 storage를 logic과 분리하고 proxy와 같은 upgradeable layer를 통해 calls를 라우팅함으로써 달성됩니다. Proxy는 모든 state를 저장하며, delegation calls는 implementation contract의 logic을 실행합니다. Upgradeable pattern에는 transparent proxies와 UUPS가 포함되며, 종종 OpenZeppelin Upgrades와 같은 framework로 구현됩니다. 주요 고려 사항은 storage layout 보존, constructor 대신 safe initialization 보장, 그리고 upgrades를 위한 robust access control 및 governance 구현입니다. Security risk에는 admin key compromise, upgrade vetos, misconfiguration 등이 있습니다. Verification 및 testing이 필수적이며, formal verification은 upgrade mechanism 자체라기보다는 correctness discipline으로 사용됩니다. Practical guidance에는 upgrade path 감사, canary upgrade 리허설, storage compatibility 및 initialization safety를 강제하는 확립된 toolchain 사용 등이 포함됩니다.
graph LR
Center["<h1>Smart Contract Upgradability</h1>"]:::main
Rel_smart_contract_wallets["smart-contract-wallets"]:::related -.-> Center
click Rel_smart_contract_wallets "/terms/smart-contract-wallets"
Rel_smart_contract_security_auditing["smart-contract-security-auditing"]:::related -.-> Center
click Rel_smart_contract_security_auditing "/terms/smart-contract-security-auditing"
Rel_smart_contract_exploits["smart-contract-exploits"]:::related -.-> Center
click Rel_smart_contract_exploits "/terms/smart-contract-exploits"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧒 5살도 이해할 수 있게 설명
Generated ELI5 content
🤓 Expert Deep Dive
Generated expert content
❓ 자주 묻는 질문
Why is smart contract upgradability important?
It enables security patches and feature updates without breaking existing state or user interactions.
What are common upgrade patterns?
Proxy based patterns such as Transparent Proxy and UUPS, with storage preserved in the proxy and logic in the implementation. Standards like EIP 1967 guide slot layout.
What are main risks?
Admin key compromise, storage layout mismatch, upgrade vetting failures, and governance risks can lead to breaches or broken state.
How can I upgrade securely?
Use battle tested frameworks like OpenZeppelin Upgrades, perform thorough testing, adopt timelocks or multisig governance, and validate storage compatibility.
How does initialization differ from constructors?
Upgradeable contracts use initializer functions to set up state since constructors execute only on deployment and do not run after upgrades.
Is formal verification required for upgrades?
Formal verification helps establish correctness but is not required for upgrading; it complements testing and review.