The token swap opened on May 14, 2025, but Vaulta did not start a new blockchain that day. The Foundation explicitly described continuity of the EOS mainnet: applications, accounts, transaction history and infrastructure remained on the existing network. A replaced EOS at a one-for-one ratio. This is different from a migration that asks every application to deploy on a separate chain. An old EOS transaction therefore belongs to Vaulta's historical ledger, even when its original interface still displays the earlier name.

The user FAQ connects A to the previous token's resource and governance functions and says the rebrand retained the existing supply and vesting arrangements. It also describes a swap contract and a time-limited initial period for swaps in both directions. Those operational windows should not be read as permanently available features. A holder must distinguish a native balance, an exchange's internal accounting and an old Ethereum sale token before following any conversion instructions; the common name EOS does not make those instruments interchangeable.

The SEC's September 2019 settlement order describes Block.one's token sale from June 2017 to June 2018 and places the launch of the EOS blockchain on June 14, 2018. It carefully distinguishes the Ethereum ERC-20 instruments sold during fundraising from the later blockchain's native tokens. The order imposed a $24 million civil penalty over the unregistered offering. That legal record is not a blanket regulatory certification for every later EOS or A transaction, nor does a change of branding erase the earlier offering's history.

The relationship between network participants and Block.one remained contested long after launch. In August 2023, the EOS Network Foundation urged eligible claimants to reject a proposed class-action settlement that it considered inadequate. This was advocacy from an interested ecosystem institution, not an independent judicial finding that its preferred outcome was correct. It illustrates why some supporters describe the network as a community rebuilding after disappointment: the dispute concerned commitments, funding and accountability as much as the capabilities of the software.

On December 8, 2021, a block-producer supermajority stopped future vesting associated with Block.one. The Foundation's contemporary account argues that the company had failed to supply expected support. It also distinguishes stopping future releases from seizing tokens already vested or changing the company's private keys. Readers can evaluate that intervention as an assertion of community control while recognizing its institutional power: coordinated producers could change the handling of a disputed future allocation.

The episode is evidence of governance action, not evidence that governance disputes disappear.

The September 21, 2022 activation of Antelope Leap 3.1 gave this separation a technical expression. Producers coordinated a consensus upgrade based on software developed beyond the original EOSIO release line. The Foundation presented the event as independence and renewed responsibility for maintaining the network. It was a change to the rules and implementation of the continuing chain rather than a fresh token sale or replacement genesis. The practical question became who would maintain compatible software and fund future work after the break.

Vaulta's onboarding guide asks users to think in accounts and resources. CPU and NET cover execution and network capacity, while RAM supports persistent state. Applications can arrange resource access for their users, which can make an interaction feel unlike a conventional gas payment. The resource requirement has not vanished merely because a particular screen does not display a fee. Someone still supplies capacity, and applications must manage the costs and availability of the resources their activity consumes.

The system-contract repository separates basic protocol capabilities from policy implemented by privileged contracts. Accounts, permissions and resource quotas sit below mechanisms for token handling, resource markets, producer selection and multisignature actions. This design makes system contracts important objects of study: changing a contract can alter economic behavior without changing the meaning of every transaction in the ledger. Repository documentation also warns that its development branch is not the production release.

Published code is inspectable evidence, but branch contents alone do not prove what a live network has activated.

The protocol overview describes delegated proof of stake, a WASM execution environment and native account permissions with threshold authorization. It also describes a producer supermajority path for protocol upgrades. These features answer different questions: execution determines what contracts do, authorization determines who can act for an account, and producer coordination governs changes to the network. They should not be collapsed into a single claim that the chain is simply fast or secure.

The same overview identifies Spring's licensing terms, which deserve separate attention from general open-source branding.

Spring 1.0 and Savanna activated on September 25, 2024. The upgrade account describes finalizer registration, coordinated multisignature steps and BLS-based finality while preserving compatibility with historical chain data. Its advertised finality improvement is an engineering claim about that consensus design, not a promise that every application, wallet, bridge or exchange settles within the same interval. Application execution, irreversible chain confirmation and a custodial platform's withdrawal policy remain separate stages even when the underlying ledger reaches agreement quickly.

The producer-approved tokenomics package announced on May 31, 2024 set a maximum supply of 2.1 billion EOS and introduced a structured allocation and release schedule. The much-publicized reduction was relative to the previous possible supply ceiling. It did not mean that four fifths of every holder's circulating coins disappeared. Approval, execution and future releases are also different milestones; the announcement described a delayed multisignature execution step. A scarcity narrative needs that accounting context before a reader tries to connect it to market value.

The original proposal explains the allocation choices behind the new ceiling: resource infrastructure, staking incentives, producers and development organizations were assigned different portions. It envisaged rewards funded through allocations and resource-related revenue rather than assuming that all rewards represent outside customer demand. Such budgets can subsidize useful activity, but they are also a distribution policy with beneficiaries and opportunity costs.

A promised reward rate is therefore not a complete explanation of token economics; the origin of the tokens, release schedule and costs borne by participants matter as well.

The March 2025 positioning describes a Web3 banking network for financial applications and institutional use. It connects settlement, identity, interoperability and the exSat relationship to a broader ambition to make digital assets usable in finance. That is the Foundation's strategic case. It does not turn A into a bank deposit, establish that every application is regulated, or make every connected asset a direct claim on an underlying financial instrument. A reader needs the issuer, custody arrangement and legal terms of each product as well as the chain's technical description.

Omnitrove's October 2025 announcement made the business direction more concrete: it proposed a treasury interface connecting wallets, exchanges and banking information for institutional teams. It discussed pilots and an early-2026 release target, with deeper Vaulta integration in later stages. The announcement is evidence of that product plan, not sufficient evidence that every promised integration subsequently shipped. This research did not establish a later production receipt for the full roadmap.

An enterprise dashboard can also aggregate off-chain accounts without placing every operation on Vaulta.

The July 2025 Spring 2 developer preview introduced experimental synchronous contract calls and a dedicated testing environment. Its notice explicitly prohibited treating preview nodes as suitable for mainnet or public testnets. The proposed feature lets one contract obtain a result from another during execution, potentially changing how developers compose applications. An attractive development capability is still not a mainnet activation record.

Preview feedback, a production release and coordinated adoption are separate steps that must be checked before describing the feature as available to ordinary users.

The Omnitrove roadmap proposes A-based staking incentives, reduced fees, participation rewards and future integration with a storage layer. These are possible links between product use and token utility, but the roadmap itself does not demonstrate actual customer demand, token purchases or distributed income. This distinction is central to the investor thesis: a product can be useful without creating the expected degree of demand for a particular token.

Evidence would have to connect implemented pricing and usage to the stated token mechanisms, rather than relying on the existence of the brand alone.

In July 2025, the Foundation announced that it would consolidate EVM support around exSat. Its explanation distinguishes the EVM framework from the particular Vaulta EVM deployment that had begun as EOS EVM. Continuing work on software does not require keeping every instance of that software operational. Equally, withdrawing support for that EVM environment is not the same as terminating the underlying native Vaulta mainnet. Confusing the two can make both historical applications and the network's continuing identity unnecessarily difficult to understand.

A September notice set October 8, 2025 as the end of Foundation infrastructure support for the legacy EVM and described an earlier gas-token transition. It is a dated warning about a specific environment, not a present-day promise of bridge availability or a complete audit of the assets left there. The distinction matters for old balances: an application interface, an RPC service, a bridge and a native account can fail or lose support independently. This article does not turn expired migration guidance into current recovery instructions.

Tether's own support notice named EOS among the implementations for which it planned to end redemption obligations and freeze remaining tokens on September 1, 2025. That issuer-level decision is separate from whether Vaulta produces blocks. A chain can continue while a particular centrally controlled asset loses issuer support. The reviewed announcement establishes the stated policy and deadline; it is not a live contract-state inspection or a guarantee that a particular intermediary will accept a deposit today.

Vaulta's migration guidance distinguishes native USDT under its issuer contract from an exchange's custodial balance and from wrapped assets associated with exSat. Those distinctions remain useful even though the page contains expired promotional rates and inconsistent descriptions of whether some services were already live. Wrapping changes the custody and redemption path; it does not eliminate it. Readers should identify the actual contract and backing arrangement rather than treating every asset displaying USDT as an identical instrument with identical operational support.

The September 2025 producer meeting records a concrete disagreement about economic alignment. Participants questioned producers with little personal stake and discussed minimum holdings or additional weight for self-staked tokens. Yves La Rose argued that the proposed costs were unrealistic and emphasized building demand through external products instead of governance redesign. The record shows different priorities within an actual operational forum; it does not prove that all tokenholders accepted either argument.

It also makes clear why a banking strategy can be evaluated differently by operators, application builders and passive holders.

The Foundation's own important notice treats its plans and ecosystem statements as conditional and forward-looking. That is a useful boundary for reading the entire transition: announced partnerships, software availability, deployed contracts and demonstrated customer use are different kinds of evidence. For this September 2026 review, historical activations are dated precisely, while later product execution remains unverified where the researched materials do not establish it.

Keeping that boundary visible preserves the network's substantial technical history without converting hopes about its next phase into established results.