Christopher Robinson, 48, from Seguin, Texas, on 9 August 2021
Victim Info
- Christopher Robinson
- Unknown
- 48
- Male
Details
Deputies began tracking a vehicle reportedly involved in a kidnapping. Deputies eventually found the vehicle and attempted a traffic stop, which resulted in a chase. Using OnStar, the deputies were able to reduce the speed of the vehicle and eventually get it to stop. Deputies claim Robinson immediately began to fire at deputies. Deputies returned fire, killing Robinson.Primary Evidence & Links
Additional Evidence
- Christopher Robinson
- 48
- Male
- Unknown race
- I-10 and Highway 130
- Seguin
- TX
- Guadalupe
- Guadalupe County Sheriff's Office
- TX0940000
- Gunshot
- Pending investigation
- No known charges
- No
- Allegedly Armed
- gun
- attack
- car
- no
- 7087
- Part 1 Violent Crime
- suspected kidnapping
Source
Source ID: 9450 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Washington Post -Christopher Robinson, 40, from Seguin, Texas - shot on 9 August 2021
- Fatal Encounters -Christopher Robinson, 48, from Seguin, Texas, on 9 August 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 63569. Submitted in Mainchain Tx BD794CF7E6D8E81EFB7EACCD2D093B387BA9AC449431D8FDE6467F01029A2173, at block height 135612
Transaction details
Tx BD794CF7E6D8E81EFB7EACCD2D093B387BA9AC449431D8FDE6467F01029A2173
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: Ed96TbJNfzAHbqxFSGbDP55EmTuc9JSFbMNfdE6jRWQgEBkdfYyw7029dTQ452wzABr5BljzOdRPJj7/JvkBoA==
Raw Tx data:
Hash Comparison
Hash stored in database: 33f935487b8890db00c8f90d3f2d4ee65f3fe05f3fcee3cc739bb6833bb8cf72
Hash from Mainchain Tx: 1655485496
Dynamically generated hash: 33f935487b8890db00c8f90d3f2d4ee65f3fe05f3fcee3cc739bb6833bb8cf72
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: