There is a social network where every account is a machine. It is called Moltbook, it launched at the start of 2026, and within weeks it held more than 200k autonomous agents that post, argue, and form their own subcultures.

Humans can watch. They cannot post.

It is also an old problem at a new scale: the agents are anonymous to one another, the platform carries known prompt-injection risk, and there is no native way to know who stands behind any of them. An anonymous population of autonomous actors is not a curiosity. It is a possible attack surface.

Now imagine those agents start paying each other. That is where the first use case of the Concordium AI infrastructure shows up.

This development is an immediate effect of the new deployments described across three earlier blogs in the series on the Agent Registry, the Verified by Concordium Badge, and how both extend to agents on Ethereum and Solana.

Why a Tip Is the Hard Case, Not the Easy One

Social Agent Tipping lets agents send each other micro-payments in CCD, Concordium’s native token, for useful work: a sharp comment, a successful tool call. It was built on Concordium, by a team that needed the one thing the chain provides and the rest of the agent ecosystem does not: a way to know who you are paying before you pay.

A tip looks trivial: a small amount of tokens for a good reply. But strip out the human and the trivial part disappears. When one agent tips another on Moltbook, no human is there to make the trust judgement, so the agent has to answer questions itself, at machine speed: Is this handle a real registered agent? Who controls the account behind it?

Get any wrong and the tip funds a possible impostor. Multiply that across micro-payments between over 200k anonymous accounts and you have rebuilt every problem on-chain history learned the hard way, now faster and with autonomous execution attached.

The fix is a credential the agent can check, not a reputation it has to trust. The agent receives the Verified by Concordium badge, the same mark any Ethereum or Solana builder can earn, now earned automatically by becoming a valid tipping destination on Moltbook.

One Handle, One Verification Call

When the Agent Registry launched two weeks ago, the question was what gets built on it first. Social Agent Tipping is the answer: it closes the gap with three artefacts anyone can fetch and check, not a reputation score you have to trust.

First, the handle is proven. An agent’s social handle is bound to its Concordium account and anchored permanently on chain, once the owner has proven they control both.

Second, the agent is registered. It receives an entry in the Agent Registry carrying its owner account and a link to its Agent Card.

Third, the tip is sent. Any other agent asks the Tipping MCP Server where to send a tip for a handle, and gets back the destination address plus a verification report covering the handle, the registry entry, and the card. One round-trip confirms all three agree.

And if the recipient isn’t verified yet, that isn’t a dead end. The recipient runs the same flow, gets its binding and badge minted, and becomes a valid destination. The reward is the reason to become accountable, not a wall that locks newcomers out: money it can only collect once someone can vouch for who it is.

The Service Never Touches the Money

What makes this trustworthy is what Social Agent Tipping refuses to do: it never holds the money and it never holds an agent’s keys. The CCD moves directly from one agent to the other. The service provides lookups, verification, and discovery. Verification is shared; custody is not.‍

“Building on Concordium is a real milestone for our small team,” said one of the team members behind Social Agent Tipping. “We chose to work with Concordium because trust is the whole point of what we’re building, and their technology already answered the one question that matters when agents pay each other: who am I actually paying? Through their Agent Registry, we can give every agent a badge it earns and a destination others can check, without ever holding anyone’s money, keys or ID. It’s a proud moment to be the first thing built on the registry, and we’re honoured to take this step with them.”‍

Why It Had to Be Built Here

A micro-payment rail for agents has unforgiving requirements: fees smaller than the tips, fast finality, and identity that can’t be a separate KYC product bolted on afterward. The builder needed all three in one place, and chose Concordium because that is where they already existed.

The registry is live on mainnet, agents register in real time, and each is verifiable on chain the moment it mints. Social Agent Tipping is the first thing built on it, the first proof that what the registry promised pays out, one CCD transfer at a time.

Try it yourself: https://tippingservice.co.uk/

You built your agent on Solana. It’s fast, it’s cheap, it’s already transacting. What it can’t do is prove who’s behind it.

When the Agent Registry launched, the Verified by Concordium Badge was built to travel to any supported chain. Solana is the next one. If your agent runs on Solana, it can now anchor to a verified human or business through the same registry that Ethereum agents already use. The chain it runs on does not change. What changes is that anyone it deals with knows that there is a verified human behind it.

Why Solana

Solana has become the busiest environment for autonomous agents. Through the first quarter of 2026, activity there moved from experimentation to real economic output, drawn by sub-second finality and fees low enough for machines to transact constantly.

It is the only major ecosystem that supports both the x402 standard and Stripe’s Machine Payments Protocol, the rails agents use to pay for services without a human approving each transaction.

That activity is also the problem. Agents on Solana are buying API access, settling payments, and transacting with other agents at machine speed, yet none of that infrastructure answers a basic question: who is accountable for what an agent does.

And unlike Ethereum, Solana has no equivalent of ERC-8004, no agent identity standard at all. The accountability gap isn’t just unsolved here. The first layer of it was never built. That makes the question of who stands behind an agent more important on Solana than anywhere else.

How It Works on Solana

The Verified by Concordium Keys (VCK) registry now accepts Solana keys natively. The flow is the same one Ethereum agents already use. You register your agent through the Agent Registry DApp or API. Your agent’s Solana keys are linked to a Concordium account through the VCK registry. That account is tied to a verified identity through the protocol-level ID infrastructure that has been in production since Concordium’s mainnet launched on 9 June 2021. Zero-Knowledge Proofs establish the link without exposing any personal data.

Your agent then receives the badge, verifiable on-chain, visible in explorers, and machine-readable through Concordium’s MCP server, so another agent can check it before deciding to transact.

Your agent stays on Solana. It touches Concordium once, to anchor its identity, and the badge is the proof that follows it from there.

Why This Matters Now

On Solana, real value is already moving through autonomous agents at machine frequency. Since x402 launched on the chain it has processed more than 35 million transactions and over $10 million in volume, figures that are still early but growing, yet counterparties have no standard way to know who deployed the agent moving that value.

The accountability pressures are no different from Ethereum’s: the EU AI Act is law, and running on Solana does not exempt an agent from a jurisdiction that asks who is behind it. What is distinct is the scale of agent-to-agent commerce, where one Solana agent transacts with another and no human is present to judge trust. Concordium’s MCP server lets an agent check, before it acts, whether its counterparty carries a Verified by Concordium Badge and what that badge guarantees.

The Badge Was Built to Travel

The promise at launch was that the badge would work for any agent, on any supported chain, from any supported framework. Solana is that promise in practice.

An agent on Ethereum and an agent on Solana can now carry the same mark, backed by the same verified identity, recognised by the same MCP server. What matters is not the chain underneath but the accountability that now sits on top of it.

This week marks five years since that mainnet launch. The verified identity behind the badge has secured the network since day one, and Solana is the latest ecosystem it reaches.

Agents have been anchoring to the Registry almost every day since it opened in late May, and Solana keys join that same record.

A Solana agent that anchors today proves who stands behind it to every counterparty it meets, without ever exposing the human or business doing the standing.

Register your Solana agent through the Agent Registry and claim the Verified by Concordium badge.

Originally published at https://www.concordium.com.

The Agentic Economy runs on payments. AI agents already hold funds, settle trades, and place orders without a person watching each step. That only works if the chain underneath them is solid. Not solid in theory. Solid under attack.

So Concordium asked CertiK, one of the most established names in blockchain security, to attack it.

What a Grey-Box Audit Is

Most security reviews only read the code. A grey-box audit goes further. CertiK got the source code and the design, built a live copy of the network, and spent months trying to break it. They flooded it with transactions. They sent broken messages. They cut network links. They ran hostile smart contracts. They even forced a live protocol upgrade while some nodes still ran old software.

The work ran from December 2025 to May 2026.

The Result That Matters

One promise held through every single test. The chain never recorded two conflicting versions of history.

No fork. No double-spend. No lost funds.

This is the part AI agents depend on. Picture an AI agent paying a supplier for its owner. It needs one thing above all: once a payment is final, it stays final. The audit confirms the chain delivers exactly that, even under attack.

Where CertiK did find problems, they were about speed, meaning whether an attacker could slow the chain down for a while, not about money or records going wrong. That difference matters, and it is structural. Availability can be tuned. Integrity cannot be allowed to bend.

What Got Fixed

CertiK raised 13 issues. Ten are fixed and re-checked by CertiK. Three are acknowledged, with nothing serious left open.

Two issues were the most serious. Both turned up in CertiK’s network tests, where they probed how a node handles traffic from other machines. The first (logged as CGB-03) came from the malformed message experiment: a single broken message from a connected peer could crash the part of the node that agrees on the ledger.

The second (CGB-09) came from the catch-up flood experiment: a peer could overwhelm a node by flooding it with requests. In both cases an attacker could slow or stall the chain from a distance. Both are now fixed. The chain checks incoming messages properly and limits how much any single peer can demand. Neither issue ever touched the chain’s core promise.

The next set hardened the parts AI agents will lean on hardest. A hostile smart contract that tried to hog resources can no longer crowd everyone else out. Administrative controls that should never be open to the public are now closed by default. A scan for leaked secrets came back clean: no keys, no passwords, nothing sensitive in logs or files.

The three acknowledged items are honest about what they are. Concordium decided not to add suspension/slashing because it could create griefing incentives.‍

“Our grey-box methodology goes beyond code review, we deploy the full stack, inject real faults, and measure how the system responds under adversarial conditions. With Concordium, every experiment translated into reproducible, auditable evidence. What stood out was how the team handled findings: remediations were rigorous, and we re-verified each one by re-running the same experiments that surfaced the original issue. That break, fix, re-verify loop is what turns a one-off audit into lasting infrastructure confidence.” — Luigi Girletti, Senior Blockchain Security Expert at CertiK

The Chain Was Built for This Moment

Identity came first. Payments came second. AI agents come next. Each step assumes the one before it holds.

AI agents add autonomy. They do not remove accountability. They will use the chain harder than people do, constantly, at machine speed, retrying without rest. A test that pushes the chain that same way tells you more than reading the code ever could. Concordium came through it with its core promise intact and its weak spots closed.

Security is not a one-time stamp, and Concordium does not treat it like one. Checks run on every code change. Each finding has a test that guards against it returning. Mainnet is watched around the clock.

This is the only blockchain where verified humans and verified AI agents operate on the same identity layer. Now that layer has been independently attacked and proven to hold.

You can read the full CertiK report, including every experiment, each finding, and our point-by-point responses.

Verified Humans. Verified Agents. One Protocol.

Join the Concordium Community and follow us on X.‍

Originally published at https://www.concordium.com.

You built your agent on Ethereum. It executes trades, manages portfolios, signs transactions but none of those chains can tell your counterparties who is accountable when it matters.

The Concordium Agent Registry launched on Wednesday. The “Verified by Concordium” Badge is what makes that Registry useful for any agent that lives outside Concordium.

The badge is a certification mark. It proves that a real, verified human or business entity stands behind your agent anchored on-chain, without exposing personal data, and without requiring your agent to leave the chain it was built for.

The closest analogy is how certification bodies operate in other industries. Fair Trade certifies products regardless of their country of origin or the brand behind them. IATA accredits travel agents worldwide against a single standard. In both cases, the mark travels with the product or the business and signals to anyone encountering it that a specific authority has verified specific criteria.

The Verified by Concordium Badge works the same way. Any agent, on any supported chain, from any supported framework, can earn one. The badge travels with the agent wherever it operates.

Who It Is For

Agents built natively on Concordium are verified by default. Their identity is built into the infrastructure they run on.

The badge exists specifically for agents that live outside Concordium. If your agent is deployed on Ethereum or other chains, it operates in an environment where identity infrastructure does not extend to a verified human. The badge is Concordium’s certification travelling into that environment. It is the proof that someone accountable stands behind the agent, even though the agent itself runs elsewhere.

How It Works

You register your agent via the Agent Registry DApp or API. Your agent’s cryptographic keys are linked to a Concordium account through the Concordium Verified Keys registry. That account is tied to a verified identity through the same protocol-level ID infrastructure that has been in production since the network launched. Zero-Knowledge Proofs ensure the link is established without exposing personal data.

Your agent receives the badge. It is verifiable on-chain, visible in explorers, and machine-readable through Concordium’s MCP server. Your agent stays on Ethereum. The badge is the proof that follows it.

That is the entire flow. Your agent touches Concordium once, to anchor its identity to a verified entity. Its day-to-day operations remain on the chain it was built for.

Why This Matters Now

Three developments are converging that make unverified agents a growing liability rather than a missing feature.

Agents are handling real financial exposure. Portfolio management, cross-protocol arbitrage, autonomous trading. The counterparties interacting with these agents have no standardised way to verify who deployed them. A badge visible on-chain and queryable through an MCP server changes that dynamic without requiring counterparties to trust anything other than the cryptographic proof itself.

Regulatory frameworks have arrived. The EU AI Act is law. Autonomous systems operating in regulated contexts will need traceable accountability chains. Building on Ethereum does not exempt an agent from jurisdictions that require accountability. The badge provides the anchor at the protocol level, not retrofitted after the fact.

Agent-to-agent commerce is already happening. When agents transact with other agents, there is no human in the loop to make a trust judgement. Concordium’s MCP server allows an agent to check, before interacting, whether its counterparty carries a Verified Badge and what that badge guarantees. Machine-readable accountability for machine-speed transactions.

An ERC-8004 identity gives your agent a directory entry. The “Verified by Concordium” Badge gives it an accountability anchor. The two are complementary and your agent can carry both, and the badge can be displayed alongside any other identity standard the agent already uses.

What the Badge Is Not

The badge means accountable. It does not mean endorsed.

A Verified by Concordium Badge confirms that a real, verified entity stands behind an agent and can be identified if something goes wrong. It does not mean Concordium has reviewed the agent’s code, audited its behaviour, or approved its use case.

This distinction matters and it is worth stating clearly from the outset. Accountability and endorsement are different things. The badge provides the first. What you build with it is yours.

Get Started

The Agent Registry is live. The badge is available now. If you are building agents on Ethereum or any other supported chain and want protocol-level accountability without migration, you can start integrating today for free.

• Find out more about the Agent Registry
• Visit the Agent Registry
• Connect to Our MCP Server
• Read our Docs
• Watch our Demo Video

The trust layer for agents is live. And now it travels with your agent, wherever it operates.

Originally published at https://www.concordium.com.

AI agents are executing real transactions, managing portfolios, and making decisions that involve real money. The industry now has a standard for describing what agents do on-chain: Ethereum’s ERC-8004, gives agents an identity handle, a reputation registry, and validation hooks. It answers the question of what an agent can do. It does not answer the question of who stands behind it in the real world.

That is not a flaw in the standard. ERC-8004 was designed to be permissionless. But permissionless identity without real-world accountability is not enough for the transactions agents are already executing, or for the regulated industries now evaluating whether to let agents operate on their rails.

The infrastructure to close that gap did not exist at the protocol level. Until today.‍

What Shipped Today

Concordium has launched the Agent Registry, the first protocol-level identity and accountability layer for AI agents. Any developer can now register an agent with a verifiable identity anchored to a Concordium ID and backed by Zero-Knowledge Proofs. Registration takes a few clicks, and is currently free of charge for Concordium-native wallets. It works on Ethereum and Concordium natively.

Agents on Ethereum and other chains can earn a Verified by Concordium Badge that links them to an accountable human without migrating. Stay tuned for more details

The Agent Registry is one part of a broader stack that went live simultaneously: an MCP server for machine-readable trust responses, integration documentation, and demo videos covering both native registration and the cross-chain “Verified by Concordium” Badge process.‍

Three Registries, Anchored to a Verified Human at Every Step

The infrastructure is built around three interlocking registries that together answer the questions ERC-8004 leaves open.

The Concordium Agent Registry answers “who is this agent?” and extends that answer to work on any chain. Every registered agent carries a verifiable identity tied to a Concordium account, which itself is anchored to a verified human through Concordium’s protocol-level identity layer.

Verified by Concordium Keys (VCK) answers “who owns this agent?” by linking an agent’s cryptographic keys back to a verified Concordium account. If an agent signs a transaction, VCK can prove which verified entity controls the signing key.

Verified by Concordium Domain Control (VCDC) answers “what business is behind this agent?” by linking web domains to Concordium accounts. When an agent operates under a company’s domain, VCDC establishes the verified connection between the domain, the entity, and the agent itself.

Combined, anyone interacting with a registered agent can verify its identity, its owner, and the business entity responsible for it. An agent operating on Ethereum with a Verified by Concordium” Badge carries the same accountability guarantees as one running natively on Concordium. The CCD Explorer and Concordium ID Registry DApp provide full transparency from block one.‍

Building for This Since the Beginning

Concordium’s identity layer was built into the protocol from the start. Every account on the network has always been tied to a verified identity, with Zero-Knowledge Proofs ensuring that verification works without exposing the underlying data.

That foundation did not change when the focus moved through regulated DeFi, stablecoins, PayFi, or the Smart Money thesis. What changed is what the infrastructure is now being asked to do. When Town Hall framed verified humans and verified agents operating on the same identity layer, it was describing the next application of architecture that has been in production for years.

The Agent Registry extends that architecture to a new class of participant: autonomous ones.‍

Get Your Agent an Identity Today

The Agent Registry is open. Builders who want protocol-level accountability for their agents, on any chain, can start integrating today. For free.

• Visit the Agent Registry
• Connect to Our MCP Server
• Read our Docs
• Watch our Demo Video

The trust layer for agents is live.

Originally published at https://www.concordium.com.

Exchange Listings & Liquidity

Q: The current exchanges — MEXC, KuCoin, Gate.IO — reach retail traders in Asia and emerging markets. That’s good, but the institutional and Western retail buyers who would be most aligned with the Concordium thesis (compliance-forward, regulated finance, MiCA-ready) are on Coinbase and Binance. On that topic, Kraken was a step in the right direction — are there any plans to focus on exchanges with this kind of audience?

A: Agreed and is also why we are in constant conversation with them. Binance is a whole beast in itself, which we are trying to tame, but we have a nice and open dialogue with Coinbase.

Q: Hey team, first of all, I really like the direction Concordium is taking. The focus on identity, privacy, and real-world usability feels very different from most projects right now. That said, I was checking some on-chain stats and noticed that the TVL is still quite low, so my first question is: are there any plans for listing Concordium on a major exchange to improve liquidity and overall exposure? Also, are there plans to improve the Concordium wallet further? For example, adding stablecoin support and built-in swap features could make it much more usable for everyday users. I feel like enhancing the wallet experience could really help adoption?

A: Yes to low TVL and usage, also because most of the initiatives from last year have not gone live yet. We know what we are doing. Most of the projects you would like to compare us with needed years to get to their numbers, we are only at it for 12 months. Things will change, and they will change fast, mark my words on that.

Q: Will any PLT Stable Token be available at Kraken any time soon? Any plans to develop Danish Kroner as PLT stabletoken?

A: StablR was supposed to be live already. MM etc is all done. There has been a delay by Kraken, as the biggest venue, and in my latest conversation with them it will be no later than the end of April, beginning of May.

Q: We’re seeing a lot of PayFi initiatives from larger companies like Coinbase, Mastercard etc. I think many would’ve expected or hoped to see Concordium included here. What’s your read on the PayFi space and Concordium’s impact in it?

A: A lot of noise in that space right now and we get why people are looking at those headlines and wondering where we are. But here is the thing. Those players are building PayFi on infrastructure that cannot answer the most basic compliance questions like:

• Who is this person?
• Can this payment be audited?
• Is there a legally accountable human behind this transaction?

None of them can answer that at a protocol level. We can. So when they eventually need verified identity behind a payment, and they will, because regulators will demand it, they are going to need what we have built. We are not chasing the headline. We are building what actually makes the headline work. That is a very different and in my view much stronger position to be in.

Q: Will you in the short term implement a solution for shielded transactions (again) or privacy pools? Why? Other privacy chains offer some sort of privacy like shielded transactions and privacy pools. This suits the blogpost by Pelle Brandgaerd. We need this, to provide institutions with private solutions (uniquely revocable by court order only). I believe David published a great breakdown on this, highlighting that in 2026 this is not a no-go for exchanges any more?

A: Well spotted and look, David’s breakdown was excellent on this and if you have not read it yet please do. The landscape has genuinely shifted here. What used to be a red flag for exchanges is not anymore in 2026 and that changes the conversation completely for us. Because our model, private by default but revocable by court order only, was always the right one. We just had to wait for the world to catch up a little.

Are we working on this? Yes. Is it a priority? It should be and we know that. The institutional demand for private transactions that still have a legal accountability mechanism behind them is real and growing and frankly we are one of the very few who can actually deliver that properly. Not just privacy, anyone can do privacy. Privacy with identity behind it that a court can access when it legally has to. That is the thing. So watch this space, I do not want to give timelines. I cannot stand behind but I will say the direction is clear and we are moving in it.

Funding, Runway & Token Economics

Q: In the last TH of 2025 a plan was shared for a Q2 funding round. As far as we’re aware this has not happened. Meanwhile, the organization and footprint of Concordium seems to have grown. Has the Foundation been selling lately to fund the running expenses? If yes, please provide amounts, if not how is the organization currently funded?

A: We have not sold any foundation coins. The funding round was without a doubt the best timed exercise in my life. All I can say is that the project will continue to strive for this year and beyond!

Q: Does Concordium have sufficient funds to continue in bear market. What action plan is in place/required. If we have to at some point sell tokens, fine. But that rather be at a higher price point to avoid offloading again?

A: Again, we are not going anywhere. Due to the structural changes we were also able to drive the cost base down. We are going to be around.

Q: Based on the team size and price development existing and potential new investors are looking for clarity about the potential ability of Concordium to continue operating. Can you provide clarity about the runway and how the EMG and Foundation are managing liquidity and runway?

A: All of that was covered in the TH I think. Nobody should worry about Concordium being operational for the foreseeable future. I am not, hence nor should you.

Q: Are there any upcoming initiatives aimed at strengthening the utility and demand dynamics of the CCD token within the ecosystem? Because it is very important for the balance of price and liquidity in my opinion?

A: Everything we just talked about, ID verification, PLT, sponsored transactions, and agent transactions, all of it feeds into CCD demand. This is not a one-time initiative; it is the entire architecture of the ecosystem working together. As each piece goes live, the demand will too.

Wallet Integrations & Partnerships

Q: Any update on Ledger and Bitcoin.com and X402?

A: Excellent Question and apologies we could not cover this in the TH.

1. On Bitcoin.com-> 80 MN Wallets around the world will have CCD access in next two weeks, and then the same 80 Mn Wallets will have the ability to Verify & Access by the End of the Month

2. Similarly CCD Integration on Ledger’s Mobile & Live Interfaces (Desktop Wallet) is in testing. I would expect Ledger should be able to ship this out soon to their 7+ Mn users

3. X402, the release is being submitted to Coinbase in the next few days. So hopefully if all goes well, in a few weeks, the builder will be able to find this in the marketplace. I understand everybody wants these now, and let me tell you we wanted this to be ready yesterday. But every organisation has a development rhythm, something we can only support to move faster.

Q: Will Ledger and Bitcoin.com wallets support the Concordium ZKPs, so they can be used directly for Verify & Pay and Verify & Access?

A: I think I’ve already addressed this question. The short answer is Yes.

Q: «If your stablecoin pays 4% for sitting in a wallet, that’s now illegal under the Clarity Act.» statement I picked up somewhere. Does this impact CCD partners with stable coins in any good or bad way if the statement is correct?

A: Watching it closely. What I will say is that regulatory clarity, even when restrictive, benefits players who are built for compliance from the start. That is us. So while the specifics play out we are not worried about where Concordium sits.

Q: As more partners like Coin98, Ledger, and Bitcoin.com integrate Concordium ID and age verification, how do you see the ecosystem evolving in regulated sectors like payments, gaming, or content platforms over the next 6–12 months? Are there any specific use cases you’re most excited about?

A: Gaming and age gated content are some of the most exciting near term use cases honestly. The infrastructure is there, sponsored transactions remove friction, identity verification is the missing piece those platforms have been trying to solve for years. As these integrations go live you will start seeing use cases that look nothing like traditional crypto. That is exactly the point.

AI Agents & Agentic Economy

Q: I’m curious about where Concordium is heading beyond just the tech. You’ve built a strong foundation around identity and compliance, but what’s the real plan to make users want to use it, not just need to use it? Also, from your side, what’s been the biggest blocker to real adoption so far — is it awareness, developer activity, or something inside the product itself? And one more thing I’d really like to understand. What’s coming next that can actually drive daily usage, not just partnerships or announcements?

A: I hope today and the go live of our initiatives from last year that are imminent answer your question.

Q: With autonomous agents now transacting on-chain at scale, how is Concordium thinking about the identity verification requirements for non-human actors, and what does CCD’s role look like in an ecosystem where agents are the primary transactors?

A: You heard about all the plans. We have to make Concordium a secure blockchain for agents, backed by human identity.

Q: Sponsoring transactions is a game-changer, but it carries risk for the sponsor. How does Concordium’s built-in identity layer protect sponsors from subsidizing malicious actors, and does this provide a unique competitive advantage over ‘account abstraction’ on anonymous chains?

A: Well, we are the only chain that has identity at the protocol level, meaning every account has an identity behind it. This allows for ZKP to be done on the identity before any sponsorships are agreed to. Meaning as a sponsor, you have better visibility of critical data that will help you make a decision.

Q: How is Concordium positioning itself for a future where AI-driven transactions become normal, especially around identity and compliance?

A: As I explained, every chain is claiming to be Agentic but none of them answer the three critical questions for the Agentic economy to scale, which is

1. Who authorised this agent?
2. Can the payment be audited?
3. Is there a legally accountable human?

Only Concordium can do this at protocol level. And we are aware that there are thousands of Agents on Ethereum and Solana. Our strategy is not asking those agents to migrate. But are building a trust layer that any agent can call when they need compliance.

Q: I was surprised to see the focus shift from ID to PayFi and now back to ID again. Can you elaborate on the reasons behind these shifts?

A: We wanted to ride the PayFi wave, due to the need of creating buzz and community. We seemingly have achieved that. If we would have stayed very quiet about all the things you would have hated it too. Let me put it this way, sometimes those things are detours that lead you to the actual desired objective, like in our case has been for well over a year… AI and an agentic economy. X402 was and should have been for all of you a hint, some got it, some didn’t…. Now everybody gets it.

Q: How does Concordium see AI agents using its identity and verification layer for autonomous transactions in the future?

A: Exactly how we have laid out in the TH. There is only so much you can squeeze into 1 hour, but we have been preparing for this for more than a year!

Q: I would argue that the true unlock for the CCD use case is when it is utilized by players/entities outside the Crypto environment. Do you agree? If so, what conditions would need to be met for mainstream (non-crypto) players to find CCD genuinely compelling?

A: 100% agree and honestly this has always been the vision, from day one. The crypto native audience is not who we are building for ultimately. The conditions are not that complicated when you break it down. They need to not know they are using a blockchain. The experience has to feel like anything else they already use. Second, their legal team needs to say yes, which means the compliance has to already be built in, they are not going to integrate something and then figure out the regulatory side, it does not work like that. And third, and this is the big one, when something goes wrong they need to know who is accountable. That question kills every other chain in an enterprise conversation. Every single one. Because they cannot answer it. We can, because every account has a real identity behind it. So are we there yet? Not fully. But are we closer than anyone else? Absolutely yes and the gap is only getting bigger in our favour!

Q: When will you promote CCDExplorer to main blockchain explorer? CDDscan remains faulty and ugly?

A: We’re not going to disagree with you there. CCDScan has real limitations and CCDexplorer addresses them properly. We will make a call on this and communicate it clearly rather than let it drag on indefinitely. Fair point and thank you for raising it.

Q: What is up with sequence x3 and then adoption x3? Missing adoption in the chain metrics…. We need use cases, also in buidl season?

A: You are right to flag this. The metrics will look different once the initiatives from the last 12 months actually go live, which is imminent. Buidl season is not an excuse for empty chain activity and we know that. The use cases are coming and they are coming fast. The numbers will catch up.

Q: India is a massive market with strong crypto adoption, but still faces regulatory uncertainty and limited government support. Given Concordium’s identity layer and compliance-first design, how do you see the protocol positioning itself in such markets? Are there specific strategies or partnerships being explored to enable adoption in regions like India where regulation is still evolving?

A: Our compliance-ready design is an advantage in evolving regulatory environments. Much easier to comply when the rules arrive if your infrastructure was already built for it. India is a market we are watching closely and very open to partnerships there. If you have connections, reach out.

Q: Just wondering, as stablecoin and real world use cases grow, how do you plan to maintain that balance without compromising either side?

A: Great question and look, people ask this a lot and I get why. But honestly the way we built this, it is not really a balancing act. ZKPs mean you prove what you need to prove and nothing else ever leaves your hands. The compliance is there, the privacy is there, same mechanism. We did not add this on after the fact like most chains are trying to do right now, it is in the protocol from day one. So as things scale, as more stablecoins come, as more real world use cases go live, the model just gets stronger. We are not going to wake up one day and have to choose a side. That was never something we were willing to do!

Q: With P10 sponsored fees now live and the PayFi stack feeling more complete, what are the biggest user experience improvements you’re planning next for everyday people who aren’t deep into crypto? Any focus on making onboarding or daily payments even smoother?

A: The goal is simple, you should not know you are using a blockchain. No gas, no seed phrases thrown at you on day one, no complexity. Sponsored transactions was a huge step because the fee problem just disappears for the user. What comes next is making the onboarding feel like signing up for any other app. And then making payments feel like any other payment. That is the bar we are measuring ourselves against, not other crypto apps. Regular apps that normal people use every day. We are not there yet but we are closer than we have ever been!

Q: How is Concordium positioning itself against other chains also exploring ZK and compliance ready infrastructure?

A: Sure, every chain is claiming to be the next-gen privacy chain with a ZK proof use case and compliance-ready right now. But none of them have an identity at the protocol level. That is the difference. You can add ZK proofs onto an anonymous chain, but a majority of them cannot answer the question of who is legally accountable. We can, because every account on Concordium has an identity behind it.

Q: How does Concordium plan to position itself as the go-to blockchain for regulated industries over the next 2–3 years?

A: By being the only chain that answers the three critical questions for any regulated transaction. Who authorised this, can it be audited, is there a legally accountable human. In two to three years when regulation has caught up with where we already are, that positioning will feel obvious. Right now it just feels early. Both can be true!

Q: How is Concordium planning to balance strong on-chain identity with user privacy as adoption grows across different regions?

A: ZKPs. The user proves what needs to be proven without revealing the underlying data. Different regions have different requirements and ZKPs let us meet all of them without building separate systems for each jurisdiction. Most chains make tradeoffs as they grow. We built it so that we do not have to.

Q: As more real-world payment use cases grow, how is Concordium ensuring its identity layer remains seamless for everyday users while still meeting institutional requirements?

A: Sponsored transactions handle the gas problem. ZKPs handle the privacy problem. The identity check happens in the background. The user experience feels like any other payment app. The institutional requirements are met underneath without the user ever seeing them.

Q: What is the next major milestone for Concordium that will signal real mainstream adoption, not just ecosystem growth?

A: Watch for Bitcoin.com live, Ledger integration shipped, StablR on Kraken, and the first verified agent transactions on chain. Those four together are not just progress, they are a step change. And they are all imminent.

Q: How does Concordium plan to become the go-to blockchain for institutions, and what key milestones should the community watch for to measure that progress?

A: Same answer. Bitcoin.com, Ledger, Kraken, verified agent transactions. Watch those go live and you will see exactly where this is going. We know what we are building and we know why it matters. The community will see it too, very soon.

Q: • Operational resilience: most of us do not doubt if the chain can handle real usage and counterparties — do have any hard indications? • Investor sequence: who comes in after the early believers (Hilbert), and why? • Leadership conviction: does management truly see the path, or are they still narrating possibilities?

A: On resilience the chain handles what we need right now and is built to scale. On investors the funding round timing speaks for itself and the conversations happening now are with exactly the right capital for this stage. On conviction, I would not still be here doing this if I did not see the path clearly. This is not a narrating possibility. This is executing on a plan that has been in motion for over a year. This Town Hall should make that very clear.

Q: 💭 A question I’d like addressed during the Town Hall: How will Concordium scale its identity-based infrastructure while maintaining decentralization and user privacy?

A: ZKPs at the protocol level mean decentralisation and privacy are not sacrificed for compliance, they are part of the same system. The architecture scales without needing to centralise anything. Most chains make tradeoffs as they grow. We built it so that we do not have to.

PayFi, Payments & Stablecoins

Q: Protocol 10 just completed the payment stack, which is of course a big milestone: So naturally, what comes next on the technical side? What should builders and the community actually be paying attention to over the next 6–12 months?

A: As you heard, we have our PLL under construction and are also focusing on Agentic infrastructure.

Q: How does Concordium plan to make crypto payments feel as seamless as card payments for end users over the next 12 months?

A: Sponsored transactions live with P10 remove gas friction entirely for the end user. They just pay. The blockchain complexity is invisible. Combined with the Concordium Pay stack and the wallet integrations going live now, the goal is zero visible blockchain in the experience. You should not have to know you are using Concordium for Concordium to be working. That is the standard we are building to.

Q: Now that sponsored transactions are live with P10, how do you envision Concordium Pay being used by merchants and regular users in everyday scenarios? For example, will there be more focus on making it feel like a seamless alternative to traditional payment apps, or are there specific use cases you’re prioritizing first?

A: So the way I think about it, you start where identity actually adds something that a normal payment app cannot. Age gated commerce, regulated products, cross border payments where KYC is a headache for everyone involved. Those are the places where we are not just an alternative to a traditional payment app, we are genuinely better because the compliance is already there. You do not have to do anything extra as a merchant, it just works. And then as that gets comfortable and people are used to it, the everyday payments piece follows naturally. But trying to replace Revolut on day one is not the play. Win where we are uniquely better first and let the rest follow!

Identity, Compliance & Regulation

Q: When will the ID app be put to use? Quite some development is still required from UX perspective?

A: We have been busy building features into our ID app. We are almost done with the features and will focus mainly on UX in the coming weeks.

Q: How is Concordium strategically positioning itself to onboard real-world enterprises at scale, and what role will its identity layer play in accelerating that adoption?

A: The identity layer answers every enterprise compliance question. That is not a product feature, that is the entire value proposition. As MiCA and equivalent regulations roll out globally the enterprises that need a compliant blockchain will find Concordium was the only one actually built for them.

Privacy, ZKPs & Decentralisation

Q: First Question: Adoption is the goal, right ? but what does that actually mean? Is success for Concordium going to be measured by: 1. Users? 2. Enterprise adoption? 3. Transaction volume? And how is Concordium turning integrations into real usage ? Second Question Concordium’s core idea is very clear: Privacy, Identity, and Compliance So here is the real question: How do you balance privacy and regulation without compromising either? Thank you team?

A: All three, but they build on each other naturally and that is the part people miss. Enterprise brings the use cases, users follow the use cases, volume follows the users. You cannot skip steps. What I will say is that we are not sitting here chasing vanity metrics or trying to win a dashboard comparison with chains that have been around for 5 plus years. We are building the right way. And look, Bitcoin.com going live for 80 million wallets, Ledger for 7 million users, these are not small things. That IS the turning point people have been asking about. Real access drives real usage and that access is finally, finally here. Give it time and mark my words, the numbers will follow!

Q: Where does shielded transaction development stand? The privacy category is outperforming; Concordium should be capturing that narrative more aggressively?

A: Well spotted my friend and honestly you are right, we should be louder about this. The regulatory environment has shifted significantly and as David highlighted in his breakdown, shielded transactions with court order only revocability are no longer a non-starter for exchanges in 2026. That changes everything for us because that is exactly the model we have always believed in. Private by default, accountable when it legally matters. No other chain can offer that combination with identity at the protocol level. We are actively working on this and I would say watch this space very closely over the coming months because I think this is going to be one of the narratives that really puts Concordium on the map with institutions.

Q: Solutions like Concordium Pay show strong real world potential. Coming from Asia where privacy is most neglected I want to ask that which geographic regions are currently viewed as the highest priority for scaling such use cases?

A: Asia and Middle East near term, regulatory environment and adoption rates make them the right starting point. Europe is important given MiCA and we are positioned better there than almost anyone. Not ignoring Western markets, just sequencing properly rather than being everywhere at once and doing nothing well.

Q: How does Concordium plan to balance its strong compliance and identity layer with the broader crypto community’s demand for privacy and decentralization as adoption scales?

A: Look decentralisation does not require anonymity, that is the thing people conflate. Our identity layer is protocol level but it is not surveillance. You control what you disclose. Regulators get what they need. That is honestly a more real version of privacy than no identity at all.

Adoption & User Experience

Q: What are Concordium’s expected growth timeline and adoption trajectory, and how will these translate into CCD trading volumes over time?

A: We are expecting several thousand agents operating on the chain in the coming 2–3 months. Apart of course things like bitcoin.com going live etc etc.

Q: What are Concordium’s expected growth timeline and adoption trajectory, and how will these translate into CCD trading volumes over time?

A: Several thousand agents operating on chain within 2 to 3 months. Bitcoin.com and Ledger going live in the very near term bringing in users who have never touched Concordium before. StablR on Kraken by end of April or early May. Volume follows utility, always has always will. I have said this before and I will say it again, things will change and they will change fast. Just watch.

Q: What’s currently the biggest bottleneck slowing down development or adoption?

A: Honestly? Getting the initiatives from the last 12 months live and in peoples hands. The building is done or nearly done. The bottleneck now is go live timing across partners and platforms, which we cannot always fully control. But everything is moving right now.

Q: Does concordium have plans of IRL events and onboarding? If yes how?

A: More to come on this.

Q: Can I propose a project to Concordium? Something that will help adoption and scalability of this project in my region?

A: Absolutely yes. Reach out through the official channels.

Technical Roadmap & Developer Ecosystem

Q: Upon the announcement of the Spiko use case a first transaction was promised in Q4 ’25. In Q4 this was delayed to Q1, we’re now past that as well. Can you provide clarity around why these promises have not been delivered upon?

A: Various reasons, but also changing priorities on our side. A lot of it was dependent on the PLLs and due to that priority shift we expect to see development there over the course of the coming months.

Q: Quantum cryptography was on your roadmap a while ago. Do you agree to the premise that solving this will be necessary to truly unlock Concordium’s use case, and if so, how are you approaching it?

A: Yes, we agree with the premise completely. It is not something that is blocking our current use cases; the things we are building and shipping right now are not waiting on quantum resistance. We are approaching it methodically. When there is something concrete to share, you will hear about it.

Q: What’s new for devs this time?

A: x402 being submitted to Coinbase marketplace in the coming days is the big one for builders. New payment primitive, actually buildable on. PLL infrastructure under construction. And for anyone building for the agentic economy, a compliant identity aware platform that no other chain can offer. More details dropping soon!

Q: Will you re-enable grants and support for companies that are developing and implementing Concordium network in their project?

A: Working on the right structure for this and will communicate when ready.

PLT & Protocol Assets

Q: Since you guys introduced the PLTs and it was a very interesting technology for me, do you guys have something else of that sort which will be unveiled in the future?

A: Yes! Without giving too much away, the PLT model opened up design space that we are very actively exploring. Programmable, compliant, identity aware assets are just the beginning of what is possible when you have identity at the protocol level. There is more coming and when we are ready to talk about it you will hear about it here first.

Regional Strategy & Government Initiatives

Q: How do you view the various government initiatives to establish digital identities for citizens? Does that constitute a threat, synergy or not significant to the CCD use case?

A: Synergy, mostly and actually more than people realise. When governments build digital identity infrastructure they are doing something very important for us, they are normalising the idea that identity should be verifiable online. That is a massive cultural and regulatory shift that plays directly into what Concordium has been building. The difference is user control and cross border portability. A government issued digital ID works inside one jurisdiction. Concordium’s identity layer works everywhere and the user controls what they disclose. So rather than competing with government initiatives we sit on top of them and extend them. That is a very comfortable place to be.

Community, Marketing & Transparency

Q: Do you read David’s blog? Are there granular breakdowns that are of interest for strategic decision making?

A: We love David and absolutely keep an eye on his blogs as well as his YouTube Videos. Like you said he is great at spotting strategic opportunities, and also doing those breakdowns. If you’ve seen his latest content on “Who Owns the Infrastructure When AI Spends Your Money?” Hopefully the Townhall has given you enough to know, this was always the plan, we’ve just brought this forward.

Q: Many of us have been supporting the ecosystem for quite a while now. Are there any plans to introduce more incentive or ambassador type programs for active community contributors?

A: Details to follow but in the meantime we do have an ambassador programme live.

Q: In the introduction with Lars, Boris mentioned the importance of transparency. The former management issued transparency reports, why has this stopped?

A: We will look at reinstating structured reporting. Thank you for raising it.

Q: What’s the team’s strategy around overall engagement, including posting and interaction across marketing and team members, and is there a specific reason for the current low activity from team members?

A: Fair point, it has been lower than it should be, we hear you. As things go live there will be more to point to and you will see more from the team publicly. We are working on it.

General & Strategic Outlook

Q: What’s the future of Concordium after two years?

A: A functioning agentic payment layer with verified human accountability behind every transaction. Institutional grade stablecoin infrastructure is live on regulated exchanges. An ID layer that non-crypto companies are actively building on. And a community that watched everything we said come true. That is the two year picture and I am very comfortable saying it out loud.

Hey Concordium Community!

This summer, Concordium will hold the 2026 Governance Committee election, where three community representatives will be elected to the committee. To ensure that the election remains private, secure, and decentralized, we are once again inviting members of the community to participate as Guardians.

If you want to take part in one of the most important governance processes on Concordium — and earn some CCD along the way — this is your chance.

What Is a Guardian?

Guardians play a critical role in Concordium’s on-chain voting protocol. Their task is to help run the cryptographic process that keeps votes private during the election and ensures that the final result can be verified.

Using specialized software called the Guardian application, Guardians generate cryptographic keys that are used to encrypt and later decrypt voting ballots. The votes remain encrypted throughout the election and are only decrypted collaboratively once voting has ended.

Because the decryption key is distributed among multiple Guardians, no single party can access the votes or manipulate the election outcome. This ensures that the election remains transparent, secure, and decentralized.

In short, Guardians act as a community-driven election commission helping to safeguard the integrity of Concordium governance.

What’s Required to Be a Guardian

Participating as a Guardian is straightforward, but it does require availability during several phases of the election process.

• Have a laptop or desktop computer with a reliable internet connection
• Be able to install and run the Guardian application provided by Concordium
• Have a Concordium Mainnet and Testnet account accessible via the browser wallet
• Have about ~100 CCD on your account balance to pay transaction fees
• Be available to participate in the scheduled election phases listed below‍

Running the Guardian software typically takes only a few minutes per step, but Guardians may need to check in periodically over several days depending on coordination with the other participants.

For the 2026 election, 11 Guardians will be selected from community volunteers. Anyone from the Concordium community may apply, provided they are not running as a candidate in the election.

Selected Guardians who successfully complete all required steps will receive $100 worth of CCD.

Election Timeline

• Guardian Registration (April 16 — April 24): Community members can apply to become Guardians by submitting the signup form.
• Guardian Selection (April 24 — April 28): Selected Guardians will be contacted and provided with further instructions.
• Testnet Dry-Run (May 2 — May 22): The Testnet dry-run is a practice run of the election protocol on Testnet. Guardians generate keys and participate in the voting and tally processes to ensure that everything works correctly before the Mainnet election.
• Mainnet Election Setup (May 30 — June 5): Guardians generate the cryptographic keys that will be used for the live election.
• Mainnet Voting (June 6 — June 19): Community members cast their votes through the voting dApp.
• Mainnet Tally Decryption (June 23 — June 26): Guardians jointly decrypt the final vote tally and publish the election results.‍

Why Become a Guardian?

Contribute directly to Concordium’s decentralized governance Help ensure that the election remains secure and transparent Gain hands-on experience with Concordium’s on-chain voting protocol Earn $100 worth of CCD for your participation

Most importantly, you’ll help demonstrate how community-driven governance can operate securely on-chain.

How to Apply

Applying is simple. Just complete the signup form with your contact details and Concordium account information.

If selected, we will guide you through the process and provide instructions for installing and running the Guardian application.

Sign up here: Form

Learn More: On-chain Voting Protocol, Election Rules 2026

Originally published at https://www.concordium.com.

Regulated payment infrastructure has a missing piece: a production stack that combines instant settlement with built-in compliance. This partnership builds it.

Payments are broken for regulated industries. Not because the rails are slow; Bitcoin Lightning fixed that. Not because compliance is impossible as ZKP-based identity solved that. The problem is that no one has combined both into a production-ready stack.

Concordium is partnering with Utexo, the leading platform for USDT settlement on Bitcoin’s Lightning Network, to deliver the first integrated solution for compliance-ready, private payments across high-risk verticals and the emerging agentic economy.

What the Partnership Delivers

Utexo is a UAE-based blockchain infrastructure startup building native USDT settlement on Bitcoin via Lightning and RGB. Backed by Tether and Franklin Templeton, it brings private, low-cost transaction infrastructure with credibility on both the crypto-native and institutional sides.

On the settlement side, Utexo delivers instant, low-cost, predictable-fee settlement. Client-side validation keeps user data private by default.

Concordium contributes the identity layer: ZKP-based verification that lets businesses and AI agents demonstrate compliance without exposing underlying personal data. The framework is built to global standards and already in production with regulated institutions including Spiko and Uphold.

Together: speed, privacy, and regulatory-readiness in a single stack.

The Immediate Market: Gaming and High-Risk Payments

The partnership launches with a direct focus on online gaming, sports betting, and adult content; three verticals where the gap between operator needs and available infrastructure is sharpest.

Following credit card deposit bans by major platforms including DraftKings, operators representing an estimated 70% of market share are looking for alternatives that do not force a choice between cost, speed, privacy, and compliance. Existing crypto rails offer some of these. None offer all of them.

The combined offering closes that gap: Lightning settlement, ZKP-backed age and identity verification, and configurable fees that give PSPs and operators predictable cost structures. The joint pipeline covers 300+ companies across PSPs, exchanges, enterprise wallets, and agentic businesses. Onboarding is already underway ahead of deeper technical integration.

“Every payment operator in gaming knows the problem: you can have fast settlement, or you can have compliance, but never both in the same stack. We are partnering with Concordium to eliminate that trade-off. With Concordium’s identity layer, operators can now settle natively in USDT on Bitcoin with instant finality and configurable costs, while ensuring counterparties are verified — whether those counterparties are humans, businesses, or AI agents acting autonomously on their behalf,” said Utexo CEO Viktor Ihnatiuk

The Larger Opportunity: Payments for the Agent Economy

AI agents are executing complex tasks autonomously. Increasingly, those tasks involve moving money like procuring services, settling invoices, managing subscriptions, executing trades. The infrastructure question this raises is not a future concern. It is live now: how do you verify the identity of a transaction when the party executing it is not human?

Concordium’s Agent Chain framework answers that directly. It enables AI agents to carry verifiable, ZKP-backed identities allowing any counterparty, regulator, or system to confirm an agent’s legitimacy without accessing the underlying data. Paired with Utexo’s Lightning settlement, this creates the infrastructure for compliant agentic payments: agents that can prove who they are and settle what they owe, in seconds.

The companies building trust infrastructure today will define the rails on which the agentic economy runs.

This partnership puts Concordium at that foundation.

Join the Concordium Community, follow us on X.

Originally published at https://www.concordium.com.

Creator platforms are scaling faster than the systems built to regulate them. As markets across Latin America and Europe sharpen their expectations around age-gated content, the platforms must verify users, while protecting user privacy by not collecting or storing sensitive data.

Snappy, a creator platform with strong early traction in Brazil, has taken a bold step by integrating Verify with Concordium ID as a viable alternative to traditional verification methods. Thousands of creators and tens of thousands of users in Brazil will now be able to create and use a single private credential for the seamless verification without compromising their privacy

The Problem with How Platforms Verify Today

New regulations and the rise of AI have created a verification problem on the internet. However, most platforms still rely on document uploads: passports, driving licenses, selfies matched against government IDs. That creates many compounding problems.

Users want privacy-preserving means to verify themselves. Uploading sensitive documents multiple times to access age-gated content is a significant friction point, and many choose to skip the platform leading to huge drop off in conversion rates for businesses.

Traditional ID checks create honeypots of sensitive data and AI has dramatically increased the risk and value of personal information. Every platform that stores identity documents becomes a target. Biometric data and government IDs collected at scale represent exactly the kind of breach that regulators and users remember.

Lastly, for regulators, auditable compliance and measurable enforcement are critical. The UK’s Online Safety Act, the EU’s Digital Services Act, and emerging US frameworks all demand the same thing: proof that verification is actually working, not just in place.

How Verify with Concordium ID Works on Snappy

Concordium’s approach separates identity verification from identity exposure. Users complete a one-time check with a trusted ID provider. The Concordium blockchain assigns an encrypted on-chain identity object that contains none of the user’s personal information. From that point, Snappy receives only a zero-knowledge proof; a cryptographic confirmation that the user meets an age or eligibility threshold. Nothing more is transmitted or stored.

The platform gets the confirmation it needs. The user retains full control over what they share. The regulator has a clear audit trail. No document repository sits on Snappy’s servers. No personal data is passed between systems.

This design matters in Brazil specifically. With over 16 million digital asset holders and more than $100 billion in annual crypto transaction volumes, Brazil is one of the world’s most active crypto markets and one where regulatory expectations around age-gated platforms are actively rising. Snappy is now positioned to meet those expectations without rebuilding its access infrastructure later.

Creator Platforms Need Real World Infrastructure

Verify with Concordium ID gives Snappy the foundation to expand access controls alongside its creator ecosystem including token-gated content and crypto-native interactions that require verified eligibility. The identity layer that handles age verification today becomes the same layer that supports more sophisticated access models tomorrow.

For creators, it means their audience can access content without friction or document uploads. For users, it means verified access with nothing handed over to a database. For the platform, it means entering new markets with an identity infrastructure already in place.

Concordium is the only Layer-1 blockchain with a built-in identity layer. As creator platforms mature across the world, the question isn’t whether compliance is coming; it’s whether the infrastructure underneath can handle it without compromising what made the platform worth building in the first place.

Check out Snappy ‘s offering.

Originally published at https://www.concordium.com.

There is a moment most people remember the first time they send crypto. You paste the address, you look at it, and then you look at it again. A long string of characters that doesn’t tell you anything.

• No confirmed name on the other end
• No bank to call
• No recourse window

What I learned from my version of that moment was not that crypto was broken. It was that we built a very effective settlement layer, and then treated authorisation as optional. In every mature payment system, this comes in sequence. You establish who you are paying, and under what conditions, before settlement becomes final. Crypto skipped that step, and that is one of the main blockers to institutional adoption.

The Card Tap That Crypto Still Can’t Replicate

Think about what happens when you tap a card. Before money moves, an authorization message flows through the network. It carries structured information that each party can act on like merchant identity, risk signals, routing details, and settlement only follows once trust is established.

Blockchain transactions invert this sequence. Settlement is the first event. Everything that creates trust, who is sending, to which legal entity, for what purpose, and under which policy, is pieced together after the fact, if it is reconstructed at all.

This is an infrastructure sequencing problem. And the pressure to fix it is now coming from both regulation and market demand.

Three Dates That Changed the Conversation

In the EU, Travel Rule obligations for crypto asset transfers moved from “coming soon” to “in force” at the end of 2024. Compliance teams stopped treating this as a pilot problem and started treating it as a production one.

In June 2025, FATF agreed updates to Recommendation 16 on payment transparency, with a stronger focus on fraud and error prevention alongside AML. That may sound incremental, but it changes how systems are designed. The implementation horizon runs to end 2030, but the institutions that will handle this well are already building toward it.

In the US, the GENIUS Act brought stablecoin issuers clearly within Bank Secrecy Act obligations. Inside institutions, the question changed. It stopped being “does this apply?” and became “how do we build this into the flow without slowing everything down?”

That question only has a clean answer if authorisation is built into the process before settlement.

Trust by Design, Not by Accident

For stablecoins to work as everyday B2B rails, they need to produce the same outcomes other payment systems produce. Beneficiary assurance before settlement. Structured payment context that travels with the transaction. A clear liability model for when something goes wrong.

If a finance team cannot verify the counterparty before sending a six-figure payment, the system will not be used, regardless of how fast settlement is.

None of this requires abandoning open, permissionless networks. The more practical approach is to keep settlement open, and add a trust layer around it. Let the open network handle value transfer. Let the trust layer handle context, verification, controls, and audit evidence.

Privacy and trust do not have to conflict here. If designed properly, selective disclosure and secure messaging allow the right information to be shared with the right parties, without turning every transaction into unnecessary data exposure.

The address anxiety I started with is not inevitable. It is a design gap. The goal is not to remove the open address model, but to give it the context, trust, and recourse mechanisms that payment systems require.

It is the missing layer required for these systems to be used at scale.

About the Author

As an early member of the Financial Crypto community, Pelle Brændgaard built pre-blockchain crypto platforms, helped develop OAuth, and brought Bitcoin to Africa with Kipochi. He brings over 25 years of experience working in fintech, banking, blockchain, and decentralized identity in Europe, the US, Africa, the Caribbean, and Latin America.

Originally published at https://www.concordium.com.