←
alin.apt3,854 posts
alin.apt avatar

alin.apt

@alinush

i put the “crypto” in “cryptocurrency.” head of cryptography at @aptoslabs 💍 + 👶 + 🏍️ = ❤️

◷ Joined July 2009▧ 651 Photos and videos
Aptos Labs avatar
⟳ alin.apt retweeted
Aptos Labs@AptosLabs·22h

Prefix Consensus has won the Distinguished Paper Award at @acm_ccs 2026 🏆 The paper defines the first leaderless consensus primitive with formal censorship-resistance guarantees. Every validator proposes in every slot, so no single leader decides what makes it into a block. It also formally proves the design choices behind Raptr, already in production on @Aptos. Congrats to our Aptos Labs researchers @XiangZhuolun, @xosmig, and @SashaSpiegelman! Read the paper: arxiv.org/abs/2602.02892

Post attachment
alin.apt avatar
alin.apt@alinush·Nov 15

“Bug-dense software incurs societal risk” 👌

So there's also an economic incentive aspect to the disclosures: bug-dense software incurs *societal risk*, so regularly surfacing this risk in the form of disclosures keeps the risk visible, and is one of the few things steering against unbounded accumulation of hidden risk ...

IACR ePrint Updates avatar
⟳ alin.apt retweeted
IACR ePrint Updates@Lhree·Nov 11

[New] How to Revoke Users in Encryption Schemes? (Sanjam Garg and Dimitris Kolonelos and Benjamin Ostrovsky and Guru-Vamsi Policharla) ia.cr/2026/2819

Sourav Das avatar
⟳ alin.apt retweeted
Sourav Das@sourav1547·Nov 10

Do consider applying. We have had great summer interns so far. Looking forward to the next batch!

We’re now accepting applications for the third year of our research internship program taking place summer ’27 in NYC! Past interns have worked directly with Category Labs researchers on problems spanning consensus, cryptography, and mechanism design resulting in academic publications and new protocol features. For full consideration, please submit applications by December 7, 2026: jobs.ashbyhq.com/category-la…

Mark Kisin avatar
⟳ alin.apt retweeted
Mark Kisin@marcusgnt·Nov 6

Yeah, the answer is shelve it entirely, and I don’t think of myself as an anti-AI hardliner. The reason is that if you can prompt this then presumably so can many other people especially once the models become stronger. So the bottleneck is no longer a written “proof” (whatever that means) but an understandable exposition which promotes human understanding. By releasing this you simply demotivate actual experts from understanding and promoting it. I’m not even saying I militantly subscribe to this point of view, but I have a lot of sympathy for it. That’s the steel man case of the argument in any case.

ʕ •ᴥ•ʔ avatar
⟳ alin.apt retweeted
ʕ •ᴥ•ʔ@alpeh_v·Oct 30

Frog put the keys in the HSM. "There" he said "now we cannot leak the private key". "But our servers can ask the box to sign with the key" said Toad. "that is true" said Frog

Post attachment
Ankita Singh avatar
⟳ alin.apt retweeted
Ankita Singh@annkkitaaa·Oct 29

7/ the actual forking lemma (the probability part) the tricky part: the forger doesn’t succeed every time. maybe they succeed with probability ε when we rewind and replay with a different challenge, they might fail the second time the forking lemma (Pointcheval and Stern, 1996) quantifies this: if the forger succeeds with probability ε and makes at most q queries to the random oracle, then the probability of getting TWO valid signatures (same R, different e) is at least: ε · (ε/q - 1/|F|) roughly: if ε is non-negligible and q is polynomial, the extraction succeeds with non-negligible probability in simpler terms: if the forger has any reasonable chance of succeeding once, we have a reasonable chance of making them succeed twice. and twice is all we need to extract the key

alin.apt avatar
alin.apt@alinush·Oct 29

This paper builds on the recent refutation of ETH by OpenAI/Anthropic. Fathomable the paper will be further improved upon. And slightly terrifying.

alin.apt avatar
alin.apt@alinush·Oct 29

ECDLP on b-bit curves can now be solved in O(2^(b/(log b)^1/4)) time. Asymptotically faster than 2^b/2, assuming no precomputation. Galactic: only kicks in for very large b; does not affect current curves. Uses point coordinates => does not care about GGM lower bounds.

The generic group model just got rug-pulled github.com/bochum-crypto/sub…

alin.apt avatar
alin.apt@alinush·Oct 28

"slop infestation"

I interviewed ~2 dozen researchers, engineers, research / engineer managers etc. asking them how they / their teams use coding agents in their work. Then I sprinkled it with my opinions and hot takes and wrote a substack post (link in the next tweet, I'd be delighted if you subscribe; of course, the post is free and any future post will be free too!) trying to triangulate the current reality of software engineering / industry research as opposed to what gets peddled on social media. TL;DR (3. and 4. are the most important!): 1. Models, harnesses, workflows: don't bother with fancy workflows, they don't really work. Use stock Claude Code / Codex (or Copilot with Claude / GPT models if you are a Microsoft stan), perhaps with subagents in some very special cases. Write a design doc, then plan a change, then implement it, then merge. Wash, rinse, repeat. Don't get swayed by people online who are trying to sell you snake oil in the form of their new harness or workflow. None of this stuff works (in general). 2. Correctness/tests/reading or not reading code: it's OK not to read code if you do one of the following three things. a) One-off stuff / demos, which you need to work on exactly one input. b) Testable / verifiable stuff, e.g., GPU kernels. c) Stuff, where it's OK to be "directionally correct" (ML / data work / research code). In other cases, especially if you require any degree of maintainability / reliability or your code is customer-facing, reading code is still necessary. Reading tests and steering the model to write better tests is a good idea too. It's often good to use a different model to review the code that the other model wrote. Even if you approve the PRs without changing them, reading still helps for future more productive prompting. 3. Team dynamics: if we are not careful, agents can really undermine team dynamics. Two biggest problems are "slop infestation", where over time all PRs / emails / Slack messages end up being unreadable slop, and "overbuilding", where we are building and shipping useless stuff to get recognition or as a form of procrastination. Other, less severe but still important problems include: reduced communication, being secretive about ideas, decreased diversity of thinking, mode collapse of the ideas, trusting LLMs more than people. 4. Call for action: we really need to be careful with preserving team work and collaboration. We still need to "form packs to hunt mammoths", but with coding agents this becomes increasingly harder. Overall, many of the agents-induced problems stem in myopic short-term thinking of the sort "we have a couple of years left until our jobs are fully automated, so I can as well extract as much value as possible, everyone else be damned". While somewhat understandable, I think it’s important to resist these urges, if nothing else, for your own sanity’s sake. [Full disclosure: until 2 months ago, I worked at OpenAI and my work directly contributed to Codex, I'm a big fan of coding agents and quite strongly AI-pilled, but there is little I hate more than fearmongering, gaslighting, lies and rage-bait that are ubiquitous in this space, unfortunately, hence spending time on all of this.]

Ilya Razenshteyn avatar
⟳ alin.apt retweeted
Ilya Razenshteyn@ilyaraz2·Oct 28

I interviewed ~2 dozen researchers, engineers, research / engineer managers etc. asking them how they / their teams use coding agents in their work. Then I sprinkled it with my opinions and hot takes and wrote a substack post (link in the next tweet, I'd be delighted if you subscribe; of course, the post is free and any future post will be free too!) trying to triangulate the current reality of software engineering / industry research as opposed to what gets peddled on social media. TL;DR (3. and 4. are the most important!): 1. Models, harnesses, workflows: don't bother with fancy workflows, they don't really work. Use stock Claude Code / Codex (or Copilot with Claude / GPT models if you are a Microsoft stan), perhaps with subagents in some very special cases. Write a design doc, then plan a change, then implement it, then merge. Wash, rinse, repeat. Don't get swayed by people online who are trying to sell you snake oil in the form of their new harness or workflow. None of this stuff works (in general). 2. Correctness/tests/reading or not reading code: it's OK not to read code if you do one of the following three things. a) One-off stuff / demos, which you need to work on exactly one input. b) Testable / verifiable stuff, e.g., GPU kernels. c) Stuff, where it's OK to be "directionally correct" (ML / data work / research code). In other cases, especially if you require any degree of maintainability / reliability or your code is customer-facing, reading code is still necessary. Reading tests and steering the model to write better tests is a good idea too. It's often good to use a different model to review the code that the other model wrote. Even if you approve the PRs without changing them, reading still helps for future more productive prompting. 3. Team dynamics: if we are not careful, agents can really undermine team dynamics. Two biggest problems are "slop infestation", where over time all PRs / emails / Slack messages end up being unreadable slop, and "overbuilding", where we are building and shipping useless stuff to get recognition or as a form of procrastination. Other, less severe but still important problems include: reduced communication, being secretive about ideas, decreased diversity of thinking, mode collapse of the ideas, trusting LLMs more than people. 4. Call for action: we really need to be careful with preserving team work and collaboration. We still need to "form packs to hunt mammoths", but with coding agents this becomes increasingly harder. Overall, many of the agents-induced problems stem in myopic short-term thinking of the sort "we have a couple of years left until our jobs are fully automated, so I can as well extract as much value as possible, everyone else be damned". While somewhat understandable, I think it’s important to resist these urges, if nothing else, for your own sanity’s sake. [Full disclosure: until 2 months ago, I worked at OpenAI and my work directly contributed to Codex, I'm a big fan of coding agents and quite strongly AI-pilled, but there is little I hate more than fearmongering, gaslighting, lies and rage-bait that are ubiquitous in this space, unfortunately, hence spending time on all of this.]

Sean Bowe avatar
⟳ alin.apt retweeted
Sean Bowe@ebfull·May 12

Zcash wouldn't exist without @zooko. He seeded the technical and cultural values of the project that have kept us vigilant in defense of its integrity. Much of Zcash's recent success has been because Zooko plays a less central role in the project, and it has decentralized and grown to transcend him. I think he would agree! But he is still a major spiritual force of the project, and an ally that wants it to succeed. Let's be mindful of the signal we send our next generation of risk takers, by how we treat his legacy. Zcash has a long road ahead of it, and no single one of us can carry it across the finish line. We're all liable to end up in @zooko's shoes one day. You do not want to be on the receiving end of the poetic justice served for the things you said when you were once on the winning team.