Audit log

Every state-changing event for Berally: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

1. #1publishby system:backfill

   2026-05-29 15:54:29Z
   Score: ? → ? (no score change)
   anchoranchored

   chain

   ●mainnet-betaslot 422,969,551

   sig

   4CajxBjscSAr…CcgGb5Grcopyexplorer ↗

   hash

   BWfUu5ZJhvMN…RZrsg1mwcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (4997 B) ▸

   {"actor":"system:backfill","investigation_id":"9c44b38b-7ccf-428b-a435-2889f25d7b0a","kind":"publish","page_slug":"berally","published_at":"2026-05-29T15:54:29.484Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Berally","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.berally.io/","type":"other","url":""},{"credibility":3,"name":"https://docs.berally.io/","type":"other","url":""},{"credibility":3,"name":"https://daic.capital/ecosystem/berachain/berally-ai-agent-social-trading","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://icodrops.com/berally/","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/ico/berally","type":"other","url":""},{"credibility":3,"name":"https://www.coingecko.com/en/coins/berally-token","type":"other","url":""},{"credibility":3,"name":"https://daic.capital/ecosystem/berachain/berally-ai-agent-social-trading","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.mitrade.com/insights/news/live-news/article-3-699081-20250316","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/news/feed/4fa8c-berally-hack-attacker-drains-liquidity-pool","type":"other","url":""},{"credibility":3,"name":"https://www.nominis.io/insights/crypto-security-incidents-march-2025","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.mitrade.com/insights/news/live-news/article-3-699081-20250316","type":"other","url":""},{"credibility":3,"name":"https://www.cryptopolitan.com/berally-hack-attacker-drains-liquidity-pool/","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/news/feed/4fa8c-berally-hack-attacker-drains-liquidity-pool","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/berally-token","type":"other","url":""},{"credibility":3,"name":"https://www.coincarp.com/currencies/berally/","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/price/berally","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://daic.capital/ecosystem/berachain/berally-ai-agent-social-trading","type":"other","url":""},{"credibility":3,"name":"https://icodrops.com/berally/","type":"other","url":""},{"credibility":3,"name":"https://docs.berally.io/","type":"other","url":""}]}],"sources_used":[],"summary":"Berally is a SocialFi and AI-agent social trading platform built on the Berachain blockchain, issuing the BRLY token via a public presale on Fjord Foundry in late 2024. In March 2025, the project suffered a significant security incident in which its deployer private key was alleged to have been leaked, resulting in all vesting tokens being dumped into its liquidity pool and approximately $90,000 drained from the pool. The BRLY token subsequently collapsed to roughly 99% below its all-time high, trading has effectively ceased, and community members have alleged the incident was an inside job, though this has not been formally substantiated.","timeline":[{"date":"2024-12-06","event":"Berally whitelist snapshot taken for Fjord Foundry presale; eligibility limited to Berachain NFT holders and FJO stakers with minimum 500 FJO.","source":""},{"date":"2024-12-15","event":"Berally presale whitelist period closes on Fjord Foundry.","source":""},{"date":"2025-02-13","event":"BRLY token reaches all-time high of approximately $0.000562 on Berachain mainnet.","source":""},{"date":"2025-03-14","event":"Berally deployer private key is compromised; attacker bypasses vesting schedule, dumps all vesting tokens into liquidity pool, and drains approximately $90,000 in ETH from the pool. Berachain co-founder Smokey posts public warning before official confirmation.","source":""},{"date":"2025-03-15","event":"Berally issues official statement confirming the deployer key leak. Team advises users to revoke dApp and staking access. Community members allege on-chain evidence of insider involvement.","source":""},{"date":"2025-03-16","event":"Berally announces a compensation plan offering up to 120% reimbursement for affected token holders and claims the attacker has been identified and restricted via centralized exchange reporting.","source":""},{"date":"2025-03-19","event":"BRLY token reaches all-time low of approximately $0.0000019, down approximately 99.7% from its all-time high.","source":""},{"date":"2025-03-19","event":"Berally migrates BRLY to a new contract address on Berachain following the exploit.","source":""},{"date":"2025-05-28","event":"CoinGecko reports BRLY has stopped trading on all listed exchanges. Fully diluted valuation stands at approximately $17,000. Trading volume near zero on Kodiak V2 DEX.","source":""}]},"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 3b1a6664-3aa2-47aa-a3af-63ea37bb174ccopy
2. #2rescoreby systemsystem

   2026-10-27 06:04:14Z
   Score: 32 → 41 (+9)
   Rescored under Scoring v2, the published formula (avoid.net/scoring): 32 → 41. Problems weighed by who is responsible: the subject's own conduct −16, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6.
   anchoranchored

   chain

   ●mainnet-betaslot 461,963,938

   sig

   3oLSDeYmh7Z5…xpTKcRjLcopyexplorer ↗

   hash

   6SdUDTUTb5Vc…bgzzTnfUcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (596 B) ▸

   {"actor":"system","decided_at":"2026-10-27T06:04:14.380Z","decision":"rescore","investigation_id":"9c44b38b-7ccf-428b-a435-2889f25d7b0a","new_score":41,"page_slug":"berally","prev_score":32,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 32 → 41. Problems weighed by who is responsible: the subject's own conduct −16, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6.","score_delta":9,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision b4e2ba22-85bd-4536-8374-b0ab55527e49copy
3. #3reviewby reviewerreviewer

   2026-11-02 05:22:55Z
   Score: 41 → 41 (no score change)
   The core incident (deployer key leak, vesting dump, Smokey warning, 'skill issue' reply, trading halt) is supported by the readable sources. The $90,000 figure is a commenter estimate and appears as fact in the summary. The 120% compensation, CEX attacker identification, residual-permissions detail and the March 19 ATL could not be confirmed. Timeline entries are unsourced. Current status could not be established beyond stopped trading.
   anchoranchored

   chain

   ●mainnet-betaslot 464,376,164

   sig

   4tYGBuG64RFs…7SSTia3Fcopyexplorer ↗

   hash

   BDcnTQwMv8pv…qfvKXE1Ncopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1245 B) ▸

   {"actor":"reviewer","artifact_identity":"648df561750c8a8a018e33a1201d9df0","decided_at":"2026-11-02T05:22:55.318Z","decision":"review","disputed_pct":0.4,"findings_hash":"EDr5hrffnoohNurhGGBzLkQXNtG1qc1vnCbLBC14WEq8","investigation_id":"9c44b38b-7ccf-428b-a435-2889f25d7b0a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":41,"page_content_hash":"219c9cef4deb01b64930f416cd1a49ab84901b9bc18b5fbfd7f8cb6a2a56c8a8","page_slug":"berally","prev_score":41,"reason":"The core incident (deployer key leak, vesting dump, Smokey warning, 'skill issue' reply, trading halt) is supported by the readable sources. The $90,000 figure is a commenter estimate and appears as fact in the summary. The 120% compensation, CEX attacker identification, residual-permissions detail and the March 19 ATL could not be confirmed. Timeline entries are unsourced. Current status could not be established beyond stopped trading.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision dba5ed6f-36e9-4624-be59-e04f65f7e206copy
4. #4review reviseby judgejudge

   2026-11-02 05:22:55Z
   Score: 41 → 41 (no score change)
   The core incident (deployer key leak, vesting dump, Smokey's warning, the 'skill issue' reply, and the trading halt) was confirmed by readable sources (claim_findings[0], [5], [6], [8]). However, 6 of 15 checked claims (40%) could not be verified, including the 120% compensation plan and exchange-based attacker identification (claim_findings[3]), the residual-permissions detail (claim_findings[4]), the March 19 all-time low (claim_findings[7]), and the unsourced ZachXBT reference (claim_findings[12]). The summary also presents the roughly $90,000 loss as fact when it is only a community estimate (claim_findings[2]), the FDV figure is stale (claim_findings[9]), and every timeline entry lacks a source. The penalty is set at the lower end of the band because nothing was found to be contradicted, the reviewer's confidence is low, and many failures stem from unreadable sources.
   anchoranchored

   chain

   ●mainnet-betaslot 464,376,168

   sig

   XiXCzMsrY2JU…WAaEnTd1copyexplorer ↗

   hash

   PLfw8HVGkQDp…ZpjYgafbcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1523 B) ▸

   {"actor":"judge","artifact_identity":"648df561750c8a8a018e33a1201d9df0","band_override":null,"decided_at":"2026-11-02T05:22:55.318Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"9c44b38b-7ccf-428b-a435-2889f25d7b0a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":41,"page_slug":"berally","prev_score":41,"reason":"The core incident (deployer key leak, vesting dump, Smokey's warning, the 'skill issue' reply, and the trading halt) was confirmed by readable sources (claim_findings[0], [5], [6], [8]). However, 6 of 15 checked claims (40%) could not be verified, including the 120% compensation plan and exchange-based attacker identification (claim_findings[3]), the residual-permissions detail (claim_findings[4]), the March 19 all-time low (claim_findings[7]), and the unsourced ZachXBT reference (claim_findings[12]). The summary also presents the roughly $90,000 loss as fact when it is only a community estimate (claim_findings[2]), the FDV figure is stale (claim_findings[9]), and every timeline entry lacks a source. The penalty is set at the lower end of the band because nothing was found to be contradicted, the reviewer's confidence is low, and many failures stem from unreadable sources.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 892de3ad-cb8d-4c57-942a-9c5b5ebe729bcopy
5. #5rescoreby systemsystem

   2026-11-02 05:22:56Z
   Score: 41 → 50 (+9)
   Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 41 → 50. Problems weighed by who is responsible: the subject's own conduct −8, concerns that are not fraud −6.4, problems around the subject, caused by others −0.8; 2 section(s) set aside until a failed fact-check is resolved.
   anchoranchored

   chain

   ●mainnet-betaslot 464,376,173

   sig

   3pzWLEeqmg15…23sMS7k9copyexplorer ↗

   hash

   AL5JTidgmE6w…X3T6a2p7copysha256 → base58

   verifying row…full verify ↗

   canonical bytes (706 B) ▸

   {"actor":"system","decided_at":"2026-11-02T05:22:55.318Z","decision":"rescore","investigation_id":"9c44b38b-7ccf-428b-a435-2889f25d7b0a","new_score":50,"page_slug":"berally","prev_score":41,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 41 → 50. Problems weighed by who is responsible: the subject's own conduct −8, concerns that are not fraud −6.4, problems around the subject, caused by others −0.8; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":9,"score_model":"v2","sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision 8c7c7094-dee9-4d77-8ba3-c9b1dfd77bb5copy