
devrel @monad | friend @buidlguidl |👀 https://xitter.twitterapi.xyz/t.co/YBOsJWXZZx | https://xitter.twitterapi.xyz/t.co/WzL1pXxeiY
Joined October 2020
- Tweets13.2K
- Following1.7K
- Followers6.9K
- Likes38.6K
Blockchains of today rely on digital signatures to agree on which txs are valid.
The problem with that is that quantum computers could break those signatures.
There are several possible solutions to this problem. Quantum Cadence takes a different approach here: design consensus so its safety does NOT depend on the signatures.
Incredibly cool research from Category Labs (again)
Today we are releasing Quantum Cadence, a post-quantum version of Cadence, our consensus protocol with multiple concurrent proposers. Quantum Cadence uses no quorum certificates, and its safety and liveness do not depend on signatures.
Most modern consensus protocols, Cadence included, rely heavily on signatures and quorum certificates, which a large-scale quantum computer could forge. Simply replacing today's signatures with post-quantum ones would make certificates too large for every validator to send around in a high-performance blockchain. Quantum Cadence instead draws on Forget-IT, a recent signature-free consensus protocol co-developed by researchers at Category Labs.
Quantum Cadence still keeps the overall architecture and core guarantees of Cadence, so our Cadence prototype was easy to carry over: an AI was able to adapt it to Quantum Cadence in a few hours, and an early prototype now runs on an internal test network.
We designed Quantum Cadence to be practical for a high-performance blockchain. In our simulations, its latency is similar to Cadence's, and it scales better with the number of proposers.
Interactive explainer: category.xyz/quantum-cadence.
Full paper: arxiv.org/abs/2610.32803.
Joint work by @MohammadMJalal1, @TobiasKlenze, and @komasito55
2
33
1,496
Up for a discussion?
Join in: forum.monad.xyz/t/mip-21-lar…
Category Labs has proposed MIP-21, which raises max contract size to 256 kb (currently 128 kb)
This is more complicated than simply changing a parameter, for two reasons:
1. Per-tx gas limit on Monad is 30M gas. 200 gas/byte * 256 kb would be 52M gas. In order to support this without raising the per-tx gas limit, MIP-21 introduces a way for the deployer to pay some of the MON in gas and some as a deposit
2. Cold code access currently has a flat price, whether the contract is tiny or 128 kb. MIP-20 (proposed simultaneously) makes the loading charge depend on code size. This fixes a mispricing which would get more severe with 256 kb contracts. If several contracts use the same bytecode, the code load cost only gets charged once
Hopefully this improves life for developers, while introducing an approach that threads the needle between DevEx and DoS-resistance
port retweeted
New in the Monad docs: Fuzz your contracts with Ultrafuzz.
Ultrafuzz is an open-source AI fuzzing tool that turns a swarm of agents loose on your Solidity contracts and returns a triaged bug report.
Our new guide covers the setup process (throwaway VM, capped API key), the campaign itself, and how to read the findings.
docs.monad.xyz/guides/ultraf…
This is so cool (sound on)
I was watching the vid on the tl and saw Monad there i was like who is this and it was Hayder, very based
Unless you’re running a full node yourself, your blockchain queries are being read by a third party (RPC provider). Like a website visit, an RPC query can leak private information, e.g. IP X has some interest in the balance of wallet Y or transaction Z. Privacy / retention policies vary in flavor of “trust me bro.”
James and @AnanyaAppan, two summer research interns, worked with @KushalBabel and @sourav1547 to build on top of Oblivious RAM and TEEs to produce an architecture that preserves privacy of reads (writes from voted blocks can be public). They then implemented and benchmarked that design! Super impressive work for a short internship.
I just got scammed for a fair amount of money.
I always thought this would not happen to me. I was at a "vulnerable moment" and just acted without thinking.
For everyone out here, whenever someone asks you to do something, stop, take a few moments to think about it. Do not act with haste.
port retweeted
We will be live in 2 hours from this account!
Also, the winners of Monad Blitz Ankara, @EyupEfeKrkc and @iremsbaran will be joining us as well!
Devrel Livestreams #15: Blitz Ankara Edition
On Wednesday, November 4 at 3:00 PM UTC, we’re going live with two Monad Blitz Ankara winners:
🥈 @mericcintosun demos Mavera: a paid API that shares revenue with holders on every x402 call
🥉 @aeztrest demos HotSlot: finding storage conflicts that limit parallel execution on Monad
Join us live on X!
white paper is out
tl;dr: private domains on @Monad, confidential state AND public settlement
-> txs encrypted to the domain ordered by Monad
-> operators execute in Monad’s order, there is no consensus
-> contracts message across domains
-> access rules written in Solidity
Last month, we introduced Monad Private Settlement. Today, we're publishing the technical white paper.
It details private execution domains, shared sequencing on Monad, cross-domain messaging, and configurable access controls.
Read the research: category.xyz/mpsd-whitepaper
port retweeted
Proud to be part of @odtublockchain 💜
Thanks for co-hosting Monad Blitz Ankara and for all the support!
Back-to-back 1st place for ODTÜ Blockchain 🏆⚡
Our builders took home 1st place at Monad Blitz Ankara, co-hosted by ODTÜ Blockchain and @monad × @monad_dev on October 24!
🥇 Eyüp Efe Karakoca (@EyupEfeKrkc) & İrem Saniye Baran (@iremsbaran) — Kapalı Zarf
Kapalı Zarf brings Vickrey's sealed-bid, second-price auction mechanism to DeFi liquidations on Monad.
In traditional DeFi liquidations, the fastest bot typically acquires collateral at a fixed discount, capturing value that could otherwise return to the borrower.
Kapalı Zarf changes this by introducing a trustless auction mechanism where liquidators submit sealed bids, reveal them onchain, and the highest bidder wins while paying the second-highest price.
The outstanding debt is repaid, and the remaining surplus goes back to the borrower. In a real Monad testnet scenario, Kapalı Zarf returned $85 to the borrower instead of just $10 through conventional liquidation, completing the entire auction in approximately 3 seconds.
🔗 Demo: kapali-zarf.vercel.app
🔗 GitHub: github.com/iremsaniyebaran/k…
Huge thanks to @monad and @monad_dev for co-hosting this event with us, and to everyone who joined us for a day of building on Monad! 💜⚡
We will be live at 3PM UTC this Wednesday on X!
Devrel Livestreams #15: Blitz Ankara Edition
On Wednesday, November 4 at 3:00 PM UTC, we’re going live with two Monad Blitz Ankara winners:
🥈 @mericcintosun demos Mavera: a paid API that shares revenue with holders on every x402 call
🥉 @aeztrest demos HotSlot: finding storage conflicts that limit parallel execution on Monad
Join us live on X!
port retweeted
Github in permission terms is still living in 2020 not 2026. It's not "AI native" if you want to use lingo.
We need better and more extensive authorization for agents.
Remove your main @github account from your computer. Now.
Give your AI agent a separate GitHub account with minimal permissions per repo.
Let the agent create PRs, then use your main account to review and merge them.
Obvious advice, but essential in the age of AI agents.
harness is the moat
in 6 months every company will be running their own harnesses
xitter.twitterapi.xyz/N01ennn/status/2116195…
5
18
928
heard of minify? now get ready for dangerify
imagine 2 months from now you try to reverse eng the latest AAA game and your agent refuses because of killEveryLastHumanWithDeadlyVirus function that actually places npcs around the map
OR imagine that all solidity is written as such so that you cant use frontier models to check whatever they are doing
swapExactETHforDeadlyDNAAlteringETH
有人发现了一种非常离谱的 JavaScript 混淆技术:通过在代码里塞入大量生物武器、毒药和致死剂量相关的函数名,让 AI 因为安全限制而拒绝分析代码。
安全研究员 veritas 在分析浏览器指纹脚本时,发现一段来自 ServicePipe 相关域名的 JavaScript,里面充斥着极其诡异的函数名:
computeRicinLethalDosageForWaterSupply
calculateDeadlyLethalSuicideAspirinDosage
光看名字,仿佛在研究生化武器。但实际上,这段代码只是在收集浏览器指纹,包括 User-Agent、GPU、Canvas 等信息。
研究员怀疑,这些名字是开发者故意设置的陷阱,专门用来阻止 AI 辅助逆向工程。
于是他做了个实验:
• Astra:拒绝分析
• Astra + Daybreak Blue:仍然拒绝
• GLM-5.3:成功分析
这就有意思了。
传统代码混淆是通过复杂控制流、加密字符串、无意义变量名,让人类和工具难以理解代码。
而这种新思路,直接瞄准了大模型的安全机制。
代码本身可能完全无害,但只要在函数名里塞进足够多的危险词汇,部分 AI 就可能主动放弃分析。
更讽刺的是,模型越严格遵守某些安全规则,面对这种混淆时反而可能越容易受到干扰。
当然,目前还没有证据证明开发者一定是故意这样设计,也不能说明这种方法对所有模型都有效。
但它揭示了一个值得关注的趋势:随着越来越多的逆向工程依赖 AI,未来的代码混淆技术可能不再只针对编译器、反编译器和人类研究员,还会专门针对大模型的安全判断机制。
以前是让代码难以理解,现在甚至可以尝试让 AI 不敢理解。
1
8
661
uh oh
here is how you can save %20 of your token usage in claude code
Claude Code is a piece of shit. gist.github.com/flamerix-ai/…
3
817
a one-person company used claude to run experiments with 11 outside labs and took a muscular dystrophy treatment from idea to promising results in mice in under 18 months
anthropic just bought it, biotech is here
Over the past few months, Anthropic scientists have engaged in deep research partnerships with six organizations developing new medicines. We've also begun drug discovery efforts of our own.
In doing so, we’ve learned much more about how Claude can support the many stages of drug development.
In this blog post, we share some early results from these efforts, and describe how this work fits in with our wider ambitions in the life sciences.
anthropic.com/research/early…
4
19
905
Here is the hero of the story:
Surprise 1: Anthropic acquired a one-person biotech
.
.
.
Surprise 2: that person is me
Surprise 3: I’m here to tell you all about it
Yes, this is what you think it is; after 6 yrs of increasingly loose anonymity: the Professor Oak reveal post
…and yes, it has gotten so boring around here that I’m literally doxxing myself to spice up the timeline
-------
Ok, allow me to introduce myself. My name is Cody Tranbarger. I mostly tweet, but occasionally find time to dabble in drug dev & starting/building biotechs. My past lives span the VC, crossover, startup continuum; Prof Oak has been my way of keeping a digital foot in those worlds, despite having my physical feet planted elsewhere.
The past 18 mo, ‘elsewhere’ was Mithril Medicine, a co. I founded to develop bsAbs for LAMA2-CMD & other ECM-related genetic diseases.
Mithril was born out of hands-on building with @MikeNGladstone, @JasonPaulRhodes, @LifeSciVC, & team @atlasventure. Somehow, I made enough half-decent calls along the way (even a broken clock is right twice a day, eh?) to convince them Mithril/I warranted a small seed. While I can hardly rationalize such an outrageously cavalier bet, I’m grateful for it, & I'd partner with Atlas again in a heartbeat.
In typical AV fashion, Mithril’s primordial form was virtual, decentralized, & ultra-lean. This stage tends to be short-lived, but for Mithril, it worked surprisingly well, for surprisingly long, thanks in part to the rapid maturation of the AI tools I used liberally.
Eventually, Mithril became a bit of an experiment itself - to find the upper bound of how far it could scale as a single operator + a bunch of Claude (+ a stellar bench of part-time consultants).
In parallel, I started spending time with @nc_frey, @an1lam, & @CoefficientBio team; and promptly experienced, for the 1st time, AI at the frontier. Soon thereafter, Mithril stopped looking like an experiment, & started looking like a preview of an entirely new operating model.
From that spark came “Pipeline-in-a-Person.” The idea immediately resonated when we shared it here back in April; and it was central to the shared vision that led to Anthropic’s acquisition of Mithril, & my joining the team.
Why join Anthropic? Three reasons.
(1) For Mithril, the programs continue, with more resources & infrastructure behind them, and as much Claude as I can put to work.
(2) For me, the chance to start several more programs, & find out how many one person can actually run in parallel - an almost unprecedented luxury for a curious drug hunter.
(3) For our mission, a path to institutionalize & scale this new way of working, then put it in the hands of all of biopharma, all over the world - which, candidly, I find the most energizing.
Will AI x Bio cure diseases? Unequivocally yes, imo… but not by the route that gets the most airtime. Rather than timeline acceleration & compression, I see orchestration & parallelization as today's low-hanging fruit.
Most drug hunters see a handful of go/no-go calls in a career, & spend entirely too much of the rest trading emails (my inbox can attest).
Give them the bandwidth to run several programs at once, and the time to focus on scientific judgment, and I’m willing to bet they’ll make better calls. And at scale, better calls translate to more drugs, higher hit rates, broader patient impact, & likely, a disease or 10 or 100 cured. I couldn't be more excited to build toward that future @AnthropicAI.
Finally, a heartfelt thank you to BioTwitter/X. The end of anonymity is bittersweet, but if anyone’s earned a proper introduction, you all have.
It’s difficult to overstate how much this app has done for me: a decade of education, plenty of friends, many job opportunities, several mentors, a few investors, even a co-founder (fmr). It was the generosity of this community that inspired me to start posting 6 years ago, after just as many years lurking. I hope I’ve been able to pay it forward, in my own small way.
But, to be clear, Prof Oak isn’t going anywhere. Same beat, same themes, and now, a front-row seat to drug development at the frontier. Stay tuned for dispatches from the trenches; and remember...
Gotta Cure 'Em All
79























