Nika Nicole Holbert, 31, from Nashville, Tennessee, on 12 March 2021
Victim Info
- Nika Nicole Holbert
- Black/African American
- 31
- Female
Details
Officer Josh Baker conducted a traffic stop of a black Chevrolet Camaro. Police said the owner of the car had six outstanding drug warrants. The owner of the car, the person with the outstanding warrants, was not the person driving, but the situation devolved into a shootout. The driver, Nika Nicole Holbert, and Baker exchanged fire. Both suffered gunshot wounds. Holbert was killed.Primary Evidence & Links
Additional Evidence
- Nika Nicole Holbert
- 31
- Female
- African-American/Black
- African-American/Black
- Not imputed
- Brick Church Pike and Ewing Drive
- Nashville
- TN
- 37207
- Davidson
- Brick Church Pike and Ewing Drive Nashville TN 37207 Davidson
- Metropolitan Nashville Police Department
- Pending investigation
- https://fatalencounters.org/wp-content/uploads/2021/03/Nika-Nicole-Holbert.jpg
Source
Source ID: 29793 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Washington Post -Nika Nicole Holbert, 31, from Memphis, Tennessee - shot on 12 March 2021
- Mapping Police Violence -Nika Nicole Holbert, 31, from Nashville, Tennessee, on 12 March 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65383. Submitted in Mainchain Tx 057ECFF78EF334D6282D3BB13B5A094C32C6A635B159375FDEF71997155DE674, at block height 140482
Transaction details
Tx 057ECFF78EF334D6282D3BB13B5A094C32C6A635B159375FDEF71997155DE674
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: waiDwRAKJzxsWwzP3MTWNoflwtV6F3obNbXs87wdp5AOVpDq9Mm72JHEuaH5/9m/ZzgJOJXnRJmLRkmeuuivYQ==
Raw Tx data:
Hash Comparison
Hash stored in database: fbb15562372e6f45a21cc14af9635dd0b7be45f04e0849a606f70a206c7e3285
Hash from Mainchain Tx: fbb15562372e6f45a21cc14af9635dd0b7be45f04e0849a606f70a206c7e3285
Dynamically generated hash: 15ad4b09d74ac9d37bf6c2b85d626300850d4afc00ff41651d91c88e75b13821
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: