Opening a blockchain to the institutional market requires more than processing capacity. Banks need to identify counterparties, protect customer data, assess who receives validation fees and comply with asset-freezing orders. A discussion paper released on November 19 by the MIT Digital Currency Initiative and Kinexys Digital Payments, part of J.P. Morgan, organizes this challenge into approximately 170 requirements for shared infrastructure.

The requirements span 21 categories and seven pillars: protocol and ledger; security, resilience and service levels; interoperability and development; participant controls; transaction controls; data, legal and assurance; and governance, economics and change management. The aim is to provide a starting point for developers and operators seeking to serve financial institutions.

The analysis considers it unlikely that an entirely decentralized, public and permissionless network could satisfy all these needs. It instead explores the possibility of an open, permissioned network in which admission follows objective, published criteria, with credible neutrality and no single party controlling the rules.

The list draws on J.P. Morgan’s experience with both Kinexys private infrastructure and tokenized products on Ethereum and Base. This combination raises the question of how to preserve participation in an open network while giving institutions the means to meet legal and operational obligations.

The work is preliminary: it does not represent the launch of a network, nor does it establish that every requirement is indispensable. The authors acknowledge that some requirements may reflect assumptions inherited from centralized systems and invite banks, developers, users and regulators to challenge the analysis. For the institutional market, its contribution is to make explicit the conditions shared infrastructure would need to demonstrate before supporting regulated financial operations.

Share this post