Register and share your invite link to earn from video plays and referrals.

Search results for IMPULホイール
IMPULホイール community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including IMPULホイール
Super GT Round 8 # 12 TRS IMPUL with SDG Z QF P 9 Race P 3 #全開魂# #スーパーgt# #インパル#
The conference days may be over, but EuroRust is not! @jonhoo and @jonasKruckie are kicking off our impl day. Thanks to @HelsingAI for hosting us! #EuroRust26# #RustLang#
I recommend VGDD ー Verified Grill Driven Development. It's not the official name. I just call like it😂 VGDD consists of grill, TDD and review by LLM itself. My favorite way of developing is to use wayfinder to VGDD to keep tracking ADR and the process of impl.
Show more
I haven’t successfully found a use case for Sol Ultra yet. I’ve run two days of side by side xhigh and ultra runs for planning and impl and I haven’t noticed any tangible quality change. I can see the difference in execution and token usage. Maybe I’m holding it wrong, but how?
Show more
🚨SlowMist TI Alert🚨 💸 @flamincome Loss: ~$345.9K 🔍 Root Cause: Share-price inflation caused by unsafe asset accounting and valuation. The Strategy treated a permissionlessly injectable Convex `BaseRewardPool` balance as its own assets and valued the injected USDP/3CRV LP using Curve `get_virtual_price()`, which significantly overstated its value in the depegged pool. The inflated share price was then redeemed against real Aave aUSDT liquidity. 📌 Attacker: 0x83381e7f7232775735169d72d237b858ffc36871 📌 Victim Strategy: 0xb8d6471cA573C92c7096Ab8600347F6a9Fe268a5 📌 Flawed Contract (Impl): 0xff20De3F3F4C7E9518035a968B4A3CEE500a2AFB Powered by Tx:
Show more
🚨SlowMist TI Alert🚨 💸 @Ostium Loss: ~11,862,445 USDC 🔍 Root Cause: An authorized oracle signer was used to submit malicious price reports through a registered forwarder. The attacker provided validly signed but manipulated oracle data, which was accepted by the oracle verification mechanism. By repeatedly opening and closing trades with artificially favorable prices, the attacker generated artificial profits and drained funds from the OstiumVault. 📌 Attacker Address: 0xd1794196f0fc99c7f27970e661597d77d9a85869 📌 Victim Address: 0x20d419a8e12c45f88fda7c5760bb6923cee27f98 (vault) 📌 Vulnerable Contract: 0x0aebc4094b60ea4e21e937e80dafdd58c07c5ebb (OstiumPrivatePriceUpKeep impl) & 0xd456939e54f68ef9b0be62abb2ec4a37397cb814 (OstiumVerifier) Impact: The attacker exploited compromised oracle privileges to submit manipulated price reports and execute repeated profitable trades, draining ~11.86M USDC from the vault. Powered by Tx:
Show more
so an update on my AI psychosis, in the last 5 days, I've picked up work on @artichokeruby. I have completely removed its mruby backend. At this point I have: * Full lowering from source to AST via Prism * Lowering from AST to a Ruby specific IR * IR optimization passes (dead store elimination, constant folding, guarded specialization for privileged class method dispatch, data structure capacity hints, ivar fast paths, DCE, DBE, basic block and frame elimination) * Several effect analyses in IR passes (tracking privileged class type hinting, identifying noexcept basic blocks, etc) * Code generation with a register based VM * LTO, whole program optimization * Large swaths of the Core classes fully implemented * Heap, GC (Immix), ivar storage, method lookup and caching machinery * CLI, including IR and bytecode dumpers to guide optimization work * A full Rust reimplementation of the Onigmo regex engine and 36 of its encodings * A "ruby semantic layer" that handles callbacks, rooting, invalidation, coercion policy, and recursion independent of any concrete interpreter; because it is generic, there are test harnesses that run it with a randomizing heap and GC after every yield point * A whole swath of data structures representing Ruby Core classes * A parallel impl of rust std and alloc that has zero infallibly allocating pathways * Native implementations of `File`, `IO`, `Dir`, and `Socket` using rustix and windows-sys * support for custom eh personalities and unwinding using C++ exception handling * "ABI skins" to project Artichoke into arbitrary ABIs, partial implementation of MRI ABI which can link the sqlite C extension The whole "Ruby" is generic over core interpreter intrinsics which means everything is replaceable (heap, object model, GC, value repr). The interpreter was also built to be embedded so it is actually a machine that must be polled with an instruction budget to run. The GC also has a configurable work budget. I expect within a day or so I'll be able to run optcarrot correctly and then will set the token machine to optimize. It is currently pretty slow, but that is, as they say, a reward signal. I've identified nearly 400 MRI errata in this process.
Show more