iiinova — where your digital self keeps evolving

alexhevans.bsky.social @alexhevans.bsky.social · 13/06/2026

No fable here, no lesson. No singing meadowlark.

Reposted by @alexhevans.bsky.social

Toni Schneider @toni.bsky.team · 09/03/2026

I'm thrilled to announce that I'll be joining Bluesky as interim CEO. I deeply believe in what this team has built and the open social web they're fighting for. More here: toni.org/2026/03/09/c...

4052013311

Reposted by @alexhevans.bsky.social

Bluesky @bsky.app · 30/01/2026

In 2025, as Bluesky grew from 25M to 42M users, we took actions to keep it welcoming, using proactive design to reduce toxic content by 79%. Our 2025 Transparency Report shares how we're building a safer platform while keeping a transparent and human-centered approach: bsky.social/about/blog/0...

bsky.social

2025 Transparency Report Overview - Bluesky

In 2025, as Bluesky grew from 25 million to 41 million users, we improved the trust and safety infrastructure to better enable our mission. Here's what that looks like in plain language.

4588061979

Reposted by @alexhevans.bsky.social

grjte @grjte.sh · 23/12/2025

🧵 Could Bitchat have 5x the range and 100x the throughput for the same power expenditure? I explored how Wi-Fi Aware could improve the reliability and throughput of Bitchat and mobile ad-hoc networks in the absence of internet connectivity. #bitchat 👇

14112

Reposted by @alexhevans.bsky.social

ZK Hack @zkhack.dev · 28/10/2025

Module 5 is live! We’re diving into The Ligero Proof System with @mvenkita and @GuilleAngeris Thanks to @BainCapCrypto for the support. Full access to all module resources zkhack.dev/whiteboard/s...

021

Reposted by @alexhevans.bsky.social

François Garillot @huitseeker.bsky.social · 24/10/2025

One thing to recall from @hdevalence.bsky.social 's work: @lmao.bsky.social, @pinged.bsky.social & @alexhevans.bsky.social showed that just encrypting a continuously updated CFMM (e.g. via FHE) fails to provide real privacy, since the very structure of a live, convex invariant leaks information.

141

Reposted by @alexhevans.bsky.social

guille @lmao.bsky.social · 27/06/2025

🫡

021

Reposted by @alexhevans.bsky.social

ePrint Updates @eprint.ing.bot · 23/05/2025

The Accidental Computer: Polynomial Commitments from Data Availability (Alex Evans, Guillermo Angeris) ia.cr/2025/918

Abstract. In this paper, we show two simple variations of a data availability scheme which enable it to act as a multilinear polynomial commitment scheme over the data in a block. The first variation enables commitments over all of the block’s data with zero prover overhead: the data availability construction simply serves both purposes. The second variation allows commitments over subsets of data with nonzero but still concretely small proving costs, since most work is already done during data encoding. This works especially well for blockchains with a high degree of data parallelism, as data-parallel computation is particularly amenable to efficient GKR proofs. Since, in GKR, opening the polynomial commitment contributes significantly to prover costs, our construction enables the prover to reuse work already done by the data availability scheme, reducing—or wholly removing—work associated with the polynomial commitment scheme.

021

Reposted by @alexhevans.bsky.social

Kobi Gurkan @kobi.bsky.social · 19/05/2025

Some thoughts about how verifications in Bluesky can be extended to ZK-based methods, to achieve Verifiable Verifications This builds on ideas from the recent verification protocol, and explores both direct integrations and lightweight ones, with different points in the tradeoff space of trust 1/2

1103

Reposted by @alexhevans.bsky.social

grjte @grjte.sh · 14/05/2025

🧵 The AT Protocol shows the power of a personal data store. All of our public atproto data is easy to find and access. We can interact with it flexibly in myriad ways and combinations. Wouldn't it be nice to do the same for our private and collaborative data? 👇

1133

Reposted by @alexhevans.bsky.social

Boris @bmann.ca · 14/05/2025

The last of @grjte.sh’s Groundmist experiments, combining #localfirst with ATProto Private, local first sync that is user centric using Lexicons, rather than app-specific sync.

0143

Reposted by @alexhevans.bsky.social

Kobi Gurkan @kobi.bsky.social · 14/05/2025

ZK provers on mobile? some thoughts on what needs to change to uphold the security guarantees we work so hard to get tl;dr - the deployment supply chain, at least, should be better www.kobi.one/The-Lies-Our...

kobi.one

The Lies Our Provers Tell Us | Notion

2025-05-14

041

Reposted by @alexhevans.bsky.social

grjte @grjte.sh · 23/04/2025

🧵 The AT Protocol (atproto), which underlies Bluesky, lets us to interface with the same data in as many ways as we can conceive of through AppViews that each provide a different "view" of the network. Can we make our local-first software as interoperable as the AT Protocol? 👇

1288

Reposted by @alexhevans.bsky.social

Boris @bmann.ca · 23/04/2025

Second in the #groundmist series - #localfirst + ATProto I’m actively using the local first essay editor (using @inkandswitch.com Automerge + tiny essay editor) - I can login with my ATProto account and work on private drafts and then publish to @whtwnd.com.

1225

Reposted by @alexhevans.bsky.social

grjte @grjte.sh · 22/04/2025

🧵 I've been experimenting with combining local-first software and the AT Protocol (atproto) to play with the design space of apps that live at both ends of the privacy spectrum - maximally private AND maximally public, without some of the downsides of the modern web. Why? 👇

16718

Reposted by @alexhevans.bsky.social

Kobi Gurkan @kobi.bsky.social · 17/04/2025

When Andrija and @lmao.bsky.social told me they're writing an extremely fast cryptography library in Julia I didn't know what to think... And then they showed me the following cool stuff: baincapitalcrypto.com/releasing-c... 1/4

baincapitalcrypto.com

CryptoUtilities.jl: A Small Julia Library for Succinct Proofs

We’re excited to open-source CryptoUtilities.jl, a collection of Julia packages built to prototype and benchmark succinct proof systems over binary fields, along with a simple walkthrough for how to…

294

Reposted by @alexhevans.bsky.social

daniel holmgren 🫠 @dholms.at · 03/04/2025

friendly reminder that building on atproto gives you immediate access to >30 million users, an existing social graph, and a huge network of open data & content it's increasingly becoming a no-brainer to build new social apps on atproto congrats to the skylight team on the launch 🙌

1967489

Reposted by @alexhevans.bsky.social

guille @lmao.bsky.social · 23/02/2025

anon, what if you could train your own personal offline model, on your phone, suited to your tastes, filtering posts with ~ bad vibes ~ and letting good ones through? well, have i got the thing for you

3245

Reposted by @alexhevans.bsky.social

🦇 DEADvin 🎃 GHASTney 👻 @devingaffney.com · 22/02/2025

15 weeks ago I sat down and wrote up some ideas about how custom feeds could become a high-leverage mechanism for fundamentally changing the economics of the attention economy. Today was my last day at my day job- I’m now full time @graze.social! Incredibly excited to give this all I got!

617412

Reposted by @alexhevans.bsky.social

guille @lmao.bsky.social · 31/01/2025

it's funny, for a long time, i always assumed that computation was this very sacred, brittle, difficult thing: so many things need to work "exactly" right to get an output but i’ve realized that it’s actually much *harder* to make a thing that doesn't accidentally enable ~ arbitrary computation!

151

Reposted by @alexhevans.bsky.social

Nico @nmohnblatt.me · 29/01/2025

These two lectures by @danboneh.bsky.social for @zkhack.bsky.social are the best explanation of IOPPs, FRI and its variants by a country mile. Cannot recommend them enough zkhack.dev/whiteboard/s... zkhack.dev/whiteboard/s...

0117

Reposted by @alexhevans.bsky.social

Nico @nmohnblatt.me · 27/01/2025

programmable* cryptography * programming difficulty may vary, developer discretion is advised.

031

Reposted by @alexhevans.bsky.social

ePrint Updates @eprint.ing.bot · 27/01/2025

How to Prove False Statements: Practical Attacks on Fiat-Shamir (Dmitry Khovratovich, Ron D. Rothblum, Lev Soukhanov) ia.cr/2025/118

Abstract. The Fiat-Shamir (FS) transform is a prolific and powerful technique for compiling public-coin interactive protocols into non-interactive ones. Roughly speaking, the idea is to replace the random coins of the verifier with the evaluations of a complex hash function.

The FS transform is known to be sound in the random oracle model (i.e., when the hash function is modeled as a totally random function). However, when instantiating the random oracle using a concrete hash function, there are examples of protocols in which the transformation is not sound. So far all of these examples have been contrived protocols that were specifically designed to fail.

In this work we show such an attack for a standard and popular interactive succinct argument, based on the GKR protocol, for verifying the correctness of a non-determinstic bounded-depth computation. For every choice of FS hash function, we show that a corresponding instantiation of this protocol, which was been widely studied in the literature and used also in practice, is not (adaptively) sound when compiled with the FS transform. Specifically, we construct an explicit circuit for which we can generate an accepting proof for a false statement.

We further extend our attack and show that for every circuit C and desired output y, we can construct a functionally equivalent circuit C^(*), for which we can produce an accepting proof that C^(*) outputs y (regardless of whether or not this statement is true). This demonstrates that any security guarantee (if such exists) would have to depend on the specific implementation of the circuit C, rather than just its functionality.

Lastly, we also demonstrate versions of the attack that violate non-adaptive soundness of the protocol – that is, we generate an attacking circuit that is independent of the underlying cryptographic objects. However, these versions are either less practical (as the attacking circuit has very large depth) or make some additional (reasonable) assumptions on the underlying cryptographic primitives.

03817

Reposted by @alexhevans.bsky.social

Nico @nmohnblatt.me · 23/01/2025

oh hello @zkhack.bsky.social 👀👀

231

Reposted by @alexhevans.bsky.social

Bain Capital Ventures @baincapvc.bsky.social · 16/01/2025

Welcome Mark Fiorentino to BCV! As Matt Harris writes, Mark is constantly learning w/ a career+life trajectory powered by changes, pivots & the quest for new experiences (ask him about being a Sommelier or upcoming CrossFit competitions). baincapitalventures.com/insight/mark... #fintech #SaaS #AI

052

Reposted by @alexhevans.bsky.social

guille @lmao.bsky.social · 09/01/2025

ZODA w/ @alexhevans.bsky.social and @nicomnbl.bsky.social : now up on eprint! (with a few updates and smol changes to the appendix)

272

Reposted by @alexhevans.bsky.social

Parth Chopra @parthc28.bsky.social · 02/01/2025

Cool checking out @graze.social -- ability to generate, share, (one day monetize?) your own type of feed. I wonder when we'll have dynamic, prompted LLM-style feeds. Aka say "make me smarter, show me things that are funnier" and the feed will be curated as such

022

Reposted by @alexhevans.bsky.social

daniel holmgren 🫠 @dholms.at · 05/11/2024

this is a great writeup on the differences between atproto & activity pub it also highlights the most meaningful ways to make bluesky more resilient

612127

alexhevans.bsky.social @alexhevans.bsky.social · 01/01/2025

Maybe the most interesting DeFi research in recent years

052

Reposted by @alexhevans.bsky.social

Tarun Chitra @pinged.bsky.social · 28/12/2024

Everyone on the X is too distracted with immigration, so I’m giving a sneak peek of some research here Decentralized Perpetuals have long been the dream but they’ve been too capital inefficient Many advances pushed DEX-CEX market share to >6% — but how are how are they related? We answer this!

3125

Reposted by @alexhevans.bsky.social

Nico @nmohnblatt.me · 04/12/2024

if someone tells you “succinct proofs are too short to leak information about the witness”, please send them this. The ZK property is not just a cool acronym. baincapitalcrypto.com/chosen-insta... This was also the theme of the "Zeitgeist" puzzle at ZK Hack 5!

074