Raphael Rueda

Launching pyptx — a Python DSL for writing NVIDIA PTX kernels. One PTX instruction = one Python call. Write pure PTX in Python. Direct Hopper + Blackwell support: wgmma, TMA, tcgen05, mbarriers. JAX + PyTorch integration. Includes GEMM, grouped GEMM, RMSNorm, SwiGLU, and a PTX→Python transpiler pip install pyptx[torch] pip install pyptx[jax] github.com/patrick-toulme…

@poetengineer__ Drop de visualizer

trying to use topological data analysis to map the shape of my x bookmarks through mapper + embedding extraction and generated 3 views: - density: where attention keeps gravitating - pca: the dominant axes of variation - centroid: center vs edge (typical -> outlier)

@KaspaPowerLaw Good post

Kaspa vs Bitcoin Power Law Price Regression Chart 2026-04-24 $KAS vs $BTC

Yay, finally! Introducing Vision Banana🍌 from @GoogleDeepMind, our unified model that outperforms SoTA specialist models on various vision tasks! By treating 2D/3D vision tasks as image generation, we unlock a new foundation for CV. Project page: vision-banana.github.io (1/5)

KiCad MCP Pro Server connects KiCad to your AI blog.adafruit.com/2026/04/22/kic…

What mechanical sorcery is this

🚀 We've submitted a CoinGecko listing request for $iKAS (Igra Bridged Kaspa), the native gas token of Igra Network, our EVM-compatible based rollup on Kaspa BlockDAG. Verification post for @CoinGecko. 🎫 Request ID: CL2004260025 Contact: Telegram @argonmining

@ZealousSwap But zealous wap has 1.2m locked right why it says 13?

👀

@kapsacoin @Igra_Labs Yes bro I feel this L2 was a paper launch no liquidity no exit, no hit throught infrastructure, what is this

@Igra_Labs Rugged again.

Exit to Kaspa L1 (aka iKAS unwrapping) is live. Anyone can send iKAS on Igra to the KasExitBridge smart contract (explorer.igralabs.com/address/0x00d3…) to receive KAS on L1 at their designated address. Parameters for the initial rollout: - Rate limit: 20 withdrawals per 2^16 blocks (~24 hours) - Minimum: 1000 iKAS (dust would congest the Kaspa-side release pipeline) - Maximum: 50000 iKAS - Processing: typically within 72 hours These conservative limits exist since the bridge is currently secured by federated multi-sig and each outgoing transaction is semi-manually reviewed as part of operational risk controls during the initial rollout. We're optimizing for zero loss of funds over speed. Process is conducted by a designated operations group, consisting of experienced ecosystem contributors familiar to the Igra team. Processing typically completes within 72 hours and may take longer in exceptional cases. Transfer of exit bridge contract ownership and control to the Igra DAO has been proposed for DAO voting. Details to follow. Developer guide: igra-labs.gitbook.io/igralabs-docs/… Detailed specs: igra-labs.gitbook.io/igralabs-docs/…

@ShalomOnKaspa @Dying_Truths @Igra_Labs Still a lot lol

@0xrnull @Dying_Truths @Igra_Labs They corrected it to one business day lol

@Dying_Truths @Igra_Labs Ahhahahaha lol I was waiting for this but now I prefer to not unwrap it wait is 72 hors and have the ikas on igra and move through zeal or nacho out to L1 for now and bridging some usdt through eth to those new LP I will wait 72 hors too much

@0xrnull @Igra_Labs Bro that was hilarious af 😂 it's true tho, I skimmed through the post as Im watching nba playoffs but when I saw how long it'll take to unwrap and then your comment directly after, I lost it 😂 🤣

@Dying_Truths @Igra_Labs Bro but it ways 72 hours lol

@0xrnull @Igra_Labs Haha not business days 😂

@Chriscrypto_89 @Kaspa_KAT @Igra_Labs Let's invalidate that cdn cache and let's deploy that to production guys hehe I need my liquidity

@0xrnull @Kaspa_KAT @Igra_Labs The timeline is in the post.

🌉 KatBridge: $KAS ↔ iKAS: Unlocking Bi-directional Bridging Two options. Your choice: 1⃣ ikas.katbridge.com → Permissionless Entry → Federated / Multi-Sig Exit (later today) 2⃣ katbridge.com→ Custodial Route → On-Demand / Immediate Bridging → FROST Distributed Signer Model → Same security as our KRC20 & KRC721 routes. Think of it as Kurve, but for Igra (coming in a few days) Both options will exist to meet the communities needs and desires for on demand exit bridging. One Place. All Bridges.

@Kaspa_KAT When can we unwrap ikas?

@CerberCrypto @TurnedTeflon Bro ski don't be silly lol, we can not unwrap ikas and the pools for hyperlane bridge are null or thin liquidity lol

@0xrnull @TurnedTeflon Liquidity is not bad here, but I wouldn't make such big changes. Waiting is the best strategy

You’re still early… but not for long ⏳🚀 $IGRA $ZEAL $KAS #KAS #ZEAL #IGRA

@coinco041 @ZealousSwap Full on chain liquidity broski

USDT, WETH, cbBTC and wstETH are now live and verified on @ZealousSwap

@Kaspa_Commons @Igra_Labs @hyperlane @ethereum Can we unwrap ikas?

Kaspa has gained a live connection to the broader crypto ecosystem. Through @Igra_Labs , @hyperlane , and the teams building around them, $KAS now has an active pathway into major EVM networks like @ethereum. What’s actually happening -> Igra runs an EVM-compatible Layer 2 anchored to Kaspa -> Hyperlane connects that environment to other EVM chains -> Kaspa.com and @ZealousSwap are building applications and liquidity on top -> @Kaspa_KAT connects Kaspa L1 and L2 for KAS and KRC-20 movement (@kasplex) Together, this creates a working route between Kaspa and external ecosystems. Assets can now move: KAS ↔ Igra (iKAS) ↔ EVM networks Already in use Kaspa.com and @ZealousSwap have launched a USDC <> KAS L2 pool #Stablecoins can bridge into Igra and be used immediately K.A.T. enables movement between L1 and L2 This is live infrastructure supporting real activity. Simply put $KAS now connects into the wider crypto economy through Igra, with applications and liquidity already in motion. So what • Stablecoin liquidity can enter and move through the Kaspa ecosystem • Builders can use familiar EVM tools while anchoring to Kaspa • Applications, trading, and asset movement are already functioning How this comes together This is ecosystem-driven development around the Kaspa base layer: • Kaspa Core advances real-time settlement at the base layer • Igra extends that capability through an EVM-compatible L2 • Hyperlane enables cross-chain connectivity Kaspa.com and Zealous bring applications and liquidity • K.A.T. keeps value moving between L1 and L2 Where this is heading? This is a working model built with today’s tools. As Kaspa evolves with #covenants++ and #KvProgs through #Toccata, builders across this ecosystem may begin moving more logic, assets, and coordination directly onto Kaspa L1. The roles of L2s, bridges, and integrations can evolve alongside that shift, as more capability becomes native to the network. The bigger picture Kaspa is becoming a system that connects, routes, and settles. This is one working example. Many teams across the Kaspa ecosystem are building in parallel, shaping how this network is used in practice.

Opus 4.7 appears to be SOTA at agentic CAD design