# $XOOB Social Sentiment & Intelligence — 2026-08-03 18:20 UTC

> **Asset:** $XOOB  
> **Momentum Status:** Stable  
> **Timestamp:** 2026-08-03 18:20 UTC (2026-08-03T18:20:00Z)  
> **Canonical URL:** https://cryptitalk.com/2026-08-03-18-20/crypto/XOOB  
> **Overview Brief:** https://cryptitalk.com/2026-08-03-18-20/crypto.md  

---

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

---


## Momentum & Sentiment Analysis
Total Engagement - Comments: 0, Retweets: 0, Likes: 0, Impressions: 1


---

## Cited Community Posts & Evidence


### Post #1 by @PavolRusnak
> **Author:** [@PavolRusnak](https://x.com/PavolRusnak)  
> **Metrics:** 180 likes · 18 retweets · 9 comments · 3.4K views  


> **Source Link:** [https://x.com/PavolRusnak/status/2084208317434384892](https://x.com/PavolRusnak/status/2084208317434384892)  


> **Visual Context:** The image shows a black screen with teal text reading "NOT AFFECTED" followed by "Mk1, and Mk2/Mk3 before 4.0.0," which relates to the post by indicating that only older Coldcard hardware wallet models running pre-4.0.0 firmware are unaffected by the Trezor code fiasco.  

> 
> "The only Coldcards that are not affected by the fiasco are the ones that are still running the original Trezor code on them"




---


## Contributing Accounts

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