April 2026
One core, many instruments.
Stablecoins, tokenised deposits, CBDC-linked flows, and tokenised assets do not land in the bank the same way. If several matter, the bank cannot afford a separate middle for each one.
Series
Banks, new rails, and digital assets: a practical starting point
This series is for bank leaders and teams working through what new rails, tokenisation, and digital-asset activity mean in practice. The point is not to add another layer of commentary. It is to make the operating decisions clearer.
Why this series exists
The market is noisy. Banks still need to decide.
Banks are moving from a world built around a small number of major rails into one where they may need to absorb more networks, more instruments, and more forms of digital-asset activity over time.
That does not just create a product question. It creates a capability question across operating model, Treasury, control design, ownership, and architecture.
Start here
Begin with the frame, then move into the operating questions
The market is noisy. Banks still need to decide.
Crypto, tokenisation, and new rails generate plenty of commentary. The harder question for banks is what they need to change in practice.
March 2026
Do banks really need crypto? Only where it solves a real banking problem.
The question is not whether crypto matters in the abstract. It is where new rails solve a real banking problem strongly enough to justify the operating change.
April 2026
Domestic banks should not copy global-bank roadmaps.
Digital-asset strategy should follow the bank's footprint, product mix, and role choice. Copying a global-bank roadmap often imports complexity before there is a business case for it.
March 2026
Why new rails become a Treasury decision first.
New rails do not just change how money moves. They change when liquidity becomes usable, how funding is timed, and what Treasury needs to control in real time.
March 2026
If you're launching 24/7 rails, ask if your bank is really 24/7.
A bank can keep digital channels open around the clock and still rely on delayed controls, overnight exception handling, and next-morning repair underneath. That gap matters quickly once new rails demand more continuous operating discipline.
March 2026
Tokenisation isn't the issue. Market infrastructure is.
Issuing a tokenised instrument is often the easy part. The harder question is whether the surrounding market infrastructure is strong enough to support it credibly.
March 2026
Most crypto pilots prove the tech. Very few prepare the bank.
A pilot should not only test whether the technology works. It should show whether the bank has a credible path to getting ready for what comes next.
March 2026
Crypto custody isn't just a vendor decision.
The hard question is not whether a bank should build custody itself or use a partner. It is which control model the bank is prepared to own.
What you will find here
Decisions on scope, Treasury, controls, architecture, and market readiness
Some notes are broad myth-busters. Others are narrower operating or market-structure pieces. Together they work as a practical series rather than a stream of isolated articles.
- What to do now and what to defer
- What can be reused and what needs to change
- Where control design and Treasury impact matter most
- Which decisions should not sit inside one team alone
Continue the conversation
If these questions are already live inside your bank, we should talk
The writing is intended to make practical decisions clearer. The next step is usually a working conversation about your specific operating context.
Book a conversation