krisoshea.eth

This has been our main obsession @OlenaProtocol for ~2 years, so it's surreal to finally say that registrations are open. The core problem we've been trying to solve is how to get accurate crowd predictions on questions that don't resolve cleanly without needing deep liquidity or an oracle to verify the answers. Prediction markets are great, but they have two bottlenecks. 1. Liquidity: Markets only get sharp when they attract enough participation, and that only reliably happens for near-term questions with fanatical bettors. Long-horizon, niche, complicated questions? They sit empty or thin. 2. Settlement: Most of what society actually argues about ("Are tariffs helping the economy?" "Is immigration too high?") doesn't have a clean outcome to resolve against. No oracle. No answer key. And without one, forecasts drift toward what's popular, not what's true. Truth is a weak equilibrium in the attention economy. So we decided to tackle this problem from first principles. The mechanism is strangely elegant. Ask people what they believe and what they think others believe. Score the gap between what people predicted vs what was actually reported. It's called Bayesian Truth Serum (BTS), and over many rounds, the best strategy is boring yet powerful. Tell the truth and be well-calibrated. We spent 2 years adapting BTS for continuous probabilities, hardening it against cartels, and wiring it to leverage @Starknet for execution and @worldcoin ID for identity verification. The result is a protocol for collective human intelligence. Sharp crowd forecasts for questions prediction markets and traditional forecasting tournaments can't touch. First competition starts in 7 days. If you're the type of person who sees things others haven't caught up to yet, this is your arena. Register now👇

EVMone is one of the most optimised EVM implementations ever written. It powers Erigon's execution engine and holds multiple performance records. Zilkworm is built on top of it. Every proving run starts from an execution trace generated by code that has been optimised for years at mainnet scale. Not a re-implementation. Not an approximation. The actual engine. What architecture choices matter most to you in a ZK prover? github.com/erigontech/evm… #Zilkworm #Ethereum

We can now fully rewrite most software in @leanprover and prove it correct: - Compiler module rewrite (AI) from Rust to Lean - Full FFI integration - All unit and integration tests pass - Formal spec and proofs!! - Under 20h wall time (unnoticed pauses) github.com/powdr-labs/cru…

@post_polar_ Congrats, looking forward to reading!

it is done:

We rewrote Uniswap V3 in Plank, it compiles up to **74x times faster** 😎⚡️ Learn why we did this and more in the vid 👇

@joshdavislight Applied 🫡

Applications close tomorrow. Submit yours today.

@joshdavislight Applied 🫡

EPF7 applications are open. Deadline is May 13. If you want to work on core Ethereum protocol — client development, testing, specs, research — this is the program for you.

@TMIYChao @austingriffith Applied 🫡

Become an Ethereum Core Dev, last chance to apply:

0/ Clear signing is now live. An open standard to end blind signing, making human-readable transactions default. This effort brings a major UX and Security upgrade to transaction signing on Ethereum.

New article: write crazy gas optimizations directly in EVM bytecode, prove them equivalent to the original in @leanprover, profit. - Compilers won't do these. - Most humans don't dare. - AI + Lean proofs can. Read more + full article link below 👇

so our DPRK Contagious Interview friends have advanced in the meantime and now have started reking people for which you only need to _unzip_ a file and run a git checkout or commit operation. so this how the attack works: 1. the attacker distributes the repo as a zip archive (which is pivotal!). this is on purpose because git clone explicitly strips hooks (since cloning goes through git's _own_ protocol which excludes them) from remote sources as a security measure but unzipping is just a _normal_ filesystem ops that git cannot control (yeah fml but also simple fact). the zip restores file permissions exactly as the attacker set them (expect `rwxrwxr-x`), so the two active hooks (`pre-commit` & `post-checkout`) arrive on disk already executable (yeah fml). 2. git _automatically_ runs a hook when two conditions are met at the same time. the file must have the correct bare name with no `.sample` extension _and_ the executable bit must be set (like `rwxrwxr-x`). both of these are already satisfied by the attacker _before_ the zip is distributed. no fucking user action, config change, or approval is needed, git's own hook dispatch system triggers everything lmfaooo. software is great innit? 3. some of the custom `.sample` files in the shipped `.git/hooks` directory are the malicious payloads. they are basically payload components _disguised_ under innocent names. once the victim does anything beyond passively inspecting the repo (e.g. git checkout or git commit), the _active_ hook copies those files into `~/.vscode` (a directory devs usually trust and ignore but well you should not trust it guys) and then starts a detached background process using `nohup` so it does not block or visibly affect the git command. the git operation still completes normally and nothing looks suspicious. fucking evil, but hey here we are! 4. now that background process then bootstraps a node.js runtime if it is not already installed, runs npm install using an attacker controlled package.json, and executes an obfuscated payload (this can ofc differ and change over time). from that point the attacker gains clipboard access, a persistent c2 channel over socket.io (usually) and the ability to read browser credential dbs

Honestly the pitch deck of the future should be: "copy and paste this megaprompt into your LLM. It will give you my pitch, give you interactive visuals explaining my idea (if necessary), and then go back and forth with you about what I'm building and answer your questions."

Introducing Tamago🍳, a standard contract suite for Verity analogous to Solady for Solidity First ever (!!!) formally verified implementations of sqrt(), cbrt(), log10(), and log256() in EVM. Also the first ever formally verified ERC-4626 vault! cc @VitalikButerin @Fricoben

LFG Labs received a grant from the @ethereumfndn to build Verity. Verity is a formally verified smart contract compiler written in Lean 4 🧵

The rot has spread so deep, the very foundations have now started falling.

PRIVACY IS MORE THAN MONEY This is what the Kohaku project is, straight from its core contributors, @VitalikButerin and @ncsgy. TLDR: it is a serious attempt to rethink online safety and privacy across money, AI, and life. Let’s dive in.

dudes in SF will be 30 and be like "yeah i'm raising a seed round" bro go raise a family

the next social network is a prediction market where your feed is ranked by accuracy not engagement. the person who is right 80% of the time gets seen while the person who is loud gets buried