TL;DR
Brickken’s Q2 marked a shift from tokenization deployment to institutional infrastructure maturity: $660M+ in tokenized assets, 150+ clients, 40+ countries, BKN 2.0 migration, ERC-7943 Final status, RAMS for regulated AI agents, Brickken CLI and Base MCP, expanded ISO certifications, new U.S. and Luxembourg presence, and partnerships across MENA, real estate data, trade finance, and certified partner execution.
Q2 was the quarter tokenization moved further away from narrative and deeper into infrastructure.
The market no longer needs another explanation of why real-world assets can be represented on distributed ledger infrastructure. It needs the operational systems that make tokenized financial instruments compliant, interoperable, auditable, and manageable after issuance.
That is where Q2 mattered.
We closed the quarter with more than $660M in tokenized assets, 150+ clients, and activity across 40+ countries. The numbers reflect a structural shift in the market. Institutions are not evaluating tokenization as a concept. They are evaluating whether the infrastructure is ready for regulated capital, live workflows, multi-jurisdictional compliance, and lifecycle management at scale.
Four developments defined the quarter:
Each points to the same conclusion: tokenization only scales when the rails are repeatable, compliant, and operational from issuance through secondary distribution and post-issuance management.
Q1 confirmed that tokenization had moved out of the pilot phase. Q2 showed what comes next.
Once issuers, funds, asset managers, and financial institutions move into production, the requirements change. The focus has shifted from an asset's mere tokenizability to whether its full operating model can actually withstand intense institutional pressure.
• Can compliance be embedded directly into transfer logic?
• Can assets move cross-chain without fragmenting liquidity?
• Can the entire asset lifecycle remain connected post-issuance?
• Can AI agents compliantly interact with regulated instruments?
• Can live transactions easily plug into a vetted network of experts?
These are the practical questions shaping the next phase of tokenization. Q2 was about answering them through infrastructure.
In June, Brickken began the migration of BKN to a new Ethereum smart contract.
The migration is not a cosmetic upgrade. It consolidates BKN into a single canonical Ethereum contract, with a 1:1 migration ratio, unchanged ticker, and an independently reviewed audit by OpenZeppelin with no Critical, High, or Medium severity findings.
The migration window opened on 25 June 2026 at 13:00 UTC and closes on 25 July 2026 at 00:01 UTC.
For institutional infrastructure, the importance of this upgrade sits in the architecture behind it.
BKN 2.0 establishes the technical foundation required for native cross-chain interoperability through Chainlink CCIP and for adaptive compliance models that support regulated tokenized assets. Institutional capital does not operate inside one isolated network. Assets, liquidity, instructions, and permissions need to move across systems while retaining control, verification, and accountability.
That is the role of the new architecture.
BKN 1.0 was built for the first phase of tokenization: bringing assets on-chain. BKN 2.0 is built for the next phase: programmable capital, cross-chain coordination, authorized AI agents, and lifecycle-managed financial instruments operating across connected infrastructure.
Institutional tokenization cannot scale on fragmented compliance logic.
For years, platforms built their own transfer restrictions, allowlists, freezing mechanisms, enforcement logic, and eligibility checks. That approach worked for isolated deployments. It does not work for interoperable capital markets.
In Q2, ERC-7943 reached Final status as an Ethereum standard for real-world asset tokenization. The standard introduces a minimal, vendor-neutral interface for compliant tokenized assets. It supports core institutional requirements such as transfer validation, frozen balances, forced transfers, and enforcement actions without binding issuers to a single identity provider, jurisdictional model, or compliance stack.
That distinction matters.
ERC-7943 does not prescribe one compliance system. It standardizes how regulated assets expose compliance functions to the market. Wallets, custodians, platforms, issuers, and infrastructure providers can integrate against a common interface while retaining flexibility over KYC, sanctions screening, investor eligibility, and jurisdiction-specific rules.
This is how compliance becomes interoperable.
Alongside ERC-7943, Brickken introduced RAMS, the Regulated Agent Mandate Standard, published as ERC-8226. RAMS addresses a new problem in regulated finance: AI agents can execute transactions, but regulated markets need to know who authorized the agent, what the agent is allowed to do, for how long, and under what financial limits.
RAMS defines a compliance delegation layer for AI agents operating with tokenized regulated assets. It allows a verified principal to delegate scoped, time-bounded, financially capped authority to an on-chain agent. The financial instrument does not simply check whether a wallet can transact. It checks whether the agent has a valid mandate to act.
This is the institutional version of agentic execution. Not autonomous activity without controls. Authorized execution under defined accountability.
ERC-7943 standardizes the regulated asset interface.
RAMS standardizes the mandate layer for agent-driven transactions.
Together, they move tokenization beyond asset issuance and into the operating architecture of programmable capital markets.
AI agents need more than intelligence. They need infrastructure.
An agent that can analyze a market, prepare an allocation, or identify an issuance opportunity still needs three operational capabilities before it can act: a way to pay, a way to prove who it is, and a way to execute.
In Q2, Brickken launched the Brickken CLI, a command-line interface for agentic transaction workflows.
The developer path is direct:
CLI → x402 → ERC-8004 → Token Deploy
A developer, or an AI agent itself, can install the CLI, pay for Brickken API calls through x402, register an on-chain identity through ERC-8004, and deploy or manage an ERC-20 token directly from the terminal.
No browser session. No API key. No manual approval loop.
The CLI gives agents the missing operational stack:
• x402 handles payment.
• ERC-8004 handles agent identity.
• Token Deploy handles ERC-20 execution.
The same logic extends through Brickken Agentic on Base MCP, where agents can interact with Brickken through one endpoint to register identity, handle x402 payments, and issue compliant tokens through a structured flow.
This is not a developer convenience feature. It is a step toward machine-operated financial infrastructure where identity, payment, permissions, and execution are connected programmatically.
For tokenization, that matters because the next stage of capital markets infrastructure will not be managed only through dashboards. Issuers, funds, family offices, and platforms will increasingly rely on agents for monitoring, routing, reporting, transaction preparation, and execution. That only works when the agent operates inside defined permissions and verifiable infrastructure.
Brickken’s agentic stack brings that model into production workflows.
Institutions do not onboard platforms on trust. They onboard them on evidence.
In Q2, Brickken achieved ISO/IEC 27701 and ISO/IEC 27018 certification, alongside ISO 27001:2022 certification and DORA alignment.
For banks, asset managers, family offices, and regulated enterprises, this is not an administrative milestone. It is part of the operating foundation they evaluate before sensitive issuer data, investor records, KYC and AML outputs, beneficial ownership information, and financial instrument documentation move through an external platform.
ISO/IEC 27701 extends privacy into an audited operating discipline. It covers roles, controls, data subject rights, sub-processors, privacy by design, retention, deletion, and risk mitigation around personal data processing.
ISO/IEC 27018 addresses personally identifiable information in public cloud environments. It covers handling, separation, transparency, restricted access, deletion, and cloud-specific safeguards for SaaS infrastructure.
Together with ISO 27001:2022 and DORA verification, these certifications support the compliance stack institutions require underneath tokenized financial instruments.
Privacy and data protection are not separate from tokenization infrastructure. They are part of it.
This compliance foundation also supports Brickken’s broader transition into a regulated broker and MiCA-compliant custodian. The market is moving toward licensed, accountable infrastructure. Q2 strengthened the operational controls required for that direction.
Q2 also expanded Brickken’s geographic and partner footprint.
Brickken launched U.S. operations in Miami, adding a third global hub alongside Barcelona and Dubai. Miami is now an operational anchor for Brickken’s work across tokenized real estate, PropTech, and U.S. market development.
We also joined The LHoFT in Luxembourg, one of Europe’s leading financial technology hubs. Luxembourg is a critical market for funds, asset management, private banking, and regulated financial infrastructure. Establishing a dedicated office within The LHoFT places us closer to the institutions and regulatory conversations shaping Europe’s tokenized asset market.
In MENA, we partnered with ADI Foundation to deploy tokenization infrastructure on ADI Chain, an institutional Layer-2 network designed for stablecoins and real-world assets across MENA and emerging markets. The integration supports compliant asset issuance, lifecycle management, reporting, and controlled secondary distribution for tokenized financial instruments including equity, debt, private credit, real estate, and funds.
In real estate, we partnered with MAGMA to deliver a Net Asset Value oracle for tokenized real estate. The framework connects verified building data with Brickken’s tokenization infrastructure so issuers and asset managers can use continuously updated, asset-level data for valuation, investor reporting, audits, refinancing, and post-issuance monitoring.
This addresses one of the structural gaps in tokenized real estate. Ownership records alone are not enough. Institutional-grade real estate tokenization requires a reliable data layer behind the asset.
In commodities and trade finance, we participated in a pilot with Blockticity, Seedcore, and XDC Network to tokenize a cacao receivable backed by a verified export shipment from licensed Philippine farms.
The model connected four layers:
The mechanism is important: the tokenized receivable referenced authenticated trade documentation rather than replicating it on-chain. The financial instrument referenced the verified record; it did not replace it.
That is how commodity-backed tokenization becomes institutionally useful. Asset origin, transaction structure, documentation integrity, and lifecycle status remain verifiable across participants.
Tokenization deals do not close through infrastructure alone.
Every live transaction involves questions around legal structuring, tax treatment, investor communication, jurisdictional restrictions, marketing rules, due diligence, and distribution strategy. Issuers cannot answer all of those questions alone. They need specialist support around the transaction.
In Q2, we introduced the Brickken Certified Partner Program to build a vetted network of legal, technology, business, tax, and marketing specialists around live tokenization projects.
The program gives certified partners an official Brickken Certified Partner badge, warm introductions to relevant client opportunities, enhanced commercial collaboration, access to tokenization know-how and sales materials, exclusive workshops and industry updates, and a dedicated Brickken account manager.
It also gives partners access to business growth materials, including RFPs, frameworks, tokenization know-how, and transaction support resources designed to improve execution on both sides.
The purpose is practical. The infrastructure is deployed. The deals that close are the ones with the right specialists around them.
Q2 also brought external recognition.
Brickken won Tokenization Platform of the Year at the Hedgeweek Digital Assets Awards, received the Rising Star award at WAIB Summit, and was selected for BeInCrypto’s Institutional 100 list.
The team was also present across the industry’s main institutional and digital asset forums, including Paris Blockchain Week and Proof of Talk in Paris, Consensus and Future PropTech in Miami, EthCC in Cannes, WAIB Summit in Monaco, TokenizeThis in New York, ETHMilan in Milan, Adminovate in Dublin, and Dutch Blockchain Week in Amsterdam.
These events were not about visibility alone. They reflected where the market conversation has moved: regulated funds, tokenized real estate, AI agents, compliance infrastructure, cross-chain settlement, fund administration, and institutional deployment.
Those are the conversations Brickken is building for.
Q2 confirmed that tokenization is no longer measured by whether assets can be issued on-chain.
The institutional standard is higher.
Tokenized financial instruments need compliant issuance. They need investor onboarding and verification. They need enforceable transfer controls. They need lifecycle management, reporting, corporate actions, valuation inputs, distribution logic, privacy controls, custody readiness, and interoperability across infrastructure providers.
They also need operating models that can support AI agents without removing accountability from regulated finance.
That is the market we are building for.
In Q2, that infrastructure became more standardized, more compliant, more interoperable, and more ready for agentic execution.
The market needs rails that traditional finance teams can trust, deploy, and scale.
That is what Q2 delivered.
Structured. Compliant. Live.
