The honest framing first: Vaulta is the rebrand of EOS. The mainnet you knew as EOS is now Vaulta, the native token symbol changed from EOS to A, and the on-chain history is preserved. If you've been routing EOS through MixPay or asking customers to pay you in EOS, none of that breaks — it just runs under a new name. The rebrand was completed during 2025 and the chain operates continuously.
This post is the reference for what merchants need to know about the change and how MixPay handles it.
What changed and what didn't
What changed:
- Network name — EOS → Vaulta.
- Native token symbol — EOS → A.
- Brand and positioning — Vaulta is positioned around financial-application use cases, particularly stablecoin-denominated and DeFi-adjacent flows.
What didn't change:
- The chain itself — same mainnet, same validator set during the transition.
- On-chain transaction history — preserved across the rename.
- Wallet addresses and existing accounts — same on-chain identifiers.
- Merchant settlement on MixPay — operationally identical for the merchant.
Why this matters for merchants
If you have customers who hold EOS — and there's a meaningful long-tail community that does — those holders are now holders of A. Their balances are intact, their wallets continue to work, and the asset is still routable through MixPay's payment infrastructure.
The practical merchant question becomes: do you label the asset "EOS" or "A" at checkout? MixPay's chain coverage tracks the post-rebrand convention, so the canonical asset symbol surfaced in the dashboard and at checkout is A. Customer wallets may still display the legacy EOS label depending on how recently they've been updated; that's a wallet UI question, not a chain question.
What MixPay routes on Vaulta
The same things MixPay has always routed on this chain:
- A as the native asset.
- Stablecoin coverage that's specific to the Vaulta deployment — see the asset list for the current set, as deployments evolve.
The merchant-side flow is unchanged from when this was labelled EOS:
- Customer pays from any Vaulta- (or EOS-display) compatible wallet.
- MixPay confirms the on-chain transaction.
- Real-time conversion applies at the time of payment.
- Merchant settlement lands in the chosen stablecoin.
- Zero merchant fees at the MixPay layer.
Where this fits commercially
Vaulta's commercial relevance has always been a specific one: an established dApp ecosystem with active developer communities, particularly in DeFi-adjacent products and gaming. The rebrand sharpens that positioning — Vaulta is being shaped as a financial-application chain rather than a general-purpose smart contract platform. For merchants whose customer base is active in those ecosystems, the chain remains worth routing.
For most consumer-facing merchants, Vaulta will sit in the long tail of chain volume — not a primary route, but available without operational cost.
A practical clarifying note
If you have integration documentation, marketing copy, or internal terminology that still says "EOS," it's not wrong yet — both labels still appear in the wild. But the stable forward-looking reference is Vaulta. MixPay's accept page tracks the post-rebrand convention, and the asset will appear there as Vaulta with the A native token.
The rebrand doesn't change anything operationally for MixPay merchants. If you're routing the chain, you're routing it under a new name with the same mechanics. If you weren't routing it before, the only change is that you're now hearing "Vaulta" instead of "EOS" — the access path through MixPay is unchanged.