Xion (XION)

Overview

Xion began as a Layer 1 blockchain designed to make crypto applications easier to use. A Layer 1 is the base network that records transactions and runs applications. Xion focused on removing steps that often slow new users down, such as setting up a wallet, saving a recovery phrase, and finding a token to pay transaction fees.

On June 17, 2026, the project adopted the name Verona, and its token changed its public ticker from XION to VERONA. Existing balances continued on the same network. The project now places greater emphasis on verifying information for apps and AI agents while keeping personal records private. Its earlier work on simple accounts and payments remains part of that system. This article uses Xion when discussing the project’s origins and Verona for its current name. (verona.micarwhitepapers.eu)

History & Team

From Burnt to Xion

Xion grew out of work by Burnt, a team that wanted blockchain products to feel more like familiar websites and mobile apps. Founder Anthony Anzalone, also known as Burnt Banksy, first drew attention by burning a Banksy artwork and creating an NFT linked to the event. The team later turned its attention to a broader problem: making digital ownership and blockchain tools practical for everyday users. (docs.verona.dev)

The Xion mainnet and its native token launched on December 5, 2024. In its early phase, the project described its approach as generalized abstraction: building simpler account, signing, and fee systems into the network itself. By 2026, its work with businesses had led to a stronger focus on proving facts about people and their activity without passing around their private records. That shift became central to the Verona name and its focus on AI agents. (xion.burnt.com)

The project has named Animoca Brands, Multicoin Capital, and HashKey Capital among its investors. In its June 2026 rebrand announcement, it reported more than $36 million raised and said its verification technology had handled over 69 million verified interactions across more than 3 million users. Those figures describe activity reported at that point, rather than a measure of how many people hold the token. (globenewswire.com)

Technology & How It Works

A blockchain beneath a simpler experience

The network uses the Cosmos SDK to build its blockchain, CometBFT to agree on transactions, and CosmWasm to run smart contracts. Validators help keep the ledger in order through proof of stake. Developers can also use Inter-Blockchain Communication, or IBC, to connect with compatible networks. Smart contracts are programs that carry out rules, such as issuing a reward after a required condition has been met. (docs.verona.dev)

Xion’s account design helps hide much of this machinery from the person using an app. Its Meta Accounts can support familiar sign-in methods, including email, passkeys, and social login. An app can grant limited permissions for a session, such as allowing certain actions for a set time. Developers can also sponsor transaction fees through Treasury tools, so an app can handle the blockchain cost in the background. (docs.verona.dev)

Turning a claim into a reusable proof

Verona adds a verification system called the Truth Engine. It is designed to prove a specific claim from a source such as a website, email, or mobile app. For example, a person could prove that an account meets a loyalty threshold without giving another app access to the whole account. The person creates a proof from the source data; the network checks it and records a verified claim, called an attestation, linked to their Meta Account. An app or authorized AI agent can then use the claim to decide what action to take. (docs.verona.dev)

The system’s methods include zkTLS for website information, zkEmail for signed emails, and app attestations for activity within mobile apps. Project documentation also describes passport-based proofs as part of its verification plans. These tools aim to let an app learn the answer it needs—such as whether a person meets an age or eligibility rule—without receiving every detail in the source record. (docs.verona.dev)

Tokenomics & Utility

The token was created as XION with an initial supply of 200 million at the December 2024 launch. Its public name and ticker later changed to VERONA on a one-for-one basis. The rename did not create a second network or require holders to move their native balances to a new contract. Some technical identifiers still contain the older name, including the on-chain denomination uxion. (xion.burnt.com)

At launch, 25,559,333 tokens were unlocked. The remaining 174,440,667 were placed under a published 48-month unlock schedule. Those figures describe the original distribution. They do not make the initial supply a permanent cap: the proof-of-stake system also has a minting mechanism whose parameters can be changed through network governance. (xion.burnt.com)

The native token has three central network roles. People can stake it with validators to help secure the chain, use it in governance, and pay for network activity. Holders may delegate tokens to a validator, while validators process transactions and take part in maintaining the ledger. Because apps can sponsor users’ fees, someone using a Verona-based service may interact with the network without handling the native token for each action. The project also describes an economic model tied to activity from applications, business verification, and agent-driven services. (xion.burnt.com)

Ecosystem & Use Cases

Verified activity for people and businesses

Ero, built by EarnOS, is a consumer application on Verona. It lets people connect everyday accounts and prove selected activity or attributes for campaigns and rewards. The proof can establish eligibility while the underlying account records stay with the user. Burnt Verified is an enterprise-facing service focused on claims such as income, employment, and credentials. Both use the network’s verification tools for different audiences. (docs.verona.dev)

The same building blocks can support other applications. A loyalty program could accept proof of a customer’s status with another service. An employer could check a credential from its source. A game could require a verified condition before granting access or a reward. An AI agent could use a fact a person has already authorized, rather than asking that person to supply the same document again. These are patterns developers can build with the verification and smart-contract tools; each app chooses its own rules and user experience. (docs.verona.dev)

Verona’s June 2026 announcement named Uber, Amazon, Nike, and BMW among brands whose experiences had used its technology. For readers assessing the ecosystem, it is useful to distinguish that reported use of verification tools from direct use of VERONA by a brand’s customers. The applications, the network, and the token have related but different roles. (globenewswire.com)

Advantages & Challenges

Xion’s main design advantage is the way it joins two ideas: familiar app access and reusable proof. A person can sign in through an account system designed for ordinary web use, while a developer can still build rules that run on a blockchain. For businesses, a narrow verified claim may be more useful than collecting an entire document. For developers, accounts, fee sponsorship, verification tools, and smart contracts sit within one network. (docs.verona.dev)

The main challenge is making those pieces work smoothly across many real products. A proof is useful only when an app can check the right source, interpret the result, and act on it. Developers must design permission flows people can understand, especially when an AI agent is allowed to reuse a verified fact. The network also depends on applications and businesses building services around its tools. Token governance and staking continue alongside that product work, so both the user experience and the underlying chain matter to Verona’s development. (docs.verona.dev)

Where to Buy & Wallets

VERONA is available on Bybit under the VERONA/USDT spot pair. Bybit changed its displayed ticker from XION to VERONA during the June 2026 rebrand. Kraken lists the asset under XION on its purchase page. Exchange names and supported networks may therefore differ: the public-facing ticker changed, while some systems still use Xion identifiers. Availability depends on the exchange and a customer’s location. (announcements.bybit.com)

Keplr supports the Verona network for people who want a separate wallet. Verona-based apps may instead use Meta Accounts, which allow sign-in without a conventional wallet setup. When moving tokens between an exchange and a wallet, the receiving address and network need to match the version the exchange supports; the asset also has bridged representations on other blockchains. (keplr.app)

Regulatory & Compliance

The project’s updated European crypto-asset white paper records the XION-to-VERONA rebrand and identifies the Netherlands as its home member state for its Markets in Crypto-Assets Regulation, or MiCAR, filing. MiCAR sets rules for crypto-asset disclosures and service providers in the European Economic Area. A white paper for this type of crypto-asset is notified to the relevant authority rather than approved by it. (verona.micarwhitepapers.eu)

In the United States, digital-asset transactions fall under federal tax rules. The Internal Revenue Service treats digital assets as property and requires reporting for relevant sales, exchanges, and rewards. The legal treatment of a token or related service can also depend on the activity involved, such as how it is offered or used. (irs.gov)

Halal or Shariah compliance for VERONA requires a token-specific assessment. Its uses include staking, governance, and network payments, so the terms of staking rewards and the activities an application supports are relevant to that assessment. Islamic-finance treatment of digital assets varies by framework; Malaysia’s Securities Commission, for example, sets out conditions for assessing digital tokens and their trading. The network’s published token materials establish its technical and economic uses, rather than a Shariah ruling for the token. (docs.verona.dev)

Future Outlook

Verona’s direction is to make verified facts useful across more apps, businesses, and AI agents. Its account tools address how people enter an app; its proof tools address what an app or agent can reliably learn; and its blockchain records actions under shared rules. Wider use will depend on developers turning those pieces into services that people find simple enough to use. (docs.verona.dev)

The shift from Xion to Verona also gives the native token a broader setting. Staking and governance remain its base functions, while the project seeks more activity from verification and applications built on the network. How strongly those uses connect in practice will become clearer as the ecosystem develops. (docs.verona.dev)

Summary

Xion began as a blockchain built to make crypto easier to use. Now called Verona, it combines that account and payment design with tools for proving facts privately and reusing them with permission. Its native token, formerly XION and now VERONA, supports staking, governance, and network activity. The project’s place in crypto lies in connecting usable applications with verifiable information for people, businesses, and AI agents. (docs.verona.dev)