跳到正文
10月8日周四
  1. MIT Technology Review · AI20

    AVEVA 如何为自主工业 AI 构建更安全的落地路径

    AVEVA 首席技术官 Arti Garg 提出,工业 AI 正从预测分析转向基础模型、physical AI 与 agentic AI,但因其直接作用于物理系统,必须把安全与可靠性置于部署核心。AVEVA 的负责任 AI 框架强调安全、效率与人类监督,主张 AI 应增强而非取代关键决策中的人。Garg 还参与 IEEE 工作组,制定覆盖电力、能源、资源、水和碳的 AI 环境影响测量标准方法。

  2. vitalik.eth48

    Vitalik Buterin 修正多签安全建议:理想规则是每位签名者在每次操作后更换自己的密钥,前提是假设 ECDSA 可能变弱但不会弱到可被即时破解。他仍建议尽可能在链下收集签名,以缩短"签名暴露"到"密钥失效"之间的时间窗口,并提醒匆忙升级配置很容易导致资金损失,不要急于操作。

    引用vitalik.eth@VitalikButerin

    I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography. The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices. (and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation) So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math. The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be? This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-. For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption. And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10. To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety. And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all. Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems. For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size). Concrete TLDR, my own personal views: * Hash-based > lattice-based, in those situations where hash-based is possible at all * For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ... * For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism. * If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**. * For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money" https://firefly.social/post/x/2107837081313505768

  3. Hugging Face Blog78

    作者用 ML Intern 两天训练并发布六个模型

    作者借助 HuggingChat 中的 ML Intern,在两天内训练并发布了六个模型,包括柑橘病害识别、Huggy LoRA、相机角度 LoRA、涂鸦替换 LoRA、Pocket Rewriter 和 Agate 4-step 蒸馏模型,总计算成本约 103 美元。

    推荐理由:作者用 ML Intern 在两天内做出六个模型,给出了提示词写法、预算控制和基线对比等可复用细节。

  4. Google Research60

    Google Research 三个月实验:AI 辅助提升专利撰写产出,但未加速初级律师判断力成长

    Google Research 与 NBER 发布一项为期三个月的专利撰写实地实验,将当时未发布的 Google Labs AI 专利写作助手(现属 Gemini Notebook)随机开放给 11 家知识产权律所的 133 名律师。

    推荐理由:三个月随机对照实验区分了 AI 带来的即时产出提升与无辅助判断力的变化,为评估 AI 对专业能力的影响提供了可参考的方法。

  5. Sam Altman68

    OpenAI 在 ChatGPT 中面向所有用户推出 GPT-6 与 Intelligent UI,ChatGPT 现在可以为用户生成自定义 UI。官方称 Intelligent UI 能提供快速、可交互的回答,让日常问题更直观、复杂话题更易理解,并可在对话中即时调用任务所需的交互工具。

    引用OpenAI@OpenAI

    GPT-6 和智能 UI,现已在 ChatGPT 中向所有人推出。 ChatGPT 中的智能 UI 提供快速、交互式的回答,让日常问题更加直观,复杂主题更易理解,并随时为你提供针对任务的交互式工具。

    推荐理由:OpenAI 在 ChatGPT 中上线 Intelligent UI,读者可了解交互式回答与即时工具这一形态变化。

  6. Greg Brockman80

    OpenAI 在 ChatGPT 中推出名为 Intelligent UI 的新能力,用完全可交互的用户界面快速回答问题。据 OpenAI 介绍,该功能让日常问题的回答更直观,复杂主题更易理解,并可在需要时就地提供交互式工具。Greg Brockman 表示该功能正在向所有人推送。

    引用OpenAI@OpenAI

    GPT-6 和智能 UI,现已在 ChatGPT 中向所有人推出。 ChatGPT 中的智能 UI 提供快速、交互式的回答,让日常问题更加直观,复杂主题更易理解,并随时为你提供针对任务的交互式工具。

    推荐理由:OpenAI 在 ChatGPT 中上线 Intelligent UI,读者可了解交互式界面如何改变日常问答的呈现方式。

  7. GitHub Blog · AI & ML62

    GitHub 推出基于 ModernBERT 的密钥检测分类器,扩展 push protection

    GitHub 发布与 Microsoft Applied Sciences 联合微调的 ModernBERT 分类器,用于把 push protection 扩展到无固定格式的密钥,可在 2 毫秒内评估一批候选密钥,官方称有望让可拦截的密钥数量增加一倍以上。

    推荐理由:GitHub 用九个季度的数据说明密钥泄露压力来自代码量增长,并给出把检测成本压到 2 毫秒内的新分类器思路。

  8. Microsoft Research71

    微软研究院开源 Agent Lightning v1.0:3500 行代码的轻量智能体 RL 框架

    微软研究院开源 Agent Lightning v1.0,一个约 3500 行代码的轻量智能体强化学习框架,提出 Harnessed Agentic RL 范式,让部署时使用的 agent harness 直接参与训练,无需在训练框架内重写智能体。

    推荐理由:微软研究院开源 Agent Lightning v1.0,读者可了解让部署用 harness 直接参与 RL 训练的思路与实测收益。

10月7日周三
  1. Greg Brockman62

    OpenAI 发布了一批由内部前沿模型产出的新数学结果,相关代码与内容已公开在 github.com/openai/math。OpenAI 表示在发布这些结果前咨询了高等研究院数学与人工智能独立顾问组,并参考其建议和公开推荐。Greg Brockman 转发该消息,称其指向加速科学发现并改善所有人的生活质量。

    引用OpenAI@OpenAI

    We’re releasing a broad range of new mathematical results produced by an internal frontier model. We’ve been consulting with the independent Advisory Group on Mathematics and Artificial Intelligence at the Institute for Advanced Study, and we have drawn on their advice and public recommendations to inform how we release these results. https://github.com/openai/math

  2. Arthur Mensch38

    我们正在这座火车站里构建 AGI

    引用Guillaume Lample @ NeurIPS 2024@GuillaumeLample

    ML4 was trained on 3,800 NVIDIA Grace Blackwell GPUs in our European datacenters -- our cluster in Bruyères-le-Châtel built using our Series B fundraise. We are investing heavily in infrastructure, with our Series C and D clusters coming online soon. This additional compute will let us train longer, pursue more ambitious post-training, and iterate faster. We expect large and rapid improvements in the weeks and months ahead. 2/n

  3. Microsoft Research22

    Microsoft 研究员 Jennifer Neville 谈 AI 评测的意外失败与真实世界表现

    Microsoft 合伙人研究经理 Jennifer Neville 在 Microsoft Research Podcast 中讨论评测如何推动 AI 系统突破传统 benchmark 的性能边界,以及模型在超出常规评测时出现的"意外失败"。她结合自身从数学、物理、认知科学转向计算机科学的经历,分享了使用当前 AI 系统的实用建议,并强调当结果偏离预期时应仔细审视数据。

10月6日周二
  1. Arthur Mensch80

    Mistral AI 发布 Mistral Large 4(代号 Le Chonk),1T 参数、49B 激活、原生多模态,官方称其在美国或欧洲开源权重模型中聚合基准表现最好,并在网络防御、制造和金融等关键负载上达到 SOTA,视觉 grounding 超过闭源前沿模型。模型端到端在欧洲打造,可通过 Mistral Cloud 从欧洲部署,今日起 API 开放,权重将于 10 月底发布。联合创始人 Arthur Mensch 补充称该模型在自家算力上训练和推理,RL 尚未出现饱和迹象。

    引用Mistral AI@MistralAI

    认识 Mistral Large 4,又名 Le Chonk。 • 1T 参数,原生多模态。49B 激活。 在综合基准测试上,它是来自美国或欧洲的最佳开放权重模型。 • 在关键工作负载上达到最先进水平,包括网络防御、制造业和金融,并且在视觉定位方面超越了闭源前沿模型。 • 端到端在欧洲打造,并可通过我们自己的 Mistral Cloud 基础设施从欧洲部署。 • 今天即可通过 API 向所有人开放。正与网络安全合作伙伴私下合作。 开放权重版本将于十月底发布。

    推荐理由:Mistral 联合创始人补充了 Mistral Large 4 的自研算力训练与 RL 未饱和信号,可对照官方发布看训练侧取舍。

  2. Mistral AI82

    Mistral 发布 Mistral Large 4 公开预览

    Mistral 发布 Mistral Large 4 公开预览,这是一个 1 万亿参数、52B 激活参数的原生多模态模型,可在 Mistral Studio 试用预览 API,权重将于本月底发布。

    推荐理由:官方给出 1 万亿参数、52B 激活的开放权重模型在编码、智能体与多模态上的具体基准,可据此判断开放权重模型当前的位置。

10月5日周一
  1. GitHub Blog · AI & ML60

    GitHub 发布 ReviewBench:面向 AI 代码审查的开放基准

    GitHub 发布 ReviewBench,一个面向 AI 代码审查智能体的开放离线基准,基于 1.039 亿个 GitHub PR 的分布构建,包含 219 个 PR、覆盖 19 种语言,采用多来源 golden set 与统一评分标准,并由资深工程师独立复核,一致率 96.6%。

    推荐理由:GitHub 公开了代码审查基准的构建方法与离线到线上的验证数据,可据此判断评测信号是否可信。

  2. MIT Technology Review · AI12

    如何把预测分析带入智能体 AI 时代

    企业 AI 的竞争前沿已从预测转向自主决策,核心难题是让预测系统在不偏离业务意图的前提下依据自身结论行动。深度学习与生成式 AI 驱动的智能分析支持实时训练,使 AI 持续演进而无需等待季度刷新,其数据来源也从规整的数值记录扩展到非结构化交互数据。Everest Group 合伙人 Vishal Gupta 称,企业已不再满足于回望式视角,"analytics"一词正让位于 AI。

10月4日周日
  1. Hugging Face Blog66

    微软 ThinkingBox 基准:按数据库终态而非模型自述评判 AI 智能体

    微软 Copilot Studio 团队与 Hugging Face 联合发布 ThinkingBox 智能体评测基准,通过隔离的 MCP 工具会话运行任务,只根据智能体留下的后端终态和副作用打分,而非其生成的文字。

    推荐理由:微软与 Hugging Face 联合发布的智能体评测基准,用数据库终态而非模型自述来判定任务成败,并给出 20 次重复下的稳定性与成本数据。

10月3日周六
  1. Du Jun17

    WIDTH 针对去中心化产品推出 Crypto Native Compliance 解决方案,核心是做好 Compliance Trail,让链上行为有迹可循、风险可识别、资金流可解释,并在监管问询时提供完整证据链与沟通语言。

    引用WIDTH@WidthGRC

    What happens when money becomes programmable and AI starts operating at its speed? We were pleased to support @sgfintech_ ’s “A Programmable Economy at the Speed of AI”, co-hosted with the Ethereum Ecosystem Fund (EEF), bringing together the FinTech community for a timely conversation on AI, blockchain and the future of programmable financial infrastructure. Our Co-Founder & CEO, Chionh Chye Kit , joined Liraz Siri and Douglas Gan for a panel discussion following @VitalikButerin ’s presentation, exploring questions around AI agents, stablecoins, security, privacy, digital identity and trust. As financial infrastructure becomes increasingly programmable, building security, privacy and trust into the system will be just as important as the technology itself. Thank you to Singapore FinTech Association, EEF, the speakers and everyone who joined us for the discussion and networking session. #WIDTH #SingaporeFinTech #ArtificialIntelligence #Blockchain #FinTech #Stablecoins #DigitalIdentity #Privacy #RegTech #FinancialInfrastructure #AI

10月2日周五
  1. GitHub Blog · AI & ML22

    AI 正在改变开发者工作方式,GitHub 给出三项需要强化的技能

    GitHub 提出 AI 时代开发者应强化的三项技能:学会指挥 AI 智能体而非只是使用它,不轻信 AI 的首次答案,以及用 AI 节省的时间去解决更大的问题。文中以 GitHub Copilot 内置的 Rubber Duck agent 为例,说明它用第二个模型来审查计划、代码和测试,从而发现首个模型遗漏的问题。

  2. Google Research62

    Google 发布基于 TEE 的新一代联邦学习系统,实现可验证的隐私保护

    Google 发布新一代联邦学习系统,利用可信执行环境(TEE)为数据匿名化提供可远程验证、可审计的端到端保证,并已在 Gboard 上线英语和日语下一词预测模型。

    推荐理由:Google 公布基于 TEE 的新一代联邦学习系统设计,读者可了解其如何让数据匿名化过程可被外部验证。

  3. Hugging Face Blog37

    ServiceNow CoreAI 推出 AutoSynthData:为企业智能体生成训练数据

    ServiceNow CoreAI 构建了 AutoSynthData,利用目标模型的失败案例与更强教师的成功轨迹定位能力缺口,再生成并验证新任务用于后训练。该流程以 system specification、user prompt、verifier 三要素定义任务,要求任务可行、真实且尚未被稳定解决,并随模型改进动态调整课程。团队以 EnterpriseOps Gym 数据集演示了该流水线。