Solana Breakpoint in London has artificial grass on the floor. That's one way to get crypto people to touch some.
Our CEO @Machacek_Ondra is there. So far he's sent three photos and zero words, so we're assuming it's going well.
Say hi if you spot him.
In two weeks, our developer Daniel Rolník (@dRolnik) will be presenting a peer-reviewed paper in The Hague, at the DeFi workshop of ACM CCS, a top security conference.
It's about @onrefinance's token (solana:5Y8NV33Vv7WbnLfq3zBcKSdYPrk7g2KoiQoe7M2tcxp5), backed by money locked into insurance contracts for months, with little kept as cash. If a few big holders sell at once, the cash runs out and everyone else has to wait.
The fix in the paper (already live), lowers the price a bit when lots of people sell at once, so the cash lasts. Even after a big sell-off, small sellers in the tests still got 99.9% of the full price.
Proud of you, Daniel. Co-written with @homoliak (@FIT_VUT) and @TheodoreGeorgas (@onrefinance).
Our developer @dRolnik went to Build Station Prague to mentor. He came back with two prizes.
He also joined the @treetino_corp team, and they took 2nd place overall and won the @MarinadeFinance track.
Congrats to every team that shipped, and thanks @SolanaCZE for a great week!
Monday at Build Station Prague, from Dan's table.
Teams kept coming over with questions. A few of the projects he worked through with them:
→ SingIt, which lets you give an AI agent a spending limit from your own wallet. Daniel went through how to make it more secure.
→ A learning platform for people new to crypto
→ An options trading platform built on Raydium
Good luck to every team heading into Demo Day!
Day 3 at Build Station Prague, and our developer @dRolnik is mentoring today.
50+ builders are spending five days shipping their projects for the @colosseum Crypto World's Fair.
At Marina Pivovar? Come find Daniel.
Big thanks to @SolanaCZE for making it happen.
Day 3 at Build Station Prague, and our developer @dRolnik is mentoring today.
50+ builders are spending five days shipping their projects for the @colosseum Crypto World's Fair.
At Marina Pivovar? Come find Daniel.
Big thanks to @SolanaCZE for making it happen.
More than 90 banks and credit unions in North Dakota can now pay each other in a stablecoin, and none of them had to build anything.
@Fiserv switched on Roughrider Coin, the @BankofND's dollar stablecoin, inside Commercial Center, the online banking screen their staff already use for interbank transfers.
Most small banks will get stablecoins exactly this way, as one more option from the core provider they've run on for years.
Most of these banks never had a crypto strategy, and now they don't need one. Their vendor made the decision for them, and the board approved it as a routine software update.
The protections people are asking for already exist in card payments. Chargebacks, fraud monitoring and deposit insurance are decades old and don't need to be reinvented on a blockchain.
What's missing is someone who stands behind the payment when it goes wrong. For most stablecoin teams, that means working with a bank or an insurer from day one instead of trying to build that trust alone.
Canada's six largest banks, @RBC , @TD_Canada, @scotiabank, @BMO, @CIBC and @nationalbank, are exploring a single shared network for Canadian-dollar tokenized deposits, rather than issuing a stablecoin.
Before any of it works, six competing banks have to agree who runs the network, who can join, and whose rules apply when a payment goes wrong.
Those answers get written into the system at the start, and they're very hard to change once money is moving through it.
If you're planning something similar inside a bank, that's the work to budget time for, because the governance will shape the product long before the code does.
The @ecb opened Pontes this week. Banks can settle tokenized securities in central bank money instead of running the cash leg on the old rails while the bond sits on a new one.
In the same announcement the ECB said it will put a small portion of its own funds into digital bonds from euro-area governments, agencies and European supranationals. Preparatory work first. The board sets timing once that finishes.
They already have every consultant in Europe. They still chose to learn this by becoming a buyer.
When you design a tokenized product, the money that settles the cash side is an early lock. Until Pontes, institutions often had to choose between a new DLT rail and settling the cash in central bank money. Pontes puts both legs there. The ECB is also preparing to buy some of these bonds itself, so its own teams learn the stack by using it.
.@circle launched @arc public mainnet yesterday. Fees on the chain are paid in USDC, and the companies producing blocks include @BlackRock, @Visa, @Mastercard and @The_DTCC.
Until now, Circle issued USDC and other companies' blockchains moved it. With Arc, Circle owns both the money and the network it runs on.
That changes what choosing a chain means. You're not comparing fee curves on yet another blockchain.
You're building on the issuer's own rail. One company controls the token you pay fees in and the network that settles your transactions.
On most public chains, validators are anonymous and easy to replace. On Arc they're named companies with regulators and legal teams.
That cuts both ways. Someone is accountable if something goes wrong, and someone can stop a transaction. Once your product depends on that setup, it's hard to walk away from.
@aave V4, @Morpho, @Uniswap and others are already live on Arc.
The DeFi apps are the obvious part. The more interesting part is the other products Arc is going after.
It's built for payouts that never leave USDC, and for swapping between stablecoins without leaving the chain. It's also courting company treasuries and tokenized collateral.
AI agents can pay for things on it too, without first buying a separate token for fees.
If your product runs on dollars end to end, Arc was designed for you. If you just need another general-purpose blockchain, there are already dozens.
.@aave put up an ARFC for Aave V4
Institutions borrow stables against collateral that never leaves a regulated custodian. First cut is bitcoin:native at @Anchorage, represented onchain as non-transferable custody tokens so the protocol can treat it as collateral without moving the assets.
Most DeFi lending still assumes collateral sits in the smart contract. Institutions often can't do that. A mandate, an auditor, or a regulator already decided where the assets live. This proposal builds around that constraint instead of asking them to break it.
Treat custody as an input to the first design. That choice locks how collateral gets recognized, who can seize it, and what the auditor will sign.
.@truemoney is the e-wallet much of Thailand already pays with. This week it said it's putting a Thai baht digital unit, THBT, inside that same app, with @FireblocksHQ running custody and keys underneath. It's a @bankofthailand sandbox pilot, not a full commercial launch.
There's no new crypto app, no seed phrase to write down, and no moment where a user has to decide whether they trust blockchain.
Most consumer blockchain products still ask someone to download a second app and start from zero. TrueMoney never asked.
Custody and keys sit under TrueMoney's brand. Users never meet Fireblocks. That is what "crypto inside" looks like when someone already owns the payers.
Revolut disclosed a data leak last week. Attackers posed as a government agency, sent a formal request for customer records, and got identity data plus bitcoin transaction histories back.
The ask went through the compliance path. Email, a PDF, someone deciding it looked legitimate. No break-in on the product. The channel did its job.
Licensed products treat that path like legal process. Payment flows get authentication and logging. Shared inboxes get a person's gut feel.
If it can release customer data, build it like a payment flow. Revolut left it as a shared inbox.
Canada's banking regulator just said tokenized deposits are deposits under existing law. Same bank, same claim, same insurance. No new framework coming.
For a lot of banks, "waiting on clarity" was why the project never started. In Canada that excuse is gone.
What's left is the part nobody wanted to own: which ledger, who holds the keys, how it reconciles with core banking, what happens on a bad day.
Those choices are slow and painful to reverse. The banks that start them now will be live while everyone else is still scoping.
And that's the work we do with clients once the legal question is settled. The architecture you can still live with for years.
Consensys just split MetaMask nto its own consumer business, away from the institutional infrastructure side.
MetaMask gets better when it asks the user for less. Institutional infra gets better when it asks for more: who approved this, who can see it, can you prove it later.
Those are opposite success metrics. Keep them under one consumer-facing brand and you water both down. Spinning MetaMask out is treating them as different products, which they already were.