May was the month the Kyan waitlist closed for good and the rewards system came online, with Krystals accruing on every trade.
The full wrap-up has the rest of what shipped this month and the numbers behind it:
https://t.co/dnG8tsgI1a
Anthropic added to Claude a new "ultracode" effort level to help you speedrunning your way back to Codex by one shotting your usage limit in one prompt 😄
My take is that options are inherently a sophisticated product.
They are undisputedly the best instrument for hedging, capital management, yield, and speculation, as proven by TradFi volumes.
Until about a year and a half ago, there were no onchain options toolkits sufficient enough for sophisticated traders.
Portfolio margin is an essential piece of the puzzle alongside things like execution and settlement on par with CEXs. That just didn’t exist before.
And while they can be a directional instrument, purely directional crypto-native retail traders lack the incentive to switch from perps to options.
Now that we have the tools that players with actual size need, it’s up to spreads and orderbook depth. We have the latency and risk engines to match CEXs.
It’s also about tenure and building institutional trust over time, but we’re closer to a giant leap in adoption than ever before.
If you’re interested in more stats to contextualize my comment, I wrote a piece on this topic that’s pinned on my profile.
@dreamsofcode_io Do you mean that you feel like a piece is missing in the AI tools / harnesses to help guiding through this structuring process ?
I personally do feel like it's more a matter of adapting my own workflow to go through that process
I've been treating AI work from the beginning as the work of an intern, and that has worked out pretty well.
Sometimes if the feature is complex I first do a pass of light scaffolding where i start to structure the code how I want it, and leave placeholders.
LLMs thrives around structure, as they are designed to recognize patterns. From my experience, if you design a whole new feature and the AI can't really find proper structure around it in your codebase, result quality will be much lower.
I then make Codex do most of the implementation work, and do a very light review myself, to make sure the code is not unnecessarily bloated. If codex doesn't structure the code the way I imagined and I can think of a more efficient way to do it, I'll guide it.
Then in a new session I ask codex to review the changes compared to the base branch, most of the time he will find issues, in which case I make him fix what's worth fixing, always making sure the fix doesn't lead to unnecessary bloat through a very light review
I then trigger a new review in a new session, and keep repeating this until there are no more issue worth fixing.
When codex is done fixing issues, I then usually make Claude do a pass of review. Claude is usually much more nitpicky and often a lot of his findings are not really worth fixing. So I feed the output to Codex, and ask it to review what is valid and worth fixing. In some case, it will highlight a valid problem than Claude found and Codex missed.
Once all those steps are completed and both Codex and Claude don't find any meaningful issue anymore, I'll do a manual very in-depth review myself, in the same manner I would review the PR of an intern.
Then another person from the team will also do another pass of manual review on my PR before it is merged.
Ultimately, I think it also depends on what type of software you are working. I could probably live with few less pass of reviews that I am currently doing if I wasnt working on a financial app like @KyanExchange where there is no room for mistake.
🚨 BREAKING: Active supply chain attack across npm, PyPI, and Crates.io.
Socket detected TrapDoor, a crypto stealer campaign hitting 34 malicious packages and 384 versions and artifacts, with attackers repeatedly pushing new releases across ecosystems.
TrapDoor targets #crypto, #DeFi, AI, and security developers, stealing wallets, SSH keys, cloud credentials, GitHub tokens, browser data, env vars, and API keys.
Socket detected releases with a median detection time of 5 minutes, 27 seconds. The fastest detection occurred 58 seconds after publication.
Kyan's liquidation orders are queryable: WebSocket orders channel or REST open-orders. Filter liquidation=true.
When an account hits liquidation the system first tries to delta hedge it. If that fails, the orders post as limits with a delta-scaled taker incentive (~20% max).
@AlgorithmicX Nah, I had my first pc while kid, running windows 95, on which I was playing age of empire 1.
Went through all windows versions since that lol
Vol was meant to be sold.
Marty + Andrew from Block Scholes on this week's Options Talk: BTC ran 30% through war with vol collapsing every week, ETH/BTC vol parity is here, and MicroStrategy might be the silent vol seller nobody can see.
Summary of the last Options Talk:
https://t.co/U2tBHh0IxS
@Sellingvol I already installed Rectangle, which I think does similar to what Magnet, cause I was already annoyed by the way windows snapping was working by default.
Track pad I'm not a big user, cause mainly gonna be working with my 2 external monitors and external mouse and keyboard
@wekaaxyz Nah always been on Windows, cause that's just the best for gaming.
Bought a KVM switch, will keep using my windows Desktop for gaming and I'll use the Mac for everything else
Standard retail options fee: ~3 bps.
Kyan: 0.25 bps to the insurance fund and that's it - zero fees besides that.
For anyone selling weekly puts as a strategy, the fee delta is your edge here. Run the math on your last 100 short-dated trades.
https://t.co/yhsUAGx8hf