From c10cf7ccbecaa4972251b4eb13fd60c9fa4708fa Mon Sep 17 00:00:00 2001
From: Andreas Schildbach <andreas@schildbach.de>
Date: Fri, 24 Mar 2023 11:05:50 +0100
Subject: [PATCH] Sha256Hash: direct use of `ByteBuffer` in `hashCode()`

A hash code is just an arbitrary number. It doesn't care about signedness and endianess.
---
 core/src/main/java/org/bitcoinj/base/Sha256Hash.java | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/src/main/java/org/bitcoinj/base/Sha256Hash.java b/core/src/main/java/org/bitcoinj/base/Sha256Hash.java
index 08df0785c..a5aef7d6a 100644
--- a/core/src/main/java/org/bitcoinj/base/Sha256Hash.java
+++ b/core/src/main/java/org/bitcoinj/base/Sha256Hash.java
@@ -245,8 +245,8 @@ public class Sha256Hash implements Comparable<Sha256Hash> {
      */
     @Override
     public int hashCode() {
-        // Use the last 4 bytes, not the first 4 which are often zeros in Bitcoin.
-        return (int) ByteUtils.readUint32BE(bytes, LENGTH - (4 + 1));
+        // use the last 4 bytes, not the first 4 which are often zeros in Bitcoin
+        return ByteBuffer.wrap(bytes).getInt(LENGTH - Integer.BYTES);
     }
 
     @Override