Skip to content
Knowledge base

BlockzHub Vaulta Wiki

A community-maintained guide to Vaulta — the network formerly known as EOS — covering how it works and how to take part on BlockzHub.

Open the Vaulta Hub for earn, vote, news, and contribute.

Network
Vaulta
Formerly
EOS
Protocol
Antelope
Core token
A (renamed from EOS, 1:1)
Consensus
Delegated Proof of Stake
Block time
~0.5 seconds

What is Vaulta?

Vaulta is a high-performance, Antelope-based layer-1 blockchain focused on Web3 banking and real-world financial applications. It offers fast, sub-second block times, predictable costs through a staked-resource model, and on-chain governance run by elected block producers. It is the rebrand of the EOS network.

From EOS to Vaulta

EOS launched in 2018 as one of the first high-throughput smart-contract platforms. Its protocol later became the open-source Antelope framework. The network subsequently rebranded to Vaulta to focus on a Web3-banking vision, and the native token was renamed from EOS to A. The technology, account names, and history carry over — it is a rename and strategic refocus, not a new chain.

The A token

A is Vaulta's core token (formerly EOS), converted 1:1. It is used to pay for network resources, stake for rewards, vote for block producers, and transact. On BlockzHub you can swap into A and stake it to earn network rewards.

Accounts & permissions

  • Human-readable names. Accounts use short names (up to 12 characters) instead of raw hex addresses.
  • Owner & active permissions. Each account has an owner key (full control, recovery) and an active key (day-to-day actions), and can define custom permissions.
  • Multi-signature. Permissions can require multiple keys/accounts, enabling shared control and DAOs.

Resources (CPU, NET, RAM)

Transactions consume three resources rather than a single per-transaction gas fee:

  • CPU — processing time, obtained by staking the core token.
  • NET — network bandwidth, also obtained by staking.
  • RAM — on-chain storage for account state, bought and sold on an on-chain market at a floating price.

Because CPU/NET come from staking (which you get back), everyday usage can feel close to feeless once you hold enough stake.

Staking & REX

The Resource Exchange (REX) lets holders lend their tokens to earn a share of network rewards and fees while still supporting the chain's resources. On BlockzHub, the Earn flow deposits into REX and votes on your behalf (voting is required to earn), so you can stake and start earning in a few clicks — non-custodially, signed by your own wallet. Unstaking moves funds to savings with a maturity period before withdrawal.

Block producers & consensus

Vaulta uses Delegated Proof of Stake (DPoS): token holders vote for block producers (BPs), and the top-ranked producers take turns producing blocks. You can vote for up to 30 producers or delegate to a proxy directly from BlockzHub. Voting strengthens the network and, via REX, is tied to earning rewards.

Governance

Vaulta is governed on-chain. Proposals are coordinated through multi-signature (eosio.msig): approving is an on-chain “yes” vote and executing enacts the change. BlockzHub's Governance page lets you propose and vote on polls anchored on-chain.

Getting started

  1. Get a wallet — Anchor (desktop/mobile) or a web cloud wallet — and create or import an account.
  2. Connect your wallet on BlockzHub using the wallet button in the top navigation.
  3. Get some A — swap into it — then stake to earn.
  4. Participate: vote for producers, weigh in on governance, and learn more in our courses.
  5. Discover apps in the dApp directory and follow updates in news.

Glossary

  • Antelope — the open-source protocol framework Vaulta is built on (formerly EOSIO).
  • BP — block producer; an elected validator that produces blocks.
  • DPoS — delegated proof of stake; the vote-based consensus model.
  • REX — Resource Exchange; the staking/lending market for earning rewards.
  • Proxy — an account you delegate your producer votes to.
  • msig — multi-signature; the on-chain mechanism used for governance and shared accounts.
  • CPU / NET / RAM — the three network resources described above.

This wiki is community-maintained and evolving. Spotted something to add or correct? Let us know