Samuel Yeager, 23, from Castle Pines, Colorado, on 3 April 2021
Victim Info
- Samuel Yeager
- White/European American
- 23
- Male
Details
Deputies responded to Happy Canyon Road around 6:15 p.m. for a report of a man with a gun. Deputies instructed Yeager to put down his gun. Samuel Yeager did not respond to orders and instead laid on his stomach on the ground, pointed his gun at deputies and began shooting. He was shot and killed.Primary Evidence & Links
Additional Evidence
- Samuel Yeager
- 23
- Male
- White
- I-25 and E. Happy Canyon Road
- Castle Pines
- CO
- 80108
- Douglas
- Douglas County Sheriff's Office
- CO0180000
- Gunshot
- Pending investigation
- No known charges
- No
- Allegedly Armed
- gun
- attack
- yes
- 6738
- Suburban
- Person with a weapon
- person with a gun
Source
Source ID: 9077 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Washington Post -Samuel Yeager, 23, from Douglas County, Colorado - shot on 3 April 2021
- Fatal Encounters -Samuel Yeager, 23, from Castle Pines, Colorado, on 3 April 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65051. Submitted in Mainchain Tx FE2D1AB5618F7E30B7F6471FE39B63A8F69393CE367CDCA1C5E3A716FD2BB3AB, at block height 139385
Transaction details
Tx FE2D1AB5618F7E30B7F6471FE39B63A8F69393CE367CDCA1C5E3A716FD2BB3AB
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: V2vqaIOhuwPATSMg1nFXeAGVyBjUwEO4IPYc+sZ2mJV6/oUh5BTrbpy2sobrAbjyg11v3zhOwA3oV3XUpPTn6g==
Raw Tx data:
Hash Comparison
Hash stored in database: 3056f46bd4da66ef733c80a56c4bee41b35ecd52ced69ce41924eddfc93a4622
Hash from Mainchain Tx: 3056f46bd4da66ef733c80a56c4bee41b35ecd52ced69ce41924eddfc93a4622
Dynamically generated hash: 3056f46bd4da66ef733c80a56c4bee41b35ecd52ced69ce41924eddfc93a4622
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: