Starknet空投在即?提及STRK的v0.13.0升级到底要做什么?

Odaily星球日报Publicado a 2023-11-13Actualizado a 2023-11-13

Resumen

调整Starknet交易内部结构,支持添加STRK为费用代币。

原创 | Odaily星球日报

作者 | Azuma

Starknet空投在即?提及STRK的v0.13.0升级到底要做什么?

11 月 12 日晚,Starknet 关于 v0.13.0 版本的升级公告在社区内引发了广泛讨论,原因在于该升级内容内明确提及了 Starknet 已生成但尚未流通的 STRK 代币(暂时仅通过少数委托代表发挥治理效用),因此该公告也被许多社区成员解读为 Starknet 即将进行 STRK 的正式分发,包括对社区进行大规模空投。

那么,昨晚的升级公告到底说了些什么呢?让我们回到原文去具体了解一番。

Starknet空投在即?提及STRK的v0.13.0升级到底要做什么?

由上图可见,昨晚 Starknet 社区论坛内的这起公告主要涉及到了对 v0.12.3 和 v0.13.0 两个版本的具体规划,抛开作为小版本优化的 v0.12.3 版本不提,让我们把目光聚焦在 v0.13.0 大版本升级之上。

简单来说,v0.13.0 升级的主要内容是新交易类型 V3, 这是关于 Starknet 交易内部结构的一次迭代,其目的是为了让 Starknet 网络能够支持未来的一些功能升级,从而允许应用层进行更复杂的构建。

  • 比如 V3 将激活费用市场(Fee market),你可以简单将其理解为 Starknet 未来也会有类似以太坊主网的费用竞价机制,网络拥堵时价高者先行;

  • 再比如 V3 将激活支付管理器(Paymaster ),你可以简单将其理解为一个更灵活的费用支付机制,允许交易发送方之外的的第三方进行费用支付;

  • 而关于 STRK 的描述其实仅有一句,原文是这么说的:“v0.13.0 将引入一种全新的交易类型 V3,该交易类型旨在为实现 Straknet 未来路线图上的部分功能奠定基础,包括在 ETH 之外添加 STRK 作为新的费用代币……”

虽然描述仅有只言片语,但从公告的引申资料中,我们却可以获悉关于添加 STRK 作为费用代币的更多细节。

10 月 23 日,Starkware(Starknet 开发团队)的产品经理 Ohad Barta 曾在社区治理论坛内提交过一份关于此议案的讨论贴

Starknet空投在即?提及STRK的v0.13.0升级到底要做什么?

Ohad 在贴内附录了一份他与另一位 Starkware 产品经理 Evyatar Oster 共同编写的 Github 资料,其内详述了添加 STRK 作为新的费用代币所需进行的协议及 API 更新。从该资料内,我们大致可以获悉以下信息:

Starknet空投在即?提及STRK的v0.13.0升级到底要做什么?

  1. 添加 STRK 作为新费用代币需要通过新的费用类型 V3 实现,但旧的交易类型同时也会共存,从而保持 ETH 继续作为费用代币的效用

  2. 使用 STRK 进行费用支付,需要依赖预言机提供 STRK <> ETH 的实时喂价,短期内 Starknet 将采用偏中心化的 Pragma 预言机作为临时方案,长期的去中心化方案则需要通过未来的治理实现。

  3. 由于在费用收取环节引入 STRK <> ETH 兑换,因此可能会招来潜在的汇率攻击,但 Starkware 方面评估认为排序器和用户所面临的潜在损失均较小,而攻击所需要的成本理论上则相当大。

总而言之,从这份发布于三周前的资料中可以看出,Starknet 很早之前就已对添加 STRK 作为费用代币进行过规划,且已整理好了潜在改动所需统一的具体规格。

而昨晚 v0.13.0 升级公告的实际意义则在于,明确了此项升级的具体时间安排 —— 2024 年 1 月 22 日进行主网启动投票。

Starknet空投在即?提及STRK的v0.13.0升级到底要做什么?

然而,这也并不能解读为 Starknet 将会在明年 1 月 22 日前大规模分发 STRK,因为公告仅仅提及了“V3 将是添加 STRK 作为费用代币的基础”,可推导出的结论仅有“先引入 V3,再激活 STRK 作为费用代币”,至于是在此之前还是之后分发 STRK 则并未提及,所以将此作为“Starknet 即将空投”的直接依据并不合理。

不过从相对意义上来看,v0.13.0 的落地确实可解读为 Starknet 正在逐步推进其路线图规划,这或许也可以理解为我们距离 STRK 的大规模分发(包括空投)正在越来越近吧。 

Lecturas Relacionadas

U.S. Government Bans Foreign Nationals from Using Fable 5, Anthropic Issues Rebuttal

U.S. Government Bans Foreign Access to Fable 5, Anthropic Issues Rebuttal On June 12th, the U.S. government ordered AI company Anthropic to immediately suspend all foreign access—including foreign nationals within the U.S. and Anthropic's own foreign employees—to its newly released Fable 5 and Mythos 5 AI models, citing national security concerns. This forced Anthropic to temporarily disable access to both models for all users globally, as it cannot technically differentiate user nationality at scale. The models, released just three days prior, represent Anthropic's highest public capability tier. Fable 5 is the first publicly available model from the advanced "Mythos" family, while Mythos 5 is a less-restricted version for approved cybersecurity and critical infrastructure partners. The government's directive was reportedly triggered by claims from another company that it could "jailbreak" Mythos 5, raising alarm within the Trump administration. Anthropic, in a detailed public statement, strongly challenged this rationale. The company argues the demonstrated "jailbreak" is a narrow, non-generalized technique that merely involves identifying minor, known software vulnerabilities—a capability common to other publicly available models like OpenAI's GPT-5.5 and routinely used by cybersecurity defenders. Anthropic stated it has complied with the order but disagrees with the government's standard, warning that applying it industry-wide would halt all new frontier model deployments. The company criticized the lack of a transparent, fact-based legal process and expressed confidence the situation stems from a misunderstanding. It is working to restore access and will release more technical details within 24 hours. Other Anthropic models remain unaffected.

链捕手Hace 9 min(s)

U.S. Government Bans Foreign Nationals from Using Fable 5, Anthropic Issues Rebuttal

链捕手Hace 9 min(s)

The Revelation from the Raydium Theft Incident: New DeFi Vulnerabilities Lurking in Forgotten Old Contracts

**Raydium Exploit Reveals DeFi's Hidden Risk: Forgotten "Zombie" Contracts** A recent attack on Raydium's deprecated V3 AMM pools resulted in a loss of approximately $1.34 million. The hacker exploited pools that were no longer supported by Raydium's current UI or SDK but remained fully functional and accessible on-chain. This incident highlights a critical, often overlooked category of risk in DeFi: inactive or legacy smart contracts that projects fail to properly decommission. Since March 2025, there have been at least 8 publicly reported attacks targeting such abandoned contracts, with total losses around $10.8 million. Including older pools and deprecated features, the count rises to 10 incidents with roughly $22.5 million in losses. These "zombie contracts" represent a lifecycle management failure rather than a code vulnerability, yet they are typically misclassified under general "code bug" categories in security reports, masking the true scale of the problem. The root cause is that projects often merely document a contract as "deprecated" without taking essential technical steps to secure it: withdrawing remaining assets, disabling external call functions, and implementing ongoing monitoring. These forgotten, under-monitored components become prime targets for attackers. To address this, the industry needs to recognize "zombie contracts" as a distinct risk category and establish standardized decommissioning protocols. Essential steps should include: 1) a formal retirement announcement, 2) removal of all front-end integrations, 3) withdrawal of locked assets, 4) disabling key contract functions, 5) ongoing security monitoring, 6) clear user communication, and 7) a post-mortem analysis. The value of a DeFi project lies not only in its current TVL but also in the security of its historical codebase, which has now become a new attack surface.

Foresight NewsHace 1 hora(s)

The Revelation from the Raydium Theft Incident: New DeFi Vulnerabilities Lurking in Forgotten Old Contracts

Foresight NewsHace 1 hora(s)

Robots Begin to 'Consume Data': The Hidden Production Chain from Indian Data Factories to Billion-Dollar Humanoid Robots

Robots have started to 'consume data,' driving the formation of a new industrial supply chain focused on producing training data for embodied AI. Unlike large language models, which are trained on vast internet text corpora, embodied AI models face a 'data desert' in the physical world. This has created a massive demand for first-person perspective video data (Ego Data), captured by workers wearing cameras in places like Indian garment factories. Companies like Neocambrian AI are establishing 'data factories' where workers perform standardized tasks (e.g., sorting clothes, kitchen organization) to generate thousands of hours of video. Research, such as NVIDIA's EgoScale, demonstrates that scaling this human demonstration data predictably improves robot performance, particularly for dexterous manipulation. This has validated a training path combining large-scale human data for pre-training with smaller amounts of robot-specific data for fine-tuning. The value of different data types varies significantly, forming a 'data pyramid.' The base consists of low-cost, large-scale internet and Ego Data. Higher layers include more expensive motion-capture data (e.g., from data gloves), simulation/synthetic data, and the most costly and scarce layer: real robot teleoperation data. This demand has spawned a layered ecosystem of data suppliers: low-cost data factories, motion capture and alignment specialists, robot-native teleoperation service providers, simulation data companies, and platforms aiming for data standardization. Robot companies themselves are adopting a 'layered procurement' strategy: outsourcing generic Ego Data while building in-house capabilities for robot-specific adaptation data and the critical deployment/failure data generated in real-world applications. The industry is shifting focus from hardware and basic mobility to the data pipelines required for general-purpose capability. While parallels exist to data labeling companies like Scale AI in the LLM boom, the physical complexity of robot data—involving action success ambiguity and sim-to-real gaps—requires more integrated solutions for data collection, annotation, and a continuous feedback loop. The race is on to build the data engines that will teach robots to operate reliably in the unstructured real world.

marsbitHace 4 hora(s)

Robots Begin to 'Consume Data': The Hidden Production Chain from Indian Data Factories to Billion-Dollar Humanoid Robots

marsbitHace 4 hora(s)

Trading

Spot
Futuros
活动图片