# $GRAM Social Sentiment & Intelligence — 2026-07-31 19:00 UTC

> **Asset:** $GRAM  
> **Momentum Status:** Trending Up  
> **Timestamp:** 2026-07-31 19:00 UTC (2026-07-31T19:00:00Z)  
> **Canonical URL:** https://cryptitalk.com/2026-07-31-19-00/crypto/GRAM  
> **Overview Brief:** https://cryptitalk.com/2026-07-31-19-00/crypto.md  

---

## 10-Minute Social Metrics
- **Posts Analyzed:** 1
- **Total Impressions:** 754
- **Likes:** 5
- **Retweets:** 3
- **Comments:** 1

---


## Momentum & Sentiment Analysis
Total Engagement - Comments: 1, Retweets: 3, Likes: 5, Impressions: 754


---

## Cited Community Posts & Evidence


### Post #1 by @provablyfairorg
> **Author:** [@provablyfairorg](https://x.com/provablyfairorg)  
> **Metrics:** 17 likes · 0 retweets · 5 comments · 3.9K views  


> **Source Link:** [https://x.com/provablyfairorg/status/2083092018977296815](https://x.com/provablyfairorg/status/2083092018977296815)  


> **Visual Context:** A July 30, 2026 email from "PR BetFury" (pr@betfury...) to the ProvablyFair org confirms that a Limbo game configuration deployed on May 29, 2026 caused incorrect RTP and win probability parameters, and outlines remediation steps including service suspension, player compensation, and CI/CD safeguards for affected sessions between May 29 and July 24, 2026.  

> 
> "Update: BetFury responded to our investigation and confirmed our core finding.

If you played Limbo on BetFury between May 29 and July 24, you may be owed money.

Contact support and ask for your session records and what compensation applies to your account.

Their response came"




---


## Contributing Accounts

- `@HopprStudio` (https://x.com/HopprStudio)