This week's published-application drop was thin on the keyword "blockchain" attached to a household financial name — the bulk of the matching records carried no assignee at all. To get a readable signal from a recognizable institution, this piece widens the window to mid-June 2026 and reads Bank of America's recent run of distributed-ledger applications as a group. Read together, they describe something more mundane, and arguably more telling, than a crypto-trading play: a bank methodically patenting the back-office plumbing of distributed ledgers.

The representative record here is application US20260161816A1, System and Method for Securing Information in a Distributed Network via a Distributed Identifier, published June 11, 2026 and assigned to Bank of America Corporation. It is directed to a recurring problem for any regulated institution that finds a distributed ledger appealing: a ledger is valuable because every node can see and verify entries, but a bank cannot scatter customer records across a shared network. The application's answer is to put a pointer on the ledger and keep the payload off it.

The system allows for generating distributed identifiers for information entries, wherein the distributed identifiers mask the information entries using a hash function and the distributed identifiers are dispersed across distributed ledgers.— System and Method for Securing Information in a Distributed Network via a Distributed Identifier, US20260161816A1

That single design choice — ledger as index, not as datastore — is the thread that runs through the cluster. It signals a bank trying to capture the verifiability and shared-state benefits of a ledger while holding the actual data inside its own perimeter, where supervision, privacy rules and access controls already live.

What the cluster is directed at

The neighboring applications fill in the rest of the stack. US20260128913A1, System for Enabling Modification of Data and Endorsements of Smart Contracts Within a Distributed Trust Computing Network (published May 7, 2026), describes holding a smart contract and its hash in a staging area where the terms remain editable until all parties accept and the contract self-executes, at which point the block becomes immutable. For an institution, that addresses an awkward feature of canonical smart contracts — that a mistake, once committed, is permanent — by inserting a human-approval window before immutability sets in.

US20260127031A1, System and Method for Digital Resource Allocation via an Interactive Computational Framework (May 7, 2026), pairs a machine-learning model with a generative-AI step that drafts a smart contract carrying ownership terms and appends it to a distributed ledger. US20260135903A1 (May 14, 2026) describes a real-time data-exchange matching engine that records results of an exchange on a distributed ledger. The earlier Customized Token Rules Generation System, US20250330460A1, is directed at building configurable controls into a token — alerting behavior, transaction blocking, geofencing and regional restrictions — and memorializing those rules immutably on the ledger.

Two more records show how concrete the control layer gets. US20250232301A1, Geolocation-Based Consensus Algorithm for Use in Monitoring Proposed Data Records for a Distributed Ledger (July 2025), traces the origin of an incoming data block by digital signature and can block records from a restricted location before the consensus process even runs. US20250294023A1, System for Off-Network Access to Resources Using a Remote Client (September 2025), is directed at unlocking a distributed-ledger credential for a user over a controlled network session and terminating that session once access is granted. These are not features a trading desk asks for; they are features a compliance, fraud and operations function asks for. The chronology reinforces the point. The 2019-era applications in the same estate — real-time net settlement between payor and payee banks, real-time processing of resource transfers over a private or semi-private chain, and distributed-ledger onboarding for standby guarantee resources — were already framed around interbank settlement and trade finance rather than open trading. The 2025 and 2026 records carry that lineage forward and add an AI and tokenization layer on top of it, but the underlying use case has stayed put: move records and obligations between known counterparties on a controlled ledger, with the bank as operator. A multi-year run of applications that keep returning to the same use case is a stronger signal of direction than any single disclosure, because it shows sustained allocation rather than a one-off experiment.

The signal for the business

Across the set, the consistent theme is access, identity, integrity and control — the requirements of a supervised institution — layered onto distributed-ledger mechanics. The applications repeatedly describe permissioned or "distributed trust" networks, masking of records behind identifiers, editable-then-immutable contract flows, and rule engines that can stop a transaction by geography or signature. They suggest a bank positioning the ledger as record-keeping and settlement infrastructure rather than as an asset class to be traded.

That reading is consistent with how large banks have publicly framed distributed-ledger work — internal settlement, tokenized records and identity rather than speculative exposure — but the value of the filings is that they show the same direction in primary documents the company controls. The drafting choices are repeated, the inventors recur across records, and the classifications cluster in the payment and cryptographic-protocol areas (CPC G06Q 20/389, the distributed-ledger payment subclass, and H04L 9/50, the blockchain-specific cryptographic class) rather than in any exchange or market-making art. None of this speaks to whether any single application will issue, how broad its claims are, or whether the described systems are in production; published applications are pending disclosures, not granted patents, and a filing is not a deployment. What the cluster does establish, on the record, is a consistent line of investment in ledger infrastructure that keeps the institution — not the network — in control of the data. For a business reader trying to separate the bank's actual distributed-ledger posture from the sector's noise, the filings are the cleaner signal: this is plumbing, filed quietly and repeatedly.