Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 54,673
| Atlanta, Georgia

Frederick Demor Asberry, 25, from Atlanta, Georgia, on 15 November 2020

Victim Info

  • Frederick Demor Asberry
  • Black/African American
  • 25
  • Male

Details

Around 4 a.m. in front of the Up Lounge a fight began between several men and a security guard. An off-duty Atlanta officer, working an extra job helping with security at the club, was alerted to the dispute. Someone in the group began to shoot. The off-duty officer fired his gun. That officer was not injured. It was not immediately clear who shot whom, but three people were shot, and Frederick Demor Asberry was shot and killed.

Additional Evidence

  • Frederick Demor Asberry
  • 25
  • Male
  • African-American/Black
  • African-American/Black
  • Not imputed
  • 150 Pine Street NE
  • Atlanta
  • GA
  • 30308
  • Fulton
  • 150 Pine Street NE Atlanta GA 30308 Fulton
  • Atlanta Police Department
  • Gunshot
  • Pending investigation

Source

Source ID: 29127 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 54790. Submitted in Mainchain Tx 26668CDE99503ABA9E2B9FD7D18F875958A468982523593689F0ADFC3F0CE6E9, at block height 2832594

Transaction details

Tx 26668CDE99503ABA9E2B9FD7D18F875958A468982523593689F0ADFC3F0CE6E9
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: TtbbXVPC14/UukcpsFlD8CHu/1CDzMX3SCZdDUA13R0DrUfzAUX3zMF+Avxas0+0ualbwIOVzUgQZycbVO5OIw==
Raw Tx data:

Hash Comparison

Hash stored in database: cf6aa100b2d0c858e064513db8e0620a259fcdb55c17a1f9458920867734c35d

Hash from Mainchain Tx: cf6aa100b2d0c858e064513db8e0620a259fcdb55c17a1f9458920867734c35d

Dynamically generated hash: cf6aa100b2d0c858e064513db8e0620a259fcdb55c17a1f9458920867734c35d

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: