Parker Thompson

@intoverflow @lucidzk SK - some knowledge

@lucidzk heck, many systems advertising themselves as “ZK” are not, in fact, “ZK” Turns out it’s possible to build a system that cryptographically achieves “verifiable compute” without providing data privacy But for marketing reasons, these systems are still called “ZK” 🥴

dear cypherpunks, do not be deceived by zk-scaling infra trying to camouflage as “privacy tech.” their designs are bound by public data availability, sequencer transparency, and regulatory-first architectures. every transaction, state root, and calldata blob leaks just enough metadata to make them fundamentally unsuitable for fully-encrypted systems. scalability ≠ privacy. rollups prove valid execution under transparent inputs. privacy requires encrypted execution under shielded state. the architectures leaking today will never be the foundation for true privacy tomorrow.

Our open models are here. Both of them. openai.com/open-models

@intoverflow That's just what big water wants you to think

I’ve been running the numbers on a massive rainwater collection system I found that I could save maybe $100/yr on irrigation But doing so would require, idk, $10-20k in infrastructure Did I mess up my math? Or is rainwater harvesting a scam??

@sashaaldrick @Conquerorr_1 @zksanti That file is haunted

Boundless prover video tutorial is coming yall

this gives me an idea

@ovanwijk @RiscZero This is a great idea. I would be curious to know how you would aggregate that across multiple CPUs, GPUs etc that go into a proving cluster.

@RiscZero Measuring this in traditional herts is actually very usefull to track the progress of ZKP research and implementations! Now I am wondering how much 'compute' / hertz was needed to achieve 32 MHZ ? That would give a very use-full metric!

BREAKING: 32mhz effective achieved internally

@intoverflow F

Sad news from our recent survey of the forest south of the De Leo Wall During a secret mission for the Rebellion, R2D2 was injured in a windstorm when a tree fell on him Pinned to the ground and with no one able to hear his beeps, he succumbed to his injuries F’s for R2

We are building @boundless_xyz, the first universal ZK protocol bringing abundant compute to every blockchain. Today, we’re excited to share our road to mainnet ↓

One of the coolest parts of this is 'pipelining' which allows us to schedule the prove tasks while the executor is still running. So with ideal saturation of GPUs to execute speed our e2e proving time is only a few % less than execution speed. (Scaling this workflow is a fun job)

@zksanti @boundless_xyz @citrea_xyz The world doesn't need another chain

The coolest part of RISC Zero /@boundless_xyz is that it’s *not* another chain. Rather, a protocol that enhances all networks with the power of ZK. Huge congrats to @citrea_xyz on their raise

@JacobEv3rly @sshankar @Xi_195

@sshankar @Xi_195 Cancel linear @m0thran, we are so back 😈

Surprised that @Xi_195 and @JacobEv3rly weren’t in attendance..

@JacobEv3rly @VitalikButerin You need headroom to build the block and source the TXNs before proving can start. Mev searching etc?

Can someone point me to a resource on why @VitalikButerin says real time proving is 4s here instead of 12s (current ETH block time)?

@clairekart @zksanti

@zksanti Plz explain…..

@sshankar @clairekart @zksanti @RiscZero Aggregated ship post

@clairekart @zksanti @RiscZero Yup.. next time, we should just post the aggregated proof of shipment. :D

PSA: @RiscZero has officially expanded into the 🚢shipping industry, because we just can’t stop shipping.

I really enjoyed getting this one playable!

Gotta prove 'em all 🫡

@intoverflow @colludingnode @JacobEv3rly Wen minecraft

@colludingnode @JacobEv3rly What should we do next? risczero.com/blog/when-the-…

New embedded hardware: “can it run doom?” New Zk proving system: “can it verify Tendermint?”

@MrPkar Closes <GHISSUE> should link correctly not just closes <LINEAR>, this allows devs to use their normal GH workflow for linking a GH issue to a PR and not needing them to copy between multiple browser windows.

@MrPkar Closing vs non-closing links should be controllable through the UI/API. I would the option to auto create a linear issue on new PR, not every PR already has a issue when developing fast and I would like a back stop for devs who forget to make a issue first.

Linear is so frustratingly close to being good with GitHub but really falls short on a couple key integration points that force extra process and overhead onto devs that doesn't need to exist imho

@emieljanson When a dev has to swap between two windows in the browser it's just more friction and doing GitHub issue linking already has tab complete inline. * Ability to control if a pr link is closing/reference in the UI / API (I'm still looking for that so maybe it exists?)

@emieljanson Hey there! I am onboarding a new and agile team, I want the lowest friction for devs so: * I would love an option create issue when a PR is opened that does not have issue linked via magic words. * Prs with `closes #123` aka the GitHub issue link should auto link in linear