0Pricing
Web3 & DApp Development Fundamentals · Pelajaran

Ekstensi Token

Pausable, Burnable

Ekstensi Token adalah pelajaran Web3 & DApp Development Fundamentals gratis di CoddyKit. Ini adalah pelajaran 3 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.

Extending Tokens

The base ERC-20 only handles transfers and approvals. OpenZeppelin provides extensions that add features by inheritance:

  • Pausable — freeze transfers in emergencies.
  • Burnable — let holders destroy tokens.
  • Capped — enforce a maximum supply.
  • Permit — gasless approvals via signatures.

Combining via Inheritance

You mix extensions by listing multiple base contracts:

import "@openzeppelin/contracts/token/ERC20/ERC20.sol"; import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Burnable.sol"; contract MyToken is ERC20, ERC20Burnable { constructor() ERC20("MyToken", "MTK") {} }
import "@openzeppelin/contracts/token/ERC20/ERC20.sol";
import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Burnable.sol";

contract MyToken is ERC20, ERC20Burnable {
    constructor() ERC20("MyToken", "MTK") {}
}

Burnable Tokens

ERC20Burnable adds two functions:

  • burn(amount) — destroys the caller's own tokens.
  • burnFrom(account, amount) — burns from an account that approved you.

Burning reduces totalSupply, which can be used for deflationary mechanics.

// holder destroys their tokens
token.burn(ethers.parseEther("100"));

Pausable Tokens

ERC20Pausable lets an authorized account halt all transfers — useful during a security incident:

import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Pausable.sol"; import "@openzeppelin/contracts/access/Ownable.sol"; contract MyToken is ERC20, ERC20Pausable, Ownable { function pause() public onlyOwner { _pause(); } function unpause() public onlyOwner { _unpause(); } }
import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Pausable.sol";
import "@openzeppelin/contracts/access/Ownable.sol";

contract MyToken is ERC20, ERC20Pausable, Ownable {
    function pause() public onlyOwner { _pause(); }
    function unpause() public onlyOwner { _unpause(); }
}

How Pause Works

When paused, transfers revert with EnforcedPause. The Pausable extension hooks into the token's internal transfer logic, so transfer, transferFrom, mint, and burn are all blocked until unpause is called.

Use pausing sparingly — it centralizes control.

Resolving Function Conflicts

When two parents define the same internal hook, Solidity requires you to override it and specify the order:

function _update(address from, address to, uint256 value) internal override(ERC20, ERC20Pausable) { super._update(from, to, value); }

This tells the compiler how to linearize the inheritance.

function _update(address from, address to, uint256 value)
    internal override(ERC20, ERC20Pausable) {
    super._update(from, to, value);
}

Capped Supply

ERC20Capped enforces a hard maximum supply set at deployment:

import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Capped.sol"; contract MyToken is ERC20Capped { constructor() ERC20("MyToken", "MTK") ERC20Capped(1000000 * 10 ** 18) {} }

Any mint that would exceed the cap reverts.

import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Capped.sol";

contract MyToken is ERC20Capped {
    constructor()
        ERC20("MyToken", "MTK")
        ERC20Capped(1000000 * 10 ** 18) {}
}

Gasless Approvals with Permit

ERC20Permit lets users approve spending with an off-chain signature instead of an on-chain approve transaction:

import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Permit.sol"; contract MyToken is ERC20, ERC20Permit { constructor() ERC20("MyToken", "MTK") ERC20Permit("MyToken") {} }

This improves UX by removing one transaction.

import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Permit.sol";

contract MyToken is ERC20, ERC20Permit {
    constructor()
        ERC20("MyToken", "MTK")
        ERC20Permit("MyToken") {}
}

Extensions for NFTs Too

ERC-721 has parallel extensions:

  • ERC721Enumerable — iterate over all tokens.
  • ERC721URIStorage — per-token metadata URIs.
  • ERC721Burnable / ERC721Pausable — same ideas as ERC-20.

The pattern of composing through inheritance is the same.

Compose Only What You Need

Each extension adds code, gas cost, and surface area. Include only the features your token actually requires:

  • Fewer extensions mean cheaper deployment and a smaller attack surface.
  • Document why each extension is present.

Votes Extension

ERC20Votes tracks historical voting power by snapshotting balances at each block, enabling on-chain governance:

import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Votes.sol";

Holders can delegate their votes, and proposals can query past voting power to prevent flash-loan manipulation.

import "@openzeppelin/contracts/token/ERC20/extensions/ERC20Votes.sol";

Quick Check

Test your understanding of token extensions.

Recap

You learned to compose token features with extensions.

  • Extensions add behavior by multiple inheritance.
  • Burnable destroys tokens; Capped enforces max supply.
  • Pausable freezes transfers in emergencies.
  • Permit enables gasless, signature-based approvals.
  • Resolve hook conflicts by overriding (e.g. _update) and include only what you need.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Ekstensi Token” gratis?

Ya — teks lengkap “Ekstensi Token” 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 “Ekstensi Token”?

Pausable, Burnable 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 3 dari 4.

Berapa lama pelajaran “Ekstensi Token” 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

  1. Mengapa OpenZeppelin
  2. Kontrol Akses
  3. Ekstensi Token
  4. Kontrak yang Dapat Di-upgrade
← Kembali ke Web3 & DApp Development Fundamentals