Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 60,726
| Seguin, Texas

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.

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

BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 60644. Submitted in Mainchain Tx 431495E602B36E522CBB8F291D13A68260332B6453E0532666C3306B62FA2761, at block height 6754581

Transaction details

Tx 431495E602B36E522CBB8F291D13A68260332B6453E0532666C3306B62FA2761
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: o3845dMyrbDkjJRahOoAbstB0ERjXMzqc9fMMTS7c90Kf/ky+8vw3E2XFzppoeM1FnCEgKj4ygh0DFjZcyTblw==
Raw Tx data:

Hash Comparison

Hash stored in database: 33f935487b8890db00c8f90d3f2d4ee65f3fe05f3fcee3cc739bb6833bb8cf72

Hash from Mainchain Tx: 33f935487b8890db00c8f90d3f2d4ee65f3fe05f3fcee3cc739bb6833bb8cf72

Dynamically generated hash: 33f935487b8890db00c8f90d3f2d4ee65f3fe05f3fcee3cc739bb6833bb8cf72

Hashes Match?
YES

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: