coop

Every trade is just a guess about future price. The "certainty" version and your real trades differ only in confidence. Anything you'd do differently if you knew = a mistake you're making today.

Thought experiment: you know with certainty that some asset will be 10x higher on a specific date next year. How do you trade it? How much leverage?

your agent is probably spending too much time adding new features and not enough hardening existing ones

you panic sell because you hold too many positions - how can you have conviction for 10 different positions at once?

Hit top 100 on HL

> (notably, we hold the view that it is not appropriate to refund users who entered their wallet’s seed phrase, as this is not behavior that impersonates CoW Swap – or any DEX for that matter) Seriously?! the interface on swap.cow.fi - at least on mobile where we were affected - stole seed phrases by posing as part of the parent web3 browser. that’s like if the connect wallet button on a browser was able to launch a native keychain prompt that prompted for a password. i would argue that is way worse as it capitalizes on that “autopilot response” that makes exploits like this so successful. i’m very surprised by this, and am almost wondering if this is specifically trying to single us out since we were the biggest loser and accounted for half the losses. in which case couldn’t you guys at least have offered a partial refund? not to mention that we’ve probably generated more than 50% our loss in revenue for cowswap.. there’s at least 10 different ways you guys could’ve gone here that makes more sense. at least including us in the conversation being one of them

User protection is a core promise of CoW Swap. We are therefore proposing a discretionary grants program so that victims of the April 14 DNS hijacking incident can be made whole as quickly as possible. Proposal details can be found on the CoW DAO forum, here: forum.cow.fi/t/cip-draft-di… Note that because of the high sums involved in the incident, this proposal will need to pass governance to go into effect. Please signal your support or give feedback directly in the forum.

my HL vault just crossed 7 fig pnl

this only happens with conviction

prediction: XMR/ZEC outperform BTC/ETH in 2026

AI has made it clear to me that coding is essentially about making decisions. I still have to make the same exact decisions, but now I make the same number of them in a day that I used to in a month.

we thought “login with wallet” was gonna be the norm. no more filling credit cards and addresses repeatedly… right? nope! we decided to login to our wallets with google instead, lmao

finally feel like a "good" trader after 10+ yrs. hit 7-fig PNL in 2025. the way I trade is so much different now. TA is useless for me. maybe i'll finally write on this app

@pseudotheos trust in @GCRClassic

ok. i have to admit something. i wanna be honest i believed eth was gonna go to 10k this cycle

@IamNomad means it’s time to buy

@dYdX a bug in your code caused me to lose ~$1M when I closed a very profitable trade within 1 second im losing my mind and am on my knees please have someone message me?

@NixonLB @safe ohhh in dumb now that makes sense. 100% agree or we should at least get an option to choose. i wouldn’t mind having to create a completely new address/safe to upgrade and manually move funds over

@_cooperton @safe it's referencing a post further up that thread about the multisig upgradeability

Update on Safe{Wallet} Restart The Safe{Wallet} UI displayed the correct-appearing transaction information according to ByBit, yet a malicious transaction that had all valid signatures was executed onchain. Our investigation so far shows: • No codebase breach found: The Safe codebase was checked thoroughly, and no evidence of a breach or modification was found. • No malicious dependencies identified: No signs of a malicious dependency in the Safe codebase affecting the transaction flow (i.e. supply-chain attack). • No unauthorised access to the infrastructure was detected in the logs. • No other Safe address has been affected As stated earlier, we have paused Safe{Wallet} functionalities temporarily to ensure absolute confidence in our platform’s security. Although our investigation shows no evidence that the Safe{Wallet} frontend itself was compromised, we’re conducting a thorough review. Some of the actions include: • Reviewing all of our service configurations • Rotating all our infrastructure credentials • Rebuilding our containers and reapply all our configurations • Conducting a codebase audit with external security researchers We are committed to bringing Safe{Wallet} back up as soon as possible.

@NixonLB @safe the contracts are fine, the hack occurred bc a virus somehow made it on each signers machine - which if i had to guess - waited til they loaded up the Safe UI and injected JS into the UI. a bad chrome extension could prob do this too

@_cooperton @safe x.com/dhkleung/statu…