⏰ Claim closes 2:00AM, August 10 — don't miss it. In just 1 WEEK: 🔥 1,317,934 holding addresses — and counting 🔥 41,390 private batch transfers already executed 🔥 96,945 $MON gas cost 🔥 $0.00129 cost per private transfer Huge thanks to our community and @monad — none of this happens without you. The privacy era is just getting started. Don't be the one who watched from the sidelines. 🚀

对长鑫的阴谋论： PVP市场繁荣周期尾声， 往往有一种东西出来，把情绪留住， 它往往是 Top1 赛道的 Top1 新晋尖子生， 可以把这种东西叫做“掩护者”。 在 Crypto 里多次故技重施过。 如果不是2021年519前后的 Shib ， 如果不是2022年单边下跌前的 Nft 、Stepn (Gmt)， 就不会有那么多人， 在2022被套在整个公链赛道基本面叙事信仰里。 所以长鑫不是吸血其他这么简单， 它承担着“掩护者”的重任。 “初始低流通”可以让它短期（1～3个月）走势 更好地撑起整个家族的脸面， 同时撬动总股本市值的伟大、观念刷新， 达到“老乡别走”的效果。 就像店铺哪怕亏钱把一个头牌产品推成爆款， 为的是吸引流量维持其他商品的倾销。 但初始低流通伴随的中长期（3个月～1年+） 的代价是什么，对领先n个版本的Crypto玩家来说， 应该是再熟悉不过了。

📢 From Managed to Self-Hosted: Giving Node Data Ownership Back to Users Stash Cloud has always auto-backed up managed nodes. It’s a platform-side default: node data lands on independent storage on a regular schedule, so when a machine fails, a container crashes, or a mis-op corrupts data, we can restore the node to the latest usable state — usually without the user noticing. This layer is on by default; users don’t have to do anything. But that solves service availability, not ownership. Auto-backups live in the infrastructure provider’s storage, managed by the provider, restored when the provider decides. They stop most technical failures — except one: a user who wants to keep their own node data and run an RGB Lightning node without depending on any infrastructure provider. This blog covers our exploration and practice of moving RGB Lightning nodes from cloud-managed to self-hosted. 🔗

最近看到一些博主预测下轮牛市哪些板块会起飞，这些板块都是基于当下和过去的推演，历史无数次证明这种预测全是放屁的。举一个最简单的例子：hyperliquid hype 并不是 perp 的创新，dydx 早就有了，订单薄、自建链，hype与dydx的整体框架其实没有太大区别，dydx 没成功，就导致了很多人对hype的误判 一个赛道、一个项目的成败，真的真的很难预判，哪怕我当时预判对了hype的成功，那也是因为hyperliquid已经跑起来了，直接看数据就行了 这个市场，真的无需去预测，hype在空投之前很长的时间数据都非常扎眼，为啥没人关注，很大程度是因为当时行情不好，以及前车之鉴dydx的失败。甚至hype空投之后还没达到今天的高度，我听到最多的质疑就是：这不就是dydx吗 推翻质疑，很简单，自己去玩下就能得出完全不同的结论。任何周期性的赛道机会，给大家参与的时间窗口其实非常长，你需要摒弃一些外部的评价、过去的经验，去老老实实的用在产品，感受下社区，看下客观的产品数据 你会惊讶于，为啥大众如此的愚昧，如此的懒惰，也庆幸自己没有被偏见、成见遮蔽双眼，找到了一个大机会 大机会就是如此，无需你去提前预判，产品数据起来了，你直接老老实实的用、老老实实的看，甚至不用多大的本金，就能拿到你的大机会

Stash Labs Official Q&A on Recent Community Questions We've received feedback from many users about Stash Labs recently. Here is our unified response 👇 On Support for $RGB and Listing Plans: The Stash Labs team has been an early supporter and user of $RGB since day one. We have been deeply involved in large-scale mainnet testing of $RGB — so there is no doubt that $RGB will be the first token listed on both: ✅ AMM Swap (Powered by ✅ Order Book Spot Trading (Powered by Flash Dex) On the PUMP Model Design: The PUMP model is designed to solve the AMM liquidity cold-start problem. Without the PUMP mechanism, a token faces severe initial liquidity constraints. Providing RLSP liquidity requires users to hold both BTC and RGB tokens at the same time, which discourages early LP participation and makes traditional AMM hard to run effectively. This is also why the BTC ecosystem has historically preferred order-book trading, which has lower liquidity requirements. The model itself is neutral. What matters is using it correctly at the right time. Our measures: ✅ Open the PUMP model with conditions and limits — not a blind full rollout ✅ Continuously optimize related strategies based on community feedback Furthermore, PUMP is only one of the launch solutions we support. We already support multiple token launch mechanisms, including Fair Mint and Dutch Auction, and will keep introducing new launch models to bring more vitality to the ecosystem. On the Product Name: We don't believe a product should be judged as similar to another platform merely because the names look alike. Please remember: we have capabilities that other protocols do not. That said, given the volume of community feedback, the team has still made a courageous decision — we will rename the product. Stash Labs is a community-driven project. We are glad to listen to the community. Within the team's principles, maximizing the fulfillment of community needs is why this team exists. The new name is not yet finalized, so we are now open to community name suggestions! 🎁 Reward Details Users whose suggested name is officially adopted will receive 300 $RGB as an additional reward. ⚠️ This reward is stackable — users who have previously received any reward may still participate and win again. 📌 The final new name will be selected from comment submissions. If yours is not chosen, please don't be discouraged — we will launch more community reward events in the future! How to participate: Follow our official account first, then leave your name suggestion in the comments! 👇

RGB Swaps on Lightning — workflow and HTTP API now documented. This post describes the swap workflow and HTTP API that Control Panel exposes today, so third parties can integrate maker and taker flows, try them in a real environment, and send feedback. Build with us. Make Bitcoin Smart.

RGB Lightning Node v0.0.5 released. Docs updated — RGB asset transfer through intermediate routing nodes: → Highlights: - Improved the BTC Carrier configuration by automatically applying a default value.. - Added node status, with pause and start controls - Fixed an issue where the client’s BTC address changed unexpectedly - Fixed import and export issues between the client and Bitlight Wallet - Improved the Open Channel flow - Fixed a node crash when querying or exporting an unimported RGB contract. - Improved Hold Invoice payment status with HTLC lock detection and Payment Hash support. - Fixed an issue where RGB on-chain recipients could not retrieve the transaction ID (TXID). - Improved RGB UTXO confirmation height retrieval and query performance. Repos: → → → Make Bitcoin Smart.

Bitlight Labs publishes a complete disaster recovery solution for RGB assets on Lightning Network channels. The wire-level specification is formalized as bLIP-0072, complementing bLIP-0070. Standard Lightning channels already have a well-defined recovery path for BTC: recover from backup, sweep your funds on-chain using your seed. Solved. RGB assets in Lightning channels are a different problem. Allocations are client-side validated and stored locally—not on-chain. When a channel loses state, the RGB allocation cannot be reconstructed from chain data alone. It exists only in the counterparty's local stock. bLIP-0072 defines how to retrieve it. Make Bitcoin Smart.

The vote is in. Turnout: 66.95%. In favor: 100%. Both thresholds cleared (>50% turnout, ≥67% approval). The result: this Erling Haaland card is heading to auction on eBay. We'll post go-live details shortly.