Nicholas Cory Kausshen, 41, from Spokane Valley, Washington, on 22 November 2020
Victim Info
- Nicholas Cory Kausshen
- Unknown
- 41
- Male
Details
A deputy attempted to stop a vehicle at about 6:45 p.m. after reportedly seeing reckless and erratic driving. Rather than stopping, the driver, Nicholas Cory Kausshen, fled, and the deputy chased him. Nicholas Cory Kausshen continued to drive recklessly, hitting parked cars and driving into opposing lanes of travel. A deputy attempted to immobilize the car using his patrol vehicle. Both vehicles sustained damage. Kausshen drove toward another marked patrol car and two deputies, and one deputy shot and killed him.Primary Evidence & Links
Additional Evidence
- Nicholas Cory Kausshen
- 41
- Male
- Race unspecified
- NA
- NA
- Sprague Avenue and University Road
- Spokane Valley
- WA
- 99206
- Spokane
- Sprague Avenue and University Road Spokane Valley WA 99206 Spokane
- Spokane County Sheriff's Office
- Gunshot
- Pending investigation
Source
Source ID: 29203 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Mapping Police Violence -Nicholas Cory Kausshen, 41, from Spokane Valley, Washington, on 22 November 2020
- Killed By Police -Nicholas Cory Kausshen, 41, from Washington on 22 November 2020
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 66676. Submitted in Mainchain Tx 82B9D12B6897A10A52ABD56D4AE53C585EF0DD4150FD5409E6BE7C4FEF145795, at block height 143303
Transaction details
Tx 82B9D12B6897A10A52ABD56D4AE53C585EF0DD4150FD5409E6BE7C4FEF145795
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: TAnGDkV87U6/9moi+RLBEi2OzaC8s6wW5xTZOpgHoqpZPF+G0z/6t7MS+NIGZVwD3e0fYLAW9ZncU3F5DXlGPQ==
Raw Tx data:
Hash Comparison
Hash stored in database: b20ac5486fe058b17f6ffd89afb441afca11696f34f25bf83e38eb50844cb093
Hash from Mainchain Tx: b20ac5486fe058b17f6ffd89afb441afca11696f34f25bf83e38eb50844cb093
Dynamically generated hash: b20ac5486fe058b17f6ffd89afb441afca11696f34f25bf83e38eb50844cb093
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: