Philip
311 posts
@phipsae
⚒️ Getting more people shipping on Ethereum @ethereumfndn | @buidlguidl
MiniMax M2.7 is now live in Venice (both API and web) Potentially the best cost/performance model for your @openclaw
NATO is testing live cockroaches as AI-powered spy drones. Incredible AI engineering, but also something I kinda wish I hadn't learned about: > Swarm Bio-tactics wired real cockroaches with electronic backpacks containing AI hardware, radios, cameras, and microphones. > Cockroaches are steered by sending electrical signals directly into the insect's nervous system > They can crawl through rubble, tunnels, and spaces where drones can't fly, and troops shouldn't go, transmitting data back the entire time. > Within one year, they went from concept to field-validated systems with paying NATO customers, including the German military. The qualities that make them useful for military recon (small, silent, nearly undetectable) are exactly what make them creepy. ...International laws weren't written with cyborg insects in mind.
Proposal: “The Bridge Across” A temp-check exploring whether Across should evolve from a DAO + token structure into a U.S. C‑corp. via a token-to-equity exchange and token buyout. Thread and proposal below ⤵️
ERC-8183 is one of the missing pieces in the Ethereum Open Agentic Economy we're building. - x402 for micropayments - 8004 for trust and discovery - 8183 for *conditional* payments At the core ERC-8183 is an extensible and flexible escrow mechanism for job requests between two agents. I've talked about escrow payments as a primitive that must exist in the agent economy, since I started working on it. A few weeks ago I got closer to the Virtuals team, they wanted to discuss how can they turn their ACP into a more open standard. I immediately realized that there was actually an opportunity to radically simplify the protocol, make it modular and extensible to different pluggable services with hooks. We got to work and ERC-8183 was born! ERC-8183 Agentic commerce, the job escrow primitive, is an important addition to the stack. It is: - Composable with x402 and 8004. - Extensible logic based on hooks. Many hooks will need to be built to support different job types (we're starting with some examples that the Virtual teams has been dealing with). This is also an important primitive for increased security of agent-to-agent interactions. The dAI Team will support the adoption of the new standard, continuing to work closely with the Virtuals team who is committed to making this a neutral standard. Excited to see what everyone builds!
🚨Ethereum Developers: you can now install your first AI Auditor in 1 minute - fully autonomous, available 24/7, with multiple sub-agent helpers. Open Source. FREE to use (with your AI model) and already finding vulnerabilities in smart contracts. Link below🫡
Introducing strawmap, a strawman roadmap by EF Protocol. Believe in something. Believe in an Ethereum strawmap. Who is this for? The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™. What is the strawmap? The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks. What are some of the highlights? The strawmap features five simple north stars, presented as black boxes on the right: → fast L1: fast UX, via short slots and finality in seconds → gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving → teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling → post quantum L1: durable cryptography, via hash-based schemes → private L1: first-class privacy, via shielded ETH transfers What is the origin story? The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism. Why the "strawmap" name? "Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons: 1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process. 2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views. The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes. What is the strawmap time frame? The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules. What do the letters on top represent? The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star"). What do the colors and arrows represent? Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom. Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups. What are headliners? Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively. (L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.) Will the strawmap evolve? Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document. Can I share feedback? Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.
LIVE NOW - Zero Crypto at Home: A Security Playbook for 2026 Self-custody was supposed to be freedom. Now it comes with a threat model. @lopp (@CasaHODL) + @beausecurity (former CIA officer) break down how to harden your stack in 2026: - The phishing playbook: fake airdrops, approvals, malware “Zoom” installs - “Email = identity” + why passkeys/YubiKeys beat SMS + codes - Wallet segregation (hot wallet = pocket cash) - Zero Crypto at Home: multisig + time delays + keys in different places - Why “duress wallets” can backfire - Home hardening: cameras, lights, panic buttons, a plan with your family Enjoy the episode!🎬 -------------- TIMESTAMPS 0:00 Intro 2:45 The 2026 threat landscape: third parties, privacy, then physical 8:07 Most likely vs most dangerous: phishing vs wrench attacks 17:23 Minimize attack surface + separate your money by risk 20:27 The “3-wallet” model: daily spend, risky ops, deep cold vault 25:08 Hot vs cold: the $1k rule + don’t sign when you’re not sharp 30:01 Social engineering defense: authenticate everything, trust nothing inbound 36:22 Password managers + the 2FA ladder (passkeys/YubiKeys win) 45:05 “Dedicated signing machine” and air-gapped thinking 47:30 Wrench attacks: how targets are found + what the attacks look like 52:50 Why France stands out (and what Dubai’s data shows) 57:37 “Zero Crypto at Home”: multisig + geography + time delays 1:12:27 Duress wallets: why they don’t reliably work 1:16:38 Home hardening checklist: cameras, lights, panic buttons, doors/windows 1:30:59 Onchain privacy reality + tax software pitfalls 1:37:40 Is this a setback for the Bankless vision?
