# US 12,120,254 B2 · Blockchain notification board storing blockchain resources > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,120,254 B2 - Document ID: US12120254B2 - Status: Granted - Kind: B2 - Application number: 17/886,117 - Filed: 2022-08-11 - Published: 2022-12-01 - Granted: 2024-10-15 - Earliest claimed: 2018-10-09 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Futoshi Iwama; Takaaki Tateishi; Shunichi Amano; Sachiko Yoshihama - Web page: https://patentgrep.com/patent/US12120254B2 ## CPC - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)} - G06F 16/2365: {Ensuring data consistency and integrity} - G06F 16/2379: {Updates performed during online database operations; commit processing} - G06F 16/955: using information identifiers, e.g. uniform resource locators [URL] - H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]} - H04L 63/123: {received data contents, e.g. message integrity} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An example operation may include one or more of receiving a resource request from a client, identifying a unique chaincode identifier associated with the resource request, re-instantiating a version of chaincode based on the unique chaincode identifier, the re-instantiation configured to disregard any subsequently implemented versions of the chaincode at the computing node, executing the resource request based on the re-instantiated version of the chaincode to generate a result, and transmitting the result to the client. ## Claims ### Claim 1 A computing node comprising: a network interface configured to receive a resource request from a client with an update to information about a blockchain peer; and a processor configured to: identify a unique resource identifier comprising information about a chaincode used to access a notification board stored within a world state database on a distributed ledger of the blockchain peer, instantiate the chaincode and execute the resource request via the chaincode which deletes one or more existing attribute values of the blockchain peer from the notification board and replaces them with one or more new attribute values based on the update to information about the blockchain peer to generate a modified notification board, and transmit information about the modified notification board to the client. ### Claim 2 (depends on 1) The computing node of claim 1, wherein the notification board is stored separately from a blockchain ledger on the distributed ledger. ### Claim 3 (depends on 1) The computing node of claim 1, wherein the notification board comprises a time at which the unique resource identifier is added to the notification board. ### Claim 4 (depends on 1) The computing node of claim 1, wherein the world state database is stored separately from a blockchain ledger on the distributed ledger. ### Claim 5 (depends on 1) The computing node of claim 1, wherein the processor is further configured to generate a read set to be read by the chaincode in which previous key values are substituted for current values. ### Claim 6 (depends on 1) The computing node of claim 1, wherein the processor is further configured to store identifiers of modifications performed to the notification board within a block on a blockchain ledger of the distributed ledger. ### Claim 7 (depends on 1) The computing node of claim 1, wherein the processor is configured to prevent a subsequent version of the chaincode from being reinstated based on a chaincode identifier and a time value associated with the blockchain peer and stored in the notification board. ### Claim 8 (depends on 1) The computing node of claim 1, wherein the processor is configured to transmit a set of current uniform resource indicators (URIs) of a plurality of peer nodes. ### Claim 9 (depends on 8) The computing node of claim 8, wherein the plurality of peer nodes are members of the distributed ledger. ### Claim 10 A computer implemented method comprising: receiving a resource request from a client with an update to information about a blockchain peer; identifying a unique resource identifier comprising information about a chaincode used to access a notification board stored within a world state database on a distributed ledger of the blockchain peer; instantiating the chaincode and executing the resource request via the chaincode which deletes one or more existing attribute values of the blockchain peer from the notification board and replaces them with one or more new attribute values based on the update to information about the blockchain peer to generate a modified notification board; and transmitting information about the modified notification board to the client. ### Claim 11 (depends on 10) The method of claim 10, wherein the notification board is stored separately from a blockchain ledger on the distributed ledger. ### Claim 12 (depends on 10) The method of claim 10, wherein the notification board comprises a time at which the unique resource identifier is added to the notification board. ### Claim 13 (depends on 10) The computing node of claim 10, wherein the world state database is stored separately from a blockchain ledger on the distributed ledger. ### Claim 14 (depends on 10) The method of claim 10, wherein the method further comprises generating a read set to be read by the chaincode in which previous key values are substituted for current values. ### Claim 15 (depends on 10) The method of claim 10, wherein the method further comprises storing identifiers of modifications performed to the notification board within a block on a blockchain ledger of the distributed ledger. ### Claim 16 (depends on 10) The method of claim 10, wherein the method further comprises preventing a subsequent version of the chaincode from being reinstated based on a chaincode identifier and a time value associated with the blockchain peer and stored in the notification board. ### Claim 17 (depends on 10) The method of claim 10, wherein the transmitting comprises transmitting a set of current uniform resource indicators (URIs) of a plurality of peer nodes. ### Claim 18 (depends on 17) The method of claim 17, wherein the plurality of peer nodes are members of the distributed ledger. ### Claim 19 A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform: receiving a resource request from a client with an update to information about a blockchain peer; identifying a unique resource identifier comprising information about a chaincode used to access a notification board stored within a world state database on a distributed ledger of the blockchain peer; instantiating the chaincode and executing the resource request via the chaincode which deletes one or more existing attribute values of the blockchain peer from the notification board and replace them with one or more new attribute values based on the update to information about the blockchain peer to generate a modified notification board; and transmitting information about the modified notification board to the client. ### Claim 20 (depends on 19) The computer readable medium of claim 19, wherein the notification board comprises a time at which the unique resource identifier is added to the notification board. ### Claim 21 (depends on 20) The computer readable medium of claim 20, wherein the world state database is stored separately from a blockchain ledger on the distributed ledger. ### Claim 22 (depends on 19) The computer readable medium of claim 19, wherein the processor is further configured to perform generating a read set to be read by the chaincode in which previous key values are substituted for current values. ### Claim 23 (depends on 19) The computer readable medium of claim 19, wherein the processor is further configured to perform preventing a subsequent version of the chaincode from being reinstated based on a chaincode identifier and a time value associated with the blockchain peer in the notification board. ### Claim 24 (depends on 19) The computer readable medium of claim 19, wherein the transmitting comprises transmitting a set of current uniform resource identifiers (URIs) of a plurality of peer nodes. ### Claim 25 (depends on 24) The computer readable medium of claim 24, wherein the plurality of peer nodes are members of the distributed ledger.