bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 2쪽 중 2쪽
enefit of using EVM/Solidity is its sheer
amount of resources from years of development. The IOTA Smart Contracts implementation is
fully compatible with these resources, allowing to leverage all existing EVM developer tools for
developing on the IOTA EVM. Any contracts previously written can be deployed on IOTA Smart
Contracts without modification. Note that while EVM has become a standard for smart contract
execution on L2s, it is not inherently designed for the unique features and capabilities of L1s like
Move smart contracts. Move, with its focus on asset safety, resource management, and formal
verification, offers a fundamentally different approach at the L1 level.
By combining these unique capabilities, IOTA delivers a resilient and future-ready infrastructure
for diverse industries, from decentralized finance to supply chain management and beyond,
all while setting a new standard for security, efficiency, and scalability in distributed ledger
technology.
3.1. Object-Centric Design
The fundamental unit of storage on IOTA is the object. Unlike many blockchains that focus on
accounts containing key-value stores, IOTA’s storage model centers around objects, each of
which is addressable on-chain by a unique ID. In IOTA, a smart contract is an object known as a
package, and these smart contracts interact with other objects on the IOTA network:
– IOTA Move Package: A collection of IOTA Move bytecode modules. Each module has a
unique name within its containing package. The combination of the package’s on-chain ID
and the module name uniquely identifies the module. When you publish smart contracts
on IOTA, the package is the unit of publication. Once published, a package object can only
be upgraded with the appropriate permissions. A package object may depend on other
package objects previously published on IOTA.
– IOTA Move Object: Typed data managed by a specific IOTA Move module from an IOTA
Move package. Each object value is a struct with fields that can include primitive types
(such as integers and addresses), other objects, and non-object structs.
Transactions in IOTA take objects as input, modify these inputs, and produce new or updated
objects as output. Each object records the hash of the last transaction that produced it as an
output. This relationship between objects and transactions can be represented as a directed
acyclic graph (DAG), where:
– Nodes represent transactions.
– Directed edges connect transaction A to transaction B if an output object of A is used as an
input for B. These edges are labeled with the reference of the object, specifying the exact
version created by A and used by B.
12
IOTA Technical and Tokenomics Whitepaper 30 May 2025
The root of this DAG is a genesis transaction that takes no inputs and produces the objects that
exist in the system’s initial state. The DAG can be extended by identifying mutable transaction
outputs that have not been consumed and issuing a new transaction that takes these outputs
(and optionally, immutable transaction outputs) as inputs.
The set of objects available as inputs to a transaction are the live objects, and the global state
maintained by IOTA consists of all such objects. The live objects for a specific IOTA address A
include all objects owned by A, along with all shared and immutable objects in the system.
When this DAG encompasses all committed transactions, it forms a complete and cryptograph-
ically auditable view of the system’s state and history. Additionally, you can construct a DAG
of the relevant history for a subset of transactions or objects, such as those owned by a single
address.
Every object on the IOTA network has an ownership model that dictates how it can be accessed
and used within transactions. The ownership type of an object determines who has the authority
to interact with it and how it can be manipulated. In IOTA, objects can be:
– Shared: Accessible for reads and writes by any transaction
– Owned: Accessible for reads and writes by transactions signed by their owner.
Both shared and owned objects offer unique advantages and trade-offs that should be carefully
considered when designing applications. Transactions involving only owned objects benefit
from very low latency to finality because they bypass consensus. However, only the owner
can access these objects, which complicates processes requiring interaction between multi-
ple parties. On the other hand, transactions that involve shared objects require consensus to
manage reads and writes, potentially leading to slightly higher gas costs and increased latency.
When multiple shared objects or particularly popular objects are accessed, contention may
further increase latency.
Below are examples of types of objects and their ownership in IOTA:
– Immutable Objects: In IOTA, objects can be either mutable or immutable. Immutable objects
are unique in that they cannot be altered, transferred, or deleted after they are created.
Once an object is made immutable, it has no owner, making it accessible to anyone on the
network.
– Address-Owned Objects: An address-owned object is tied to a specific 32-byte address,
which can either be an account address derived from a particular signature scheme or an
object ID. These objects are exclusively accessible by their owner, meaning no other entity
can interact with them unless ownership is transferred.
– Shared Objects: Shared objects are made accessible to everyone on the network through
13
IOTA Technical and Tokenomics Whitepaper 30 May 2025
the 0x2::transfer::share_object function. Unlike address-owned objects, shared objects
are not restricted to a single owner and can be read or modified by any entity on the
network. This extended accessibility can be advantageous for certain applications, but it
also requires careful consideration of security, especially when sensitive operations are
involved.
3.2. Consensus Mechanism
IOTA employs the Mysticeti consensus mechanism, a cutting-edge protocol designed to ensure
security, scalability, and energy efficiency. Mysticeti operates within a Delegated Proof-of-Stake
(DPoS) framework, where validators are selected based on stake to participate in the consensus
process. This combination of technologies enables IOTA to achieve robust decentralization and
network stability while maintaining high performance and sustainability.
Mysticeti utilizes a Directed Acyclic Graph (DAG) architecture to process transactions in paral-
lel, achieving sub-second finality and supporting a throughput of over 50,000 transactions per
second. Unlike traditional blockchain systems, Mysticeti eliminates explicit block certification
by embedding consensus directly into the DAG structure, significantly reducing computational
overhead and latency. Its leaderless design enhances fault tolerance by ensuring no single entity
controls the process of transaction validation.
The Mysticeti protocol is underpinned by advanced cryptographic techniques, ensuring the
security and integrity of the network. By leveraging the DPoS framework and the innovative
properties of the DAG, IOTA achieves a scalable, efficient, and decentralized infrastructure suit-
able for powering secure, real-world applications across various industries.
3.3. Smart Contracts
IOTA’s baselayer protocol is designed not only as a robust distributed ledger but also as a
flexible foundation that paves the way for additional technical standards and contract-based
protocols. Central to this vision is the Move Virtual Machine (MoveVM), which provides a secure
and resource-oriented programming environment. The MoveVM layer empowers developers
to define and enforce new technical standards through smart contracts, ensuring that proto-
cols built atop the IOTA baselayer can evolve alongside emerging technological and industry
demands.
The IOTA protocol leverages the Move Virtual Machine (MoveVM) and the Move programming
language to enable secure and efficient smart contracts and native asset management. Move’s
resource-oriented programming model ensures strict safeguards for the creation, transfer, and
destruction of digital assets, preventing vulnerabilities such as double-spending and re-entrancy
14
IOTA Technical and Tokenomics Whitepaper 30 May 2025
attacks. This robust model supports the development of advanced decentralized applications
(dApps) and tokenized ecosystems.
IOTA’s ledger natively supports the creation and management of digital assets without relying
on external layers or additional smart contracts. Developers can programmatically mint and
burn assets with custom logic such as conditional transfers, vesting schedules, or compliance
requirements.
Move smart contracts seamlessly interact with native assets, enabling secure and programma-
ble functionalities for decentralized finance (DeFi), NFTs, and other tokenized applications. The
resource-oriented design enforces asset integrity and simplifies complex workflows, ensuring
efficiency and scalability.
IOTA’s combination of Move and native asset capabilities delivers a secure, scalable platform
for creating and managing digital ecosystems with minimal complexity and maximum flexibility.
3.4. Transaction Lifecycle
A high level overview of the transaction lifecycle is depicted and detailed below
– Transaction creation: A user submits a transaction to a full node and signs it with a private
key. The transaction can affect objects owned by the user, as well as shared objects.
– Submission to Validators: The full node sends the transaction to the validator set. They
check if it’s valid and lock the involved “owned objects” to prevent double-spending. After
validation, they send their signature back to the full node.
– Transaction Certificate creation: After collecting responses from a supermajority of vali-
dators, the full node can form a transaction certificate, which includes the transaction and
the validator signatures. This certificate is sent back to all validators.
– Consensus and Execution: The validators verify the certificate transaction validity and
begin the process required for transaction inclusion. If the transaction involves only owned
Validator 1
Validator 2
…
Validator n
Client
1. Make
Transaction
2. Process
Transaction
3. Assemble
Certificate
6. Assemble
Effect Certificate
7 . Checkpoint
Certificate
4. Sequence
Direct Fast Path
5. Process
Certificate
Checks Checks Consensus Execution Checkpoint
15
IOTA Technical and Tokenomics Whitepaper 30 May 2025
objects, IOTA can process and execute it immediately without waiting for consensus
(fast path consensus). Otherwise, the transaction is submitted to IOTA’s consensus and
sequencing modules, and only later executed.
– Effects Certificate: After the transaction is executed, each validator signs off on the effects
of the transaction and sends them back to the full node. The effects of a transaction are
essentially a detailed record of what happened, including objects that were changed,
created, wrapped, unwrapped, or deleted, the amount of gas spent, and the transaction’s
execution status. The full node then gathers these signed effects from a majority of valida-
tors, forming an effects certificate, which guarantees that the transaction is final.
– Checkpoint inclusion: The final stage in a transaction’s life is its inclusion in a checkpoint.
The consensus layer produces a globally agreed-upon ordering of transactions. Validators
take chunks of this ordered list and use them to form checkpoints, containing a list of
transaction digests and the digests of their effects. Once a transaction is included in a
checkpoint, it becomes part of the permanent record on the IOTA network.
16
IOTA Technical and Tokenomics Whitepaper 30 May 2025
Appendix: Total and Circulating Supply
IOTA employs minting and burning mechanisms to dynamically regulate its circulating token
supply. While there is no predefined upper limit on either the total or circulating supply, the
design ensures that supply growth remains, at most, linear over time.
Total Supply Overview
The IOTA network launched (at the Rebase) with an initial total supply of 4,600,000,000 IOTA
tokens. In each epoch—approximately one per day—up to 767,000 IOTA can be newly minted
and distributed among participants. At the same time, every network transaction burns a small
amount of tokens.
Assuming maximum daily issuance and no burning, the total supply could increase by up to
279,955,000 IOTA per 365 epochs (roughly one year), representing a maximum annual growth
rate of 6.1% in the first year. In subsequent years, while the percentage increase will vary due to
supply changes, the absolute annual supply increase remains constant.
Circulating Supply Overview
The circulating supply includes all tokens that are not locked at a given time. At the launch of
the new IOTA mainnet on May 5, 2025, a portion of the initial total supply remained locked, in
accordance with the IOTA Stardust and Tokenomics updates. At launch, the circulating supply
stood at 3,746,223,720 IOTA.
In addition to the minting and burning mechanisms, the circulating supply will increase until
October 2027 due to scheduled token unlocks. From that point onward, total supply and circu -
lating supply will be equal, as all tokens will have been unlocked.
Unlocking Schedule
May 14 – October 1, 2025: Every two weeks, 19,137,719 IOTA will be unlocked, totaling 210,514,906
IOTA by October 1. Including token minting, the maximum circulating supply at that point will be
approximately 4,074,089,626 IOTA.
October 2025 – September 29, 2027: The biweekly unlocking amount reduces to 12,370,411 IOTA,
resulting in an additional 643,261,373 IOTA being unlocked over this period. Including continued
minting, the maximum circulating supply at the end of this period will reach 5,274,192,999 IOTA.
A graph below illustrates the projected maximum total and circulating supply over time. This
trend can be extrapolated beyond 2027, as token issuance continues at a consistent rate.
17
IOTA Technical and Tokenomics Whitepaper 30 May 2025
IOTA Maximum Supply (millions of IOTAs)
Jan Mar May Jul Sep Nov Jan Mar May Jul Sep Nov Jan Mar May Jul Sep Nov Jan Mar May Jul Sep Nov
2025 2026 2027 2028
6,000
5,500
5,000
4,500
4,000
3,500
3,000
Circulating Supply Total Supply프로젝트로 돌아가기