Bismark Asare, 40, from Houston, Texas, on 2 August 2020
Victim Info
- Bismark Asare
- Black/African American
- 40
- Male
Details
8/2/2020: A 17-year-old sped off from a traffic stop after being pulled over by a Harris County deputy, leading to a high-speed pursuit. Police say the fleeing vehicle made a sudden U-turn and turned eastbound in westbound lanes. He tried to turn into the entrance ramp to a freeway, cutting off an Uber driver, Bismark Asare, who was able to avoid them, but was then fatally struck by the deputy. https://abc3340.com/news/nation-world/uber-driver-killed-after-police-slam-into-car-trying-to-stop-another-driver-08-02-2020Primary Evidence & Links
Additional Evidence
- Bismark Asare
- 40
- Male
- African-American/Black
- African-American/Black
- Not imputed
- 18211 Katy Fwy
- Houston
- TX
- 77094
- Harris
- 18211 Katy Fwy Houston TX 77094 Harris
- Harris County Sheriff's Office
- Vehicle
- Pending investigation
- No
- 2020
- https://fatalencounters.org/wp-content/uploads/2020/08/Bismark-Asare.jpg
Source
Source ID: 28521 - Fatal Encounters
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 68766. Submitted in Mainchain Tx 4DB4B4BA141A8EC256E56BAC990EBE04F18FD436C524E1CE556543B7B7A08F20, at block height 149211
Transaction details
Tx 4DB4B4BA141A8EC256E56BAC990EBE04F18FD436C524E1CE556543B7B7A08F20
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: kg05EPBDiHQpUfXqRd/HlIKFUsNUtCzoFgQkkGFozP4qycSAl+K430Jc9TKaxAsQFJAjd4Rg1/4LDpGJe4H29g==
Raw Tx data:
Hash Comparison
Hash stored in database: cf998b54baff9a661d0e2cd01d565c52170c4ebf5c3c2d75a37d97a945877f77
Hash from Mainchain Tx: cf998b54baff9a661d0e2cd01d565c52170c4ebf5c3c2d75a37d97a945877f77
Dynamically generated hash: cf998b54baff9a661d0e2cd01d565c52170c4ebf5c3c2d75a37d97a945877f77
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: