!(NoRisk)

insecure underachiever.
short term strats & mm/hft. ml rl nn (non critical path).
rust, python.

[!(NoRisk) @risk_generator]

@annanay how do managed accounts work from a regulatory and legal perspective at QFEX?

[!(NoRisk) @risk_generator]

@teortaxesTex RL FTW

[!(NoRisk) @risk_generator]

@loraclexyz true, cast iron can also help with ferritin deficiency (lots of health issues).

[Dr. Catharine Young @DrCatharineY]

A cancer vaccine, using the same core mRNA technology as the COVID vaccine, has shown an almost 50% reduction in the risk of melanoma recurrence or death when combined with immunotherapy.

This is why we fund MRNA technology.

[!(NoRisk) @risk_generator]

@MarkBestForex

[Citrini @citrini]

Morgan Stanley’s price discovery happens on @tradexyz

[!(NoRisk) @risk_generator]

@skooookum this is how you can avoid those cancers: getting vaccinated with Gardasil (since 2006).

[!(NoRisk) @risk_generator]

this is why you password protect ssh keys

[Andrej Karpathy @karpathy]

Software horror: litellm PyPI supply chain attack.

Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.

LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.

Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.

Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.

Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

[!(NoRisk) @risk_generator]

@06duggy @Lighter_xyz @vnovakovski https://t.co/6uXRcHQMxH

[!(NoRisk) @risk_generator]

@systematicls max(complexity, !(norisk))

[!(NoRisk) @risk_generator]

@DEXoverCEX @0xLoris you mean this $AVNT ?

[!(NoRisk) @risk_generator]

@AgustinLebron3 have you experimented with asynchronous algorithms like IMPALA in trading? If so, what was your experience?

[!(NoRisk) @risk_generator]

@MarkBestForex @BeatzXBT @DegenSugarBoo @0xFaust12 @neogoose_btw yes, servers would use EPYC cpus for generic apps. Threadrippers for heavy parallel computation where a higher clockrate per core is needed, for example running environment simulations in RL.

[!(NoRisk) @risk_generator]

@AgustinLebron3 @Lifrordi gl, RL is fun!
on which timeframes? sub-second?

[!(NoRisk) @risk_generator]

@FormulaDeltaOne did u learn anything new+exciting in your QR roll in the last year? not refering to mundane things.

[!(NoRisk) @risk_generator]

@Dub0x3A @TaiwanQuant @OBS_orderflow sounds awesome!!

[!(NoRisk) @risk_generator]

@Dub0x3A @TaiwanQuant @OBS_orderflow like way more number of cards and LOB with depths?

[!(NoRisk) @risk_generator]

my quant

[!(NoRisk) @risk_generator]

@Vertox_DF senior manual hft mm