Feng Liu
6K posts

Feng Liu
@fishkiller
I built @ChainNewscom & shut it down. Now helping/supporting fearless crypto builders via https://t.co/6vlWPdowYj | 🐈ailurophile🐈⬛


Circle 在公布季报的同时,公布了自己做的 EVM 链 Arc 的 2.22 亿美元的融资信息(估值 30 亿美元),并且明确说明:完成的是代币融资。也就是说,这条链会发币,这让 Circle 成为首家进行代币预售的上市公司。 在这之前,Arc 的文档中写的很清楚:Arc 链 gas 用的是 USDC。 那这个即将推出的 ARC 代币是干什么用的呢? 看了看刚公布的白皮书:ARC 被设计成整个 Arc 系统的「原生协调资产」,也就是,通过 staking 确保链的安全、通过 ARC 代币获得平台权益、获取协议费收入的价值捕获、参与经济治理等等。 这是现在流行的稳定币公链的两层代币模型设计:USDC 负责做 gas 来「使用链」;ARC 负责「拥有链、协调链、治理链、分享链的增长」。 ARC 代币经济的信息: • 初始供应量 = 100 亿 • 早期通胀率预计约为每年 2–3% • 通胀率随时间递减 • 长期目标 = 通胀中性 • 25% — Circle(基金会/核心团队) • 60% — 生态系统(代币销售、开发者资助、网络增长计划等) • 15% — 长期储备


@fishkiller 对于agent来说,现阶段有哪些支付场景呢


This is my 3rd week as VP of Engineering DeFi at @Polymarket , and I'm going to be straight: the traction @Polymarket has seen has massively outpaced our infrastructure, and we haven't done nearly enough to scale to keep up. I hear you, and fixing this is our entire focus. We're a major company now, and we need to engineer like one. Here's exactly what we're doing: - Onchain data latency. We're working on making this near-instant so the experience is incredible. - Chain migration. We need more block space, cheaper gas and much smaller block times so settlement is instant. - Transactions are getting cancelled. We understand this is one of the most frustrating issues right now, and we have a complete fix coming very soon. - Massive focus on the website to make it faster, more responsive, and with better UX. - We added observability everywhere. Proper alerting so we catch issues ourselves, market makers should not be the ones telling us something is down. That's been unacceptable, and we know it. - E2e tests throughout, starting with the CLOB, so issues get caught in CI before anything ships. - CLOBv2 is not a rewrite. It won't improve performance or stability on its own; it's an upgrade that unlocks us to move fast right after. We'll do better with communication next time. - We are rebuilding the CLOB from the ground up. Most important thing we're doing. Without it, we can't be the best DeFi exchange in the world. We know it, we're on it, it's mission critical. - Unified TypeScript SDK for all APIs, which is shipping soon. - Unified API. One WS connection for everything, with a schema that's actually readable. - New Polymarket contract in the works that unlocks things that are simply impossible on the current protocol. - New hires: Head of QA Automation, Head of Dev Tooling, Head of Internal Tooling, Head of Data Engineering. - Smaller, dedicated teams. Fewer focus points per person, clearer ownership. People do what they're good at and are accountable for it. - Working closely with customer support to give them real debugging tools so any user issue gets properly diagnosed, not lost. - Proper communication with marketing and market makers so everyone knows what's coming and when, and MM can submit feature requests with a clear path to get them into engineering and shipped. - Working with 4 security teams daily to ensure we're super secure and that funds are always safe. - Perps incoming. Brand new contracts and a backend built from scratch in Rust. We're proud of this one. - A lot of other fixes are running in parallel right now. Starting next Friday, I will be posting weekly engineering updates. I joined because I genuinely believe in what @Polymarket is trying to do. @shayne_coplan built this so the world has somewhere to go to find out what's actually going to happen, not what the media thinks, not what a pundit says, but what thousands of people are willing to put money on. But right now, our engineering isn't living up to that. We've let people down, and I'm not going to dress that up. I came here to fix it, and that's exactly what we're going to do. The next few months are going to speak for themselves. Stay with us.


Sad news on nouns. Still think they are one of the best looking pfp of all time



Claude explains the $71M @arbitrum clawback: What this transaction is Tx: 0x5618...0f6b on Arbitrum, block 454686044, April 21, 2026 03:35 UTC From: 0x5d39...7Ccc — labeled on Arbiscan as “Kelp DAO Exploiter 1” To: 0x0000000000000000000000000000000000000DA0 — a special system/recovery sink (not the normal 0x...dEaD burn address) Value: 30,765.667 ETH (~$71M) — effectively the entire Arbitrum-side balance of the attacker’s hub wallet Tx type: ArbitrumUnsignedTxType (EIP-2718 type 0x65 / 101) The “type 101” is the key. That is not a user-signed transaction — a normal EOA physically cannot produce one. ArbitrumUnsignedTxType is an ArbOS system transaction that only the chain itself (via the sequencer / ArbOS upgrade path controlled by the Arbitrum Security Council) can inject. It bypasses the attacker’s private key entirely. The remediation (this tx): Arbitrum’s Security Council used its emergency powers to inject an ArbitrumUnsignedTxType that forcibly moved the attacker’s full 30,765 ETH from the hub address into a protocol-controlled recovery sink (0x...0DA0). Why it’s “extraordinary” Arbitrum did not perform a reorg or historical rewrite — the chain’s ordering is intact. Instead, the Security Council used a privileged state-override transaction type that is part of ArbOS but has essentially never been used before. It is functionally a state-level clawback: the attacker’s private key still signs txs, but that address’s ETH was moved by the chain itself. This is the mechanism Arbitrum’s progressive-decentralization docs reserve for “catastrophic” emergencies (12-of-N Security Council action), and this is one of the clearest public demonstrations of it being invoked. Note that it only recovered the Arbitrum leg of the theft — the ~75,700 ETH on Ethereum is outside Arbitrum’s control and remains with the attacker, which is why Aave is still facing up to ~$230M of potential bad debt on the Ethereum side. Sources: Arbiscan tx: arbiscan.io/tx/0x561804424… Arbitrum Docs — ArbOS / Sequencer forced inclusion: docs.arbitrum.io/run-arbitrum-n… Arbitrum Foundation — progressive decentralization & Security Council: docs.arbitrum.foundation/state-of-progr…

Spark在1月份就停掉了rsETH相关的市场,所以在这次安全事件中没有受到波及。 与其他协议不同,Spark在借贷市场上的安全控制策略是主动收紧,而不是扩张。 整个Sky体系都是这种风控哲学,虽然可能导致协议发展缓慢,但在关键时刻体现出了价值。

开源圈最近爆出了一个大瓜,我仔细扒完了 Evolver 团队发布的这篇深度拆解博客evomap.ai/zh/blog/hermes…,把这两个项目的仓库翻了个底朝天,帮大家理清这起抄袭风波背后的蛛丝马迹。 先看时间线,这是最硬的锤。 Evolver 早在 2026 年 2 月1日就开源了,连带着那套核心的 GEP 协议也全盘托出。而 Nous Research 的 Hermes Agent 呢?直到 3 月中旬才上线。 这中间足足有一个多月的空窗期,在瞬息万变的 AI 圈,这几乎是半个世纪了。 当时在 GitHub 搜自进化 Agent,Evolver 是唯一的头部,要说大厂团队没看过,那真的很难让人信服。 再聊聊技术架构,如果说英雄所见略同,那这相似度也太高了。 Evolver 提出了三层资产体系和三层记忆体系,Hermes 换了个皮,但层级逻辑和语义划分简直是 1:1 像素级复刻。最离谱的是那个 10 步进化的主循环,从加载、评估到最后的持久化,每一步的编排顺序都一模一样。 虽然代码从 Node.js 换成了 Python,但这种底层的工程决策,比如原子写入、多维加权评分、约束门控模式,全都对上了号。 我把两者的核心概念做了一个对比,大家可以直观感受一下这种系统性的概念替换(见下图)。  最让我感到不平的是零归属。 Hermes 团队在文档里引用了学术界的论文,也提到了其他大厂的项目,但唯独对这个在架构上给他们提供无限灵感的独立开发者项目 Evolver 闭口不提。 这种换汤不换药的搬运,确实伤害了开源社区的根基。








