Timelock dan Eksekusi
Upgrade yang aman
Timelock dan Eksekusi adalah pelajaran Web3 & DApp Development Fundamentals gratis di CoddyKit. Ini adalah pelajaran 4 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Web3 & DApp Development Fundamentals, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Web3 & DApp Development Fundamentals mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Why Timelocks Exist
A timelock is a mandatory delay between when a proposal passes and when it executes.
It protects users by giving them time to react to changes they disagree with — for example, withdrawing funds before a risky upgrade.
The TimelockController
OpenZeppelin's TimelockController is a contract that schedules, delays, and then executes operations.
The Governor proposes and queues actions into the timelock, which actually owns the protocol's admin rights.
contract Timelock is TimelockController {
constructor(uint minDelay, address[] proposers, address[] executors)
TimelockController(minDelay, proposers, executors, msg.sender) {}
}Schedule, Wait, Execute
Operations flow through three steps:
- schedule — queue the action with a delay
- wait — the minDelay must elapse
- execute — run the action after the delay
timelock.schedule(target, value, data, predecessor, salt, delay);
// ... wait minDelay ...
timelock.execute(target, value, data, predecessor, salt);The minDelay Parameter
The minDelay sets how long every scheduled operation must wait. Common values range from 1 to 7 days.
Longer delays mean more safety but slower governance — a deliberate trade-off each DAO must tune.
Roles in the Timelock
The timelock uses access roles:
- PROPOSER — can schedule operations (the Governor)
- EXECUTOR — can run them after the delay
- ADMIN — manages roles (often renounced)
Timelock Owns the Protocol
For governance to be meaningful, the timelock contract should hold the protocol's admin and ownership rights — not any individual.
This ensures every privileged change must pass through the full govern-then-delay pipeline.
protocol.transferOwnership(
address(timelock)
);Defense Against Malicious Proposals
If an attacker sneaks a harmful proposal through voting, the timelock delay is the last line of defense.
The community can spot the queued action and exit or coordinate a response before it executes.
Predecessor and Salt
Each scheduled operation can specify a predecessor (an operation that must run first) and a salt to make its identifier unique.
These let DAOs order dependent operations and avoid hash collisions between similar actions.
Cancelling Operations
A scheduled operation can be cancelled before execution by an address with the canceller role.
This provides an emergency brake if a queued action is found to be dangerous during the delay window.
timelock.cancel(operationId);Upgrades Done Safely
Combining Governor + Timelock + a proxy pattern lets DAOs upgrade contracts safely: vote, queue, delay, then execute the upgrade.
Every step is transparent and reversible up until execution, balancing flexibility with security.
Putting It Together
The timelock enforces a delay between approval and execution, owns the protocol's privileges, and uses roles plus cancellation to keep upgrades safe.
It is the crucial buffer that makes on-chain governance trustworthy.
Quick Check
Test your timelock understanding.
Recap: Timelocks and Execution
You learned that:
- A timelock delays execution after a proposal passes
- TimelockController schedules, waits, then executes
- minDelay tunes the safety vs speed trade-off
- The timelock should own the protocol; roles control access
- Operations can be cancelled during the delay
Course complete! Next course: Layer 2 and Scaling.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Timelock dan Eksekusi” gratis?
Ya — teks lengkap “Timelock dan Eksekusi” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Web3 & DApp Development Fundamentals, upgrade ke CoddyKit PRO. Kursus Web3 & DApp Development Fundamentals mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Timelock dan Eksekusi”?
Upgrade yang aman Kamu berlatih Web3 & DApp Development Fundamentals dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Web3 & DApp Development Fundamentals?
Tidak diperlukan pengalaman sebelumnya. Web3 & DApp Development Fundamentals di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 4 dari 4.
Berapa lama pelajaran “Timelock dan Eksekusi” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Web3 & DApp Development Fundamentals ini?
Ya. Setiap pelajaran Web3 & DApp Development Fundamentals menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Apa Itu DAO
- Token Governance
- Proposal dan Pemungutan Suara
- Timelock dan Eksekusi