BenCrox ⌚️ SHOWTIME_WATCH 🇭🇰 🌅 🛠️

@xuanotw @Nohomework0 甚麼叫五六年前不至這樣⋯廿年前已經是這樣

@Nohomework0 五六年前还不至于这样。。

路人：香港留学性价比很高啊，尤其phd，一个月1.8万工资，宿舍也便宜一个月才2千。怎么说都是赚爆吧 实际读过的人（我）：香港留学卷上天，看似境外读书实则周围都大陆卷王。PhD奖学金水分很深，有很多学校出一部分导师出一部分的，这种等着横向干到爆吧。一个月工资一万8义务带课监考。学校宿舍（1/2

不在阿布扎比现场？ 没关系！ 收看 Breakpoint 直播，一网打尽全部最新现场信息！

@LordLochFergus @kevinkfyam Everyone is committed and doing their best, until such lackeys purge us for their own photo ops.

@kevinkfyam Can we like, find and care for the people first? Before we start doing the whole "the government is evil" thing?

Narratives of this (now) ongoing incident is running hot on Chinese language Facebook. It reflects a number of things: 1. The Hong Kong public does NOT trust its Government and its lackeys with supplies that are intended for victims. It reflects the fact that the years of distrust which culminated in the 2019 protests has not gone away despite 5 years of national security crackdown, media censorship and constant pro-Government propaganda. 2. The Hong Kong Government and its lackeys are not acting in good faith. If this was merely a case of them believing that they have the resources and logistics to do things on a larger scale and more efficiently, they could have chosen to work with the citizen-led cohorts of volunteers, rather than reporting the volunteers to the police for unlawful assembly. At best this is an act of revenge for Government lackeys having been shown up in the last day or so for being only interested in photo opportunities for performative purposes rather than actually helping victims. At worst this is yet another sign of the Government and its lackeys treating civic-minded ordinary Hong Kong people as enemies. 3. These moves to monopolise the narrative and the audio visuals (let’s face it these lackeys aren’t really into helping people) is yet another reminder for ordinary Hong Kong people that their city is now subject to Mainland Chinese official malpractice in the aftermath of disasters (ie all political and PR show all about self-benefit no real assistance to victims). In other words, even in times of disaster and grief, it is now made known to Hong Kong people in no uncertain terms than they are now subject to a bad faith colonial master.

today, Solana changes forever we've solved the biggest data/RPC problem that exists solana historical/archival data — has now been redesigned quick context: today when you query historical data (getBlock/getTransaction/getSignaturesForAddress), it hits Google BigTable this is i) slow, ii) expensive, iii) inflexible for queries e.g., you physically can not get the first tx for a Solana address without looping back endlessly from the latest tx for busy addresses, this can take thousands of RPC calls — extremely slow, expensive, and annoying also, imagine you wanted to get the most recent 100 txs for an address, how do you do it? you first hit getSignaturesForAddress to get all the tx signatures and then call getTransaction on each tx to get its details — this can take 1,001 RPC calls in the worst case not anymore we have built a new distributed archival storage system that is 1,000x faster, more flexible, and more scalable the best part? we're introducing a new API method: getTransactionsForAddress with this method, you can now: i) combine getSignaturesForAddress and getTransaction calls into just 1 call instead of 1,000 ii) you can search in reverse order without needing to traverse iii) you can search historical transactions by time and slot ranges (e.g. get me all the txns from January 5th, 2025 until February 5th, 2025) what's more: - getBlock calls are now 10x faster - getTransaction calls are now 10x faster - getSignaturesForAddress calls are now 10x faster 10x lower latency, 100x fewer RPC calls, and 1000x less code enjoy! docs below

@demonoidzz 🥶

RT @Solana_zh: 👨‍💻熟悉的开发者咖啡活动回归，​这次搬到了广州！这也是Solar第一次在广州举办社区活动，尝试在大湾区布局更多站点。期待开发者们的加入！ ​​🗓️时间：9月13日 周六14:30-18:00 📝现在报名 https://t.co/xPSCxV4…

1/ SIMD-0268 by Alexander M. & @realbuffalojoe raises the CPI nesting limit from 4 to 8. This allows programs to make twice as many cross-program calls within a single transaction, improving composability across the network 🧵

i'm hearing oracle updates are about to get a priority boost no simds or gatekeepers required. ibrl

The community governance process for SIMD-0326: Alpenglow is complete. The proposal has passed: 98.27% voted Yes 1.05% voted No 0.69% voted Abstain 52% of stake cast a vote

I'm going to do an AMA about Alpenglow on Reddit right around the start of the SIMD-0326 governance voting phase. My temp reddit account is u/AlpenglowAMA

On tonight's market turbulence. As market's went into a flurry during J. Powell's update, @Backpack had a period of a bit over 10 minutes of degraded performance. Specifically, - Reading and loading the UI did not work for some users (orderbook wouldn't load for example). - Trading did work for most users. If you look at the trade stream, orders continued to get executed and everyone was able to open and close positions. - However, because the the UI did not work for many, or because it was slow/laggy, it meant that, in practice, trading was not working for most users. Why does the above happen? Well, it's because our system prioritizes writes over reads. And so all the writes to adjust positions, cancel orders, etc. all go through for API traders while the UI is unable to read data out of the engine because they are being starved, creating the above situation. So WTF Armani. This literally happened during the last PPI print a week ago. What are you doing about it? Yes it did, and it's the exact same issue. We took the critical feedback, previously, and as a result, we already have the fix. It just needs to be tested and released, which will happen over the next 1-2 weeks. Lag is extremely frustrating for a trading product during volatile moments. We take it EXTREMELY seriously, and we already have a very straightforward path to 10x our system capacity imminently. To be honest, we just never really prioritized performance as it was never really an issue. We got the high level architecture right, but some of these details never became an issue until we started hitting the scale that we are at today. As a result, we prioritized things other than performance (like daily proof of reserves). However, now performance is our number one priority. To everyone trading on Backpack and upset at today's lag, we hear you loud and clear, and we're on it.

Rust is a good thing. Yet sometimes readability in assembly is a lot more vivid than that in those decorated languages.

@YouKnowEno @SolanaFndn @SuperteamKorea @partyactionppl @solana @humafinance @perena @sphere @etherfuse @saros_xyz If I am in I will fly.

ANNOUNCING - SOLANA STABLE FUTURE 🇰🇷 - invite only. 250 builders/institutions. - sept 23rd. seoul. - summoning solana's stablecoin cabal. reach out to partner (sponsor/speak) cohosts:@solanafndn @superteamkorea @partyactionppl

👀

Huge news today for Jito, Solana, and defi in the US! The @vaneck_us JitoSOL ETF S-1 was just published - this will be the first 100% LST ETF! We've long said a 100% staked ETF will offer investors the best product and we're excited to see @vaneck_us pushing forward here 🫡

1/ SIMD-0306, authored by @bw_solana, raises the per account compute unit limit from 12M to 40% of the total block CU capacity. This change lets more transactions write to a single account per block. 🧵

@deanmlittle How many CU does it waste in monad ?

Have I made it? Am I officially a KOL now?

現在已 epoch 836 ﹐仲快過閃擊戰⋯ ⚡️⚡️⚡️🏁

1/ The governance process has begun for SIMD-0326: Alpenglow. Alpenglow is a new consensus protocol for Solana, replacing Proof-of-History and TowerBFT. It aims to reduce block finality from 12.8s to 150ms 🧵

按⋯目前 Pump 上的 Swap ，一單大約耗 200k CU 。Jup 上一般 120k CU，但也可以很複雜。 直接跑 AMM （例如 Raydium ) ，就一般 85k CU 再用心優化些，20k CU 也是可能的，要嘛把 Oracle 報優都去除，約 10k 亦可能。 總之這個測試反映主網 Leader 在 CU / Slot 極限下做到甚麼，內網又是否反應得來

日後每 Slot 的總 CU 量還有上調空間，樽頸仍是在注入 Leader 的帶寬和排除 DDoS 的效果。 現在連所有機械人高頻交易，每秒常見 1000~2000 非投票交易，高峰期也就 4000~7000 。

Solana 開發者們經常會在主網 ( 仍是叫 mainnet-beta ⋯ ) 做測試，包括壓力測試 昨天，便有人在主網測試了一秒內處理 10 萬單交易 x.com/cavemanloverbo… 所涉的四「塊」無恙，接著下一手 Leader ( 領驗證方 ）無恙，但當中仍涉很多準備 x.com/0xMert_/status… 細節看英文原推或續此⋯