The Foundation's incorporation announcement traces IOTA's origins to 2015 and describes the ambition to support an economy of connected devices. It records the Foundation's establishment in Germany on November 3, 2017 and credits community contributions to its funding. This source explains how the project wanted to organize development. It does not turn the Foundation into the whole network or make every later decision a direct expression of unanimous community preference.

The May 2018 DNB announcement is a useful example of the early institutional story. The bank and IOTA described cooperation to explore distributed-ledger applications and data-related opportunities. An exploration agreement can be meaningful without establishing a production deployment. Readers should preserve that distinction when old partnership announcements are used to imply that a bank, industry, or national economy already depends on the token.

In February 2020, a compromise involving a third-party integration in the Trinity wallet led to thefts. The Foundation's subsequent account described the response, affected users, and the decision to halt the Coordinator before restarting it on March 10. This was not evidence that every base-ledger cryptographic assumption had failed. It was evidence that a wallet dependency could have serious consequences and that the legacy system had an intervention point capable of stopping value transfers.

Both parts belong in the history. Describing the incident only as a chain hack obscures the wallet supply chain; describing it only as a wallet issue obscures the Coordinator's role in the response. A reader evaluating decentralization should ask which actor could interrupt normal operation and why. A reader evaluating wallet safety should examine dependencies and key handling. Those investigations overlap, but they address different control surfaces.

The April 2021 community-treasury announcement records the launch of Chrysalis and discusses genesis validation and unclaimed assets. It shows that a network migration involves more than replacing a technical term in documentation. Balances, account access, software support, and decisions about resources can all become governance questions. The community was asked to examine the state being carried forward rather than merely accept a fresh marketing description.

Stronghold's 2022 stable-release announcement describes a separate effort to improve the handling of sensitive material through a security-focused software component. This is part of the operational history, but a key-management library cannot guarantee that an entire application is safe. Its value depends on how it is integrated, maintained, and used. The distinction keeps a concrete engineering response visible without turning a product release into an assurance against every future compromise.

The Stardust announcement introduced a changed tokenomics plan and discontinued the proposed Assembly token path. It connected additional resources with ecosystem development, making funding part of the architecture's next stage. Existing holders therefore faced an economic as well as a technical change. A description that carries the old fixed-supply story forward unchanged would miss the substance of the decision and the reason it became controversial.

The Foundation's supply repository records the October 4, 2023 transition and provides the corresponding supply data. Such a record is preferable to relying on a historical exchange page that may preserve an obsolete number. It also illustrates the limits of a single supply statistic: issuance schedules, circulating balances, allocations, and lockups answer different questions. A nominal supply change does not by itself reveal whether funded projects deliver useful results.

The November 2024 Rebased proposal replaced the earlier development path with a Move-based architecture and delegated proof of stake. Its discussion makes clear that this was a strategic choice, not simply the final release of every earlier Tangle design promise. Participants argued about readiness, opportunity cost, and the loss of distinctive features. The same upgrade could look like overdue pragmatism to one holder and abandonment of the original research direction to another.

The published voting result reported 98.37 percent support among cast votes, with 7.52 percent participation under the stated measure. Both figures matter. Reporting only the larger percentage would misleadingly imply support from almost every tokenholder. A strongly favorable result within the participating electorate can authorize a process under its rules while still leaving unanswered why most eligible weight did not participate or how dissenting users evaluated their alternatives.

The May 5, 2025 announcement confirmed that Rebased was live. It introduced an operating Move-based network rather than another indefinite research roadmap. Earlier migration guidance described preserving existing balances and moving users toward updated tools, not requiring an unrelated third-party token swap. For historical clarity, the IOTA name spans this migration, but a transaction's behavior must be understood under the architecture and software in use at the time.

The genesis-validator announcement describes the participants involved in bringing up the new system. That launch set should not be confused with every aspirational maximum in an architecture document. A network can plan for a broader committee while initially relying on a smaller group. The relevant evidence for decentralization is who actually operates validators, how stake and admission work, and how those conditions evolve after launch.

Move treats resources and their permitted operations as explicit parts of the programming model. IOTA's explanation emphasizes the relationship between assets, ownership, and checks enforced by the language. That can help prevent particular classes of accidental duplication or misuse, but a well-typed contract can still implement an economically harmful rule. Language safety and the desirability of a lending, trading, or identity application are separate questions.

The Rebased technical account explains the object-oriented execution model and the role of validator consensus. The important comparison with old IOTA descriptions is architectural: this is a programmable proof-of-stake platform with fees and validator economics. It should not be introduced to a newcomer solely as a feeless Tangle in which each user validates earlier transactions. That description belongs to an earlier period and cannot explain the current system's operating responsibilities.

The validator-committee documentation explains how the active participants and voting power are formed. Stake is part of the security mechanism, so an account of decentralization needs more than a raw validator count. Common operators, concentrated delegated stake, infrastructure dependencies, and the ability to enter or remain in the committee all matter. A list of validator names is useful evidence, but it is not a complete map of independent control.

The staking-reward documentation describes epoch-based accounting and validator-related reward conditions. Delegating supports the consensus system while exposing the user to the token's economic and operational setting. It is not a promise that a stated reward rate will offset every other risk or remain fixed. When comparing providers, the useful questions include commission, performance, applicable rules, and whether the user's chosen interface explains the conditions for moving or withdrawing stake.

The Foundation's 2026 reporting records Starfish activation on April 23. The later technical explanation identifies mainnet release v1.21.1 and protocol version 24 as the enabling release. This means that describing the network as Rebased with its original Mysticeti consensus alone is already incomplete. Network history needs versioned descriptions: the Move migration and the subsequent consensus revision solve different problems and happened at different times.

Sebastian Mueller's technical explanation focuses on dissemination: validators need the information required for agreement to arrive reliably. Starfish separates headers from payload and uses erasure-coded fragments with availability acknowledgments, while its pacemaker constrains round progress. The intended benefit concerns robustness under delayed or uneven communication, not a magical absence of outages. The source also discusses bandwidth and latency tradeoffs, which should remain visible beside performance claims.

The January 2026 manifesto presents international trade, data, identity, and finance as the next focus. It describes initiatives including TWIN as part of a strategy to connect real-world processes with the network. This is an official vision statement with ambitious projections. The size of world trade is not a forecast of IOTA's revenue, transaction fees, or token value, and a blockchain record cannot independently verify every fact about physical goods.

The February 2026 account of trade-related work describes trials and practical implementation tasks. It helps distinguish a program's development stages from a claim that an entire government has migrated its trade systems. Integrating public and commercial organizations requires software, process changes, and durable agreements. Even when a network component is live, the surrounding institutional workflow can still be under trial or limited to a particular corridor.

The July 2026 progress update describes additional network hardening and work on transaction flow, including items still awaiting public-network testing. These distinctions are important. Completing development or validating an idea locally is not the same as activating it for users. A release history should identify where a feature is running rather than allowing every research milestone to appear as a production guarantee.

The same update links technical work with trade-oriented implementation. This gives readers a way to examine the current strategy through deliverables: maintained tooling, functioning integrations, and evidence of repeated use. A chain can achieve faster consensus while an application still struggles with onboarding or data quality. The value of an engineering improvement therefore depends partly on whether the people and institutions using the network can turn it into a dependable workflow.