ISTP, Otaku, Developer

localhost
Joined July 2022
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
Replying to @AlanShao111
❌薄肌俱乐部 ✅性压抑俱乐部
27
Replying to @polebug
恭喜!!
141
liqwang.eth retweeted
TanStack Start 1.0 is officially stable! 🎉 A full-stack web framework for React and Solid, already used to build millions of apps, from Fortune 500 companies to your favorite tools and weekend projects. tanstack.com/start
164
598
222
4,342
358,264
Replying to @aliez_ren
我操我操我操
201
安全下车 15寸MacBook Air M4 24G+512G 2026年生产的所以预装的macOS 26,手动刷回macOS 15了 参考:depp.wang/2026/m4-macbook-ai…
1
244
Replying to @Viem_viem
强强
1
134
Replying to @liujiayi1111
真正年入百万的00后一般不会告诉别人赚钱路子的
2
294
Replying to @L_eacc
以前扫描PDF用的Microsoft Lens,但是现在停用只能用OneDrive了
1
91
Replying to @Ehco1996
看成gta6了
68
回学校准备秋招啊,实习已经拿到转正了
1
1
122
Replying to @Labrin
牛逼,感谢开源
2
615
liqwang.eth retweeted
Weakness and ignorance are not barriers to survival. Arrogance is. @injective got hacked. I joined forces with @S7iter_ to analyze the attack. Injective binary options are zero-sum by design. Buy Q at price P and the long locks P * Q, the short locks (1 - P) * Q. Total collateral should stay equal to Q. This exploit breaks that invariant, then stops the normal refund haircut from putting it back. The break is how a binary options market is bound to its insurance fund. market_id was hashed from fields concatenated with no separator and no length prefix: oracleType, ticker, quoteDenom, oracleSymbol, oracleProvider. Same byte string, two different parses. Example: insurance fund uses ticker = X, quote = inj, oracle_base = USDC_DENOM + SYMBOL. Binary options market uses ticker = Xinj, quote = USDC_DENOM, oracle_symbol = SYMBOL. Different objects, same market_id. An INJ insurance fund can sit on a USDC-denominated binary options market. Attacker traded against themselves across subaccounts. 1) Open long + short at 0.10. Long locks 0.1Q, short locks 0.9Q. 2) Close the long at 0.90 with margin = 0. Gets ~0.9Q back (original margin + realized PnL). 3) Old short still has 0.9Q margin on the books. Open a new long at 0.90 with another 0.9Q. 4) Deposited 1.9Q total. Old long already took ~0.9Q out. Remaining positions still show 1.8Q refundable margin. 5) Market settles with no oracle price and hits the -1 refund path. Missing 0.8Q should haircut the leftover positions. Instead settlement tries to cover the hole from the attached insurance fund. 6) Fund is INJ. Deficit is USDC. Code treats the raw integer from the INJ fund as coverage for the USDC shortfall. Dust INJ is “enough”, haircut is skipped, remaining positions refund in full. 7) Withdraw the inflated subaccount balance. One sampled USDC cycle: 44,099.025531 in, 62,666.979111 out. Extra 18,567.953580 is exactly the 0.8Q gap. Same loop on short-lived markets quoted in USDC, Peggy USDT, Noble USDC, and ATOM. Create an INJ insurance fund that collides on market_id with a quote-denominated binary options market → 0.10 to 0.90 self-trades to manufacture a refund deficit → no-price settlement → INJ atoms cover a USDC/USDT/ATOM deficit by raw amount → withdraw. github.com/InjectiveFoundati… hi @al_f4lc0n 👀
I Saved Injective's $500M. They Pay Me $50K. I like hunting bugs on @immunefi . I'm decent at it. - #1 — Attackathon | Stacks - #2 — Attackathon | Stacks II - #1 — Attackathon | XRPL Lending Protocol - 1 Critical and 1 High from bug bounties (not counting this one) Life was good. Then I found a Critical vulnerability in @injective . This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk. I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity. Then — silence. For 3 months. No follow up. No technical discussion. Nothing. A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either. I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten. I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve. Full Technical Report: github.com/injective-wall-of…
3
11
3
110
16,622
艹,学到了
86
Replying to @S7iter_
牛逼😭
43
Replying to @__oQuery
相亲基本上是奔着结婚去的,如果目的是恋爱不适合相亲
1
279
这下不得不吃了
21
艹,学到了
1
34