​I feel like almost nobody in the casual crypto space is talking about what just went down in Washington, and it is a massive red flag for anyone trading on-chain. ​On June 9, 2026, the House Ways and Means Committee held a full-committee hearing on a new package of crypto tax bills. One specific bill in that pile is an absolute trainwreck for retail traders. ​It’s called H.R. 9172: The Applying Existing Tax Anti-Abuse Rules to Digital Assets Act (introduced by Rep. Jodey Arrington). ​What does H.R. 9172 actually do? ​It officially forces traditional Wall Street Section 1091 Wash Sale Rules and Constructive Sale Rules straight onto crypto. If you sell a volatile token at a loss to manage your risk during a dip, you cannot buy that token (or a "substantially identical" wrapped/bridged variant) back within 30 days without forfeiting your tax deduction. submitted by /u/semaj_1028 [link] [Kommentare]

I'm confused at what kind of coin this is and why it has value. It's available on coinbase. ​ SPYBOX ​ (DEX) ​ It went up 50% in like five minutes. submitted by /u/comment_dummy [link] [Kommentare]

https://finance.yahoo.com/markets/crypto/articles/riches-rags-buying-crypto-etf-181012001.html submitted by /u/CriticalCobraz [link] [Kommentare]

https://www.fxstreet.com/cryptocurrencies/news/monero-prices-rocket-to-438-amid-120-million-onchain-laundering-maze-202606121217 submitted by /u/CriticalCobraz [link] [Kommentare]

my preprint is on SSRN and i feel somewhat shy to share it here... but the PKU lab's paper that cited mine got accepted by ICML 2026: https://arxiv.org/html/2602.06358v2 submitted by /u/max6296 [link] [Kommentare]

Posting this to document my case and ask if anyone has had something similar resolved. Late last year I deposited a large amount of WETH on the Unichain network to a Kraken-provided deposit address (worth a substantial five-figure sum at the time). After it never credited, support told me that only native ETH — not WETH — was supported for deposits at that time. They opened a ticket to arrange a manual recovery. I knew Kraken doesn't guarantee recovery of unsupported tokens, but WETH is trivially convertible to ETH (it's just wrapped ETH; wrap/unwrap is a native function on the chain — you literally just call it), and given the amount I expected it to be slow but eventually resolved. Timeline: Late 2025 — Deposit made. Doesn't credit. Support confirms WETH unsupported and opens a ticket for manual recovery. January 2026 — Email from support: they "confirm that unsupported asset deposit mistake issue is now escalated with our technical team who will be executing a manual recovery attempt." Following months — Repeated copy-pasted "under active investigation" replies. I file a formal complaint to speed things up. Early June 2026 — Standard support still tells me my case is "under active investigation." The next morning (about ten hours later) — Compliance responds to my complaint: "due to technical limitations associated with this specific network and asset combination, recovery is not currently possible," adding that "at no stage has a recovery been confirmed or completed." My problem with this: The January email used plain indicative language ("will be executing a manual recovery attempt") with zero mention of any technical limitation that could make it impossible. Months later, it's suddenly "not possible" with no detail. The two June emails came roughly ten hours apart and contradict each other — one says active investigation, the next says it's impossible. It's hard to believe a recovery promised in January was only discovered to be technically impossible in that short window. It reads like the "technical impossibility" line is there to limit liability rather than reflect an actual engineering finding. Has anyone here recovered an unsupported-token deposit (especially WETH or a wrapped asset) after a similar back-and-forth? Did escalation, a regulator complaint, or a legal letter move things? Any pointers appreciated. (I have the ticket number and redacted email screenshots with timestamps — happy to share if a Kraken rep reaches out.) submitted by /u/That_Ring_5604 [link] [Kommentare]

I used to be into crypto from 2016-2021. Between 2019-2021, i made a x33 and just exited with my gains to focus on my personal life. I used to visit coinmarket everyday religiously back in those days. But now I don't know shit. A lot has changed. I don't really know where to start. Do you guys have any interesting coin to shill me up ? Or any newsletter of some good researcher that do macro analysis ? (i don't mind paying) Ty submitted by /u/NoiseDr [link] [Kommentare]

I’ve been working on a mission assurance architecture called Parallax and recently completed another validation run in a degraded operating environment. In this sim run, an autonomous USV fleet experienced GNSS/RF degradation resulting in conflicting navigation observations across multiple assets. Rather than assuming all telemetry was trustworthy, the system continuously evaluated observation integrity, measured divergence from a shared world model, isolated compromised data sources, reconstructed authority through distributed consensus, and maintained mission continuity without operator intervention. One of the problems I’m interested in is what happens after sensor fusion. Most autonomy stacks do a good job combining observations, but what happens when those observations can no longer be trusted? The entire system runs locally at the edge with no cloud dependency. All processing, validation, trust scoring, consensus generation, and decision support remain completely air-gapped and self contained. Current areas of development: • Distributed trust scoring • Reality integrity assessment • Consensus reconstruction • Autonomous recovery and reintegration • GNSS degradation and spoofing resilience • Edge-native operation with no cloud connectivity Interested in hearing how others are approaching sensor trust, degraded navigation environments, and resilient autonomy. submitted by /u/DraevenOfficial [link] [Kommentare]

Been working on a PiCar-X build on a Raspberry Pi 4B. v1 goal: detect an AprilTag (36h11 family, ID 0), steer toward it with a PID controller, drive forward, and stop at a configured distance threshold. Toggle it on from a browser dashboard, 3-second countdown, and it goes. I built this entirely with Claude Code. It’s been a massive productivity boost while balancing a full-time job, and the process of building agentically has been a great learning experience. WebSocket concurrent send corruption The broadcast coroutine and the sensor push loop were both calling send_json() concurrently. At await boundaries they interleaved, Starlette threw, and the client was silently dropped from the send set — meaning the toggle-off confirmation never arrived and the button stayed stuck in active state even after the car stopped. Fixed by replacing the shared client set with a per-connection asyncio.Queue and a single drain task per connection. Camera color inversion that didn't respond to the obvious fixes BGR888 didn't fix it. RGB888 + cvtColor didn't fix it either. Root cause: capture_array() on this Pi hardware returns RGB regardless of the format name, and this platform's libjpeg encodes from RGB input correctly without any conversion. One-line fix once the actual data layout was confirmed via a frame diagnostic log. Had to fully remove Vilib It uses a Picamera2 internal API (allocator) removed in 0.3.36 — crashes on any camera restart after a chase session. Server now owns Picamera2 directly for the full session lifetime. What's next v2 candidates on the list: distance-proportional speed, latching stop behavior, camera tilt tracking, and operator override during chase. Stack: Raspberry Pi 4B · PiCar-X v2.0 · Picamera2 · pupil-apriltags · FastAPI · Python 3.13 submitted by /u/okineedaplan [link] [Kommentare]