Lucas

AI & crypto builder

[陈成 @chenchengpro]

OpenAI 昨天低调开源了一个框架，叫 Symphony 🎵

它能把你的 Linear 看板变成一条全自动的研发流水线。
我扒了一遍代码，说说它到底怎么运作的 👇

1/ 核心逻辑只有一句话：
监控 Issue → 分配 Agent → 写代码 → 提 PR → 循��

2/ 技术栈是 Elixir，OTP 架构，天然支持多 Agent 并发。
每个 Issue 对应一个独立 Workspace，互不干扰。

3/ 最有意思的设计是 WORKFLOW.md：
把 Agent 的行为策略写进项目仓库，随代码一起提交、review、回滚。
Agent 怎么干活，团队说了算。

4/ 开源地址：https://t.co/kSf9Ns9eUz

你们团队用 Linear 吗？这东西值得试试。

[Raycast @raycast]

Today we're launching Glaze 💠

Create any desktop app in minutes by chatting with AI.
Beautiful, powerful, and truly personal.

Learn more on https://t.co/tTL644I574
Follow @glazeapp for updates.

[OKX中文 @okxchinese]

OKX OnchainOS，现已全面上线！

我们原生自研的 OKX Wallet、OKX DEX 底层能力栈，现在全面开放给开发者以及 AI Agent；
一套接口整合日均 12 亿次调用的自用同款 API，打通 20+ 链的交易、行情，MCP 原生支持，Agent 自由调用。

和 OKX 一起，构建 AI 原生的 Web3 未来👉https://t.co/55o6Wpj3Cl

[vitalik.eth @VitalikButerin]

Now, account abstraction.

We have been talking about account abstraction ever since early 2016, see the original EIP-86: https://t.co/E4xJymAxiH

Now, we finally have EIP-8141 ( https://t.co/YD9nIpsxcC ), an omnibus that wraps up and solves every remaining problem that AA was intended to address (plus more). Let's talk again about what it does.

The concept, "Frame Transactions", is about as simple as you can get while still being highly general purpose. A transaction is N calls, which can read each other's calldata, and which have the ability to authorize a sender and authorize a gas payer. At the protocol layer, *that's it*.

Now, let's see how to use it.

First, a "normal transaction from a normal account" (eg. a multisig, or an account with changeable keys, or with a quantum-resistant signature scheme). This would have two frames:

* Validation (check the signature, and return using the ACCEPT opcode with flags set to signal approval of sender and of gas payment)
* Execution

You could have multiple execution frames, atomic operations (eg. approve then spend) become trivial now.

If the account does not exist yet, then you prepend another frame, "Deployment", which calls a proxy to create the contract (EIP-7997 https://t.co/sIQrtJDXLt is good for this, as it would also let the contract address reliably be consistent across chains).

Now, suppose you want to pay gas in RAI. You use a paymaster contract, which is a special-purpose onchain DEX that provides the ETH in real time. The tx frames are:

* Deployment [if needed]
* Validation (ACCEPT approves sender only, not gas payment)
* Paymaster validation (paymaster checks that the immediate next op sends enough RAI to the paymaster and that the final op exists)
* Send RAI to the paymaster
* Execution [can be multiple]
* Paymaster refunds unused RAI, and converts to ETH

Basically the same thing that is done in existing sponsored transactions mechanisms, but with no intermediaries required (!!!!). Intermediary minimization is a core principle of non-ugly cypherpunk ethereum: maximize what you can do even if all the world's infrastructure except the ethereum chain itself goes down.

Now, privacy protocols. Two strategies here. First, we can have a paymaster contract, which checks for a valid ZK-SNARK and pays for gas if it sees one. Second, we could add 2D nonces (see https://t.co/1cRegaXpHM ), which allow an individual account to function as a privacy protocol, and receive txs in parallel from many users.

Basically, the mechanism is extremely flexible, and solves for all the use cases. But is it safe? At the onchain level, yes, obviously so: a tx is only valid to include if it contains a validation frame that returns ACCEPT with the flag to pay gas. The more challenging question is at the mempool level.

If a tx contains a first frame which calls into 10000 accounts and rejects if any of them have different values, this cannot be broadcasted safely. But all of the examples above can. There is a similar notion here to "standard transactions" in bitcoin, where the chain itself only enforces a very limited set of rules, but there are more rules at the mempool layer.

There are specific rulesets (eg. "validation frame must come before execution frames, and cannot call out to outside contracts") that are known to be safe, but are limited. For paymasters, there has been deep thought about a staking mechanism to limit DoS attacks in a very general-purpose way. Realistically, when 8141 is rolled out, the mempool rules will be very conservative, and there will be a second optional more aggressive mempool. The former will expand over time.

For privacy protocol users, this means that we can completely remove "public broadcasters" that are the source of massive UX pain in railgun/PP/TC, and replace them with a general-purpose public mempool.

For quantum-resistant signatures, we also have to solve one more problem: efficiency. Here's are posts about the ideas we have for that: https://t.co/xzG3Jp7Yky https://t.co/WikL7gJ5qg

AA is also highly complementary with FOCIL: FOCIL ensures rapid inclusion guarantees for transactions, and AA ensures that all of the more complex operations people want to make actually can be made directly as first-class transactions.

Another interesting topic is EOA compatibility in 8141. This is being discussed, in principle it is possible, so all accounts incl existing ones can be put into the same framework and gain the ability to do batch operations, transaction sponsorship, etc, all as first-class transactions that fully benefit from FOCIL.

Finally, after over a decade of research and refinement of these techniques, this all looks possible to make happen within a year (Hegota fork).
https://t.co/p7XOgId5NN

[Stephen Haney @stephenhaney]

Hello!

Today we're releasing Paper Desktop

Paper is now a canvas for Cursor, Claude Code, Codex. Any agent can read and write html to Paper.

• push or pull from your codebase
• pull real data from anywhere
• less work, more design

What will you ship? Sound on 🎶

[Lucas @HoulamTeng]

剩下的假期vibe个agent试试看。

[kepano @kepano]

skill files are distilled thinking

don't import thinking that you don't understand

[dax @thdxr]

everyone's talking about their teams like they were at the peak of efficiency and bottlenecked by ability to produce code

here's what things actually look like

- your org rarely has good ideas. ideas being expensive to implement was actually helping

- majority of workers have no reason to be super motivated, they want to do their 9-5 and get back to their life

- they're not using AI to be 10x more effective they're using it to churn out their tasks with less energy spend

- the 2 people on your team that actually tried are now flattened by the slop code everyone is producing, they will quit soon

- even when you produce work faster you're still bottlenecked by bureaucracy and the dozen other realities of shipping something real

- your CFO is like what do you mean each engineer now costs $2000 extra per month in LLM bills

[OpenAI @OpenAI]

Introducing EVMbench—a new benchmark that measures how well AI agents can detect, exploit, and patch high-severity smart contract vulnerabilities. https://t.co/op5zufgAGH

[Lucas @HoulamTeng]

I'm claiming my AI agent "LukaClaw" on @moltbook 🦞

Verification: kelp-X4MZ

[Lucas @HoulamTeng]

在考虑用 AI 写一个钱包自己用，栽也要栽在自己手里。
自托管需要从代码开始，否则宇宙第一钱包都不靠谱🤣

[Cos(余弦)😶‍🌫️ @evilcos]

Trust Wallet 浏览器扩展带后门版本是 2.68.0，修复后的是 2.69.0，对比了下，正常代码和后门代码的代码差异，���图。

后门代码增加了个 PostHog 来采集钱包用户的各种隐私信息（包括助记词），并发送到攻击者服务器 api.metrics-trustwallet[.]com。

预估时间线：攻击者至少 12.8 开始做的准备，12.22 成功植入后门，12.25 圣诞节开始转移资金，于是被发现。据 @zachxbt 的统计，用户损失超 $6m...

cc @SlowMist_Team @MistTrack_io

[Lucas @HoulamTeng]

@jesseBitget Jan

[Lucas @HoulamTeng]

除了支付之外，RWA也是很���要的方向。
虽然最终活下来可能还是链上casino。🤷

[Lucas @HoulamTeng]

@jesseBitget 连夜开通蓝标
实习生 help 实习生 ❤️

[Lucas @HoulamTeng]

7️⃣ 总结建议大家去 Tempo 的网站体验一下（https://t.co/hknb9xbboV）。 不为别的，就为了看看“当基础设施成熟时，Web3 支付该有的样子”。

如果你也是当年因为 Infra 不成熟而创业失败的 Builder，欢迎在评论区拥抱一下。🫂

End.

[Lucas @HoulamTeng]

看到 Tempo 上测试网，我那是“悲喜交加”

Tempo 终于推出 Testnet 了。 作为在行业里苟了 6 年的资深实习生，看完他们的产品文档和愿景，我点燃了一根烟。🚬

不仅是因为他们做的东西很牛，更是因为——这简直就是我 3 年前死在 PPT 里的梦想的“完全体”。

聊聊为什么我看好它，以及一个老产品人的血泪教训。👇

[Tempo @tempo]

Tempo’s testnet is live!

Any company can now build on a payments-first chain designed for instant settlement, predictable fees, and a stablecoin-native experience.

Tempo has been shaped with a wide group of partners validating real workloads including @AnthropicAI, @Coupang, @DeutscheBank, @DoorDash, @Lead_Bank, @mercury, @nubank, @OpenAI, @Revolut, @Shopify, @StanChart, and @Visa.

Since our announcement, @brexHQ, @Coastal, @crossriverbank, @deel, @faire_wholesale, @Figure, @GustoHQ , @Kalshi, @Klarna, @Mastercard, @Payoneer, @withpersona, @tryramp, and @UBS have also joined as design partners.

Dedicated payment lanes, stablecoin gas, deterministic finality, a built-in stable asset DEX, and programmable smart accounts are all live on testnet.

If you’re building or modernizing payment flows, you can start integrating and testing today.

[Lucas @HoulamTeng]

6️⃣ 赛道拥挤，好戏在后头当然，盯上这块肥肉的不止 Tempo。 隔壁 @arc 和 @noble_xyz 也在磨刀霍霍，构建面向稳定币的专用区块链网络。 “稳定币应用链” 正在成为新的叙事战场。