Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,385
| Lake Township, Michigan

Adam Briggs, 30, from Lake Township, Michigan, on 4 April 2021

Victim Info

  • Adam Briggs
  • Unknown
  • 30
  • Male

Details

Troopers were performing a welfare check at 8 p.m. when they found a 62-year-old woman dead from an apparent homicide inside her home. No one else was in the home when the victim was found, but troopers developed a suspect -- a 30-year-old relative of the victim -- and put out a broadcast alert. The Cadillac Police Department located the vehicle and attempted a traffic stop shortly after 1 a.m. The driver fled and officers pursued him. He allegedly fired at police, missing the vehicles and officers. Missaukee County Sheriff's deputies deployed stop sticks, which disabled the vehicle, police said. The man fled on foot. Police found the body shortly after 6 a.m. with a fatal, self-inflicted gunshot.

Additional Evidence

  • Adam Briggs
  • 30
  • Male
  • Race unspecified
  • NA
  • NA
  • M-55 near M-66
  • Lake Township
  • MI
  • 49651
  • Missaukee
  • M-55 near M-66 Lake Township MI 49651 Missaukee
  • Cadillac Police Department, Missaukee County Sheriff's Office, Michigan State Police
  • Suicide

Source

Source ID: 29972 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65046. Submitted in Mainchain Tx C5BF16B2060565650117A086BA448A762345FB6DDD415BCA8FE9E671B1F7F67A, at block height 139380

Transaction details

Tx C5BF16B2060565650117A086BA448A762345FB6DDD415BCA8FE9E671B1F7F67A
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: AwMa3Tu1lx1mujpUVyrynUV3MoQOBb/ZgoO4LPsomwIsSqNKUTJu5B+54UEN3nlPgmLhGE/VKT3lYoPgyvxZmQ==
Raw Tx data:

Hash Comparison

Hash stored in database: 2514b373ff284dff63db6f389e2755bdbdfa67ff410c89cb011ba9bcae63d5df

Hash from Mainchain Tx: 2514b373ff284dff63db6f389e2755bdbdfa67ff410c89cb011ba9bcae63d5df

Dynamically generated hash: a06397f35c580ee7496fe0b8bb22be91e93d294e83dd8b8208b04ea43b3781e8

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: