Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Huntsville, Alabama

Brian Lee Potts, 39, from Huntsville, Alabama, on 29 April 2021

Victim Info

  • Brian Lee Potts
  • White/European American
  • 39
  • Male

Details

Brian Potts fled when deputies attempted to take him into custody for outstanding warrants for reckless endangerment and attempting to flee and elude. Potts reportedly lost control of his vehicle and crossed into the opposing traffic lane and struck a deputy's patrol vehicle that was traveling west, killing Potts and reportedly injuring the deputy.

Additional Evidence

  • Brian Lee Potts
  • 39
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • University Drive and Enterprise Way
  • Huntsville
  • AL
  • 35806
  • Madison
  • University Drive and Enterprise Way Huntsville AL 35806 Madison
  • Madison County Sheriff's Office
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/05/Brian-Lee-Potts.png

Source

Source ID: 30132 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64725. Submitted in Mainchain Tx D55C48C6D393EB40FD37FC3939B7E06EBD41FA832D9718013ED41D21DF3C4506, at block height 139059

Transaction details

Tx D55C48C6D393EB40FD37FC3939B7E06EBD41FA832D9718013ED41D21DF3C4506
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: XFfeaYlnXWp+SQPiHFKF4EbscwEsmRtTaZMx47tdULF00LGhGkH8RDqUZQ8/Iqt0sL3iFJexYsgZMpxzdJJZoA==
Raw Tx data:

Hash Comparison

Hash stored in database: 0452ba3557fbde5f2a5e483ae199a827269ddb09e169cc32545cf15a07b3fda3

Hash from Mainchain Tx: 0452ba3557fbde5f2a5e483ae199a827269ddb09e169cc32545cf15a07b3fda3

Dynamically generated hash: ad675d44248c6c1cda3006f5e7bf590d8fe79f74c9fefc31841e1bba9f746404

Hashes Match?
NO

How is the comparison calculated?

The hash stored in the database is used as the identifier for this report, and can be seen in the URL. The hash from the Mainchain Tx is the hash sent to and stored on Mainchain. Finally, the "generated hash" is generated each time this page is loaded, using the same data used for the hash submitted to Mainchain.

Raw data used to generate the hash, using the Node.js crypto.createHash('sha256') algorithm: