Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,469
| Nashville, Tennessee

Nika Nicole Holbert, 31, from Nashville, Tennessee, on 12 March 2021

Victim Info

  • Nika Nicole Holbert
  • Black/African American
  • 31
  • Female

Details

Nashville police officer Josh Baker pulled over Holbert's vehicle while she was driving. Police allege Baker pulled Holbert over as he recognized her vehicle in connection to another individual wanted on drug warrants. That individual was not in the vehicle, and Baker proceeded to question Holbert. Holbert tells Baker the vehicle is not hers and Baker proceeded to search through Holbert's bag. Baker alleges he found drugs in Holbert's purse and walked back to his patrol vehicle. Holbert gets her purse again and gets back into the vehicle. Baker escalates and uses his taser on Holbert and tugs on her to exit the vehicle. He then shoots Holbert, killing her.

Additional Evidence

  • Nika Nicole Holbert
  • 31
  • Female
  • Black
  • Brick Church Pike and Ewing Drive
  • Nashville
  • TN
  • 37207
  • Davidson
  • Nashville Police Department
  • TN0190100
  • Gunshot, Taser
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • gun
  • attack
  • not fleeing
  • yes
  • 6696
  • Suburban
  • https://fatalencounters.org/wp-content/uploads/2021/03/Nika-Nicole-Holbert.jpg
  • Other
  • vehicle's owner has drug warrants, was not the person killed

Source

Source ID: 8791 - Mapping Police Violence

Cross References

This report has possible entries from multiple sources

BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65377. Submitted in Mainchain Tx C24378636112342BE6AAF91F4252B845240D08C7B3B57463A3BB34AC82245BC7, at block height 140476

Transaction details

Tx C24378636112342BE6AAF91F4252B845240D08C7B3B57463A3BB34AC82245BC7
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: 2H8UO1dAtxkwRxgZwsXt0UKADYFx9t51vp6NXbFDmCgckgn5U0jOGNGcw+Hoq/9W2AkEo7oUi+FUH7QbmU+07g==
Raw Tx data:

Hash Comparison

Hash stored in database: ad2b16b282a01f57a753142427ac2f77b19a42b912e0de1c1da6c48841889291

Hash from Mainchain Tx: ad2b16b282a01f57a753142427ac2f77b19a42b912e0de1c1da6c48841889291

Dynamically generated hash: ad2b16b282a01f57a753142427ac2f77b19a42b912e0de1c1da6c48841889291

Hashes Match?
YES

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: