Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Eatonton, Georgia

James David Mathis, 38, from Eatonton, Georgia, on 25 April 2021

Victim Info

  • James David Mathis
  • Black/African American
  • 38
  • Male

Details

About 9 p.m., dispatch got a be-on-the-lookout from neighboring Jasper County for a murder suspect. Deputies thought James David Mathis was likely at a home near Eatonton. A few minutes after deputies got there, someone fired at them from outside the home. When he arrived a few minutes later, the sheriff tried to negotiate with the man, but couldn't reach him. A family member told him Mathis threatened to kill himself and was last seen outside of the home. Around 9:20 p.m. after still not hearing from him, deputies Mathis dead.

Additional Evidence

  • James David Mathis
  • 38
  • Male
  • African-American/Black
  • African-American/Black
  • Not imputed
  • 426 Glenwood Springs Road
  • Eatonton
  • GA
  • 31024
  • Putnam
  • 426 Glenwood Springs Road Eatonton GA 31024 Putnam
  • Putnam County Sheriff's Office
  • Suicide
  • https://fatalencounters.org/wp-content/uploads/2021/05/James-David-Mathis.png

Source

Source ID: 30106 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64757. Submitted in Mainchain Tx 3F28551D04E5D04BD4DD1FB8CF28AA0CC73EBCC88865BE1228BEE895FBD488C1, at block height 139091

Transaction details

Tx 3F28551D04E5D04BD4DD1FB8CF28AA0CC73EBCC88865BE1228BEE895FBD488C1
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: pf99eId96KXVot0kKwfMJs4VKNcO2VmiBi3FruwIt6MGf3DDOwgylIYBmqCCmqm2dT6Rvv4ivKrmVHm3ciPaDg==
Raw Tx data:

Hash Comparison

Hash stored in database: bbdbfa3f1fa6a1ecd90577af81210eccef6f636633f7dda89b1e7990e97ec091

Hash from Mainchain Tx: bbdbfa3f1fa6a1ecd90577af81210eccef6f636633f7dda89b1e7990e97ec091

Dynamically generated hash: c84232af9d98a4b99ea87c733e3ccef0306745a8c1dc06442502093f22e50f9e

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: