justNick

You weren’t meant to live an uncomfortable life. $STRC

justin sun vs wlfi the original token deployed sep 2024 had no blacklist and no seizure, but it was upgradable. the blacklist was added in v2 on aug 24, 2025. 11 months after sun invested and one week before trading opened. on nov 19, 2025, another upgrade added batch reallocation, essentially seizing, justified with saving phished funds. whatever the paper contract said, the code for vesting contract supports cliff dates, linear schedules, and up to 8 segments per category. wlfi used none of these to restrict sun. they chose 20% instant lump-sum unlock, then punished him for using a fraction of it. the remaining 80% has no vesting schedule at all, 7+ months later, claimable() returns 0. the vesting contract has per-category schedules to enforce token lockups. what's interesting is wlfi has carved out a special category 3 specifically for justin sun, he's the only user in it. the other 519 investors are in category 1. 14 minutes before sun activated his wallet, wlfi's own 3-of-5 multisig configured category 3 to release 20% of his 3b allocation as freely transferable tokens at trading start. over the next 3 days sun transferred out 55m. a single guardian eoa (also on multisig) blacklisted him. that address is also the sole owner of a second guardian safe with threshold 1. so one person can freeze anyone, while seizing requires 3-of-5. meanwhile, the same multisig is using 5b wlfi as collateral on dolomite to borrow $250m in stablecoins. they represent 98% of all wlfi on dolomite and 86% of the protocol's entire borrow volume. two safes with the same five signers, running a usd1/usdc loop that recycles borrowed usd1 as collateral to borrow usdc and feed it back.

AMD Senior AI Director confirms Claude has been nerfed. She analyzed Claude's session logs from Janurary to March: > median thinking dropped from ~2,200 to ~600 chars > API requests went up 80x from Feb to Mar. less thinking and failed attempts meaning more retries, burning more tokens, and spending more on tokens > reads-per-edit dropped from 6.6x → 2.0x. model stops researching code before touching it. > model tried to bail out or ask "should i continue" 173 times in 17 days (0 times before March 8). > self-contradiction in reasoning ("oh wait, actually...") tripled. > conventions like CLAUDE.md get ignored because there's less thinking budget to cross-check edits > 5pm and 7pm PST are the worst hours, late night is significantly better. this means the thinking allocation is most likely GPU-load-sensitive.