Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,569
| North Lauderdale, Florida

Jeffrey Guy Sacks, 26, from North Lauderdale, Florida, on 15 April 2021

Victim Info

  • Jeffrey Guy Sacks
  • White/European American
  • 26
  • Male

Details

Dispatch received several 911 calls complaining there was a man with a knife who cut himself inside of the Ross clothing store. After the first deputy asked the man to drop the knife after seeing him outside of the store, the man reportedly charged at the deputy. The deputy shot and killed Jeffrey Guy Sacks.

Additional Evidence

  • Jeffrey Guy Sacks
  • 26
  • Male
  • White
  • 7300 West McNab Road
  • North Lauderdale
  • FL
  • 33068
  • Broward
  • Broward County Sheriff's Office
  • FL0060000
  • Gunshot
  • Pending investigation
  • No known charges
  • Yes
  • Allegedly armed
  • knife
  • other
  • not fleeing
  • no
  • 6792
  • Urban
  • https://fatalencounters.org/wp-content/uploads/2021/04/Jeffrey-Guy-Sacks.jpg
  • Person with a Weapon
  • person with a knife/welfare check

Source

Source ID: 9194 - 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 64880. Submitted in Mainchain Tx 67020262F48B3C3224F574AA311DE46DE8988EB10D678159AB0E3B5367121048, at block height 139214

Transaction details

Tx 67020262F48B3C3224F574AA311DE46DE8988EB10D678159AB0E3B5367121048
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: VpKTH+4xvpNkuXwLVCuYn0X5D27M+mZJOno5OeVy+B4jVzs9PJjI7byfCeYAjMODLAb4EcFtIeI8heTUdCK6ZA==
Raw Tx data:

Hash Comparison

Hash stored in database: e9c460a40b8119b3e5870a2a05e7ffa9adcdc4b9df82df395055306cef315341

Hash from Mainchain Tx: e9c460a40b8119b3e5870a2a05e7ffa9adcdc4b9df82df395055306cef315341

Dynamically generated hash: 6c93726002d629132c39aef5f43b19ed2820e54a464839525a641725201bc0ba

Hashes Match?
NO

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: