Layer 1 blockchain
Vaulta ticker A
Summary
Delegated proof of stake with Savanna finality, run by the Spring node software (descended from EOSIO through Leap). Holders stake A to vote for up to 30 producer candidates, weighted by stake; the top 21 take turns producing blocks every half second, 12 in a row each (six seconds), as set in Spring's source code. Since the Spring 1.0 hard fork on 25 September 2024 the same 21 also act as finalizers: they sign BLS votes on every block, and a block becomes irreversible once 15 of the 21 agree, normally about one second after it is produced. Producers bond no stake that could be slashed, and the docs say a missing vote carries no penalty. System contract upgrades are approved by 15 of the 21 through the eosio.prods multisig account. A third-party vote tally read on 2026-09-29 showed each of the top 21 with about 2.4% to 4.2% of producer vote weight. 1261522252628
Design
- System
- Layer 1 blockchainVaulta is the network formerly called EOS, renamed in 2025 with no new chain: accounts, contracts and state history carried over, and the native token symbol changed from EOS to A through a one-to-one swap contract. It runs its own delegated proof-of-stake consensus in the Spring node software and settles to no other chain. It also runs an EVM as a smart contract inside Vaulta transactions: the Vaulta EVM contract (formerly EOS EVM) and a second deployment of the same framework operated by exSat.
- Settlement family
- Its own design
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- The 21 producers with the most stake-weighted votes, re-ranked continuously as votes change, publish blocks on a schedule; a producer that misses its turn is skipped. Candidates below the top 21 are standby producers. No minimum self-stake is required: at the September 2025 producer meeting community members said some top-21 producers hold little or no stake, and the Foundation said a minimum would need a hard fork and is not on its roadmap.
- Fork choice
- Committee voting, not open weight-based chain selection. Finality advances only with votes from 15 of the 21 finalizers; if votes are missing or disagree, the last irreversible block stays where it is. Among blocks not yet final, Spring's fork database prefers the branch whose latest quorum certificate points to the most recent block, then the most recent block timestamp.
Qualifications
- Settlement family · Partial. Recorded as other. Vaulta's own terms: an Antelope-protocol chain run by the Spring node software (descended from EOSIO through Leap), with delegated proof of stake, Savanna finality, human-readable accounts with layered permissions, WebAssembly smart contracts and a CPU, NET and RAM resource model. EVM contracts run inside Vaulta transactions through an EVM contract.
- Finality · Partial. Recorded as other. Vaulta's own terms: Savanna consensus. The top 21 producers act as finalizers and sign BLS votes on every block; a block is marked irreversible once 15 of the 21 agree, which Spring 1.0's notes put at about one second under typical conditions. Producers are not required to bond stake and no slashing mechanism was found, so this is committee finality without stake at risk.
- Scarce resource · Partial. Stake decides who produces blocks: holders stake A to vote for up to 30 candidates, weighted by the amount staked. Producers themselves are not required to hold or bond A, and no slashing mechanism was found. Staking for rewards goes through a separate system called REX with a 21-day unstaking period.
- Transaction fees · Partial. Vaulta's user guide describes low or no fees, sometimes covered by developers, and there is no per-transaction gas price on the base layer. Each transaction draws on the paying account's CPU, in microseconds, and NET, in bytes, and is rejected if the account lacks them; accounts rent CPU and NET with A through PowerUp for up to 24 hours and must buy RAM for stored data from a system market priced by a Bancor algorithm.
- Name and token · Applies. The EOS network was renamed Vaulta in 2025. On 14 May 2025 a producer multisig deployed core.vaulta, which is at once the new system contract, the A token contract and a swap contract: sending EOS to it returns the same amount of A with no fee. A keeps EOS's precision of four decimal places and 2.1 billion maximum supply. Vaulta said its swap portal would work in both directions for four months, then only from EOS to A, with no deadline for swapping.
- Evm compatibility · Partial. Two EVM environments run as contracts executed inside Vaulta transactions, so they share Vaulta's producers and finality and are neither rollups nor side chains. Vaulta EVM (chain ID 17777) launched in April 2023 as EOS EVM; the Foundation announced a gas token switch from EOS to A for 1 October 2025 and the end of its infrastructure on 8 October 2025, while the contracts remain; its RPC host did not resolve when checked on 2026-09-29. exSat EVM (chain ID 7200) launched in October 2024 on the same framework and is where the Foundation now directs EVM activity.
- Core development status · Partial. The last stable release of the reference node software, Spring v1.2.2, came out in August 2025, and the last v2.0 developer preview build for test networks was published that month. At the 25 September 2025 producer meeting, recapped on 1 October 2025, the Vaulta Foundation told producers it would make no protocol-level changes, hard forks or system contract adjustments for the foreseeable future. EOS Rio, a producer, publishes a community 1.2.x maintenance line that it says continues Spring after upstream work stalled; its builds were still alpha at review.
- Staking rewards · Contested. Vaulta's developer docs say a May 2024 tokenomics change ended inflation and set aside 250 million tokens for staking rewards, paid out on a four-year halving schedule starting at 31.25 million a year, and Unicove showed 85.6 thousand A paid daily at review, which fits that rate. Vaulta's user guide instead gives about 76 million a year, and its producer page still calls producer rewards newly issued; these statements were not reconciled.
- Tps · Contested. The only throughput figure is a project-stated capacity without a published method; it is kept in the classified claims list and is not comparable with observed rates.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Open block production and finality. Twenty-one producers elected by stake-weighted votes make and finalize every block, and 15 of them can finalize blocks or approve system contract upgrades. Producers need not hold stake and no slashing mechanism was found, so misbehaviour costs votes and rewards, not bonded tokens. Running a full API node needs server-class memory and storage.Security is not listed as an emphasis because irreversibility rests on 15 of 21 elected producers behaving honestly with no stake at risk; readers who count one-second committee finality as a security property may disagree. Vaulta's user guide describes the design as decentralized through voting; the vote tally read here gave each of the top 21 between about 2.4% and 4.2% of producer vote weight, but who controls the stake behind those votes was not examined.
- Full node at home
- Demanding 1112Vaulta's hardware guide (written June 2023) gives a minimum for an API node without the block log of 2 CPU cores at 3.7 GHz or more, 16 GB of RAM plus 16 GB of swap, 1 TB of disk and a 100 Mb/s link, and warns this setup will face problems if the network's RAM use passes 32 GB and can respond slowly because of swapping; its suggested setup is 4 cores, 64 GB of RAM and 1 TB, rising to 4 TB with the block log and 5 TB for a state history node. The docs suggest starting a new node from a producer's state snapshot, which means trusting it rather than replaying history.
- Throughput claims
- Theoretical peak: 17,000 tx/s 16Theoretical peak; not comparable across chains or with observed load.Stated as '17,000+ transactions per second' in the key specifications of Vaulta's user guide page for its base layer.No measurement window, date range or workload statedProject-stated capacity with no published method, transaction mix, hardware or date; it is not an observed network rate. Each transaction is billed CPU time as measured by the producing node, so the achievable rate depends on what the transactions do and on block CPU limits set on chain. The same guide page says the network can scale further by adding side chains; such chains would not add capacity to this chain itself. The figure ignores state growth in RAM, block propagation and spam or decoy load, and no observed rate was found.
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Built into the protocolLimited scope | Limited to exchanges on Vaulta itself. A Vaulta transaction can carry actions authorized by several accounts, must be signed with keys that satisfy every listed authorization, and executes its actions atomically as a whole, with state restored if any action fails, so two parties can exchange A and other tokens in one transaction without an intermediary. No hash-locked or time-locked swap with other networks was reviewed. 68 |
| Authenticated data publication | Unknown | Contract data is kept in tables held in RAM and served by node APIs, and block headers carry transaction and action Merkle roots. These are building blocks: no reviewed feature gives readers a recorded commitment to published data together with a documented way to check retrieved data against it. 910 |
| Light clients | Unknown | Spring 1.0's notes say Savanna's faster finality supports cross-chain consensus and that other Antelope chains need an updated inter-chain contract to stay compatible with this chain, and finalizer votes are BLS signatures that are aggregated and verified. No documented light client for end users was reviewed; Vaulta's docs offer a producer-published state snapshot to speed up syncing a new node. 21224 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel network settling to Vaulta was found in the reviewed sources. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Any account can host one WebAssembly smart contract, usually written in C++. Accounts also have a built-in permission system: each permission is controlled by weighted keys or other accounts with a threshold, custom permissions can be limited to specific contract actions, and multi-signature approval is native. EVM contracts run inside Vaulta transactions through the Vaulta EVM contract. 61014 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Recovery rests on building blocks only: the owner permission can replace the keys of the active permission, and a permission can be controlled by other accounts with weights and a threshold, which is key rotation by the account's own controllers. Delayed sends are not offered: Savanna, active on Vaulta since 25 September 2024, depends on the Spring features that disable deferred transactions, which turn the native action for cancelling a delayed transaction into a no-op and stop deferred transactions from executing. 36726 |
| Rollups | Unknown | No rollup settling to Vaulta was found in the reviewed sources, but absence was not exhaustively verified. The two EVM environments on Vaulta run as contracts executed by Vaulta's own producers, not as rollups. 1427 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | A signature covers the whole transaction digest, including every action and account it names, so a maker's signature fixes the counterparty in advance; no reviewed mechanism lets a maker sign one side for any taker to complete. Exchanges on Vaulta run as ordinary contracts. Not researched further under this row's definition. 8 |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | ThinDefibox | DeFiLlama lists Defibox as a decentralized exchange on this chain, and Vaulta's August 2025 notice on USDT says Defibox supports on-chain swaps to A and to USN. The RAM market is a system contract that prices RAM against A with a Bancor algorithm and trades nothing else. Defibox's pool design, operator and audits were not checked on a Defibox-authored page, and its site renders only in the browser. 42329 |
| Issuer-native stablecoins | None found | Tether's supported-protocols page says it no longer issues or is obliged to redeem USDT on EOS, and Vaulta said on-chain EOS USDT balances would be frozen after 1 September 2025. Circle's USDC address list does not include Vaulta or EOS. Vaulta now points users to exSat USDT, a wrapped token backed by USDT on another chain, which is not issuer-native here. The same notice announced a planned USD1 integration with World Liberty Financial; no USD1 issuance on Vaulta was verified. 233031 |
| Algorithmic stablecoins | Unknown | Vaulta's USDT notice calls USN a third-party collateral-backed stablecoin available through Defibox; its design and backing were not reviewed, and no other algorithmic stablecoin was checked. 23 |
| Bridges | ThinexSat EVM trustless bridge, Vaulta EVM trustless bridge (Foundation support ended October 2025) | exSat's docs describe a bridge that locks tokens in its EVM runtime contract on Vaulta and mints the same amount inside exSat EVM, and back. The Vaulta EVM bridge worked the same way; the Foundation announced the end of its infrastructure for 8 October 2025, and its bridge and RPC hosts did not resolve when checked on 2026-09-29. Other routes listed in Vaulta's directory were not checked. Risk: Both bridges move tokens between Vaulta accounts and an EVM contract on the same chain, so users trust that contract's code and whoever can upgrade it. Tokens that arrive from other chains, such as exSat USDT, also depend on exSat's custody and bridges off Vaulta. The Foundation said funds lost in the Multichain bridge hack will not be recovered. 21222327 |
| Block explorers | Established in the ecosystemUnicove (Greymass), EOS Authority | Vaulta's user-guide directory lists Unicove and EOS Authority as block explorers. Unicove, run by Greymass, describes itself as the Vaulta web wallet and block explorer; EOS Authority's site is still branded for EOS. Listing is not a quality or completeness check, and explorer data is provider-indexed. 183233 |
| Hardware wallets | ThinLedger (through Anchor or Fairy-wallet) | See custody rows: Ledger's own page for EOS tells users to pair the device with a third-party wallet, and Greymass documents Ledger support in Anchor. Trezor says it does not support EOS or Vaulta. 343640 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Through an intermediaryAnchor wallet (Greymass) or Fairy-wallet, signing with the Ledger EOS device appSame as native: Unknown | Can: Import a Ledger-held account into Anchor desktop and approve transactions on the device, per Greymass's guide Can: Connect a Ledger to Fairy-wallet to send, receive and swap, per Ledger's EOS wallet page Can: Use a Ledger with Anchor's browser version in Chrome-based browsers, per its August 2026 launch post Cannot: Find an A or Vaulta entry in Ledger's published currency list (@ledgerhq/cryptoassets 13.56.0), which has only an EOS entry with no explorer Cannot: Manage EOS or A in Ledger's own wallet app: Ledger's EOS page directs users to a compatible third-party walletLedger's EOS pages were last modified in 2024 and predate the rename. The Vaulta Foundation keeps the Ledger device app's source and points to Anchor as its wallet. Whether the device app displays A transfers from core.vaulta clearly was not tested. 3435363738 |
| Trezor | None foundSame as native: No | Cannot: Manage EOS or A in Trezor Suite; Trezor's pages say it does not currently support EOS or VaultaTrezor's pages ask users who used these assets with Trezor before to contact support; no third-party path was checked. 3940 |
Public data
iKnow Blockchain has no public-data lookups for Vaulta yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Reviewed Sep 29, 2026 Next review due Oct 9, 2026, 12:00 UTC.
Publication date · newest first
-
Greymass launched a browser version of the Anchor wallet with free Vaulta accounts
Aaron Cox of Greymass announced Anchor for the web, a non-custodial wallet that runs in the browser with passkey-protected keys and Ledger support in Chrome-based browsers. It creates Vaulta accounts for free after a Google or Apple sign-in, and apps built on Greymass's Wharf libraries can trigger account creation from inside the app. The post says the project began as network-funded work and was first planned as an account.vaulta.com service.
- Implementation:Launched
- Release:available at anchorwallet.io
- Activation:available per Greymass; not tested in this review
Sources: Aaron Cox (Greymass), jesta.blog — Anchor for the web (external site) · Greymass — Anchor Wallet (external site) · Vaulta Documentation — Accounts (external site)
-
EOS Rio published alpha builds of a community Spring 1.2.x maintenance line
EOS Rio, a producer, released Spring v1.2.3-alpha1 from its own fork, describing it as continuing Spring after upstream work stalled. It is built on v1.2.2 with a rule of no consensus, wire-format or API changes, moves the optimized contract compiler to a current LLVM version and collects unreleased upstream fixes. A second alpha, proposed in September 2026, adds fixes for security and stability reports, including checks in BLS host functions and Savanna vote handling.
- Implementation:alpha builds published by a producer
- Release:alpha, for testing only
- Activation:none; no consensus rule changes
Sources: EOS Rio (GitHub) — Spring v1.2.3-alpha1 (eosrio/spring maintenance line) (external site) · EOS Rio (GitHub) — release: v1.2.3-alpha2, community security and stability fixes (external site) · AntelopeIO (GitHub) — Spring v1.2.2 release notes (external site)
-
Spring node software moved from a chain-bound Business Source License to MIT
A commit to the Spring repository's main branch replaced its Business Source License, which granted free use only in service of this chain, with the MIT License. The new license file names the Vaulta Foundation and the EOS Network Foundation as copyright holders and credits the EOSIO code the software is based on.
- Implementation:license file changed on the main branch
- Release:no tagged Spring release includes it
- Activation:not a protocol change
Sources: AntelopeIO (GitHub) — Spring commit e6a99f6: Update LICENSE (Move to MIT License) (external site) · AntelopeIO (GitHub) — Spring v1.0.0 release notes (external site) · AntelopeIO (GitHub) — Spring v1.2.2 release notes (external site)
-
Vaulta Foundation told producers it would make no protocol-level changes for the foreseeable future
At the September 2025 producer meeting, recapped by Vaulta on 1 October 2025, the Foundation's founder and CEO said it would step away from protocol-level work: no hard forks and no system contract adjustments, with effort moving to an external business product. The same meeting heard a proposal for a minimum producer stake, which the Foundation said would need a hard fork and is not on its roadmap, and guidance to move off Vaulta EVM before its October shutdown.
- Implementation:policy statement at a producer meeting
- Release:announced in the meeting recap
- Activation:no protocol change involved
Sources: Vaulta — Vaulta BP Meeting Recap: September 2025 (external site) · AntelopeIO (GitHub) — Spring releases (external site)
Topics your AI can explain
Your AI can explain these topics for Vaulta through the connection, with sources.
Known gaps
What this profile's review did not establish:
- The swap and staking figures in Vaulta's user guide and its developer docs disagree (staking rewards per year, and whether producer rewards come from new issuance); the developer docs and Unicove's daily payout were followed.
- Whether the EOS-to-A swap still runs in both directions was not verified: the May 2025 announcement said it would become one-way after four months, while a September 2025 notice still said A can be swapped back.
- Who controls the stake behind each producer's votes, and how many producers share operators, were not examined; the vote tally comes from a third-party portal read once on 2026-09-29.
- No producer penalty beyond losing votes and rewards was found in the reviewed docs, but the system contract code was not reviewed for one.
- Whether mainnet has activated the Spring v2.0 sync-call feature or any later protocol feature, and which node versions producers run, were not verified beyond two public API nodes reporting Spring v1.0.5 and v1.2.2.
- Trade press reported leadership and treasury disputes at the Vaulta Foundation from late October 2025; no primary source was found, so they are not described here.
- Whether Vaulta accounts have any recovery design beyond weighted multisig permissions was not researched.
- Storage needed for a full node today, and current state size in RAM, were not measured; the hardware guide dates from June 2023.
- No light client, rollup, payment or state channel, swap with other networks or signed open offer was found; absence was not exhaustively verified.
- Defibox's operator, pool design and audits, and the design of the USN stablecoin, were not reviewed.
- Whether the Ledger EOS device app shows A transfers from core.vaulta clearly, and whether Fairy-wallet is still maintained, were not tested.
- Bridges other than the two EVM bridges, such as the third-party routes in Vaulta's directory, were not checked.
- Vaulta's user guide says each producer makes six blocks in a row in rounds of 126, while Spring's source code sets 12 consecutive blocks per producer; the code was followed.
- The USD1 stablecoin integration that Vaulta announced in August 2025 was not verified as live on Vaulta.
- Trezor's firmware support data lists signing for EOS-format transactions on the Model T only, not on the Safe 3, 5 or 7; no wallet documenting a Trezor path for this chain's accounts was found, and none was tested.
Sources
Oldest dated source check: Source checked Sep 29, 2026 Next check due Oct 29, 2026.
- Consensus (external site)
- Introduction to Finalizers and Voting (external site)
- Switching Over To Savanna Consensus Algorithm (external site)
- Resources (CPU, NET and RAM) (external site)
- Upgrading to Vaulta from EOS (external site)
- Accounts (external site)
- libraries/chain/protocol_feature_manager.cpp (Spring v1.2.2): Savanna and the features that disable deferred transactions (external site)
- Transactions Protocol (external site)
- State Data (external site)
- Glossary (external site)
- Hardware Requirements (external site)
- Snapshots (external site)
- Staking: Token Flows (external site)
- Vaulta EVM Architecture Overview (external site)
- libraries/chain/include/eosio/chain/config.hpp (Spring v1.2.2): block interval and producer repetitions (external site)
- Vaulta Native (external site)
- Tokenomics (external site)
- Directory (external site)
- The Era of $A: Vaulta's Token Swap Begins May 14 (external site)
- Consolidating EVM Support Around exSat (external site)
- Notice: Vaulta EVM Support Ending October 8, Transitioning Gas Token to $A October 1 (external site)
- Vaulta BP Meeting Recap: September 2025 (external site)
- Final Call for EOS USDT: What Vaulta Users Need to Know (external site)
- Spring v1.0.0 release notes (external site)
- libraries/chain/fork_database.cpp (Spring v1.2.2): best-branch ordering (external site)
- EOS Completes Historic Hard Fork to Spring 1.0 with Savanna Consensus Algorithm (archived copy) (external site)
- Trustless Bridge for Native Tokens (external site)
- Vaulta Block Producer Research Portal (read 2026-09-29) (external site)
- DeFiLlama protocols API (EOS entries: Defibox, 1DEX and others) (external site)
- Supported protocols (external site)
- USDC contract addresses (external site)
- Unicove: The Vaulta web wallet and block explorer (external site)
- EOS Authority explorer and wallet (external site)
- EOS wallet (external site)
- @ledgerhq/cryptoassets 13.56.0 currency list (external site)
- Connecting Ledger to Anchor (external site)
- Anchor for the web (external site)
- ledger-app: EOS wallet application for Ledger devices (external site)
- EOS wallet (external site)
- Vaulta wallet (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding