Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,385
| Gobles, Michigan

Jacob Bender, 39, from Gobles, Michigan, on 26 July 2021

Victim Info

  • Jacob Bender
  • White/European American
  • 39
  • Male

Details

Police responded to reports of a domestic assault. After getting a warrant, police returned to the home and Bender's wife stated Bender was hiding in a basement crawl space. Police attempted to get Bender out of the crawl space with a K-9, who Bender allegedly stabbed. Bender eventually exited the crawl space and a deputy confronted Bender. A deputy shot and killed Bender.

Additional Evidence

  • Jacob Bender
  • 39
  • Male
  • White
  • N. State Street
  • Gobles
  • MI
  • 49055
  • Van Buren
  • Van Buren County Sheriff's Office
  • MI8018000
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • knife
  • attack
  • not fleeing
  • no
  • 7057
  • Rural
  • Part 1 Violent Crime/Domestic disturbance
  • domestic assault

Source

Source ID: 9372 - 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 63706. Submitted in Mainchain Tx 30C7AB7027DA3209567ECB8162ECF8286F16A475AC19C964FCCDCA216F83B3AC, at block height 136511

Transaction details

Tx 30C7AB7027DA3209567ECB8162ECF8286F16A475AC19C964FCCDCA216F83B3AC
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: D1Xo4tUaOfLfxG3HnXY2AFcUmnvOnlnLmwpSPJdLEA4wCCHoqCYhDHS8IUfFHrYgV4oK985X9mJuu1XVs02x6Q==
Raw Tx data:

Hash Comparison

Hash stored in database: 88e08deb5cab65fd0c05fb4fb2b787d9e774a958df414da058215db3e2517a54

Hash from Mainchain Tx: 88e08deb5cab65fd0c05fb4fb2b787d9e774a958df414da058215db3e2517a54

Dynamically generated hash: 88e08deb5cab65fd0c05fb4fb2b787d9e774a958df414da058215db3e2517a54

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: