JPMorgan and MIT Listed 150 Things Banks Need From Public Blockchains. That's the Problem.
A November 13 discussion paper from JPMorgan's Kinexys and the MIT Digital Currency Initiative catalogs more than 150 institutional requirements for public blockchains, from privacy to sanctions screening. The list is reasonable item by item, but stacked together it starts to describe something that isn't really public at all.
More than 150. That's how many separate requirements JPMorgan's Kinexys and the MIT Digital Currency Initiative say banks need satisfied before they'll trust a public blockchain with real money.
They published the list on November 13, in a discussion paper that reads less like a victory lap and more like a design brief. And it lands at a moment when every major bank is testing tokenized deposits and settlement rails while quietly wondering whether the public chains they're testing on will ever clear their own compliance desks.
The List, and Why It's Long
Kinexys, the JPMorgan unit that used to be called Onyx, has been running tokenized payments for years, so the paper isn't theoretical. The MIT side brings Neha Narula's Digital Currency Initiative, which has been poking at central bank and stablecoin design since 2015 or so. Together they walked through what institutional users actually need, then sorted it into buckets that keep colliding.
Privacy is the obvious one. A bank can't broadcast its clients' positions to the world, and it certainly can't let competitors watch the flow.
Sanctions controls are the second. Regulators expect screening at the wallet level, in real time, with the ability to block a counterparty before settlement clears. Public chains weren't built with an off switch.
Accountability is the third, and the messiest. When something goes wrong, someone has to be legally answerable, and there has to be a documented chain of who did what. On a permissionless network, that's not a given.
The paper doesn't resolve any of this. It asks the industry for input, with a fuller whitepaper to follow.
The Tension Nobody Wants to Say Out Loud
Here's what strikes me. Each of those requirements is reasonable on its own. Stacked together, they start to describe a private network with a public viewfinder.
If you need 150 controls before you can use a shared rail, what exactly is being shared?
Proponents will tell you that's the wrong framing. The point of a public chain isn't radical transparency, it's shared settlement and a common standard, so that JPMorgan, Citi and a dozen others aren't rebuilding the same plumbing in incompatible ways. Fair enough. Interoperability has real value, and the track record of bank consortia to date is thin enough that the skeptics have earned their seat at the table.
But the burden here runs in one direction. Banks should have to show which of these 150 requirements are actual legal obligations and which are institutional habit dressed up as compliance. "We've always done it this way" isn't a design constraint. It's a preference.
So my strong opinion: the requirements that survive scrutiny will be the ones tied directly to law, and that's maybe half of them. The rest are negotiable, and that negotiation is the whole ballgame.
What to Watch
Watch the comment period. If the feedback is mostly banks agreeing with banks, we'll get a whitepaper that restates the list and a pilot that quietly turns into a permissioned network with a bridge bolted on. If developers push back on specific items, and the number drops meaningfully, that's a signal the design tradeoffs are actually being worked rather than recited.
Watch, too, whether Kinexys puts its own operation where the paper is. JPMorgan has pushed real volume through tokenized deposits. If its own stack can't meet all 150, that tells you something useful about the list.
The question worth asking: is this paper a map toward public networks, or a carefully worded argument that they won't work for banks? I'm not entirely convinced it's the first one.
Related Articles
Explore More
Key Terms Explained
A bundle of transactions that gets permanently added to the blockchain.
A distributed database where transactions are grouped into blocks and linked together cryptographically.
A protocol that lets you move tokens between different blockchains.
Following the laws and regulations that apply to financial activities, including crypto.