Christopher Eric Cook, 41, from Reed Point, Montana, on 23 March 2021
Victim Info
- Christopher Eric Cook
- White/European American
- 41
- Male
Details
The Montana Highway Patrol tried to pull over Christopher Eric Cook outside Laurel but he fled along the interstate through Stillwater County. U.S. Marshals and the Stillwater County Sheriff's Office were also involved in the chase. Cook stopped around 11 a.m. around mile marker 399. The westbound lanes of the interstate were then closed. He allegedly got out of his vehicle, walked away, and turned toward police and brandished a gun. He reportedly ignored commands to surrender, and the two deputies shot and killed him.Primary Evidence & Links
Additional Evidence
- Christopher Eric Cook
- 41
- Male
- White
- I-90
- Reed Point
- MT
- 59069
- Stillwater
- Stillwater County Sheriff's Office
- MT0480000
- Gunshot
- Pending investigation
- No known charges
- No
- Allegedly Armed
- gun
- other
- Rural
- https://fatalencounters.org/wp-content/uploads/2021/04/Christopher-Eric-Cook.jpg
- Traffic violation
- traffic violation
Source
Source ID: 8758 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Fatal Encounters -Christopher Eric Cook, 41, from Reed Point, Montana, on 23 March 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65227. Submitted in Mainchain Tx ABB48BDDE3403EF2BF7702A176D230B175C017F4C255EB616338A5032CD04084, at block height 140326
Transaction details
Tx ABB48BDDE3403EF2BF7702A176D230B175C017F4C255EB616338A5032CD04084
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: J7RAg8AZiodlk3z1egHf4Lo/8RMgTvmN+O6p2lV8pJlY9F1trn+7sWgY3A7H8wpPR92YIzEOUndD3Txllrll+w==
Raw Tx data:
Hash Comparison
Hash stored in database: 1d9875e6ae6ee6ea075347b625d37df8dd180e26cddbe12944764276adb1abf2
Hash from Mainchain Tx: 1d9875e6ae6ee6ea075347b625d37df8dd180e26cddbe12944764276adb1abf2
Dynamically generated hash: 1d9875e6ae6ee6ea075347b625d37df8dd180e26cddbe12944764276adb1abf2
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: