小冷

唱的是小冷最喜欢的 #あくあ色ぱれっと Singing my favorite song, Aqua Color Palette bilibili.com/video/BV1TY4y1… 当年小冷在学校的毕业演出～因为喜欢所以再发一遍！ This was my graduation performance back in school~ Posting it again because I like it so much!

@ah230891 It might be because Re7 Capital / Re7 Labs did not even ask Binance to do so. As far as we could see, the only thing Re7 attempted to do might be to cover things up.

以下是Re7管理的Euler金库的链上合约分析 The following is an on-chain contract analysis of the Euler vaults managed by Re7 分析表明USDX的预言机价格存在故意操纵 The analysis shows that the USDX oracle price is subject to deliberate manipulation 问题复现 / Reproducing the Issue: 在Euler上复制USDX的预言机地址 On Euler, copy the USDX oracle address: 0x119a51c9d585e9613a48932772E3Dbbc0113Cf65 打开bscscan，输入上述地址查看合约 你会马上发现: Open BscScan, paste the address, and inspect the contract. You will immediately observe that: 它不读取任何市场真实价格,只做无意义的数据混淆,再把混淆后的值作为Euler 的 USDX 价格 The contract does not read any real market price. It only performs meaningless data obfuscation and then uses the obfuscated output as the USDX price on Euler 具体步骤 / Step-by-step Breakdown: 1. aggregator → 入口函数，调用多个 fundamental feed 理应该提供“真实价格”，实际不提供任何价格 The entry function calls multiple fundamental feeds. In theory, this layer should provide a real market price. In practice, it provides no market price at all 2. fundamental feed → 写入者随便写的uint256 值 The value is an arbitrary uint256 written by the feed operator 3. uint256 哈希 → 输入的是随机数 输出的自然还是随机数 The output remains a deterministic but economically meaningless number 4. 20 个与 USDX 市场价格无直接映射关系的固定输入数组→ Fixed input arrays with no USDX price mapping→ 先给20个数组起个名字，就叫： Twenty fixed input arrays are introduced, given names such as: wstETH， SolVBTC，USD1，WLFI 名字是随便起的，看上去在调用币价，实则改名为FlexYangDLLM也不会有任何变化，都是固定数组，每次输出都一样 These names are cosmetic only. Renaming them to FlexYangDLLM would not change the result in any way 结果是奇数？取总和中间值 If the count is odd → take the median 结果是偶数？取中间两个值，加起来除以2 If the count is even → average the two middle values 5. 数组输出再哈希 → Re-hashing the array output → 上一步的返回值uint256哈希一下 和第3步一模一样 无任何可验证市场锚点的数值输出 The output from the previous step is hashed again, producing a deterministic value with no verifiable market anchor 6. pickMedian() → 把所有数字排序之后: All values are sorted: 是偶数？取中位两值平均 If the count is even → average the two middle values 是奇数？取中位数 If the count is odd → take the median 7. 送入 USDX oracle (Re7 vault)→ Fed into the USDX oracle (Re7 vault)→ Re7 在未验证其价格是否具备市场代表性的情况下直接采用该预言机，当做Euler上的USDX价格 Re7 adopted this oracle directly as the USDX price on Euler without verifying whether the price has any market representativeness 混淆亮点：拖无关的币安下水： 币安hotwallet16有USDX充值提款=此合约被执行=更新Euler 预言机价格 Key Obfuscation Mechanism: Dragging Binance into the Narrative Whenever Binance Hot Wallet 16 performs USDX deposits or withdrawals, this contract is triggered, updating the Euler oracle price 散户一看有binance hotwallet？口号先喊：抄斩币安，刀砍CZ As a result: Slogans shift to “go after Binance” or “attack CZ” 维权群被绕成团，无法聚焦真正的攻击者 攻击者（Stables Labs）获得逃离窗口 Victim groups become disorganized Attention drifts away from the actual attacker This confusion creates an escape window for the real actor: Stable Labs 即使小冷和James是天才能在数天内做好逆向工程 Even if analysts like James and I can reverse-engineer the system in a few days, 但凡再多喊几句 绝对得先花半个月处理混乱 any additional noise would easily consume weeks of collective effort dealing with confusion 散户越乱喊，越掩护攻击者 The more retail users argue among themselves, the better the real attacker is shielded Stable Labs利用这套设计，利用散户在维权群里互相乱骂，互相误导，藏身自己于混乱背后 Stable Labs exploits this design to hide behind chaos, allowing victims to mislead and attack each other while the real responsibility remains obscured 参考：链上论证（PDF） Reference: On-chain Evidence PDF 🔗 xln.moe/dl/Re7_RedSton…

@skura_ku 夏奇拉

@skura_ku @willa_citrus

A manager who was made the scapegoat?

Your cutest idol Xiaoleng doesn’t flinch at any threat, not now, not ever. 😏😇

OMFG still pretending?? 😑

Re7 is posting weekly reports like nothing happened while their users still can't withdraw and are asked to submit passports + apology letters.

@ZhaoSam11 官方认证🤭所以你身份证呢🤣

@xia0leng 厉害👍

Re7拿了你的钱 还要让你发身份证，写道歉信😅😆 Re7 is demanding users' ID and a formal apology letter😅😆 媒体和KOL看过来 这已经不是项目事故 是离谱币圈小剧场😏🔥🔥🔥 Media and KOLs, take a isn't a protocol incident anymore, it's a full-blown absurd crypto drama😏🔥🔥🔥

@changq1ng 来来来 身份证交出来😆

@xia0leng 倒反天罡😅😅

@ah230891 Hand over your asset!

@xia0leng True face of Re7

@JohnJianggg 哥你怕国际刑警不😆

@xia0leng 让人们看看re7是如何对待客户的！

@ProDevEth Bro u dare against INTERPOL?🤣

@xia0leng What a disgrace, who do they think they are?

@johntravolta317 Hey bro r u ready to face arrest by INTERPOL? 🤣

@xia0leng INTERPOL .. lol 😂

律师函全文链接（PDF原件） / Full letter (official PDF): xln.moe/dl/2025-11-27-…

Re7律师函重点: Re7's legal letter - key content: 道歉信交给 Re7 审核(9.2) → apology letter for Re7 to approve(9.2) 上交设备、包括钱包(9.3) → hand over all devices - even crypto wallet(9.3) 上交姓名、住址、朋友名单(9.4) → disclose name, address, and collaborators list(9.4)

3. Legal Posturing Instead of Progress The emphasis on law firms and “investigations” provides authority and buys time, but lacks concrete steps, timelines, or verifiable on-chain evidence—indicating the focus is on optics rather than actual recovery.

2. Shift the Narrative By framing Stream Finance and Stables Labs as the primary cause and positioning themselves as “one of the victims,” they are building a future liability-shielding narrative.

Re7’s current strategy can be summarized in three points: 1. Delay and Dilute They repeat the same message across multiple posts with no new information, aiming to slow down community pressure and create the appearance of “ongoing action.”