Web3 & DApp Development Fundamentals · レッスン

定数と不変値

Gas効率の高い値

「定数と不変値」はCoddyKit上の無料Web3 & DApp Development Fundamentalsレッスンです。これはレッスン4/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはWeb3 & DApp Development Fundamentals学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Web3 & DApp Development Fundamentalsコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Fixed Values Save Gas

Some values never change after a contract is deployed. For these, Solidity offers constant and immutable keywords that store the value in the contract bytecode instead of expensive storage slots.

Using them reduces gas and signals intent to readers.

Declaring Constants

A constant must be assigned at the point of declaration and known at compile time. Its value can never change.

By convention constants use UPPER_CASE names.

<code>uint256 public constant MAX_SUPPLY = 1000000;
string public constant NAME = 'MyToken';</code>

How Constants Work

A constant does not occupy a storage slot. The compiler inlines its value everywhere it is used, so reading it costs almost nothing.

This makes constants ideal for configuration like decimals, caps, and fixed fees.

<code>uint8 public constant DECIMALS = 18;

function unit() public pure returns (uint256) {
    return 10 ** DECIMALS; // inlined at compile time
}</code>

Declaring Immutables

An immutable variable is set once, either at declaration or in the constructor, and then can never change.

Unlike constants, its value can depend on runtime data such as deployment arguments.

<code>address public immutable owner;

constructor() {
    owner = msg.sender; // set at deploy time
}</code>

Constant vs Immutable

The key difference is when the value is fixed:

constant - fixed at compile time, must be a literal expression
immutable - fixed at deploy time, can use constructor inputs

Both are stored in bytecode, not in storage slots.

Immutable with Constructor Args

Immutables shine when each deployment needs different fixed parameters, like a token's total supply or an associated contract address.

<code>uint256 public immutable cap;

constructor(uint256 _cap) {
    cap = _cap; // unique per deployment
}</code>

Gas Savings

Reading a regular state variable requires an SLOAD (storage read), which is costly. Constants and immutables are read directly from bytecode, which is far cheaper.

Converting frequently-read fixed config to constant/immutable is an easy optimization.

<code>// Expensive: storage read each call
uint256 public feeStorage = 100;

// Cheap: read from bytecode
uint256 public constant FEE = 100;</code>

What Cannot Be Constant

A constant cannot depend on anything computed at runtime. Values like block.timestamp, msg.sender, or storage reads are forbidden for constants.

For those, use immutable instead.

<code>// ERROR: not compile-time known
// uint256 constant T = block.timestamp;

// OK as immutable
uint256 immutable deployedAt;
constructor() { deployedAt = block.timestamp; }</code>

Immutables Are Read-Only

After the constructor finishes, an immutable can never be reassigned. Any attempt to write to it outside the constructor is a compile error.

<code>address public immutable factory;
constructor(address f) { factory = f; }

function change(address x) public {
    // factory = x; // ERROR: cannot assign
}</code>

Common Use Cases

Typical patterns:

constant for token decimals, max supply caps, and fixed fee rates
immutable for the owner, deployment timestamp, and linked contract addresses

Both improve clarity and reduce gas compared to mutable state.

<code>uint8 public constant DECIMALS = 18;
address public immutable deployer;
constructor() { deployer = msg.sender; }</code>

Naming Convention

By widespread convention, constant names are written in UPPER_SNAKE_CASE, while immutable names often use normal camelCase or a leading underscore for constructor params.

Consistent naming makes audits faster.

<code>uint256 public constant MAX_HOLDERS = 500;
address public immutable treasury;</code>

Quick Check

Test your understanding of constants and immutables.

Recap

You learned about gas-efficient fixed values:

constant - compile-time literal, inlined into bytecode, UPPER_CASE
immutable - set once at deploy time (often in the constructor), then read-only
Both avoid expensive storage reads (SLOAD)

Use constants for known literals and immutables for per-deployment configuration.

よくある質問

「定数と不変値」レッスンは無料ですか？

はい。「定数と不変値」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Web3 & DApp Development Fundamentalsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Web3 & DApp Development Fundamentalsコースには全4レッスンが含まれています。

「定数と不変値」で何を学びますか？

Gas効率の高い値ブラウザで直接実行するハンズオンコードでWeb3 & DApp Development Fundamentalsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Web3 & DApp Development Fundamentalsを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのWeb3 & DApp Development Fundamentalsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン4/4です。

「定数と不変値」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このWeb3 & DApp Development Fundamentalsレッスンでコードを書いて実行できますか？

はい。すべてのWeb3 & DApp Development Fundamentalsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Web3 & DApp Development Fundamentalsに戻る