JPMorgan and MIT Map More Than 150 Requirements for Institutional Blockchains

NewsBTC
NewsBTC에서 열기
JPMorgan and MIT Map More Than 150 Requirements for Institutional Blockchains

TL;DR

A November 13 discussion paper maps more than 150 institutional requirements. Privacy, sanctions controls and accountability create difficult design choices. The work invites industry input before a further whitepaper.

JPMorgan’s Kinexys and the MIT Digital Currency Initiative have put a detailed question to public-blockchain developers: how much of what banks need can a network accommodate while retaining the qualities that made it attractive? A November 13 discussion paper identifies more than 150 institutional requirements and invites the industry to work through the tensions.

A shared network brings competing expectations

The Kinexys announcement highlights sanctions compliance, accountable governance, client confidentiality and interoperability. The paper is a starting point for discussion, with a further whitepaper intended to reflect responses. It does not certify a particular chain as suitable for regulated finance.

The underlying trade-off is easy to see. A bank may value infrastructure that no competitor controls, yet still need someone to answer for an outage or implement a legally required restriction. Giving one operator extensive powers could make that responsibility clearer while changing the network’s neutrality. The right arrangement may vary between a payment token, a trading venue and an asset register.

Some problems sit below the application

An earlier MIT and Kinexys report published in June examined transaction front-running, omitted transactions, unsolicited tokens and sanctions exposure through network fees. Its layered framework separates changes an institution can make inside an application from changes requiring cooperation at protocol, governance or regulatory level.

That distinction helps explain why a polished banking interface cannot settle every underlying question. 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. Likewise, internal approval controls do not by themselves determine how validators order transactions.

These are concrete operating questions for firms already experimenting with public networks. NewsBTC’s coverage of JPM Coin on Ethereum illustrates how restricted institutional participation can coexist with public-chain infrastructure.

Payment-token design is a separate layer

The research partners have also examined payment-token standards , including how transaction information and administrative recovery controls can be represented. That work proposes more targeted, composable capabilities instead of assuming one broad token standard will satisfy every banking use case.

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 another layer. As NewsBTC’s examination of Solana’s delivery-versus-payment tool shows, coordinating the asset and payment legs addresses a specific transaction problem. It does not settle every question about custody, eligibility or governance around that transaction.

Useful standards need choices about responsibility

A long requirements list will be valuable if it 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 are difficult to explain.

There is also a coordination problem. A bank can approve its own software release, but a shared network may depend on participants with different incentives and upgrade schedules. Institutions therefore need to assess how changes are agreed, how dissent is handled and what continuity means when a network evolves.

The discussion paper makes those decisions explicit. Its next contribution 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 adoption than announcing another token on an existing chain.

Written by the News Desk and edited by Samuel Rae.