Trade six types of strategies
If you have momentum trades, add in a system for mean-reversion. If you have trend-following trades, add some carry strategies. +5 from one strategy, could be -4 from the other and it'll auto-reduce scale
h/t discussion w/ @SimpelAlpha
Thread👇
The key to approaching this is to be very optimistic (slightly ignorant) on the work required
Not being facetious, because if you *knew* how much work it was up front, the smart thing would be to never start
And if you never start, you'd never improve, and that's no way to go through life
Inspired by recent discussion about whether it's possible to learn trading outside an elite firm.
If you're the kind of person that reads this project and thinks it sounds fun, imo you'll be able to learn employable trading skills just fine on your own. https://t.co/czZMfucmpT
@0xMolodykh I have other tricks too, like if the week number is <12, i dont start at 1-31 because its confusing
2027.1.15 looks like a date, but 2027.1.40 is YYYY.W.N
YYYY.W.N is the best versioning
W is week number, and you just cut a new N on every deploy
Every time you bump a repo for deploy, you bump the monorepo version as well, so with a single YYYY.W.N monorepo version, you get the full state of the system at any point in time
@o_wutang My view on this - humans were meant to make art (express creativity) and explore (learn and push knowledge)
What we call “work” just happens to be one of the expressions of those
@fuckyourputs Yeah it’s pretty good
I have it wired up multi-server thru NFS
For some bots I give them their own OptMem to not contaminate
It’s not a wiki system though. Since you have to manually “memo forget” I.e. no dreaming by default built in
When Anthropic says “wiki” do they mean a wiki-like system of markdowns
Or literally MediaWiki because that context is already rich
I’ll try some experiments. OptMem does similar things that objects recent memory into every session but does not by default have “dreaming” or “correct/forget” loops
Memory is what allows Claude to learn from experience. In a new Engineering Blog post, we share how “dreaming” helps Claude organize what it’s learned, correct its mistakes, and find what it needs more easily the next time. https://t.co/uUEN4bNkr9
@0xLightcycle didnt read anything of what they posted. But knowing that karpathy works w them i would confidently assume this is what they refer to https://t.co/Hs177tTy5R since its something he has been praising for a while
@gkhalin@VictorTaelin I see it as a combination of the model and harness trained together
I used claude-in-opencode for a while before they banned it
Now the native harness is better
The native harness is much better than any custom harness you can make
You only need three things to manage a swarm and use the native harnesses:
1. Shared memory (e.g. your custom location or OptMem from @VictorTaelin )
2. Communication method (hijack Claude's SendMessage and Codex's queue)
3. Native subagents - e.g. spin up agents and initialize w/ tmux
Then for any fancy schedule/bot/manager/coordinator you can just use a long running session
@samuellhuber Close, but wrong direction. Let’s build a new modern window server starting from terminal primitives so we can eventually build better GUIs. As a hint, the Rex server has zero knowledge about terminals :) they’re just an app.
Poor phrasing, this sounds like it’s the completely the engineers fault
What generally happens is attackers get into one service and start privilege escalation attacks until they reach the service they need
So it’s issues in the backend, just the entry point was the laptop
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
https://t.co/ywB2mKFy0p