ben 𐤊

Gate now supports @kasplex Layer 2 $KAS deposits & withdrawals! Access the Kasplex L2 ecosystem seamlessly — no bridges required. Faster, safer, smoother than ever! Explore now: gate.com/myaccount/fund… More details: gate.com/article/50787

#Kaspa 近期信息总结 #24节气 之 #惊蛰 26.02.18 - 26.03.05 1、算力方面：2月18号实时算力 411 PH/s，3月5号实时算力 414PH/s 2、币价方面：2月18号是0.032，3月5号是0.031，下跌3% 3、开发进度方面：预计26年完成2个硬分叉，cov++ 5月初，dk三季度末。

#Kaspa 近期信息总结 #24节气 之 #立春 26.01.20 - 26.02.04 1、算力方面：1月20号实时算力 466 PH/s，2月4号实时算力 443PH/s 2、币价方面：1月20号是0.042，2月4号是0.033，下跌22% 3、开发进度方面：dk、vprogs 等核心功能正在同步开发中

@kenracco stealth mode -> a final release.

@benrod3k what happened to pony alpha?

Pony Alpha 很好用啊 404 The Pony Alpha stealth model has sunsetted, and its identity will be revealed soon!

众所周知 404 Pony Alpha was a stealth model revealed on February 11th as an early testing version of GLM-5. Find it here: {{SITE_UR}}/z-ai/glm-5

#Kaspa 近期信息总结 #24节气 之 #大寒 25.01.05 - 26.01.20 1、算力方面：1月5号实时算力 441 PH/s，1月20号实时算力 466PH/s 2、币价方面：1月5号是0.05，1月20号是0.042，下跌16% 3、开发进度方面： “契约脚本”、vprogs等特性正在开发中

As many of you are likely aware, kas(.)fyi has been shut down. We would like to extend our sincere thanks to CryptoK for building and maintaining kas(.)fyi, as well as for his valuable contributions to the $KAS ecosystem, including coverage of KRC20 and Kasplex L2 data. Thanks to @supertypo_kas, the existing integrations and data from kas(.)fyi can be migrated to kaspa.stream. Please see Supertypo’s Discord message below for further details. "For krc20, a mixture of ecosystem tools should do the job, for integrators you can replace links: FROM: kas.fyi/address/ kas.fyi/transaction/ kas.fyi/token/krc20/ TO: kaspa.stream/addresses/ kaspa.stream/transactions/ kasbay.org/tools/tokens/ Additionally krc20 token icons are available here: api.kaspa.org/krc20/icons/.jpg"

I don’t see any problem with cryptok’s request, and no problem with the decline. Those are all legit negotiable numbers. Re some of the comments - It makes no sense to attack a brilliant volunteering contributor who built and maintained a beautiful platform with top-of-the-class ux, just bcs he decided to move on and has his principles/aspirations. --- Thx @cryptok777 for everything you have done for Kaspa and I genuinely hope you find the time and place to rejoin this ride, bcs I can promise you it will be there waiting for you when you do <3

Based on my understanding of @cryptok777 , he doesn't actually care about the 150,000, what he's really seeking is a sense of recognition and acknowledgment. After providing free services to the KASPA community for three years, some people in the community take it for granted that such contributions are expected, while others feel genuinely grateful. Over the past 18 months, KASPA has experienced a prolonged price downturn, leaving all KASPA holders with a sense of frustration and bitterness. Some individuals try to find emotional release in their own ways. There have been internal discussions within KEF about kas(.)fyi, but considering the accusatory voices in the community toward KEF - which might lead to perceptions of attempting to "cheaply" seize KASPA's infrastructure - and the fact that @cryptok777 needs a considerable period of time to rest and recover, as well as KEF's desire to support project development rather than dominate or own the project, these two factors combined led to the final decision to abandon the acquisition of kas(.)fyi. I hope that, due to the departure of kas(.)fyi, the KASPA community will reflect more deeply on the situation of a project's founder who, without complaint, silently supported the KASPA community for so long yet did not receive sufficient respect and recognition (if anyone disagrees, you can check the replies in Wolfie's post), and ultimately left due to disappointment. Everyone's contributions should not be taken for granted.

@jaygo_jiege 看到评测了，就想知道待机的功被耗在哪了，也许是灯

摩尔线程股票坑不了矿佬。他家三年前出的2999元的mtts80，待机功耗120w，注意是待机功耗，打游戏180w，比同时代的n家显卡整机正常运行功耗都大了。挖矿就更别想了。这种水平追赶个屁，70亿募集资金拿去理财合情合理啊！

sb 真的多😂

AutoGLM 智谱AI输入法 太丝滑了，工作效率翻倍，强烈推荐！autoglm.zhipuai.cn/autotyper 邀请码：SHHYNFXZ（注册咱俩都可获得积分哦）

best eco project ever

Heya. In some areas, you are correct, in some ...not quite. I can’t do an in-depth response to this post as it would require an even larger post :) So I’ll just focus on what I consider to be key elements. 1) vProgs paper is really just a set of guidelines. It has been reviewed in detail by me and the developers working with me. It has a number of issues, but nothing a team can’t solve within a day in front of the whiteboard. The key pillar (CDAG structure) is solid (but its implementation is very complex). 2) The way vProgs are designed is that they are basically the same as on-chain SCs. If properly done, the UX would be indistinguishable from traditional high-performance smart-contract-capable chains. (but vProgs bring numerous superior capabilities that TBH wipe the floor with all existing tech). 3) vProgs are absolutely possible and feasible - we have been doing R&D in this domain for 1.5 years now, and I have absolutely no red flags. 4) Adoption-wise, vProgs are just like any other SC system - all they need is a well-harmonized SDK with a bunch of primitives. I am trying to steer the design toward zkVM framework neutrality, which increases the project complexity, but for good reasons. 5) The economics of different system layers are actually well understood by some of the people involved. There is, however, no published material on the subject. Typically, this is addressed once you have a PoC. 6) There is a “one size fits all” solution, and that’s vProgs. It is important to understand that vProgs is a ZK composability layer that turns Kaspa from a global sequencer into a global ZK sequencer - without imposing any limitations or obstructing anything. 7) I have recently published a document called vProgs JAM SESSIONS on the TG R&D channel ( aspectron.org/docs/vprogs-ja… and aspectron.org/docs/EPA.pdf ). This document is meant as a "soft bridge" between the R&D performed by my team (Sparkle) and the Kaspa vProg research team. While the document identifies various subjects and poses suggestions, most of them are well understood and, in many cases, have been prototyped on our end ✨. So none of the questions you are raising (specifically) in relation to vProgs are my concern. The REAL problems are the team communication, project management, and the lack of a holistic software architecture (which I am attempting to solve). This is further aggravated by the lack of properly structured funding and ad-hoc attempts by different developers to tackle the challenge. There is currently “no one in charge”. There are a number of developers “developing”, but no one gave guidance with respect to what they should be developing. It is literally a group of construction workers making a building without any architectural plans. Build a sky-scraper, they said, …and everyone is trying to make one. The problem is the fact that the complexity of the project and layers involved are extremely multidisciplinary, and this is not something that a single developer can construct (neither, as a developer, would I be able to). In my recent comms with @michaelsuttonil I’ve stated that in fact the complexity of this is comparable to KIP-1. It’s a very large and complex project. However, if properly executed, with concise and _coordinated_ efforts, an MVP can be achieved within 6-8 months. (note "coordinated" being bold, italics, and underlined). I am currently trying to steer @hashdag toward a proper project execution structure based on the clearly defined architecture. I have huge respect toward @michaelsuttonil, @hus_qy, @FreshAir08, @Max143672, and everyone else working on this, so I can’t just “barge in” and start telling everyone what to do. I can guide and coordinate everyone, but only if they align behind the effort and adopt the architecture I am proposing. So, at this point, I have helped the team to identify key stress points and problems related to ZK (that took us months to understand), and gave a tentative architectural blueprint to the team that is meant to envelop the vProgs Yellow Paper design. I have suggested to @hashdag that we schedule a few weeks of in-person R&D meetings in front of a whiteboard to solidify the architecture, understand everyone’s proficiencies, understand what code and subsystems already exist and can be reused …and execute.

Update : #LehmanBush is likely a scam. The Kaspa Chinese Community visited their Shenzhen office and found it to be an empty room—no people, no logo, nothing. Please be on high alert. #kaspa #kas $kas

Kaspa 社群又完成了一次具有里程碑意義的實證。 一位開發者將 Kaspa 完整節點功能封裝為 MCP（Model Context Protocol）伺服器，使 Claude 等大型語言模型能夠直接調用 Kaspa 原生操作：查詢餘額、構建交易、簽名並廣播。整個過程無需人類介入，交易手續費僅 0.00002 KAS，數百毫秒內最終確認。 這不僅是一次技術展示，更是對「AI Agent Economy 最終結算層」這一論斷最直接的驗證。當數以億計的 AI 代理開始互相委託任務、即時結算報酬時，它們需要的是： - 高達萬級 TPS 的真實吞吐 - 毫秒級最終性 - 近乎零的邊際成本 - 完全去信任的底層協議 Kaspa 是目前唯一同時滿足以上全部條件的 Layer 1。 今天，一個 AI 能夠自主支付另一個 AI。 明天，數百萬個 AI 將在 Kaspa 上形成自我維持的經濟網絡：發任務、競標、交付、結算，全程鏈上自動執行。 我們從 2022 年就看懂了這張圖紙。 沒有預挖、沒有機構輪、沒有內部份額， 只有公開、公平、純粹由社群推動的技術與共識。 歷史再次證明：最顛覆性的基礎設施，往往誕生於最純粹的去中心化土壤。 Kaspa 已經準備好了。 未來正在鏈上運行。 $KAS We were early. Now we are on time. #Kaspa #AIAgents #Layer1

#Kaspa 近期信息总结 #24节气 之 #大雪 25.11.22 - 25.12.07 1、算力方面：11月22号实时算力 625 PH/s，12月07号实时算力600PH/s 2、币价方面：11月22号是0.038，12月7号是0.051，上涨34% 3、开发进度方面：明晚8点，有关于Yonatan伦敦演讲的探讨，有空的朋友可以去听。

中文社区的 #kaspa 兄弟们不要错过 😇😇😇 @oneforonehaha 也会加入！

上个月终于做到了用 Git 管理矿机脚本，跳板机装了 happy，从手机控制几个长工没日没夜的干活。只要代码有任何更新自动拉取，并自动重启相应服务，例如主、CPU、GPU 或者节点之类。终于可以摆脱 HiveOS 的各种版本限制，且能第一时间更新挖矿程序，很稳。