与「LAY」相关的搜索结果

X Layer has crossed 10,000 registered ERC-8004 agents onchain! As of Aug. 5, 10,126 of 10,463 registrations were attributable to the @OKX Agentic Marketplace. That concentration points to strong early traction for OKX Agentic Marketplace on @XLayerOfficial.

开发系统最极致高效的Agents.md，没有之一： # AGENTS.md ## Core Principles - Choose the simplest implementation that fully satisfies the current requirements. Avoid unnecessary abstraction, configuration, indirection, or speculative extensibility. - Make the smallest necessary change that fixes the root cause. Do not refactor unrelated modules or change strategy semantics unless explicitly requested. - Grow the system in layers. Start from the smallest working end-to-end version and add new capabilities incrementally. Never replace a working system with unfinished complexity. - Reuse existing project components before creating new ones. Prefer extending proven modules over introducing parallel implementations. - Prefer well-maintained libraries when they reduce overall complexity or improve reliability. Do not reimplement common functionality without a clear benefit. - Keep components modular with clearly defined responsibilities. Avoid unnecessary coupling between strategy logic, execution, accounting, replay, and infrastructure. - Design for long-term maintainability once a feature or strategy has been validated. Do not over-engineer speculative ideas before evidence exists. --- ## Strategy Development - Validate hypotheses with historical replay before introducing forward-only logic whenever historical validation is possible. - Every trading strategy must progress through Replay → Shadow → Canary → Live. Do not skip validation stages. - Base design decisions on measurable evidence rather than intuition. Optimize only after demonstrating that an edge exists. - Treat every strategy as an independent contract. Do not silently alter frozen behavior without explicit authorization. --- ## Existing Systems - Do not break running Shadow or Live systems for unrelated work. - Preserve compatibility only when required by active production or validation workflows. Otherwise, remove obsolete code instead of accumulating compatibility layers. - Reuse existing infrastructure whenever possible, including replay engines, accounting, execution, wallet management, order book handling, logging, monitoring, and daemon frameworks. --- ## Engineering Standards - Prefer deterministic behavior over hidden automation. - Fail loudly when assumptions are violated. Do not silently ignore errors or fall back to unexpected behavior. - Keep configuration minimal. Introduce new configuration only when behavior genuinely needs to vary. - Remove dead code instead of leaving unused paths behind. - Write code that is easy to inspect, replay, test, and reason about. - Keep implementation consistent with existing project architecture unless an architectural change is explicitly requested. --- ## Scope Discipline - Implement only the requested scope. - Do not introduce unrelated optimizations, redesigns, migrations, or feature expansions. - Non-blocking findings outside the requested scope may be noted separately but must not be merged into the current task. - Consider a task complete once its agreed acceptance criteria are satisfied. Treat subsequent improvements as separate work items.

RAG system that skips HTML parsing entirely! PixelRAG is an open-source visual RAG framework that renders documents as screenshots instead of parsing them into text. Most RAG pipelines start by converting HTML to text. Tables flatten into unstructured rows. Charts disappear. Layout context is gone before the LLM ever sees it. The paper measured this directly: HTML-to-text conversion accounts for 36.6% of retrieval failures on SimpleQA. PixelRAG skips that step entirely. It renders pages as screenshot tiles using Playwright, embeds those tiles with a fine-tuned Qwen3-VL-Embedding model, builds a FAISS index, and passes retrieved images directly to a VLM reader. No text abstraction in between. Benchmarked across six datasets against the strongest text-based baselines: - SimpleQA: 78.8% vs 71.6% (+7.1 points) - NQ-Tables: 48.8% vs 42.5% (+6.3 points) - EVQA: +15.5 points - LiveVQA: +11.3 points One honest caveat from the authors: this requires Qwen3-VL-4B class models or larger to see the benefit. Smaller models trail text retrieval. The authors also recommend using PixelRAG as an enhancement layer alongside existing text systems rather than a full replacement. Ships with a pre-built Wikipedia index covering 8.28M articles across 28.1M screenshot tiles. A Claude Code plugin lets Claude take screenshots of any URL and reason over the visual content directly. Key capabilities: • Renders web pages, PDFs, and images as screenshot tiles via Playwright • Fine-tuned Qwen3-VL-Embedding model for visual retrieval • FAISS index for fast vector search • Pre-built Wikipedia index: 8.28M articles, 28.1M tiles • 3x token cost reduction via image compression • Claude Code plugin for direct URL screenshot and visual reasoning • LoRA fine-tuning support via pixelrag-train 100% open source. I've shared the link in the replies!

底层看稀缺，顶层看客户！看到 @chamath 分享的这张 AI Stack，感觉这个架构划分和 Rewire Index 5 Layer 相当类似，分享一下我对每一层的理解： 1. 能源与基础设施层（最底层） 与 Rewired Index 的逻辑一致。电力会迎来爆发式增长，尤其是无需接入电网的独立供电商（IPP）；而土地受政策影响太大，弹性有限。在大众的舆论压力之下，太空基建应该会是未来几年的新机会，无需土地，无限电力⚡️ 2. 芯片层 做独立芯片，初创公司基本没有机会：性能要求极高、工艺极其复杂，最关键的是供应链已被完全锁死——这是头部玩家的战场。 真正的机会在融合与生态。从 Google TPU 的发展路径，到 Cerebras 等高速推理芯片的崛起，可以看出芯片会与云厂商、模型公司深度绑定。围绕芯片构建数据中心的整体供应与创新，机会很多；单做独立芯片，机会渺茫。 3. 云服务层 云可以分为 Hyperscaler 和 NeoCloud两类。模型商品化之后，几乎所有的负载都要靠云来承载，这会是非常赚钱的生意。但构建极其复杂，堪称 AI 时代的重资产业务——或者说，智能时代的房地产。 4. 模型层 模型公司面临的核心问题是正在被商品化： - 如果 Scaling Law 已到极限，模型百分之百会被商品化； - 即使 Scaling Law 还有很大空间，大家对「最好智能」的需求也在被分解——大量日常应用不需要最顶级的智能，中等水平模型和开源模型会逐渐接管这些需求，反而加速了商品化； - 最尖端的头部模型公司，更像是「先进制程」的芯片：能从中获取很高的价值，但并非所有任务都需要它。 5. 应用层：Harness vs Application 这张图最有趣的地方，是把应用层拆成了 Harness 和 Application 两层。 我的判断是：按目前模型的进化速度，Application 还没有任何机会，但 Harness 的机会已经大量出现，尤其在企业端。企业内化的知识只能通过 Context 和约束来落地，所以 Harness 就是新的企业应用层；它们会替代旧的 SaaS，或倒逼旧 SaaS 升级。 如果把 AI 扩展到大语言模型之外的更广义范畴，应用层更可能以垂直集成的形态出现，例如：自动驾驶 / RoboTaxi / 任何可端到端自动化工业流程和武器系统；生物研究 / Wet Labs；把执行能力直接部署进企业内部的模式（类似 Palantir 的服务方式）

That's exactly what I'm doing right now. Next, I'll create a layer of abstraction for the GUI, then integrate a small proprietary model to automatically identify unsupported TUI controls and perform escaping on them. The first time an unsupported TUI is encountered, it will be more resource-intensive, but after that it'll just be regular pattern matching

Dash now runs Zcash's privacy tech. Orchard powers Dash's new privacy layer—with a focus on delivering the same privacy model through a much better user experience. @TheDesertLynx explains why, with @VladCostea on @BTCTKVR.

Olivia Miles finishes the scoop reverse layup through the contact for the and-1 😤 She finishes with a team-high 28 PTS on 11-14 FGM to help the Lynx clinch their 10th straight win!

An agent economy needs four things: identity, capability, payments, and accountability. BNB Chain is bringing those layers together through standards like ERC-8004, BAP-578, x402, and ERC-8183, backed by a massive stablecoin ecosystem. Explore the full landscape 👇

Here is my AI investing guide. Sitting here August 2026, my current best thoughts are as follows: 1. LPS (Land Power Shell) is still the most obvious and fastest path to cash on cash returns. Lots of value can be assembled and traded quickly at this layer. And as data centers get more pushback, energized land can explode in value. Very bullish here. I’ve stepped into this layer very aggressively. My partner @anitavlallian and I have acquired almost 6GW coming online in a ramp from today thru 2029 of grid power and behind the meter. 2. Silicon - I helped get @GroqInc off the ground in 2015 and we licensed it to @nvidia for $20B Dec2025. I won’t invest or incubate anything in this layer now. The perf demands of the chips are too high, manufacturing precision is too complex and supply chain influence to get adjacent components like memory isn’t possible for a startup anymore. Lots of capital will be wasted here chasing Groq and Cerebras’ success. Note that both startups made sense a decade ago when these constraints were much more modest. 3. Clouds - Clouds are very very lucrative but very hard to build and very expensive and technically complicated to maintain. And as alignment becomes a more important issue, I expect the clouds will be asked to build robust KYC and attest to it. This makes the risk:reward ratio skewed. I don’t want to be responsible when the USG says a cloud allowed a bad actor to do something bad because of poor KYC. 4. Models are complicated. The big open question is how much of the revenue being generated by them today is because of tokenmaxxing and poor model behavior. If it’s a lot, then the annualized revenues will diminish meaningfully even as token consumption inflects upwards. This is the big economic question at this layer. 5. Harnesses are where the action is and why I started @8090solutions two years ago. In a nutshell, the harness helps enterprises owns their proprietary context (what Alex Karp calls their ‘alpha’). This is an enterprise’s data, workflows, evals, and business rules. A harness that gives this to an enterprise is what creates very low model-agnostic switching costs, which further reinforces my views of #4# above. 6. Applications will be another long term winner along with harnesses. This is where the differentiation between “off the shelf” and “custom time and materials” melts away. Every company, with the right harness, can now imbue their alpha into the software that runs their company. I expect this to mean that “off the shelf” is largely replaced with custom software creating a huge opportunity to write these solutions for companies. Build once and sell repeatedly is a laggard GTM motion for a SaaS world that isn’t needed here. Think custom by design, alpha embedded, proprietary by nature. Fin. Good luck to all the players!