k:Kit (e/acc)

📝 GAME | ZKPCP | MARL | OmniVerse 🔮 Wizard @RootDataCrypto @CatcherVC 🌎 $Gundam ified PFP

[k:Kit (e/acc) @bamboobee5]

@grvt_io working ways to save both crypto newbies and crypto naive to avoid another disaster of #CEX by insuring “abosolute withdrawals ” rights, and leveraging #ZK #Validum & Faster Statements finalization on #Layer1.
✍🏻

[CatcherVC @CatcherVC]

🚀 Discover the Future of Crypto Trading! 🌐🔒

Learn how @grvt_io #hybridexchange utilizes #ZKrollup technology #Validium to deliver a trustworthy and lightning-fast trading experience for cross-hedging options + perpetual contracts. 💪✨

READ HERE 🔽
https://t.co/g2FNyHoZXU

[k:Kit (e/acc) @bamboobee5]

@SuhailKakar Rust SDK no longer maintain?

[k:Kit (e/acc) @bamboobee5]

@hylarucoder @toooo_moon 4.6 满血版感觉就是现在内测的mythos很明显，之后降了10倍不止

[k:Kit (e/acc) @bamboobee5]

@oran_ge opus4.6满血版> 4.8>4.7，关键是这算力和模型到底为什么被砍，无从得知

[k:Kit (e/acc) @bamboobee5]

个人觉得短期内加密应该会反弹，$spcx SpaceX IPO最利好的除了加密货币，我想不到是什么了，毕竟芯片开始被SpaceX吸血，连美国养老金都必须开始配置SpaceX

[k:Kit (e/acc) @bamboobee5]

@willo2_Poly Let me in the group, I am in YES side as well

[0xDinosaur @0xDinoCrypto]

I’m 20 years old, still a university student.

Before this dispute, I was one of the top 10 YES holders in the Polymarket MicroStrategy market. I lost around 35,000 USDC because I trusted the written rule.

The rule said YES if MicroStrategy sold Bitcoin by May 31.

It did not say the sale had to be publicly disclosed by May 31.

That is the whole issue.

If you want to help:

Repost this.
Tag a journalist.
Tag a lawyer.
Send this to a crypto researcher.
Submit your case if you were affected.

https://t.co/pmXUtr9jFD

Silence is what platforms count on.

Don’t give them that.

[k:Kit (e/acc) @bamboobee5]

Watching Binance and all CEXs listing #stocks being play by the 50+ years of hardware competition by Tradfi, #CT being eaten alive with no bones left 🤣 @cryptomanran

[k:Kit (e/acc) @bamboobee5]

5个月后，交易所开始全面拥抱自己杀鸡取卵的后果，去跟人家IBKR和顶级做市商做布局了几十年的军备竞赛，全面加速抛弃链上和去中心化，自作自受

[k:Kit (e/acc) @bamboobee5]

There will be compensation if they trying to be list on NASDAQ

[willo2 @willo2_Poly]

Here's my honest opinion on the MSTR market resolution.

It will close NO.

This is because UMA is forced to respect the rules as written by Polymarket. Polymarket changed the rules, and now the outcome is literally in the rules.

Even if UMA voters think that this outcome is ridiculous... they are forced to ratify it. They must abide by the rules that Polymarket wrote.

So really... in 5 hours, we simply receive confirmation that UMA is forced to follow centralized Polymarket decisionmaking. Polymarket can change the rules, at any time, for any reason, and UMA are forced to respect it. No voting needed.

So is UMA really that independent? Does UMA hold any power whatsoever? Not really. It's puppet decentralization so that Polymarket can shift dispute blame onto a separate entity.

This market most likely closes NO in 5 hours. But that doesn't change anything.

The scam already occurred. Clearly, the way that this gets solved will not be through Polymarket's internal processes. So let's take it to the next level.

In my opinion, Polymarket made a massive mistake here by changing the rules so brazenly. They fucked up... BAD.

If you're going to rely on a system that offloads dispute blame to another entity, you shouldn't take it upon yourself to cut that entity out of the resolution process. Now, the blame falls entirely on Polymarket's shoulders. This really isn't a difficult argument to make.

Any rational individual who looks at this market can conclude that Polymarket themselves now have the responsibility of this market's resolution. Big mistake, and that's what makes this case very different from prior UMA voting disputes. You can't hide behind UMA now.

Polymarket markets are resolved according to a set of pre-defined and stated rules. Polymarket themselves modified these market rules. The clarification materially changed the conditions for a Yes outcome after trading had already occurred.

Polymarket's own documentation says clarifications "cannot change the fundamental intent of the question."

Clearly, this one did.

Polymarket, your time is running out.

[k:Kit (e/acc) @bamboobee5]

5个月后，交易所开始全面拥抱自己杀鸡取卵的后果，去跟人家IBKR和顶级做市商做布局了几十年的军备竞赛，全面加速抛弃链上和去中心化，自作自受

[k:Kit (e/acc) @bamboobee5]

Told you so, 知道什么是连带效应和吸血效应了，1011出来骂爆仓的是仓位管理问题的人，没想到回旋镖是3个月后整个加密流动性榨干，被黄金/白银按在地上摩擦

[k:Kit (e/acc) @bamboobee5]

exactly~

[kaulboy @kaulboy]

.@shayne_coplan @Polymarket

$74M of volume handed to ten wallets who treat your oracle like their personal fleshlight

your "mstr-sold-btc-by-may-31" market is resolving NO.

the 8-K filed june 1 confirms mstr sold 32 btc between may 26-31. on-chain shows ~411 btc moved to coinbase prime on may 29, first outflow in 3.5 years per @arkham. june 30 and december 31 sub-markets both at 100% YES because the sale fucking happened in the window

your rules name three resolution sources: MSTR filings, on-chain data, consensus reporting. all three confirm sale in window. resolving NO requires every voter to check which way the whales pissed and aim the same direction

then you dropped a banner saying "confirmation achieved outside of the market's time frame does not qualify" and quietly rewrote the question from "did mstr sell btc by may 31" to "did a press release land by may 31." you ran the first one for 35 days, ate $74M of volume on it, and resolved the second one. clarification dragged wherever the bag needed it to go

mstr files weekly on mondays. every trader bidding YES knew the 8K was coming. smart money front ran the disclosure exactly as the rules were written. then a discord circle jerk of UMA bagholders reframed event timing as announcement timing mid dispute, and every voter who could read the room said yes sir to avoid getting slashed

easy fix: when primary resolution source confirms event in window, market resolves on the event. if you want announcement timing markets, write the fucking words "publicly confirmed by [deadline]" into the rules. you override sports payouts when umpires fuck up. all it takes is a junior engineer and a weekend to ship the same logic. you have a bunch of UMA whales on speed dial and shipping the fix means admitting that out loud

ngmi

[k:Kit (e/acc) @bamboobee5]

https://t.co/tGZP4VNl7S

There is no discussion of whether it was annouce or not, it was onchain for MicroStrategy that actually sold 6 days ago, and only being annouced later. It is whether facts or annoucement for @PolymarketTrade @PolymarketDevs @Polymarket

[Tyche @TycheTerminal]

🚨 A 500x return or a $52M Rug Pull? The Polymarket MicroStrategy Dispute.

Look at the screenshot. On May 31, the market was 99.9% certain MicroStrategy didn't sell any Bitcoin. The "Yes" shares were trading at 0.2¢.

Then, on June 1, an SEC filing dropped: they actually sold 32 BTC last week.

Now, a $52,665,828 market is stuck "In Review".

"Yes" buyers bought the ultimate bottom and are demanding resolution based on the actual sale date.

"No" buyers argue the public didn't know until after the deadline.

Prediction markets aren't just about being right. They're about knowing exactly how the Oracle interprets the rules.

[Lea @Lea_EFC]

Arsenal fans at full time:

[Grvt @grvt_io]

Every major asset issuer is onchain. BlackRock, Apollo, Janus Henderson. $24B in tokenized RWAs on Ethereum and counting.

The supply is here. What's been missing is a platform that makes it composable, liquid, and most importantly - accessible.

That's the wealth layer we're building, and here's the quick preview.

@hong_grvt explains exactly what that means, and why we built it this way. 👇

[k:Kit (e/acc) @bamboobee5]

@tomo_trader @ClaudeDevs notice that as well, invoke tool call, have to ask him to explicitly use tool no <invoke>

[k:Kit (e/acc) @bamboobee5]

@liamzebedee About to become history

[Samuel Tinnerholm @SamTinnerholm]

Remember when we dropped the full Polymarket order book archive? 30M+ rows per hourly dump, raw parquet files, everyone loved it

The problem: you had to download 500MB-1GB parquet files, write your own parser, reconstruct the book yourself from tick deltas

That's over. You can now query historical order books directly from the API. 4 lines of Python. 🧵

[思维怪怪 @0xLogicrw]

OpenAI 后训练核心成员翁家翌之前证明了「纯靠大模型写代码能通关 Atari 游戏」，流体动力学博士生 Paul Garnier 现在把这套方法搬进了更硬核的流体力学控制。

他全程没训练任何神经网络。单纯让 Codex 5.5 充当程序员，靠读取仿真的测试得分与诊断日志，自己查错并反复改写 Python 脚本。在这场工业脚本测试中，Codex 5.5 压过了 Claude Opus 4.7 与 Gemini 3 Pro，硬是在超半数的物理场景里把顶级的强化学习（DRL）基线挑落马下。

给汽车减阻、安抚管道湍流，工业界以前只能靠砸算力，硬喂出一个看不懂的黑盒模型去控制气流阀门。 Codex 避开了这条死胡同。它写出来的规则极其直白，例如「当局部曲率过大时，延迟喷气」。几十行带着物理常识的短代码，直接替代了神经网络无脑的暴力试错。

把黑盒换成代码，干掉了神经网络僵化、一碰就碎的死穴。 以前只要硬件稍微改动（比如控制喷嘴从 5 个换成 10 个），旧模型当场报废，必须重新烧钱训练。现在只要在代码里改个常数，系统瞬间就能对接新设备。

当测试时间被强行拉长四倍时，走出经验区的传统 DRL 模型全盘崩溃；但大模型写的代码由于直接遵循了物理逻辑，始终运转稳定。跑通这一整套控制策略，大模型只消耗了 2125 万 Token，总花费不到 14 美元。

[k:Kit (e/acc) @bamboobee5]

@indigox @xiashan3 难以置信，以这个电力和水力供应难

[RootData | We're Hiring @RootDataCrypto]

Binance Alpha Deepens Integration with RootData to Boost Project Transparency

@binance has now embedded RootData's team information across all 400+ Binance Alpha tokens, including roles, social links, X follower counts, and influence scores. This gives users clearer insight into project backgrounds and their industry influence, helping them make more informed investment decisions.
Through this collaboration, Binance and RootData are working together to significantly raise transparency standards across the crypto industry, turning team background from a major "black box" into verifiable data and better protecting users.

🔸Full article:
https://t.co/C8xrWaV8pq

[k:Kit (e/acc) @bamboobee5]

继续去思考人机交互：
1/LLM Fire Too Fast
2/Human Review/Understand Too Slow
3/Web UI如何跟上LLM越来越恐怖的记忆和TPS呢

[k:Kit (e/acc) @bamboobee5]

人机交互mardown已经成了我和ai的桥梁，接下来不知道有什么能解决人机交互上，人类大脑上下文和记忆跟不上1M 上下文的办法。 人脑已经太笨了，成了大参模型的瓶颈，人脑和手指的tps，也跟不上context的增长