0x734415407344…73441543
JPMorgan's Kinexys and MIT List 150-Plus Requirements for Bank-Ready Blockchains
A November 13 discussion paper from JPMorgan's Kinexys and MIT DCI maps over 150 institutional requirements for public blockchains and invites industry input before a follow-up whitepaper.

Outputs
JPMorgan's Kinexys and the MIT Digital Currency Initiative published a discussion paper on November 13.
The paper identifies more than 150 institutional requirements for public blockchains.
An earlier MIT–Kinexys report from June covered front-running, omitted transactions, unsolicited tokens and sanctions exposure via network fees.
A follow-up whitepaper will incorporate industry responses to the discussion paper.
JPMorgan's Kinexys and the MIT Digital Currency Initiative have identified more than 150 requirements that institutions need before they can operate on public blockchains. A discussion paper published November 13 lays out the list and asks a blunt question of developers: how much of what banks demand can a network absorb before it loses the qualities that made it attractive in the first place?
The paper is explicit about its own limits. It does not certify any particular chain as suitable for regulated finance. Instead, it serves as a starting point for industry discussion, with a further whitepaper planned to reflect the responses the partners receive.
What sits at the top of the list?
The Kinexys announcement highlights four recurring pressure points: sanctions compliance, accountable governance, client confidentiality and interoperability. Each one pulls institutional design in a different direction.
The core trade-off is not hard to see. A bank may value infrastructure that no competitor controls, yet still need someone to answer for an outage or to implement a legally required restriction. Giving one operator extensive powers could make that responsibility clearer. It would also change the network's neutrality. And the right arrangement may differ depending on the use case — a payment token, a trading venue and an asset register may each call for a different balance of control.
Why a polished banking app is not enough
Some of the hardest problems sit below the application layer. An earlier report from MIT and Kinexys, published in June, examined transaction front-running, omitted transactions, unsolicited tokens and sanctions exposure through network fees. That work produced a layered framework separating changes an institution can make inside its own application from changes that require cooperation at protocol, governance or regulatory level.
The distinction matters. A customer-facing application might reject an instruction, but it cannot necessarily stop another blockchain participant from sending a token to the bank's address. Internal approval controls do not, on their own, determine how validators order transactions. These are concrete operating questions for firms already experimenting with public networks — restricted institutional participation on public-chain infrastructure of the kind JPM Coin has pursued on Ethereum shows the two worlds can coexist, but only up to the boundaries the June framework describes.
How should a payment token behave?
The research partners have also examined payment-token standards, including how transaction information and administrative recovery controls can be represented. That work proposes targeted, composable capabilities rather than assuming one broad token standard will satisfy every banking use case.
The paper offers a practical illustration. Consider a transfer that is technically valid but sent to an unintended eligible recipient. The business needs a process for investigating the error and deciding whether remediation is possible. A token with administrative controls may offer options. But those controls create their own questions about authority, access and misuse — making a function available in code is only part of deciding who may invoke it.
Settlement design adds yet another layer. Coordinating the asset and payment legs, as delivery-versus-payment tooling on Solana attempts, addresses a specific transaction problem. It does not settle every question about custody, eligibility or governance around that transaction.
What does this change for adoption?
The paper's real value, if it lands, is triage. A long requirements list helps participants identify which demands are essential, which belong at a different layer, and which cannot coexist without compromise. Simply adding every requested control could produce a costly system whose advantages over existing infrastructure become difficult to explain.
There is also a coordination problem the paper makes explicit. A bank can approve its own software release on its own schedule. A shared network may depend on participants with different incentives and different upgrade calendars. Institutions therefore need to assess how changes are agreed, how dissent is handled, and what continuity means when a network evolves — questions that have no clean answer in today's multi-client governance setups.
The discussion paper puts those decisions in front of the industry rather than resolving them. Its next contribution — the follow-up whitepaper — will depend on whether developers, institutions and policymakers can turn broad requirements into practical arrangements with identifiable responsibility. That is a more demanding test of institutional adoption than announcing another token on an existing chain, and the quality of the responses the partners receive between now and the whitepaper will determine whether this becomes a working roadmap or another archive of unresolved trade-offs.
via newsbtc.com (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,456 articles