Too much sophistication leads to fakeness.
Too much desiness leads to illiteracy.
We need a moderate path:
Desi + sophistication = perfect balance.
#SophisticatedDesi
The MM playbook is purely predatory. They weaponize negative funding to manufacture these squeezes.
I tracked a similar engineered trap by DWF on $ SIREN. They spoofed a 3M token transfer to ChangeNOW to fake a sell signal, deliberately baiting retail into shorts right before the squeeze.
https://t.co/p2yTxLihxn
The pattern seems recurring: Scam wick up -> Sideways consolidation -> Fake natural rally -> Double top -> Crash.
The Citadel intern story is great, but jumping from a $5 VPS to institutional-grade arbitrage is hilarious. ๐ญ
Polymarket is an off-chain CLOB with on-chain settlement. You're fighting Polygon block times and state syncs.
Real arb requires at least a self-hosted node for sub-millisecond execution. The infra costs alone eat this "bot" alive.
@zachxbt@timahhl The payloads are hyper targeted. Where dependencies are poisoned with duplicate packages like crypto js and tailwind in these interview repos, running postinstall scripts in the background to silently scrape keys.
https://t.co/t2MmOsxx3W
@feross They especially target web3 devs for validator keystores, MEV configs and raw private keys sitting in .env files. By the time you check node_modules, the postinstall script has already self-destructed. The lockfile is your only forensic witness.
@Nethermind M curious how the index handles high-cardinality address sets. For dense queries, thousands of pool addresses over a 1-2 block range. The Bloom filter bottleneck doesn't apply. Does the index lookup cost scale with array size at the narrow end?
@feross They especially target web3 devs for validator keystores, MEV configs and raw private keys sitting in .env files. By the time you check node_modules, the postinstall script has already self-destructed. The lockfile is your only forensic witness.
Disabling postinstall by default sounds good until web3 devs hit it. secp256k1, keccak and half your crypto bindings need those hooks to compile. First time hardhat breaks, devs just dump everything into trustedDependencies to move on. You traded one attack surface for alert fatigue on another. supply chains still broken.
Directional alpha decays in milliseconds on a CLOB like Hyperliquid. Good alpha means absolutely nothing if your LLM takes a full second to process the signal. By the time the agent fires the execution call, enterprise C++/Rust bots have already repriced the book and eaten the liquidity