# $NOID Social Sentiment & Intelligence — 2026-07-10 01:20 UTC

> **Asset:** $NOID  
> **Momentum Status:** Trending Up  
> **Timestamp:** 2026-07-10 01:20 UTC (2026-07-10T01:20:00Z)  
> **Canonical URL:** https://cryptitalk.com/2026-07-10-01-20/crypto/NOID  
> **Overview Brief:** https://cryptitalk.com/2026-07-10-01-20/crypto.md  

---

## 10-Minute Social Metrics
- **Posts Analyzed:** 1
- **Total Impressions:** 366
- **Likes:** 15
- **Retweets:** 2
- **Comments:** 7

---


## Momentum & Sentiment Analysis
Total Engagement - Comments: 7, Retweets: 2, Likes: 15, Impressions: 366


---

## Cited Community Posts & Evidence


### Post #1 by @reddit
> **Author:** [@reddit](https://x.com/reddit)  
> **Metrics:** 3 likes · 0 retweets · 1 comments · 300 views  


> **Source Link:** [https://x.com/reddit/status/419234e84ca17eb10cb30bb77d51906dbadb3fd8bdd76d824c9246872562e1f9](https://x.com/reddit/status/419234e84ca17eb10cb30bb77d51906dbadb3fd8bdd76d824c9246872562e1f9)  


> 
> "Feature Request: Separate Tax Lot Settings for Sales vs. Withdrawals (HIFO for Sales, LOFO for Transfers)

Hey Strike Team, I love the platform and use it for my regular DCA, but I'm currently running into a roadblock regarding tax optimization and self-custody. Right now, Strike uses a blanket HIFO (Highest In, First Out) accounting method for all outgoing transactions. While HIFO is perfect for sales because it minimizes capital gains, applying it universally to on-chain withdrawals/transfers creates a headache for users who want to move their bitcoin to a hardware wallet and use strike as their “bitcoin bank account” from a tax loss harvesting perspective. My current problem:
During the recent price dip, my DCA is getting cheap sats with a low cost basis (50-60k price lots). I want to transfer these newly acquired, low-cost lots to my hardware wallet for long-term storage. However, because Strike applies HIFO to withdrawals, executing a transfer takes my older, high-cost basis lots (the ones currently sitting at a loss - 120k price lots)."




---


## Contributing Accounts

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