wasabi.eth @wasabieth

Prompt: Build me a cel-shaded arcade boat racing game in Three.js, running on an infinite open ocean, at a level of visual and mechanical quality that a AAA studio would ship. Not a demo, not a prototype — a finished, beautiful, playable game. Non-negotiable constraints Stack: Vite + Three.js (latest r1xx), TypeScript, ES modules. I must be able to run npm install then npm run dev and play it in the browser immediately. Nothing else. No frameworks I have to configure, no build steps I have to debug. Zero external assets. No downloaded models, textures, HDRIs, or audio. Every mesh is built in code (procedural geometry / BufferGeometry), every texture is generated in-code (canvas 2D or noise in a shader), every sound is synthesized with the Web Audio API. If it isn't generated by your own code, it doesn't ship. Target hardware: MacBook M5 Pro, Chrome. Lock a solid 60fps at retina resolution. Use instancing, frustum culling, adaptive pixel ratio, and a proper LOD scheme. Performance is a quality requirement, not an afterthought — a beautiful game that stutters is a failed game. Art direction — this is the heart of the project The entire game is NPR (non-photorealistic rendering), anime cel-shaded. Think Guilty Gear Xrd's ink work and Wave Race 64's stylized water energy, rendered with modern shader technique. Zero PBR realism. If any surface in the final game reads as "physically based," you have failed the art direction. Implement, properly, all of the following: Ramp / step lighting. Custom ShaderMaterial (or a heavily extended MeshToonMaterial) with a 3–4 band gradient ramp texture, NearestFilter, no interpolation. Quantized diffuse is the single most important part of the look — tune the band thresholds by eye, not by default values. Inverted-hull outlines on boats, riders, buoys, and gates. Duplicate mesh, push vertices along smoothed normals, side: BackSide, black or deep-toned ink. Scale the push with view distance so line width stays constant in screen space — no fat lines up close, no vanishing lines far away. Screen-space edge detection as a post pass for interior lines the hull trick can't produce. EffectComposer + a normal/depth prepass (MRT) + Sobel filter. Two line systems working together, tuned so they don't double up. Fresnel rim light on every character and boat, so silhouettes pop against the water. Banded specular. Hard-edged highlight shapes, no smooth falloff. Fake environment reflection with a matcap or ramp, never a real cubemap probe. Sky and atmosphere: gradient sky dome shader, stylized cel clouds (flat shapes with hard rim edges, drifting), a sun with a bloom-ish stylized flare that stays graphic rather than photographic. Limited, high-saturation, deliberately chosen palette — pick one and commit to it across water, sky, hulls, and UI. The water — treat this as its own AAA-sized problem The ocean is the star of the game and most of the screen. Give it a dedicated sub-agent and more iterations than anything else. Displacement: sum of 4–6 Gerstner waves in the vertex shader, with a low-frequency swell and higher-frequency chop layered on top. Real wave motion, real crest sharpening — not a sine ripple. Infinite ocean: projected grid or tiled/recentred mesh that follows the camera so the player can drive forever with no visible seam, no visible tiling repetition, and no LOD popping. Cel-shaded water color: banded by wave height and by depth, hard transitions between bands, no smooth gradient. Deep tone, mid tone, crest tone. Stylized foam, done properly: hard-edged white foam that appears on wave crests above a threshold; a foam ring around every hull driven by a depth-difference mask; a persistent wake ribbon behind each boat that scrolls, spreads, and dissipates over time; spray particles on hard landings and hard turns. Foam is what sells stylized water — it should be a real system, not a decal. Quantized sparkle highlights on the surface, animated, reading as anime light-glitter rather than specular noise. The game Format: 4 boats — me plus 3 AI opponents. 3 laps. Countdown start, finish line, results screen with times and placement. Course: a closed circuit marked on open water by a glowing green racing line — a CatmullRomCurve3 spline rendered as a ribbon that sits on the water surface and rides the waves with it, so it rises and falls with the swell instead of clipping through. Plus floating checkpoint gates along the route, wrong-way detection, and a corner-preview indicator. Design an actual interesting circuit: fast straights, a hairpin, a wide sweeper, a chicane, one section that runs across the swell so the boats get airtime. Boat handling: arcade, weighty, satisfying. Buoyancy sampled from real Gerstner wave height at 5–6 hull points so the boat genuinely pitches, rolls, and slams into troughs. Throttle, steering that tightens with speed, a drift/powerslide with a boost payoff, airtime off crests with a landing impact. It should feel like the boat is fighting water, not sliding on glass. AI racers: spline-following with lookahead steering, per-racer personality (one aggressive, one clean, one erratic), mild rubber-banding so races stay close, collision avoidance between boats, and mistakes — they should occasionally take a bad line so beating them feels earned. Riders: a cel-shaded character on every boat, and their animation matters as much as the boats. Rigged and animated in code: lean into turns, weight shift on acceleration and braking, arms working the throttle, crouch on landings, idle bob synced to the wave motion, a celebration on finishing. No T-posed statues, no rigid props. A stiff rider will sink the whole look. Camera: spring-damped chase cam, FOV kick with speed, subtle screenshake on slams, a cinematic orbit during the countdown and on the results screen. HUD: in the same cel style — speedometer, lap counter, position, split times, boost meter, minimap showing the spline and all four racers. Hand-designed, not default HTML. Audio: synthesized engine tone that pitches with RPM, water rush that scales with speed, impact thuds, a start horn. All Web Audio, all in code. How I want you to work Fan out sub-agents. One owns the water shader system. One owns the cel-shading and outline pipeline. One owns boat physics and feel. One owns AI racers and race logic. One owns riders and character animation. One owns HUD, camera, and audio. One owns performance. Have them work in parallel against a shared architecture you define first. Build a screenshot harness before anything else. Playwright, headless, capable of loading the game, driving it to a given moment, and capturing frames at retina resolution from several camera angles. Every visual claim gets verified against a real captured frame — never against your assumption about what the code does. Run a dedicated visual critic sub-agent whose only job is to look at those screenshots and be harsh. Its standard: would this frame pass as a shipped, published cel-shaded racing game? It should name specific defects — banding thresholds that read as mush, outlines that break on silhouettes, foam that looks like static, a rider that reads as a prop, water that repeats. It reports defects; it does not approve work to be polite. /loop each subsystem against its critic until the critic runs out of specific defects to name. Don't move on early, and don't declare something done because it "works" — working is the floor, not the goal. Build in milestones, each one playable: (1) ocean + camera, (2) player boat with buoyancy and feel, (3) cel pipeline and outlines applied to everything, (4) course, laps, checkpoints, (5) AI racers, (6) riders and animation, (7) HUD and audio, (8) performance and polish pass. Show me something runnable at every milestone. Track your own quality bar honestly. If a subsystem is at 70% of the target, say so and tell me why, rather than describing it as finished. I would rather hear that the foam needs another pass than find out myself. Deliverable A repo with a README, clean architecture, readable and commented shader code, and a working npm install && npm run dev. When I run it, I want to be dropped into a race that looks like a piece of published anime-styled game art, and want to play it again immediately after finishing. Ultracode.

Vibe-coding 核心工具清單 #mbkVIBE 1️⃣ 核心編碼引擎：大腦與環境 (The Engines) 這些工具是 Vibe-coding 的起點，負責將你的想法轉化為高品質的程式碼。 • @AnthropicAI (Claude)：當前 Vibe-coding 的靈魂。Claude 3.7/4 系列以其卓越的邏輯推理和「人味」十足的 Debug 建議，成為開發者的首選大腦。 • @cursor_ai (Cursor)：AI 原生編輯器的王者。其 Composer 模式讓你可以同時操控多個檔案，真正實現「說句話，App 就改好」。 • @Replit (Replit)：雲端開發的先驅。透過 Replit Agent，你甚至可以在手機上用對話方式部署一個完整的全端應用。 • @github (GitHub Copilot)：憑藉最強大的程式碼生態系，Copilot Extensions 與 Workspace 讓企業級的 Vibe-coding 變得可能。 • @zeddotdev (Zed)：追求極致速度的開發者首選。這款用 Rust 編寫的編輯器結合了強大的 AI 協作功能，快到讓你的靈感不會被任何卡頓中斷。 • @aider_ai (Aider)：最強大的終端機（CLI）AI 配對編程工具，適合喜歡在指令列中快速迭代的高級 Vibe-coders。 • @codeiumdev (Codeium) & @tabnine：如果你追求極致的自動補全速度與私有化部署，這兩者是除了 Copilot 之外的最佳 AI 助手選擇。 2️⃣ 介面與快速原型：視覺即產品 (The Visuals) 在 Vibe-coding 的世界裡，UI 不再需要像素級的調整，而是透過生成與挑選。 • @vercel (v0)：前端開發的黑科技。輸入描述或上傳截圖，v0 就能為你生成完美的 React/Tailwind 組件。 • @lovable (Lovable)：專為「想把想法變成產品」的人設計。這是一個強大的 AI App 建造器，能幫你從零到一構建出美觀且具備功能的軟體。 • @stackblitz (bolt.new)：基於瀏覽器的 Prompt-to-App 引擎，一鍵生成、運行並部署 Full-stack 專案，完全不需配置本地環境。 • @Dribbble：當你缺乏「Vibe」靈感時，Dribbble 依然是獲取頂尖設計趨勢與 UI 靈感的聖地。 3️⃣ 後端與基礎建設：穩定與變現 (Infrastructure) 強大的產品需要穩定的支撐。這些工具讓後端配置變得「無感」。 • @supabase (Supabase)：Firebase 的最強競爭對手。提供即時資料庫、身份驗證與存儲，且 AI 助手能幫你搞定所有 SQL 語法。 • @vercel：Vibe-coding 的終點站。極簡的部署流程，讓你的產品在幾秒鐘內面向全球用戶。 • @RevenueCat：想讓你的 Vibe 變現？RevenueCat 處理了所有麻煩的訂閱邏輯，讓你輕鬆在 iOS/Android 上收錢。 • @zencoderai (Zencoder)：新興的 AI Agent 平台，專注於自動化處理複雜的編碼任務與專案重構。 4️⃣ 數位資產與生態連結 (The Ecosystem) • @NanoBanana：2026 年崛起的新秀，專門為開發者提供 AI 生成的 UI 資產與圖像素材。 • @midjourney：生成高品質品牌圖、插畫與背景的首選，為你的 App 注入獨特的視覺氛圍。 • @rainbowdotme (Rainbow)：如果你在開發 Web3 應用，Rainbow 提供了最優雅的錢包連結體驗。 • @OpenAI (ChatGPT)：不僅是萬能的百科全書，也是梳理複雜業務邏輯與撰寫行銷文案的最佳夥伴。 • @rork：協助開發者優化行動端應用的發布與成長路徑。 🔥🔥 如何開始你的 Vibe-coding？ Vibe-coding 的核心不在於掌握多少門語言，而是在於如何與 AI 溝通以及如何組合這些工具。 1. 用 Claude 構思邏輯。 2. 用 Cursor/v0 實作介面。 3. 用 Supabase 存儲數據。 4. 用 Vercel 一鍵上線。 在這個時代，創意才是唯一的瓶頸。現在就拿起這些工具，開啟你的第一個 Vibe-coding 專案吧！

本来我定的价格69元，出版社说影响不好，改成了68元😂 现在走链接7折，只要47.6，你买不了吃亏也买不了上当: u.jd.com/nzldvrX 家人们，买完记得好评！

0xAA @0xAA_Science

3 years ago

WTF Solidity教程已经出版了，可以在京东买到: u.jd.com/nzldvrX 本来想在链上预售的，但是最近准备答辩，耽搁了。之后会开放，随书赠送写真集和数字签名👿

46 18 83 193K 37

Midjourney是图像生成的野兽。 但是Midjourney的价格为10美元/月。 这是图像生成的10个免费替代方案： [先🐴后看]

Announcing roomGPT! Redesign your room in seconds with AI! 100% free and open source. roomgpt.io

@mrblock 看他發文的確是很有樂趣

神級空投 EigenLayer：全面概述 EigenLayer 在 Ethereum 挖礦領域中帶來了一次範疇轉變。讓我們一步步解釋其複雜性。 挖礦地點：app.eigenlayer.xyz 什麼是 EigenLayer？ EigenLayer 是在 Ethereum 上的一個協議，提出了再挖礦的概念，這基本上意味著在共識層上重用已經挖掘的 ETH。這為挖礦者帶來了額外的安全性和獎勵，同時使 Ethereum 更加多功能和互聯互通。 Gitbook: docs.eigenlayer.xyz/overview/readme 優點： （ETH 的重用）：Ethereum 挖礦者可以使用相同的挖掘 ETH 來保護多個服務。 （較低的資本成本）：重用 ETH 降低了挖礦者為多個服務提供安全性的成本。 （更高的信任保證）：通過匯集安全資源，單個服務獲得了更高水平的安全性。 （目前系統中的挑戰）： 在目前的 Ethereum 景觀中，每個新的去中心化服務都必須從零開始建立信任。這導致了安全性碎片化。EigenLayer 提供了解決方案，允許任何服務利用 Ethereum 的集體安全性，為更安全和互聯的生態系鋪平了道路。 術語： Restaking = 再挖礦 （加密經濟安全）：結合經濟誘因和加密技術以確保網絡的完整性和安全性的策略。 （服務模組，服務或 AVS）：需要分佈式驗證機制的系統，如側鏈、預言機網絡等。 （通過再挖礦的匯集安全）：Ethereum 挖礦者可以通過在 EigenLayer 上支持新服務來增強安全性。 （自由市場治理）：EigenLayer 通過提供選擇賦予挖礦者權力。挖礦者可以決定基於自己的風險和回報感知來支持哪些服務。 （流動性挖礦）：用戶挖掘他們的 ETH，反過來得到流動性挖礦代幣 (LST)，稍後可以交易或兌換。 （原生再挖礦）：Ethereum 挖礦者通過將他們的提款詳細信息鏈接到 EigenLayer 合約直接再次挖掘他們的 ETH。 （LST 再挖礦）：使用 Liquid Staking Tokens (LSTs) 通過將它們轉移到 EigenLayer 合約進行再挖礦。 （EigenLayer 中的委派）：挖礦者可以將其資產分配給其他實體，由其處理在 EigenLayer 上構建的軟件模組，而不是自己操作軟件。 （鏈上削減合約）：確保任何不當行為的削減的合約。 （EigenPod）：一個針對用戶部署的合約，促進原生再挖礦。 （Restaking Points 挖礦點）：它量化了您對 EigenLayer 再挖礦的貢獻。它考慮了您的挖礦金額和持續時間。 （再挖礦比率）：顯示您與所有重新挖掘者的總貢獻之間的比率。 （部分提款）：從 ETH 挖礦中積累的獎勵。 （全部提款）：整個挖掘金額（32ETH）加上獎勵。 結論： EigenLayer 通過引入再挖礦的概念增強了 Ethereum 的能力。這是向更安全、互聯和經濟的 Ethereum 生態系邁出的具有遠見的一步。無論您是開發者、挖礦者還是普通用戶，了解 EigenLayer 的潛力都可以讓您在快速發展的去中心化系統世界中獲得優勢。 融資： 二月EigenLayer 公布在加密貨幣寒冬期間籌集了5,000萬美元，估值高達2.5億美金。 coindesk.com/business/2023/…

AI是下一个学习的最大技能。 AI专家每年最多可赚取200000美元以上。 以下是Google和Microsoft的5个免费课程，大多数人不知道：🧵

Noticed that someone's bot was copying my bids on Blur, so I decided to trick him... Made 800 ETH profit thanksss

刚刚遇到了一个年收入 20 万美元以上的人。 他甚至没有写过一行代码。 以下是他每天用来赚钱的 15 个令人惊叹的人工智能工具： 收藏起来以后使用🧵

最近很多人拜托傻哥找工作。 来，先用免费的AI工具来写简历吧： 1. Kickresume.com 2. Novoresume.com 3. Resumenerd.com 4. Livecareer.com 5. Flowcv.com 6. Resume.io 7. Zety.com 8. Wozber.com 9. Rxresu.me via @hasantoxr

花了一天时间总结的linea策略。 2分钟学会。。。你确定不看一下吗? #Linea #Airdrop

@laofeiyyds 已關@求互關

"Wen $ZRO airdrop? Wen zkSync airdrop? " Have snapshots for the airdrops been taken yet?📷 I've done some digging and got the scoop. Find out all the details that I dug up for you👇🧵

Turn your $8 into $10,000 with this airdrop strategy! Get your hands on FREE DASHBOARD and qualify for $ZRO, zkSync, and Polygon zkEVM airdrops in just 10 minutes. Click the link below 🔽

增加你的L0智能合约数量和tx！几乎零成本！还有可能一鱼多吃！快点做起来吧！ @OmniX_NFT 是一个全链NFT市场，使用L0的底层技术，目前推出了一个活动，可以免费mint限量版ONFT。 需要注意的是，仅仅mint你的NFT是不使用L0技术的，将NFT跨链到其他链才会交互到L0。 以下是详细教程👇👇👇

Linea 上主网了，这生态项目多的，根本撸不过来。 家人们，谁懂啊。。。 传送门：linea.build/apps @LineaBuild

⚡️ 懒人利器：从 tx 到 web3 代码 👀 zkSync Era 主网上线几个月以来，相对靠谱的项目方以肉眼可见的速度在增长（如 Odos)，但基础设施建设似乎没能一起跟上 😳 比如：目前仅官方一个 RPC 服务器可选（垄断往往是坏的）、官方的区块链浏览器经常性崩溃无法打开 🥺 但最糟糕的是，不知是项目方有意，还是技术问题，部署在 zkSync Era 上的合约，少有验证合约源代码的 🫠 这就导致一个问题：绝大多数的合约调用，都成了一种“盲掉“，不但增加风险，对于我们解读这笔交易具体做了什么，难度增加了不知多少倍 😈 鉴于此，打算为羸弱的 zkSync 基建添砖加瓦，花了N个小时，改了N版的 “WTFtx 工具“上线 🎯 作用： 解析 tx 调用函数具体信息、提取函数名、参数类型、参数值，“附带“生成基于 web3. py 的代码 💡 使用方式： 输入交易 tx 的 hash，点击“解析tx“按钮，稍等片刻，即可获取tx详情 🙋 备注：不是每一条 tx 都能成功解析，取决于 API 接口返回数据 ⚠️ 注意：显示信息仅供参考，免费使用，责任自负 🌍 ： wtftx.pages.dev ❤️ ： 网站尚未注册独立域名，欢迎大佬在页面底部打赏域名费 💬 ：有任何使用问题或改进建议请在此推文下留言，后续会酌情处理

使用AI应该是完全免费的。 这张图是付费AI工具的免费替代方案：

ChatGPT现在有一个严肃的竞争对手。 Anthropic刚刚发布了Claude 2，它非常强大。 以下是您应该免费使用Claude 2而不是ChatGPT的原因： [Thread]