David Wade Gaither, 49, from Murfreesboro, Tennessee, on 24 July 2021
Victim Info
- David Wade Gaither
- White/European American
- 49
- Male
Details
Officers responded to a domestic disturbance call. Officers arrived at the duplex about 10:40 p.m. They attempted to speak with David Gaither, who his wife reported was acting belligerent and punching holes in the wall and doors. As officers entered the home, Gaither exited a bedroom, pointed a handgun at one of the officers in the hallway, and reportedly pulled the trigger. The pistol malfunctioned. Gaither followed and fired two more shots at the officers in the front yard before closing the door and going back inside. Due to a lack of response, officers entered the home and found Gaither in a bedroom with a self-inflicted gunshot.Primary Evidence & Links
Additional Evidence
- David Wade Gaither
- 49
- Male
- European-American/White
- European-American/White
- Not imputed
- 1500 block Old Lascassas Pike
- Murfreesboro
- TN
- 37130
- Rutherford
- 1500 block Old Lascassas Pike Murfreesboro TN 37130 Rutherford
- Murfreesboro Police Department
- Suicide
- https://fatalencounters.org/wp-content/uploads/2021/08/David-Wade-Gaither.jpg
Source
Source ID: 30649 - Fatal Encounters
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 63731. Submitted in Mainchain Tx 728B28973EB482D4AF34DD2BACF79F918F173F719BDD46BD70085DFFADEC2612, at block height 136536
Transaction details
Tx 728B28973EB482D4AF34DD2BACF79F918F173F719BDD46BD70085DFFADEC2612
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: wg0CqJ88Oh4xWq/y/pRdCZpPcB6HN2wPmvRB3Gl8aGIPeLBPIiuH4OJxM2kX79myiSARo3Pb04n5evxuG+/GvQ==
Raw Tx data:
Hash Comparison
Hash stored in database: 5a0e0616a5873ab9f5ebb45e85c40338ccadaf6eb3964a77e7fb128f27458480
Hash from Mainchain Tx: 5a0e0616a5873ab9f5ebb45e85c40338ccadaf6eb3964a77e7fb128f27458480
Dynamically generated hash: afbe047ffeff143132c64dc250c4e53db2af62330b3d20f77b81478e65b83925
Hashes Match?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: