philogy

After 6 months of work, we're proud to finally share our first release of our new smart contract language: Plank v0.1 🚀 To fix the fundamental issues plaguing smart contract development we're rebuilding the language stack from the ground up. 🏗️ Learn more 👇

@cyberthirst Well having to write assembly (whether it’s your or your agent) is typically less fv friendly, but I’d say why not all. The stronger the optimizer the more you can focus on the high level types and FV and less about the details

@real_philogy a sharp optimizer is pretty great, but i think going forward a strong type system, and fv friendliness is the more important factor as you can just unleash your agents and have them produce correctness proofs, and have humans move towards spec production & verification

basic bug and a clever exploit. check your return values! i partially blame this on the evm, as the codesize limit and high gas prices encouraged similar practices unfortunately, gas golfing patterns might still be deeply entrenched in the training data, and agents will still use them even as evm evolves, and more defensive code could and should be written

if by feasibility you mean "project can't launch at all because gas would be prohibitive" then no, not in practice, although because of survivorship bias we'll never know which protocols/designs we missed out on because engineers were forced to compromise. In terms of decode I mainly mean pretty basic stuff like not reallocating and copying the same bytes 5 times, or letting you decode to a calldata slice from calldata.

@real_philogy those are just expensive primitives, but every other protocol uses them, so they don't pose feasibility limitations for most. p.s. it's hard to write a cheap and safe decoder. interested what you came up with haha

@cyberthirst Yes, this is the case *all the time* in Solidity. The default codegen for anything memory related (abi encode, decode, extcalls) is pretty bad

@real_philogy you can't write the logic in source because the compiler's e2e pipeline is inefficient, so you drop to assembly

@cyberthirst wdym by "impossible to satisfy in source-level"?

@real_philogy do you have real protocol requirements that are impossible to satisfy in source-level? like where the user is forced to pay such high fees where it crosses the feasibility threshold for the protocol

@colludingnode it's very telling that you're complaining about Uniswap not being fully free rather than delivering the free alternative yourself because the latter is much harder (and more expensive) than the former!

to the bin with it

@levelsio Just let him opt out of the emails lmao. Man will really use any excuse to hate on Germans.

2 hours after a German signs up to your site

@DrNickA Pavel larps as some kind of freedom advocate when he runs a chat app that supports e2e encryption but for *some* reason doesn't make it the default ensuring >99% conversations aren't using it.

this guy fucks

@justinmk will there be a keyboard version where I can place my cursor one-by-one where I want it or mouse only?

Neovim multicursor (local branch 😇) is in a "mergeable" state now (but you can see some bugs in this demo :D) This will quite literally be a killer feature: Vim will have no choice but to copy it (like :terminal and jobs). No changes needed from any plugin; everything Just Works, including "surround" plugins. Visual-mode and completion were the trickiest parts... The architecture is the Right Way: all user input is structured as Atoms. Plugins can subscribe to Atoms and react to literally any user action.

@durov big words coming from the guy who runs a chat app which doesn't have e2e encryption as the default yet

Once typical of banana republics, such tricks are now used by the EU to pass surveillance laws.

@EPPGroup @zarzalejosj @Europarl_EN You are saying "it's temporary" and "voluntary" like you aren't pushing for Chat Control 2.0 which makes it permanent and mandatory. That you can stand there and blatantly lie to people is incredible, it's as if you're stupid enough to believe these things yourself.

A must-watch! MEP @zarzalejosj debunks the chat control hoax. Thanks to the @EPPGroup’s efforts, the @Europarl_EN moved one step furthe towards the adoption of a crucial measure to tackle child sexual abuse online. Now, we urge the Council to find a solution to close the current legal gap immediately. We will never give up on building a safer space for minors online, with an effective and robust permanent legal framework.

@danrobinson Didn't Anthropic say that downgrades for AI research would be silent?

That depressing feeling when your AI research project doesn't trigger a downgrade from Fable and you realize you're not on the frontier

Two companies, two philosophies.

@debasishg Shouting "skill issue" and lobbing personal attacks at Jared (even if true) are a terrible look ngl. Should've taken a page out of Bun's post and given some concrete examples why doing Zig safely is "pretty easy actually". But otherwise interesting points.

Andrew's thoughts on the Bun Rust rewrite .. andrewkelley.me/post/my-though…

🇪🇺 Chat Control has passed 😔 They can and will now legally scan any person's messages, emails and photos you send without a warrant The way they passed this law when the majority of the European Parliament was against it will shock you: They waited until most EP members were on holiday so only a few were present and then created an "urgent" vote for it to pass it through There's nothing democratic about any of it and big powerful forces are behind this that can manipulate the EU for whatever they want Democracy in Europe died a bit today 😔

Rewriting Bun in Rust bun.com/blog/bun-in-ru…

@RadicalFalk Nothing more German than complaining about Germany constantly

This Video is BANNED in Germany.

I know I haven't given an update on Plank in quite a while but no worries we've been *COOKING* 🧑‍🍳 v0.2 coming in <5 weeks with: - fully featured stdlib (abi encode/decode, storage, events, dispatcher, eip712) - SOTA stack scheduling - `inline while` ... and maybe more? 👀

> Succinct verification (ZK proofs) lets you verify the whole chain, natural language → spec → verified code, in under a second. That's what lets vericoding keep pace with vibe coding. Maybe I'm misunderstanding but this statement makes 0 sense in the context of developer workflows. They sound similar but ZK proofs / FV proofs are entirely different things. They can overlap (ZK circuits are software so like anything you want to establish correctness with FV, or using ZK to reduce the cost of verifying an FV proof) but in the context of a developer or team workflow this doesn't really make sense, the cost of creating ZK proofs for the FV proofs of your own code would far outweigh the speedup.

6/ Succinct verification (ZK proofs) lets you verify the whole chain, natural language → spec → verified code, in under a second. That's what lets vericoding keep pace with vibe coding.

1/ Vibe coded software of uncertain quality is flooding the world. Vericoding is the counterpart to vibe coding, i.e. the AI generation of formally verified code from a formal spec. Read my blog post on vericoding: bwetzel.medium.com/vericoding-for…