Loading video...

Video Failed to Load

Go Home

V1 update for 🚀 – Expo SDK 55, Router v7, Widgets – SwiftUI view refactor (real native feel) – PostHog analytics – Superwall integration Cleaner architecture. Stronger native layer. More scalable foundation.

rsStats_'s profile picture

Rayan

1,845 subscribers

24,842 views • 6 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Current progress on my AI Tattoo app 🤓 The Tattoo Playground is powered by: - CSS animations in RN (hat tip Kacper Kapuściak) - Expo Module for a native SwiftUI input view (via Kavsoft) - Custom haptic engine with expo-modules by vo—va 🇺🇦 (also used in Fuse 🤩) - Pressto for seamless pressable handling (thanks Enzo Manuel Mangano) - Sonner Native for toasts thanks to Gunnar Torfi - Apple Foundation Models for on-device prompt suggestions (via expo-modules) - Expo Router v7 (canary) for routing + API Routes on EAS Hosting - React Native Screens (v4.18.0) with UITabBarItem support - Expo UI (context menus) + Expo Image - React Native Reanimated by Software Mansion - Nano Banana 2 Lite for amazing image results - And more! :) Source code is available for Code with Beto members — link below 👇
2:37

Current progress on my AI Tattoo app 🤓 The Tattoo Playground is powered by: - CSS animations in RN (hat tip Kacper Kapuściak) - Expo Module for a native SwiftUI input view (via Kavsoft) - Custom haptic engine with expo-modules by vo—va 🇺🇦 (also used in Fuse 🤩) - Pressto for seamless pressable handling (thanks Enzo Manuel Mangano) - Sonner Native for toasts thanks to Gunnar Torfi - Apple Foundation Models for on-device prompt suggestions (via expo-modules) - Expo Router v7 (canary) for routing + API Routes on EAS Hosting - React Native Screens (v4.18.0) with UITabBarItem support - Expo UI (context menus) + Expo Image - React Native Reanimated by Software Mansion - Nano Banana 2 Lite for amazing image results - And more! :) Source code is available for Code with Beto members — link below 👇

Beto

35,480 views • 10 months ago

Expo Router just unlocked a new level of native on iOS 🚀 For years, cross-platform meant tradeoffs. Your app worked everywhere, but it never felt quite right. That gap is finally closing. With the latest version of Expo Router, native iOS APIs are now exposed declaratively. No UIKit wrestling. No fake UI. If you want your app to feel truly native on iOS, these are the APIs you should be using: - Native Tabs (real system tab bar) - Stack Toolbar (native header controls) - Bottom toolbars with placement=“bottom” - Bottom accessories attached to the tab bar - Zoom transitions for fluid navigation - Native sheet footers (experimental) I wrote a full breakdown with code examples and video demos of these features in my blog (link below 👇)
0:52

Expo Router just unlocked a new level of native on iOS 🚀 For years, cross-platform meant tradeoffs. Your app worked everywhere, but it never felt quite right. That gap is finally closing. With the latest version of Expo Router, native iOS APIs are now exposed declaratively. No UIKit wrestling. No fake UI. If you want your app to feel truly native on iOS, these are the APIs you should be using: - Native Tabs (real system tab bar) - Stack Toolbar (native header controls) - Bottom toolbars with placement=“bottom” - Bottom accessories attached to the tab bar - Zoom transitions for fluid navigation - Native sheet footers (experimental) I wrote a full breakdown with code examples and video demos of these features in my blog (link below 👇)

Beto

91,618 views • 7 months ago

Announcing RevenueCharts 🙀 100% FREE subscription analytics with an open source commitment in 2025. No SDK needed, although it is recommended (see replies). Let us explain 👇 At Superwall, we spent the last few months building infrastructure for subscription analytics, revenue charts, and webhooks. At first, we expected to sell this the same way others do, but then we realized something... The real innovation here is a transform layer that standardizes subscriber lifecycle events to an interoperable schema, and the real value here is managed infrastructure that supports a long tail of integrations. All this points to open source as the optimal solution. Developers will have the opportunity to leverage the evolving simplicity of native StoreKit, Google Billing and Stripe APIs without vendor lock-in, while the community adds support for integrations on an ad-hoc basis. We've already built the transform, infrastructure and UI layers which are available in Superwall's dashboard today. The second thing we realized is we're uniquely positioned to offer this for FREE. Already ingesting app events for billions of users per month, the incremental costs of handling subscription events are marginal. Revenue Charts are in public beta. All existing Superwall customers gained access last Friday, and new customers can sign up today. If all you're after are charts & subscription analytics, you can set up Revenue Tracking by forwarding ASC events to Superwall for free. If you add our SDK, we'll tie provided App User Ids to webhook and integration events in the future. We'll only ever charge customers who use Superwall for paywalls. Available today: Revenue, Proceeds, Refunds, Trial and Subscriber analytics, for iOS only. Coming Soon: Android, Stripe, Webhooks, Integrations, ARR, MRR, LTV, Retention & every other chart you ReallyCare about... but free.
2:05

Announcing RevenueCharts 🙀 100% FREE subscription analytics with an open source commitment in 2025. No SDK needed, although it is recommended (see replies). Let us explain 👇 At Superwall, we spent the last few months building infrastructure for subscription analytics, revenue charts, and webhooks. At first, we expected to sell this the same way others do, but then we realized something... The real innovation here is a transform layer that standardizes subscriber lifecycle events to an interoperable schema, and the real value here is managed infrastructure that supports a long tail of integrations. All this points to open source as the optimal solution. Developers will have the opportunity to leverage the evolving simplicity of native StoreKit, Google Billing and Stripe APIs without vendor lock-in, while the community adds support for integrations on an ad-hoc basis. We've already built the transform, infrastructure and UI layers which are available in Superwall's dashboard today. The second thing we realized is we're uniquely positioned to offer this for FREE. Already ingesting app events for billions of users per month, the incremental costs of handling subscription events are marginal. Revenue Charts are in public beta. All existing Superwall customers gained access last Friday, and new customers can sign up today. If all you're after are charts & subscription analytics, you can set up Revenue Tracking by forwarding ASC events to Superwall for free. If you add our SDK, we'll tie provided App User Ids to webhook and integration events in the future. We'll only ever charge customers who use Superwall for paywalls. Available today: Revenue, Proceeds, Refunds, Trial and Subscriber analytics, for iOS only. Coming Soon: Android, Stripe, Webhooks, Integrations, ARR, MRR, LTV, Retention & every other chart you ReallyCare about... but free.

Superwall

961,172 views • 1 year ago

Split layout framework update. Since the last video: focus views animate, corner drags can move both axes, cross-window drag and drop with animation, all animations backed by CoreAnimation, and full accessibility framework integration (e.g. compat with VoiceOver). The focus view work was the hardest and most complicated. We allow caller-provided SwiftUI views for the focus style, but have to drop that back to a native AppKit/UIKit hosted view for smooth CoreAnimation integration with our other animations so they move in lock-step with our other stuff. Lot of work to get that to work, but I think it turned out great. The caller lives in easy SwiftUI land we handle that complexity. The animation timings and curves need to be tweaked. I think some animations are too long or don't feel right. But thats just parameterization at this point...
0:23

Split layout framework update. Since the last video: focus views animate, corner drags can move both axes, cross-window drag and drop with animation, all animations backed by CoreAnimation, and full accessibility framework integration (e.g. compat with VoiceOver). The focus view work was the hardest and most complicated. We allow caller-provided SwiftUI views for the focus style, but have to drop that back to a native AppKit/UIKit hosted view for smooth CoreAnimation integration with our other animations so they move in lock-step with our other stuff. Lot of work to get that to work, but I think it turned out great. The caller lives in easy SwiftUI land we handle that complexity. The animation timings and curves need to be tweaked. I think some animations are too long or don't feel right. But thats just parameterization at this point...

Mitchell Hashimoto

104,095 views • 2 months ago

Every week another AI image app hits the top charts. The window is open, but not forever. That's why I built Platano. Today it's production ready. What's inside: - Expo SDK 56 - Agent skills for setup, rebranding, adding languages, and more - Fully native iOS and Android - Material You on Android, Liquid Glass with iOS 18 fallbacks - Onboarding flow battle-tested in my AI Tattoo app (live in the App Store) - RevenueCat payments - AI editor with Nano Banana 2 - Clean architecture your agent can extend - Interactive CLI to spin it up I use this as the base for every real app I'm building now, not just AI image apps. Ship something maintainable. Validate fast. (link below)
0:48

Every week another AI image app hits the top charts. The window is open, but not forever. That's why I built Platano. Today it's production ready. What's inside: - Expo SDK 56 - Agent skills for setup, rebranding, adding languages, and more - Fully native iOS and Android - Material You on Android, Liquid Glass with iOS 18 fallbacks - Onboarding flow battle-tested in my AI Tattoo app (live in the App Store) - RevenueCat payments - AI editor with Nano Banana 2 - Clean architecture your agent can extend - Interactive CLI to spin it up I use this as the base for every real app I'm building now, not just AI image apps. Ship something maintainable. Validate fast. (link below)

Beto

11,477 views • 4 months ago

Introducing Arc, an open Layer-1 blockchain purpose-built for stablecoin finance. From payments to FX to capital markets, Arc is the home for builders innovating with digital money and tokenized value on the internet. Stablecoins have shown us what’s possible. They’ve powered trillions in onchain transactions and unlocked a faster, more open financial system. Arc is designed to provide an enterprise-grade foundation with the performance, reliability, and liquidity needed to scale stablecoin use cases worldwide. Featuring: ✅ USDC as native gas ✅ Built-in FX engine ✅ Deterministic sub-second finality ✅ Opt-in privacy ✅ Full Circle platform integration At its core is Malachite, a high-performance consensus engine developed by Informal Systems that powers Arc with safety, liveness, and resilience at scale. Arc expands the design space for stablecoins by uniting speed with certainty and delivering the native tooling needed to meet real-world business obligations. Open and composable, Arc is designed to interoperate seamlessly with the broader multichain ecosystem. Fully EVM-compatible, developers will be able to build on Arc using the same frameworks and tooling they know and trust. Together, we’re laying the foundation to move stablecoin finance from early adoption to globally trusted infrastructure. Arc will enter private testnet in the coming weeks, with public testnet expected this fall. Read the litepaper → Join us in building the new internet financial system →
2:50

Introducing Arc, an open Layer-1 blockchain purpose-built for stablecoin finance. From payments to FX to capital markets, Arc is the home for builders innovating with digital money and tokenized value on the internet. Stablecoins have shown us what’s possible. They’ve powered trillions in onchain transactions and unlocked a faster, more open financial system. Arc is designed to provide an enterprise-grade foundation with the performance, reliability, and liquidity needed to scale stablecoin use cases worldwide. Featuring: ✅ USDC as native gas ✅ Built-in FX engine ✅ Deterministic sub-second finality ✅ Opt-in privacy ✅ Full Circle platform integration At its core is Malachite, a high-performance consensus engine developed by Informal Systems that powers Arc with safety, liveness, and resilience at scale. Arc expands the design space for stablecoins by uniting speed with certainty and delivering the native tooling needed to meet real-world business obligations. Open and composable, Arc is designed to interoperate seamlessly with the broader multichain ecosystem. Fully EVM-compatible, developers will be able to build on Arc using the same frameworks and tooling they know and trust. Together, we’re laying the foundation to move stablecoin finance from early adoption to globally trusted infrastructure. Arc will enter private testnet in the coming weeks, with public testnet expected this fall. Read the litepaper → Join us in building the new internet financial system →

Arc

789,241 views • 1 year ago

QVAC SDK 0.15.0 is live. This release adds multiple prompts batching, brings a native AMD GPU backend to the stack, moves more vision encoders onto mobile GPUs, and adds a second local coding-agent integration. Main highlights: - Prompt batching for the LLM addon. Batch multiple prompts into one job and process them concurrently, with each answer returned the moment its generation finishes. - Native AMD GPU backend. A first-class HIP/ROCm backend in @qvac/vla-ggml, auto-selected over Vulkan with clean fallback when ROCm is absent. - A second local coding agent. OpenClaw joins OpenCode for local, cloud-free agent workflows. AGENTS - OpenCode plugin update (@qvac/opencode-plugin). Aligned with the current SDK, CLI, and AI SDK provider packages. A fresh install runs OpenCode against managed local QVAC models out of the box, from the default qvac/qwen3.5-9b, with no manual qvac serve setup. - OpenClaw plugin (@qvac/openclaw-plugin). A second coding-agent integration alongside OpenCode. A fresh setup installs the plugin, creates a local qvac provider through onboarding, and runs a QVAC model through OpenClaw🦞's local service path. LANGUAGE MODELS - Prompt batching (LLM addon). Batch multiple prompts in one job and run them concurrently, each answer returns the moment its generation finishes, no waiting on the others. - Reasoning-context trimming on hybrid + recurrent models (@qvac/llm-llamacpp). remove_thinking_from_context now works beyond pure-attention models. Same JS API, no throw. VOICE AND SPEECH - Transcription (transcription-parakeet 0.9.0). More robust CPU fallback on GPU failure and a faster Vulkan backend on Pixel 9. - Text-to-speech features (tts-ggml 0.4.0). Adds LavaSR for noise removal and adjustable output frequency up to 48 kHz, plus Japanese via Chatterbox. - Text-to-speech fixes (tts-ggml 0.4.1). CPU fallback on GPU failure, a q8_0 KV crash fix on Metal with Chatterbox. VISION - Qwen3.5 vision encoder on GPU (Android). Image encoder moves onto the phone GPU, with a smarter tile-grid preprocessor and default image-token caps, for flagship Android: Vulkan on Mali (Pixel 9 Pro) and OpenCL on Adreno 830 (Galaxy S25). - Gemma-4 vision encoder on GPU (Android). Vision encoder runs on the phone GPU instead of CPU, same flagship Android targets. PLATFORM AND PERFORMANCE - AMD GPU backend (@qvac/vla-ggml). Native HIP/ROCm backend, auto-selected over Vulkan with clean fallback when ROCm is absent (Linux x64 only). Comes with ~23% faster than Vulkan, ~14% faster than PyTorch-ROCm, parity preserved. Unified code style. A cleaner, more consistent, easier-to-contribute codebase. Let's build. npm install @qvac/sdk
1:25

QVAC SDK 0.15.0 is live. This release adds multiple prompts batching, brings a native AMD GPU backend to the stack, moves more vision encoders onto mobile GPUs, and adds a second local coding-agent integration. Main highlights: - Prompt batching for the LLM addon. Batch multiple prompts into one job and process them concurrently, with each answer returned the moment its generation finishes. - Native AMD GPU backend. A first-class HIP/ROCm backend in @qvac/vla-ggml, auto-selected over Vulkan with clean fallback when ROCm is absent. - A second local coding agent. OpenClaw joins OpenCode for local, cloud-free agent workflows. AGENTS - OpenCode plugin update (@qvac/opencode-plugin). Aligned with the current SDK, CLI, and AI SDK provider packages. A fresh install runs OpenCode against managed local QVAC models out of the box, from the default qvac/qwen3.5-9b, with no manual qvac serve setup. - OpenClaw plugin (@qvac/openclaw-plugin). A second coding-agent integration alongside OpenCode. A fresh setup installs the plugin, creates a local qvac provider through onboarding, and runs a QVAC model through OpenClaw🦞's local service path. LANGUAGE MODELS - Prompt batching (LLM addon). Batch multiple prompts in one job and run them concurrently, each answer returns the moment its generation finishes, no waiting on the others. - Reasoning-context trimming on hybrid + recurrent models (@qvac/llm-llamacpp). remove_thinking_from_context now works beyond pure-attention models. Same JS API, no throw. VOICE AND SPEECH - Transcription (transcription-parakeet 0.9.0). More robust CPU fallback on GPU failure and a faster Vulkan backend on Pixel 9. - Text-to-speech features (tts-ggml 0.4.0). Adds LavaSR for noise removal and adjustable output frequency up to 48 kHz, plus Japanese via Chatterbox. - Text-to-speech fixes (tts-ggml 0.4.1). CPU fallback on GPU failure, a q8_0 KV crash fix on Metal with Chatterbox. VISION - Qwen3.5 vision encoder on GPU (Android). Image encoder moves onto the phone GPU, with a smarter tile-grid preprocessor and default image-token caps, for flagship Android: Vulkan on Mali (Pixel 9 Pro) and OpenCL on Adreno 830 (Galaxy S25). - Gemma-4 vision encoder on GPU (Android). Vision encoder runs on the phone GPU instead of CPU, same flagship Android targets. PLATFORM AND PERFORMANCE - AMD GPU backend (@qvac/vla-ggml). Native HIP/ROCm backend, auto-selected over Vulkan with clean fallback when ROCm is absent (Linux x64 only). Comes with ~23% faster than Vulkan, ~14% faster than PyTorch-ROCm, parity preserved. Unified code style. A cleaner, more consistent, easier-to-contribute codebase. Let's build. npm install @qvac/sdk

QVAC

29,260,217 views • 2 months ago

BREAKING - EARLY EXCLUSIVE: XPENG Partners with Google Maps to Fuel Global Expansion The global autonomous driving landscape is becoming even more competitive! XPENG has announced a milestone global partnership with Google Maps, bringing a complete refresh of its in-car navigation and advanced driver assistance systems (ADAS). This major upgrade will come standard in the newly debuted XPENG L03. At the official launch event for the L03 in Munich, Germany, XPENG Chairman and CEO He Xiaopeng announced that the Next-Gen AI SUV Coupe will launch simultaneously in 64 countries and regions. XPENG is building its native in-car navigation system using Google Maps’ Auto SDK for vehicles outside China, which I’m sure MANY of you will be excited about. First in APAC to Adopt Google Maps Auto SDK XPENG is the first automaker from the APAC region to ship a vehicle with Google Maps Auto SDK integration. Instead of using your smartphone for basic screen mirroring, drivers get a native, custom in-car map application designed entirely by XPENG and powered directly by Google Maps. This integration brings: Real-time precision: Live traffic-aware guidance and highly accurate place search. Smart EV routing: Direct in-car EV energy estimation and trip planning. Native control: Full compatibility with voice control and multi-screen display transfer. Laying the Foundation for Global Autonomous Driving This partnership goes beyond finding directions. XPENG is officially utilizing Google Maps' in-vehicle Map Data Services to support its flagship full-scenario ADAS, Next Generation Pilot (NGP), as well as its foundational assist system, XPILOT ASSIST. To scale XPENG's advanced driving systems internationally, future applications of NGP (VLA 2.0) must rely on highly accurate map data and navigation maneuvers. Google Map Data Services will serve as the cornerstone for this phased global rollout, excluding markets in the Commonwealth of Independent States (CIS). Think of it as a fusion of XPENG’s technology with Google Maps Technology to get a more robust, intelligent, powerful, and safe autonomous driving experience. Overseas users of the XPENG L03 will be the very first to experience this upgraded, Google-powered native navigation system. My Thoughts I personally love and use Google Maps, so I’m glad to see this partnership, and I find it really neat how XPENG and Google Maps technology will work together. What are your thoughts and questions on XPENG integrating Google Maps natively to power its global self-driving tech? Let me know in the replies, and I will try to find the answers to your questions.
2:59

BREAKING - EARLY EXCLUSIVE: XPENG Partners with Google Maps to Fuel Global Expansion The global autonomous driving landscape is becoming even more competitive! XPENG has announced a milestone global partnership with Google Maps, bringing a complete refresh of its in-car navigation and advanced driver assistance systems (ADAS). This major upgrade will come standard in the newly debuted XPENG L03. At the official launch event for the L03 in Munich, Germany, XPENG Chairman and CEO He Xiaopeng announced that the Next-Gen AI SUV Coupe will launch simultaneously in 64 countries and regions. XPENG is building its native in-car navigation system using Google Maps’ Auto SDK for vehicles outside China, which I’m sure MANY of you will be excited about. First in APAC to Adopt Google Maps Auto SDK XPENG is the first automaker from the APAC region to ship a vehicle with Google Maps Auto SDK integration. Instead of using your smartphone for basic screen mirroring, drivers get a native, custom in-car map application designed entirely by XPENG and powered directly by Google Maps. This integration brings: Real-time precision: Live traffic-aware guidance and highly accurate place search. Smart EV routing: Direct in-car EV energy estimation and trip planning. Native control: Full compatibility with voice control and multi-screen display transfer. Laying the Foundation for Global Autonomous Driving This partnership goes beyond finding directions. XPENG is officially utilizing Google Maps' in-vehicle Map Data Services to support its flagship full-scenario ADAS, Next Generation Pilot (NGP), as well as its foundational assist system, XPILOT ASSIST. To scale XPENG's advanced driving systems internationally, future applications of NGP (VLA 2.0) must rely on highly accurate map data and navigation maneuvers. Google Map Data Services will serve as the cornerstone for this phased global rollout, excluding markets in the Commonwealth of Independent States (CIS). Think of it as a fusion of XPENG’s technology with Google Maps Technology to get a more robust, intelligent, powerful, and safe autonomous driving experience. Overseas users of the XPENG L03 will be the very first to experience this upgraded, Google-powered native navigation system. My Thoughts I personally love and use Google Maps, so I’m glad to see this partnership, and I find it really neat how XPENG and Google Maps technology will work together. What are your thoughts and questions on XPENG integrating Google Maps natively to power its global self-driving tech? Let me know in the replies, and I will try to find the answers to your questions.

M. Brandon Lee | THIS IS TECH TODAY

65,878 views • 2 months ago

Pera Wallet 7.0 is here, and it's our biggest update yet 🚀 We rebuilt the entire app from the ground up, which means faster updates, a lighter install, and full feature parity across iOS & Android. Here's what's new: 🏠 New portfolio home screen with a portfolio slider (hide the chart if you prefer a cleaner view) 👀 See the exact balance impact of a transaction before you sign it 🧊 Freeze transactions on demand 🎭 Duress mode — set a fake PIN that opens a fake account 📳 Shake to close the app instantly 🌱 Native staking & funding screens — no more webview 🔍 Global search across accounts, assets & NFTs 🎲 3D NFT support 🗂️ View your wallet's full derivation structure 🌐 Add custom networks (localnet, betaNet, fNet) 🤝 Fee delegation — new users can get started with zero balance in Fund 🔌 USB Ledger support on Android 📬 Streamlined notifications inbox 📱 Fully optimized for iPad Full details in the blog 👇
1:01

Pera Wallet 7.0 is here, and it's our biggest update yet 🚀 We rebuilt the entire app from the ground up, which means faster updates, a lighter install, and full feature parity across iOS & Android. Here's what's new: 🏠 New portfolio home screen with a portfolio slider (hide the chart if you prefer a cleaner view) 👀 See the exact balance impact of a transaction before you sign it 🧊 Freeze transactions on demand 🎭 Duress mode — set a fake PIN that opens a fake account 📳 Shake to close the app instantly 🌱 Native staking & funding screens — no more webview 🔍 Global search across accounts, assets & NFTs 🎲 3D NFT support 🗂️ View your wallet's full derivation structure 🌐 Add custom networks (localnet, betaNet, fNet) 🤝 Fee delegation — new users can get started with zero balance in Fund 🔌 USB Ledger support on Android 📬 Streamlined notifications inbox 📱 Fully optimized for iPad Full details in the blog 👇

pera.algo

26,309 views • 1 month ago

🚀Announcing v2.4 of GeroWallet – now rebranded as Gero Dashboard! Submitted to the Chrome Store and going live in a few days. This update is free for thousands of users, with seamless migration of your wallets & private keys. Enjoy features that were once beta-exclusive: • Cashback – Pay with any credit card online & unlock crypto rewards • Governance – Delegate to DReps & engage in Cardano’s decentralized decisions • Cardano Shield – Advanced phishing defense using ML & community insights • Swap – Seamlessly exchange between Cardano native tokens • Wallet Analytics – Visualize your tokens & NFTs with detailed insights And now, support for Apex Fusion: Create, import & stake your AP3X tokens with our own stake pool. Coming soon, we’re working on: • Bank Integration • Multi-Sig Transactions • Social Login • zkFiat & Off-Ramp Reporting • Rollup Fees, ADA Flow, Subscriptions Plus exclusive benefits for $GERO holders! Note: Trezor Keystone Hardware Wallet import isn’t available yet but will be soon. Major announcements are on the horizon – stay tuned for more updates as we redefine your crypto experience with Gero Dashboard! #CardanoCommunity #Cardano #Ap3x
1:00

🚀Announcing v2.4 of GeroWallet – now rebranded as Gero Dashboard! Submitted to the Chrome Store and going live in a few days. This update is free for thousands of users, with seamless migration of your wallets & private keys. Enjoy features that were once beta-exclusive: • Cashback – Pay with any credit card online & unlock crypto rewards • Governance – Delegate to DReps & engage in Cardano’s decentralized decisions • Cardano Shield – Advanced phishing defense using ML & community insights • Swap – Seamlessly exchange between Cardano native tokens • Wallet Analytics – Visualize your tokens & NFTs with detailed insights And now, support for Apex Fusion: Create, import & stake your AP3X tokens with our own stake pool. Coming soon, we’re working on: • Bank Integration • Multi-Sig Transactions • Social Login • zkFiat & Off-Ramp Reporting • Rollup Fees, ADA Flow, Subscriptions Plus exclusive benefits for $GERO holders! Note: Trezor Keystone Hardware Wallet import isn’t available yet but will be soon. Major announcements are on the horizon – stay tuned for more updates as we redefine your crypto experience with Gero Dashboard! #CardanoCommunity #Cardano #Ap3x

Gero

17,324 views • 1 year ago

📣 Community Update: Cyborgs! We’ve just reached a major milestone that signals a clear shift in what Arcane and Spectre are becoming, and where this project is heading. Arcane is no longer just a wallet. It’s evolving into the foundation for on-chain privacy. With the Arcane wallet extension now complete, alongside a working privacy dApp interacting directly through the SDK, we’re seeing the first fully connected version of this system come to life. 📌 The wallet extension introduces a real user interface across desktop, complementing mobile, and bringing Arcane into everyday use rather than remaining purely backend infrastructure. Public release by the end of Q2. 📌 Arcane now supports both public and private transactions seamlessly, with Invisible Routing automatically detecting the transaction type so the user doesn’t need to think about it. 📌 The integration between the wallet and the dApp via the SDK creates a complete flow from wallet > action > private execution. This is live, functional privacy in action, not just theory. 📌 The Arcane SDK is a major unlock. It allows any dApp on EVM compatible chains to integrate our privacy stack, positioning Arcane as infrastructure rather than a single product. 📌 Our relayer network will power all private transactions, not only within the Arcane wallet, but across every third party application that integrates the SDK. 📌 As more integrations come online, this drives increased volume through the ecosystem, expanding the revenue streams flowing back to holders. What we’re seeing now is the early formation of a connected ecosystem, where wallet, SDK, dApps, and relayers all work together as one unified privacy layer. This marks the transition from isolated development into something functional and expandable. The rails are being laid. The system is coming online. And what we’re building here doesn’t just participate in the future of crypto, it helps define it ♾️🚀
1:00

📣 Community Update: Cyborgs! We’ve just reached a major milestone that signals a clear shift in what Arcane and Spectre are becoming, and where this project is heading. Arcane is no longer just a wallet. It’s evolving into the foundation for on-chain privacy. With the Arcane wallet extension now complete, alongside a working privacy dApp interacting directly through the SDK, we’re seeing the first fully connected version of this system come to life. 📌 The wallet extension introduces a real user interface across desktop, complementing mobile, and bringing Arcane into everyday use rather than remaining purely backend infrastructure. Public release by the end of Q2. 📌 Arcane now supports both public and private transactions seamlessly, with Invisible Routing automatically detecting the transaction type so the user doesn’t need to think about it. 📌 The integration between the wallet and the dApp via the SDK creates a complete flow from wallet > action > private execution. This is live, functional privacy in action, not just theory. 📌 The Arcane SDK is a major unlock. It allows any dApp on EVM compatible chains to integrate our privacy stack, positioning Arcane as infrastructure rather than a single product. 📌 Our relayer network will power all private transactions, not only within the Arcane wallet, but across every third party application that integrates the SDK. 📌 As more integrations come online, this drives increased volume through the ecosystem, expanding the revenue streams flowing back to holders. What we’re seeing now is the early formation of a connected ecosystem, where wallet, SDK, dApps, and relayers all work together as one unified privacy layer. This marks the transition from isolated development into something functional and expandable. The rails are being laid. The system is coming online. And what we’re building here doesn’t just participate in the future of crypto, it helps define it ♾️🚀

0x0

10,476 views • 4 months ago

🚀 NEW EPISODE 🚀 Scaling the Agentic Internet Friederike Ernst 🦉 chats with Bowen Wang, Head of Protocol @ Near One, about blockchain scaling, AI, and how NEAR Protocol sets the ground for AI-native apps & the agentic economy. ‘Attention Is All You Need’, co-wrote by Illia Polosukhin in 2017, laid the foundation for arguably one of the most consequential tech breakthroughs in our recent history. 1 year later, Illia founded Near AI, which later became NEAR Protocol. They were visionaries ahead of their time and, although AI took several more years before becoming a viable product, the experience of scaling databases would later prove valuable and applicable in blockchain world. As a result, NEAR Protocol is one of the first blockchains to implement execution layer sharding, asynchronous execution and stateless validation, bringing the finality time down to 1.2 seconds, with a block time of 0.6 seconds. Don't forget to RT & follow Epicenter Podcast! Topics discussed in this episode: 0:00 - Introduction 3:30 - Bowen’s background 4:47 - Near’s pivot from AI to blockchains 8:26 - The role of Near One 9:13 - Near’s tech stack upgrades 13:39 - Optimizing network architecture 17:08 - Stateless validation & block propagation 21:10 - Sharding & asynchronous execution 29:12 - Message passing between shards & shard ‘equality’ 35:51 - Challenges of implementing stateless validation 41:05 - Applications benefiting from Near’s finality speed 44:18 - Intent-based infrastructure 47:10 - AI use cases on Near 52:27 - Expanding Near’s ecosystem 54:43 - Development challenges 57:55 - Near’s vision and goals
1:01:40

🚀 NEW EPISODE 🚀 Scaling the Agentic Internet Friederike Ernst 🦉 chats with Bowen Wang, Head of Protocol @ Near One, about blockchain scaling, AI, and how NEAR Protocol sets the ground for AI-native apps & the agentic economy. ‘Attention Is All You Need’, co-wrote by Illia Polosukhin in 2017, laid the foundation for arguably one of the most consequential tech breakthroughs in our recent history. 1 year later, Illia founded Near AI, which later became NEAR Protocol. They were visionaries ahead of their time and, although AI took several more years before becoming a viable product, the experience of scaling databases would later prove valuable and applicable in blockchain world. As a result, NEAR Protocol is one of the first blockchains to implement execution layer sharding, asynchronous execution and stateless validation, bringing the finality time down to 1.2 seconds, with a block time of 0.6 seconds. Don't forget to RT & follow Epicenter Podcast! Topics discussed in this episode: 0:00 - Introduction 3:30 - Bowen’s background 4:47 - Near’s pivot from AI to blockchains 8:26 - The role of Near One 9:13 - Near’s tech stack upgrades 13:39 - Optimizing network architecture 17:08 - Stateless validation & block propagation 21:10 - Sharding & asynchronous execution 29:12 - Message passing between shards & shard ‘equality’ 35:51 - Challenges of implementing stateless validation 41:05 - Applications benefiting from Near’s finality speed 44:18 - Intent-based infrastructure 47:10 - AI use cases on Near 52:27 - Expanding Near’s ecosystem 54:43 - Development challenges 57:55 - Near’s vision and goals

Epicenter Podcast

66,601 views • 1 year ago

Build uncompromising high-performance, high-fidelity apps with React. What you see is not the Apple Messages app, nor is it meant to be 1:1. Rather it serves as an aspirational and real example of UI/UX that is possible. Every detail from the bubble animations to keyboard gestures to scroll view insets and safe areas to parallax timestamps required care and attention. Quality UIs come from caring hard. The little chat bubble tails that morph away when the next message animates in. Timestamps that scroll at a different rate than the bubbles. Peek gestures powered by UIKit that lift a chat bubble, tail and all, with a gentle haptic pulse. The subtle shadow of the text composer and responsively sliding down the keyboard in pixel-perfect concert. The composer shrinking its width to fit iPhone’s rounded bezel. The beautiful Liquid Glass refractions have the level of glassiness chosen by the user (new in iOS 27). Scroll view insets that adjust to fit the home bar and keyboard dynamically, creating a sense of depth as the chat bubbles are slightly visible as they scroll under the keyboard. Keeping the keyboard on screen if the prior screen already presented it. Sliding the keyboard and composer with the screen when the user drags to navigate back. I am excited to explore using the new iPhone Duo view controllers natively with React when the time comes. There is always room for innovation and improvement. This chat demo runs at 120 FPS on iOS 27 even on my phone that’s four versions old now. There are several approaches to high-performance lists. I explored a new Expo scroll view that uses the native gesture systems along with react-native’s VirtualView (codenamed “Fling” to reflect the speed of flinging a scroll view), which Meta’s React team designed to prioritize scroll momentum with React’s scheduler. There are tradeoffs with other scroll strategies for how the scroll views gracefully degrade, and they can be swapped out based on what’s best for your app’s use case. And, by virtue of using modern React, high-priority events like user gestures can preempt lower-priority ones like a network response. Let us dispel any myth that using React requires compromising on beautiful, smooth, user-friendly UI/UX that Uses the Platform. Let us dispel any myth frame-perfect UI coordination is not achievable. The Hermes thread and the UI thread can coordinate when needed, like for controlled text inputs. Let us dispel any myth that React Native’s performance is impacted by a bridge, let alone has a bridge. Bridgeless JSI and the Fabric renderer are here for apps that use the New Architecture. What about Android? The app runs and I’ll share a screenshot from my cloud agent’s emulator. With some attention to detail dedicated to Android I’m confident crafted UX is attainable. I’ve spent my tokens once and have a structural head start everywhere. One more thing! Most of this chat’s application code is written with , , , and other familiar elements. The styling is mostly CSS, including linear-gradient(), background-attachment: fixed, and semantic platform colors that adapt to dark mode. Not just appearance - CSS Animations and CSS Transitions run entirely natively. There are a handful of custom native components written in Swift and Kotlin, like the chat bubbles and a custom CAShapeLayer and UIBezierPath for the tails. Native coding is a first-class feature. The way to think about building beautiful apps this way is React and Native, not React vs. Native. Aspire high and raise your ambitions for what is possible!
2:49

Build uncompromising high-performance, high-fidelity apps with React. What you see is not the Apple Messages app, nor is it meant to be 1:1. Rather it serves as an aspirational and real example of UI/UX that is possible. Every detail from the bubble animations to keyboard gestures to scroll view insets and safe areas to parallax timestamps required care and attention. Quality UIs come from caring hard. The little chat bubble tails that morph away when the next message animates in. Timestamps that scroll at a different rate than the bubbles. Peek gestures powered by UIKit that lift a chat bubble, tail and all, with a gentle haptic pulse. The subtle shadow of the text composer and responsively sliding down the keyboard in pixel-perfect concert. The composer shrinking its width to fit iPhone’s rounded bezel. The beautiful Liquid Glass refractions have the level of glassiness chosen by the user (new in iOS 27). Scroll view insets that adjust to fit the home bar and keyboard dynamically, creating a sense of depth as the chat bubbles are slightly visible as they scroll under the keyboard. Keeping the keyboard on screen if the prior screen already presented it. Sliding the keyboard and composer with the screen when the user drags to navigate back. I am excited to explore using the new iPhone Duo view controllers natively with React when the time comes. There is always room for innovation and improvement. This chat demo runs at 120 FPS on iOS 27 even on my phone that’s four versions old now. There are several approaches to high-performance lists. I explored a new Expo scroll view that uses the native gesture systems along with react-native’s VirtualView (codenamed “Fling” to reflect the speed of flinging a scroll view), which Meta’s React team designed to prioritize scroll momentum with React’s scheduler. There are tradeoffs with other scroll strategies for how the scroll views gracefully degrade, and they can be swapped out based on what’s best for your app’s use case. And, by virtue of using modern React, high-priority events like user gestures can preempt lower-priority ones like a network response. Let us dispel any myth that using React requires compromising on beautiful, smooth, user-friendly UI/UX that Uses the Platform. Let us dispel any myth frame-perfect UI coordination is not achievable. The Hermes thread and the UI thread can coordinate when needed, like for controlled text inputs. Let us dispel any myth that React Native’s performance is impacted by a bridge, let alone has a bridge. Bridgeless JSI and the Fabric renderer are here for apps that use the New Architecture. What about Android? The app runs and I’ll share a screenshot from my cloud agent’s emulator. With some attention to detail dedicated to Android I’m confident crafted UX is attainable. I’ve spent my tokens once and have a structural head start everywhere. One more thing! Most of this chat’s application code is written with , , , and other familiar elements. The styling is mostly CSS, including linear-gradient(), background-attachment: fixed, and semantic platform colors that adapt to dark mode. Not just appearance - CSS Animations and CSS Transitions run entirely natively. There are a handful of custom native components written in Swift and Kotlin, like the chat bubbles and a custom CAShapeLayer and UIBezierPath for the tails. Native coding is a first-class feature. The way to think about building beautiful apps this way is React and Native, not React vs. Native. Aspire high and raise your ambitions for what is possible!

James Ide

139,599 views • 12 days ago

What's next for OpenTUI? Here's a technical write-up. Over the last few months OpenTUI gained a lot of stability improvements, new unnecessary but fun features like live audio streaming, and useful features like rendering to the scrollback buffer mixed with a live TUI, called footer mode. Overall the feature set enables building large and complex applications. React and Solid make it super simple and convenient. There is still so much to do though. Three big milestones we have set out to achieve are: - Moving most of the behavioural logic currently living in TypeScript down to the native Zig core - Node compatibility - Optimizing the hell out of primitives like text rendering The render tree mechanisms are currently only usable from TypeScript. Think of the DOM, but controllable like a scene graph. Elements in the render tree are called renderables. They can expose a render method to draw themselves. All renderables are derived from a BaseRenderable. Renderables and the render tree will become native primitives. Building blocks usable from any language bindings. Reducing the TypeScript bindings to a very thin layer, with all the behavioural logic living in the native binary. Moving this down is not just a matter of porting TypeScript classes to Zig. TypeScript currently owns the tree, dirty-state propagation, layout reads, culling, and render ordering. If it still has to walk every node and call into native code for each step, we keep most of the complexity and add FFI overhead. Whole passes and their state need to move together. We took a big step towards this recently by building yoga-layout into the native binary. It exposes part of the official yoga-layout TypeScript package via FFI. Only the API surface that is actually used by OpenTUI. Covered by the test suite of the original yoga-layout package. This already gave a median speedup of ~2.5x, and up to 30x for narrow scenarios. The yoga-layout integration is useful beyond the speedup. Built-in text and editor measurement can now happen entirely in native code during layout instead of calling back into JavaScript. I ran an experiment last month taking this even further, having GPT 5.6 port yoga-layout from C++ to Zig, which gave extremely good results. It would be a burden to maintain right now though, so that's off the table for now. I might come back to it. Simon Klee is working relentlessly on Node compatibility and already has a full Node version of OpenCode running. Node got FFI support in v26.4.0, thanks to help from the Node community, namely Matteo Collina and Paolo Insogna. Behaviour and interfaces seem similar between Node and Bun, but there are some major differences. To get the best performance out of the Node FFI implementation, its usage has to follow some rules. Node has three ways to call native functions: the generic C++/libffi path, the SharedBuffer path, and the V8 Fast API. The generic path converts every argument in Node's C++ layer and then calls the function through libffi. It is flexible, but also the slowest option for frequently called functions. The SharedBuffer path is a middle ground. JavaScript writes scalar values and BigInt pointers into a small per-function buffer, reducing some conversion work. The actual native call still goes through libffi though. Typed arrays used as pointers cannot be packed into this buffer and fall back to the generic path. The path we really want is the V8 Fast API. Node generates a small machine-code trampoline for the exact function signature, allowing optimized JavaScript to call the native function without going through the generic converter or libffi. This only applies to JavaScript-to-native calls. Callbacks from native code into JavaScript still use libffi closures. Getting onto this path is quite strict. A signature can have at most eight arguments and everything must fit into CPU registers. x86-64 Unix systems have room for six GP (general-purpose) and eight FP (floating-point) arguments. AArch64 has room for seven GP and eight FP arguments. Anything that spills onto the stack falls back to a slower path. These are Node fast-path restrictions, not general FFI restrictions. Bun also does not support passing structs by value through its current FFI API. OpenTUI uses bun-ffi-structs to pack ABI-aligned struct data into an ArrayBuffer and passes a pointer instead. Despite the name, the package also works with Node. Pointers need some care too. Typed arrays and ArrayBuffers normally have to be resolved into BigInt addresses first. Eligible functions with exactly one pointer argument get another Fast API entrypoint that can extract the address directly from the buffer. An eligible signature is still not enough. V8 has to optimize a direct call with a fixed number of consistently typed arguments. Wrappers that collect arguments and forward them using spread or Reflect.apply can hide that call shape and keep the function on a slower path. The practical rules are: keep hot signatures within register limits, use direct fixed-arity calls with stable argument types, reuse owned buffers safely, and batch small operations. Then measure the real call site, because eligibility only makes a function fast-capable. We have to design the ABI around these constraints where it makes sense and gives the expected performance improvement. The third big area is text rendering. Today a Text renderable accepts a string, StyledText, or a tree of TextNodes. Before rendering, the TextNode tree is walked and flattened into styled chunks. Those chunks are packed in TypeScript, sent through FFI, copied into a native TextBuffer, and stored in a rope. Styles are represented separately as highlights. A TextBufferView then wraps the rope into visual lines, which are drawn into the visible buffer. This works, but updates are much more expensive than they should be. setStyledText effectively throws away and rebuilds the rope, copies and reparses all text and recreates the style highlights. Changing one TextNode also walks and flattens the complete tree before going through this path again. Text and style segments should instead live directly in the rope and support incremental replacement. Memory ownership is split between retained JavaScript buffers, the native memory registry, rope arenas, wrapping caches, styled-text storage, and highlights. Different operations preserve or reset different parts of that state. This is hard to reason about and can retain memory for much longer than expected. Text storage needs clearer ownership, with fewer lifetimes split across JavaScript and native code. The public API reflects the same split. The t template literal is convenient, but creates another intermediate chunk representation that is mutable, not cached, and not merged. Text also maintains both StyledText content and a special TextNode tree, which do not compose properly. TextNode is only a style scope, not a normal layout primitive, so Text renderables cannot naturally compose inside each other. I think this should become one Text primitive backed directly by rope segments. The template literal API might disappear or become a very thin helper around those native segments. Editing has another temporary layer in TypeScript. Extmarks currently monkey-patch editing operations, scan and adjust all marks after changes, maintain their own undo state, and recreate native highlights. They should become native marks anchored directly in the rope. A proper mark tree, similar to Neovim's marktree, could update marks together with edits, undo, and redo, and provide the foundation for highlights and concealment. Text wrapping has also become too complex. Supporting CJK, emoji, combining characters, ZWJ sequences, tabs, and different terminal width rules currently mixes byte offsets, grapheme indexes, and display-cell columns across several custom algorithms. Dirty views rewrap the complete document. Measurement and drawing can repeat some of the same work. The wrapping implementation needs an overhaul, but the exact shape is still open. The goal is to make Unicode handling easier to maintain, avoid repeated full-document work, and clearly separate byte offsets, graphemes, and terminal display cells. None of this will happen as one big rewrite. We will replace pieces when we understand the problem well enough and when the result is clearly simpler, faster, or more useful. To achieve all of this we might break public interfaces. Thanks to OpenCode and a lot of good models, migration to a new version with breaking changes mostly is not an issue anymore. What do you want to see next for OpenTUI?
0:57

What's next for OpenTUI? Here's a technical write-up. Over the last few months OpenTUI gained a lot of stability improvements, new unnecessary but fun features like live audio streaming, and useful features like rendering to the scrollback buffer mixed with a live TUI, called footer mode. Overall the feature set enables building large and complex applications. React and Solid make it super simple and convenient. There is still so much to do though. Three big milestones we have set out to achieve are: - Moving most of the behavioural logic currently living in TypeScript down to the native Zig core - Node compatibility - Optimizing the hell out of primitives like text rendering The render tree mechanisms are currently only usable from TypeScript. Think of the DOM, but controllable like a scene graph. Elements in the render tree are called renderables. They can expose a render method to draw themselves. All renderables are derived from a BaseRenderable. Renderables and the render tree will become native primitives. Building blocks usable from any language bindings. Reducing the TypeScript bindings to a very thin layer, with all the behavioural logic living in the native binary. Moving this down is not just a matter of porting TypeScript classes to Zig. TypeScript currently owns the tree, dirty-state propagation, layout reads, culling, and render ordering. If it still has to walk every node and call into native code for each step, we keep most of the complexity and add FFI overhead. Whole passes and their state need to move together. We took a big step towards this recently by building yoga-layout into the native binary. It exposes part of the official yoga-layout TypeScript package via FFI. Only the API surface that is actually used by OpenTUI. Covered by the test suite of the original yoga-layout package. This already gave a median speedup of ~2.5x, and up to 30x for narrow scenarios. The yoga-layout integration is useful beyond the speedup. Built-in text and editor measurement can now happen entirely in native code during layout instead of calling back into JavaScript. I ran an experiment last month taking this even further, having GPT 5.6 port yoga-layout from C++ to Zig, which gave extremely good results. It would be a burden to maintain right now though, so that's off the table for now. I might come back to it. Simon Klee is working relentlessly on Node compatibility and already has a full Node version of OpenCode running. Node got FFI support in v26.4.0, thanks to help from the Node community, namely Matteo Collina and Paolo Insogna. Behaviour and interfaces seem similar between Node and Bun, but there are some major differences. To get the best performance out of the Node FFI implementation, its usage has to follow some rules. Node has three ways to call native functions: the generic C++/libffi path, the SharedBuffer path, and the V8 Fast API. The generic path converts every argument in Node's C++ layer and then calls the function through libffi. It is flexible, but also the slowest option for frequently called functions. The SharedBuffer path is a middle ground. JavaScript writes scalar values and BigInt pointers into a small per-function buffer, reducing some conversion work. The actual native call still goes through libffi though. Typed arrays used as pointers cannot be packed into this buffer and fall back to the generic path. The path we really want is the V8 Fast API. Node generates a small machine-code trampoline for the exact function signature, allowing optimized JavaScript to call the native function without going through the generic converter or libffi. This only applies to JavaScript-to-native calls. Callbacks from native code into JavaScript still use libffi closures. Getting onto this path is quite strict. A signature can have at most eight arguments and everything must fit into CPU registers. x86-64 Unix systems have room for six GP (general-purpose) and eight FP (floating-point) arguments. AArch64 has room for seven GP and eight FP arguments. Anything that spills onto the stack falls back to a slower path. These are Node fast-path restrictions, not general FFI restrictions. Bun also does not support passing structs by value through its current FFI API. OpenTUI uses bun-ffi-structs to pack ABI-aligned struct data into an ArrayBuffer and passes a pointer instead. Despite the name, the package also works with Node. Pointers need some care too. Typed arrays and ArrayBuffers normally have to be resolved into BigInt addresses first. Eligible functions with exactly one pointer argument get another Fast API entrypoint that can extract the address directly from the buffer. An eligible signature is still not enough. V8 has to optimize a direct call with a fixed number of consistently typed arguments. Wrappers that collect arguments and forward them using spread or Reflect.apply can hide that call shape and keep the function on a slower path. The practical rules are: keep hot signatures within register limits, use direct fixed-arity calls with stable argument types, reuse owned buffers safely, and batch small operations. Then measure the real call site, because eligibility only makes a function fast-capable. We have to design the ABI around these constraints where it makes sense and gives the expected performance improvement. The third big area is text rendering. Today a Text renderable accepts a string, StyledText, or a tree of TextNodes. Before rendering, the TextNode tree is walked and flattened into styled chunks. Those chunks are packed in TypeScript, sent through FFI, copied into a native TextBuffer, and stored in a rope. Styles are represented separately as highlights. A TextBufferView then wraps the rope into visual lines, which are drawn into the visible buffer. This works, but updates are much more expensive than they should be. setStyledText effectively throws away and rebuilds the rope, copies and reparses all text and recreates the style highlights. Changing one TextNode also walks and flattens the complete tree before going through this path again. Text and style segments should instead live directly in the rope and support incremental replacement. Memory ownership is split between retained JavaScript buffers, the native memory registry, rope arenas, wrapping caches, styled-text storage, and highlights. Different operations preserve or reset different parts of that state. This is hard to reason about and can retain memory for much longer than expected. Text storage needs clearer ownership, with fewer lifetimes split across JavaScript and native code. The public API reflects the same split. The t template literal is convenient, but creates another intermediate chunk representation that is mutable, not cached, and not merged. Text also maintains both StyledText content and a special TextNode tree, which do not compose properly. TextNode is only a style scope, not a normal layout primitive, so Text renderables cannot naturally compose inside each other. I think this should become one Text primitive backed directly by rope segments. The template literal API might disappear or become a very thin helper around those native segments. Editing has another temporary layer in TypeScript. Extmarks currently monkey-patch editing operations, scan and adjust all marks after changes, maintain their own undo state, and recreate native highlights. They should become native marks anchored directly in the rope. A proper mark tree, similar to Neovim's marktree, could update marks together with edits, undo, and redo, and provide the foundation for highlights and concealment. Text wrapping has also become too complex. Supporting CJK, emoji, combining characters, ZWJ sequences, tabs, and different terminal width rules currently mixes byte offsets, grapheme indexes, and display-cell columns across several custom algorithms. Dirty views rewrap the complete document. Measurement and drawing can repeat some of the same work. The wrapping implementation needs an overhaul, but the exact shape is still open. The goal is to make Unicode handling easier to maintain, avoid repeated full-document work, and clearly separate byte offsets, graphemes, and terminal display cells. None of this will happen as one big rewrite. We will replace pieces when we understand the problem well enough and when the result is clearly simpler, faster, or more useful. To achieve all of this we might break public interfaces. Thanks to OpenCode and a lot of good models, migration to a new version with breaking changes mostly is not an issue anymore. What do you want to see next for OpenTUI?

kmdr

31,132 views • 2 months ago

The Solana TCG scene is getting crowded, so I dug through it and made a curated map. 🎴 Bookmark this if you’re into packs, cards and onchain collectibles. Core Solana first 👇 • Collector Crypt One of the main infrastructure layers for tokenized TCG on Solana. Vaulted graded cards, digital packs, instant sellback, physical redemption and onchain ownership. • Gacha A dedicated pack-ripping platform for graded cards. Digital packs, real collectibles and global redemption, with a clean consumer experience. • gachasports Sports cards meet pack ripping. Powered by Collector Crypt, but focused on real sports collectibles instead of the usual Pokémon/One Piece angle. • phygitals Physical collectibles connected to digital ownership. Cards and other real assets become easier to trade, track and move through crypto rails. • Artifacte A broader collectibles and RWA project. Cards are part of the picture, but the angle extends into luxury collectibles and gacha-style mechanics powered by Collector Crypt. • BONKUJI An onchain oripa-style project for Pokémon/One Piece grails. The distinctive part is the connection to the wider BONK brand and culture, which makes it feel very native to Solana. • Token Rips Not really TCG, but worth including for the pack mechanic. Instead of opening packs for cards, users open packs for Solana tokens. Same “rip and reveal” behavior, different prize layer. • PokeRescue A Pokémon-focused collector tool around graded cards and NFTs. More about discovery, alerts and finding opportunities than classic pack ripping. • CollectorRoll 1v1 Pokémon pack battles on Solana. Two players open packs against each other, and the best pull wins the pot. • Slabz A Solana collectibles arcade. Games, packs and real cards, with more going on after the initial rip. • dm.fun A broader Solana consumer app with pack ripping inside. Chat, trade, meme, predict and open Pokémon packs in the same app. • Rosentica: One Arena A gameplay layer for TCG collectors. Online battles with real-world TCG cards, built with MagicBlock and powered by Collector Crypt. • TheCollectorGroup Live pack ripping with a Solana-native feel. Buy, queue, watch the rip on stream, then view or redeem cards through the site. • Pull.Fun Graded slabs with verifiable odds. Inventory-backed pulls, instant settlement and trade/redeem mechanics. • RipRip.io A straightforward digital-to-physical pack model on Solana. Open packs online, then ship or redeem the real cards. • Solflare - The Solana Wallet - Not a TCG project but Solflare Packs matters because it brings pack opening directly inside a crypto wallet (powered by Collector Crypt) Multi-chain and Solana-supported 👇 • Packy.GG A multi-chain pack platform for Pokémon/One Piece collectibles. Packs, races, battles, raffles, buybacks, withdrawals and SOL support. • Beezie A tokenized collectibles marketplace expanding into Solana. The arcade angle stands out: claw machines, transparent odds, authenticated collectibles and redemption. • DYLI A broader collectibles platform. Collect digitally, own physically, ship globally. More marketplace/infrastructure than pure TCG app. • Shiny A broader collectibles and entertainment platform. Less focused on one mechanic, more on the collector experience around cards and related assets. • Monster A trading card collecting platform with an active pack-opening experience. Focused on making trading cards easier and more fun to collect online. • Grailed Digital packs and pack battles around collectible cards. The focus is on opening packs, competing with others and shipping the real cards. • Verity A premium collectibles platform with provable ownership. Still early, but already experimenting with gacha-style drops and physical collectible ownership. Which one have you tried? And which one caught your attention the most and why?
0:24

The Solana TCG scene is getting crowded, so I dug through it and made a curated map. 🎴 Bookmark this if you’re into packs, cards and onchain collectibles. Core Solana first 👇 • Collector Crypt One of the main infrastructure layers for tokenized TCG on Solana. Vaulted graded cards, digital packs, instant sellback, physical redemption and onchain ownership. • Gacha A dedicated pack-ripping platform for graded cards. Digital packs, real collectibles and global redemption, with a clean consumer experience. • gachasports Sports cards meet pack ripping. Powered by Collector Crypt, but focused on real sports collectibles instead of the usual Pokémon/One Piece angle. • phygitals Physical collectibles connected to digital ownership. Cards and other real assets become easier to trade, track and move through crypto rails. • Artifacte A broader collectibles and RWA project. Cards are part of the picture, but the angle extends into luxury collectibles and gacha-style mechanics powered by Collector Crypt. • BONKUJI An onchain oripa-style project for Pokémon/One Piece grails. The distinctive part is the connection to the wider BONK brand and culture, which makes it feel very native to Solana. • Token Rips Not really TCG, but worth including for the pack mechanic. Instead of opening packs for cards, users open packs for Solana tokens. Same “rip and reveal” behavior, different prize layer. • PokeRescue A Pokémon-focused collector tool around graded cards and NFTs. More about discovery, alerts and finding opportunities than classic pack ripping. • CollectorRoll 1v1 Pokémon pack battles on Solana. Two players open packs against each other, and the best pull wins the pot. • Slabz A Solana collectibles arcade. Games, packs and real cards, with more going on after the initial rip. • dm.fun A broader Solana consumer app with pack ripping inside. Chat, trade, meme, predict and open Pokémon packs in the same app. • Rosentica: One Arena A gameplay layer for TCG collectors. Online battles with real-world TCG cards, built with MagicBlock and powered by Collector Crypt. • TheCollectorGroup Live pack ripping with a Solana-native feel. Buy, queue, watch the rip on stream, then view or redeem cards through the site. • Pull.Fun Graded slabs with verifiable odds. Inventory-backed pulls, instant settlement and trade/redeem mechanics. • RipRip.io A straightforward digital-to-physical pack model on Solana. Open packs online, then ship or redeem the real cards. • Solflare - The Solana Wallet - Not a TCG project but Solflare Packs matters because it brings pack opening directly inside a crypto wallet (powered by Collector Crypt) Multi-chain and Solana-supported 👇 • Packy.GG A multi-chain pack platform for Pokémon/One Piece collectibles. Packs, races, battles, raffles, buybacks, withdrawals and SOL support. • Beezie A tokenized collectibles marketplace expanding into Solana. The arcade angle stands out: claw machines, transparent odds, authenticated collectibles and redemption. • DYLI A broader collectibles platform. Collect digitally, own physically, ship globally. More marketplace/infrastructure than pure TCG app. • Shiny A broader collectibles and entertainment platform. Less focused on one mechanic, more on the collector experience around cards and related assets. • Monster A trading card collecting platform with an active pack-opening experience. Focused on making trading cards easier and more fun to collect online. • Grailed Digital packs and pack battles around collectible cards. The focus is on opening packs, competing with others and shipping the real cards. • Verity A premium collectibles platform with provable ownership. Still early, but already experimenting with gacha-style drops and physical collectible ownership. Which one have you tried? And which one caught your attention the most and why?

Sailor

22,391 views • 3 months ago

⛵️💎⛵️💎Zebec Network $ZBCN~2️⃣0️⃣2️⃣6️⃣ Synopsis~Prediction🚀🌍 By 2️⃣0️⃣2️⃣6️⃣, Zebec Network is positioned to be one of the most advanced real~time payment and payroll infrastructures in crypto and fintech. What started as a streaming~payments protocol has evolved into a full~stack financial rails provider + consumer~facing Super App: 💳📲🏦 🔴 Real~time payroll (second-by-second settlement) 🔵 On~chain + card-based payments ⚫ Enterprise~grade payroll APIs 🔴 Stablecoin~native settlement layer 🔵 ISO 20022~aligned financial messaging ⚫ Compliance~first global architecture 🔴 Zebec Super App, all~in~one payroll, spending, cards, crypto & banking hub 🔵 Self~custody + compliant fintech UX ⚫ Designed for employees, freelancers & enterprises With partnerships and integrations across: 🔴 NatPay. ACH + U.S. banking rails 🔵 World Liberty Financial, Stablecoin & RWA ecosystem ⚫ XRP / XRPL, liquidity corridors 🔴 SWIFT compatibility via ISO 20022 standards 🔵 Card networks & fintech payment providers ⚫ Enterprise payroll platforms Zebec is no longer just crypto payroll. It is becoming financial infrastructure + a global financial Super App. How High Can Zebec Network Go? 📈 Conservative scenario, Fintech niche adoption 🔴 Market cap: $3B ~$6B 🔵 ZBCN price: $0.30 ~$0.60 ⚫ Focus: crypto companies + startups Strong execution scenario, Global fintech rails + Super App adoption 🔴 Market cap: $8B ~$15B 🔵 ZBCN price: $0.80 ~ $1.50 ⚫ Focus: enterprises + freelancers + cross~border payroll Full breakout scenario, Institutional + consumer financial layer 🔴 Market cap: $20B+ 🔵 ZBCN price: $2.00+ ⚫ Focus: banks, governments, global payroll processors, millions of users via Super App Why the Market Is Watching Zebec 👀 🔴 Payroll = trillion~dollar industry 🔵 Cross~border payments are broken ⚫ ISO 20022 is becoming the global standard 🔴 Stablecoins replacing legacy settlement 🔵 Institutions demand compliant blockchain rails ⚫ Consumers want simple all~in~one financial apps 🔴 Super App = daily usage + sticky ecosystem 🔵 Real utility drives real token demand ⚫ Zebec sits at the intersection of all of it Bottom Line👌 Zebec in 2️⃣0️⃣2️⃣6️⃣ becomes: 🔴 Payroll infrastructure 💼 🔵 Payment rails 🌐 ⚫ Consumer Super App 📲 🔴 Stablecoin settlement layer 🪙 🔵 Institutional compliance network 🏛️ All inside one ecosystem ⚙️🌍 From crypto project ➡️ Global Financial Operating System Zebec Network. 🔥🚀💎 THIS IS NOW FINANCIAL ADVICE 😎📈 Zebec Network Donald J. Trump WLFI Eric Trump Donald Trump Jr. ⁿᵉʷˢ Barron Trump 🇺🇸 Bo Hines Brad Garlinghouse BlackRock Nacha Uphold Zach Witkoff Warren Buffett Grant Cardone Bitcoin Stellar Cardano Foundation Ripple Solana Swift Algorand Foundation
0:21

⛵️💎⛵️💎Zebec Network $ZBCN~2️⃣0️⃣2️⃣6️⃣ Synopsis~Prediction🚀🌍 By 2️⃣0️⃣2️⃣6️⃣, Zebec Network is positioned to be one of the most advanced real~time payment and payroll infrastructures in crypto and fintech. What started as a streaming~payments protocol has evolved into a full~stack financial rails provider + consumer~facing Super App: 💳📲🏦 🔴 Real~time payroll (second-by-second settlement) 🔵 On~chain + card-based payments ⚫ Enterprise~grade payroll APIs 🔴 Stablecoin~native settlement layer 🔵 ISO 20022~aligned financial messaging ⚫ Compliance~first global architecture 🔴 Zebec Super App, all~in~one payroll, spending, cards, crypto & banking hub 🔵 Self~custody + compliant fintech UX ⚫ Designed for employees, freelancers & enterprises With partnerships and integrations across: 🔴 NatPay. ACH + U.S. banking rails 🔵 World Liberty Financial, Stablecoin & RWA ecosystem ⚫ XRP / XRPL, liquidity corridors 🔴 SWIFT compatibility via ISO 20022 standards 🔵 Card networks & fintech payment providers ⚫ Enterprise payroll platforms Zebec is no longer just crypto payroll. It is becoming financial infrastructure + a global financial Super App. How High Can Zebec Network Go? 📈 Conservative scenario, Fintech niche adoption 🔴 Market cap: $3B ~$6B 🔵 ZBCN price: $0.30 ~$0.60 ⚫ Focus: crypto companies + startups Strong execution scenario, Global fintech rails + Super App adoption 🔴 Market cap: $8B ~$15B 🔵 ZBCN price: $0.80 ~ $1.50 ⚫ Focus: enterprises + freelancers + cross~border payroll Full breakout scenario, Institutional + consumer financial layer 🔴 Market cap: $20B+ 🔵 ZBCN price: $2.00+ ⚫ Focus: banks, governments, global payroll processors, millions of users via Super App Why the Market Is Watching Zebec 👀 🔴 Payroll = trillion~dollar industry 🔵 Cross~border payments are broken ⚫ ISO 20022 is becoming the global standard 🔴 Stablecoins replacing legacy settlement 🔵 Institutions demand compliant blockchain rails ⚫ Consumers want simple all~in~one financial apps 🔴 Super App = daily usage + sticky ecosystem 🔵 Real utility drives real token demand ⚫ Zebec sits at the intersection of all of it Bottom Line👌 Zebec in 2️⃣0️⃣2️⃣6️⃣ becomes: 🔴 Payroll infrastructure 💼 🔵 Payment rails 🌐 ⚫ Consumer Super App 📲 🔴 Stablecoin settlement layer 🪙 🔵 Institutional compliance network 🏛️ All inside one ecosystem ⚙️🌍 From crypto project ➡️ Global Financial Operating System Zebec Network. 🔥🚀💎 THIS IS NOW FINANCIAL ADVICE 😎📈 Zebec Network Donald J. Trump WLFI Eric Trump Donald Trump Jr. ⁿᵉʷˢ Barron Trump 🇺🇸 Bo Hines Brad Garlinghouse BlackRock Nacha Uphold Zach Witkoff Warren Buffett Grant Cardone Bitcoin Stellar Cardano Foundation Ripple Solana Swift Algorand Foundation

AlphaLion

11,805 views • 8 months ago

This is why Nebius will be a trillion dollar hyperscaler (Save this). Nebius is not building another GPU rental shop but rather building a vertically integrated hyperscaler that owns everything from the physical data center, to the server rack hardware it designs in house, to the software stack, to the inference delivery layer. Nearly every other neocloud is essentially a reseller of someone else's infrastructure but Nebius owns the full stack end to end and that distinction is the entire thesis. Here is why vertical integration is the winning architecture for the inference era. AWS and Azure were architected for general purpose computing and every AI workload they run sits on top of infrastructure that was never designed for it, patched, adapted and optimized after the fact. Nebius was built from day one specifically for AI which means every layer of the stack is purpose built and co optimized. The rack design, the networking topology, the cooling systems and the software that orchestrates it all are engineered together as a single system rather than assembled from parts that were never meant to work together. That architectural difference compounds with every passing quarter as AI workloads grow more complex and the performance gap between purpose built and general purpose infrastructure widens. The software layer is where the real competitive moat lives. Most infrastructure companies think of software as a wrapper around hardware while Nebius thinks of software as the product with hardware as the substrate it controls. The company is building an AI native cloud platform where the software layer handles model serving, inference optimization, fine tuning pipelines and developer tooling as first-class primitives. This matters because inference efficiency is almost entirely a software problem. Two companies running identical GPUs can deliver dramatically different performance and cost per token depending on how intelligently the software schedules, batches and routes inference requests across the cluster. Nebius is also building for a fundamental shift in how AI infrastructure gets consumed. Today, enterprise developers navigate massive cloud service catalogs spinning up clusters, managing configurations and building deep expertise in AWS or GCP-specific tooling. The next generation of builders will simply provision agents to interface with infrastructure directly. Nebius is architecting its software layer for that future , one where the interface between the developer and the compute abstraction layer looks nothing like what AWS built in 2006. The entire available capacity has been sold out every quarter. And that is the best possible validation that what Nebius is building is exactly what the market needs and that the market is willing to commit at a scale that makes the current valuation look like the beginning of a much longer story. Long Nebius and make sure to follow me Melvin for more overlooked AI stocks.
4:44

This is why Nebius will be a trillion dollar hyperscaler (Save this). Nebius is not building another GPU rental shop but rather building a vertically integrated hyperscaler that owns everything from the physical data center, to the server rack hardware it designs in house, to the software stack, to the inference delivery layer. Nearly every other neocloud is essentially a reseller of someone else's infrastructure but Nebius owns the full stack end to end and that distinction is the entire thesis. Here is why vertical integration is the winning architecture for the inference era. AWS and Azure were architected for general purpose computing and every AI workload they run sits on top of infrastructure that was never designed for it, patched, adapted and optimized after the fact. Nebius was built from day one specifically for AI which means every layer of the stack is purpose built and co optimized. The rack design, the networking topology, the cooling systems and the software that orchestrates it all are engineered together as a single system rather than assembled from parts that were never meant to work together. That architectural difference compounds with every passing quarter as AI workloads grow more complex and the performance gap between purpose built and general purpose infrastructure widens. The software layer is where the real competitive moat lives. Most infrastructure companies think of software as a wrapper around hardware while Nebius thinks of software as the product with hardware as the substrate it controls. The company is building an AI native cloud platform where the software layer handles model serving, inference optimization, fine tuning pipelines and developer tooling as first-class primitives. This matters because inference efficiency is almost entirely a software problem. Two companies running identical GPUs can deliver dramatically different performance and cost per token depending on how intelligently the software schedules, batches and routes inference requests across the cluster. Nebius is also building for a fundamental shift in how AI infrastructure gets consumed. Today, enterprise developers navigate massive cloud service catalogs spinning up clusters, managing configurations and building deep expertise in AWS or GCP-specific tooling. The next generation of builders will simply provision agents to interface with infrastructure directly. Nebius is architecting its software layer for that future , one where the interface between the developer and the compute abstraction layer looks nothing like what AWS built in 2006. The entire available capacity has been sold out every quarter. And that is the best possible validation that what Nebius is building is exactly what the market needs and that the market is willing to commit at a scale that makes the current valuation look like the beginning of a much longer story. Long Nebius and make sure to follow me Melvin for more overlooked AI stocks.

Melvin

34,306 views • 2 months ago

been diving deep into Solstice lately...and honestly, this feels like the next stage of defi evolution on solana !! i actually spent 6+ hours researching and breaking it all down in a full detailed video > from how usx works to the ai-powered yieldvault, staking architecture, and why solstice might change the solana defi landscape. here’s what makes it stand out 👇 ================================ The Core Idea: solstice is building a self sustaining defi economy on solana, blending tradfi reliability with defi creativity. the focus? real yield, transparent onchain activity, and long term wealth creation, not hype cycles. ================================ 3 Pillars driving it all: 1. usx > solana native stablecoin fully collateralized, programmable, and scalable. more than a stablecoin, it fuels the entire solstice ecosystem. think of it as the liquidity backbone for all yield and staking strategies. 2. yieldvault > automated compounding engine ai-powered, delta-neutral strategies that generate yield in any market. capital protected, transparent, and designed for passive income. no inflated apy gimmicks. just sustainable, on-chain compounding. 3. solstice staking > institutional grade non-custodial validator network, 100% renewable energy, 99.99% uptime. over $1b in staked assets already powering solana. built for both individual stakers and large protocols. ================================ Why it matters: while most defi projects chase trends, solstice is building infrastructure that scales - for users, investors, and institutions. it’s aiming to onboard the next billion into defi by keeping things fast, clean, and reliable. ================================ How your capital grows here: • mint or hold $USX - always fully backed • deposit into yieldvault - earn stable returns through delta-neutral ai strategies • stake in the validator network - earn yield while securing solana • reinvest and compound - every token works, every second counts ================================ Key advantages: ✅ built on solana - instant txs + ultra-low fees ✅ yield from real onchain activity, not emissions ✅ cross-integrated products that reinforce each other ✅ powered by renewable energy ✅ transparent analytics + verifiable smart contracts ================================ this isn’t “degen defi” it’s infrastructure for the next wave of sustainable onchain finance. if you’re into yield, stability, and scalable defi... keep an eye on Solstice. the future of defi might just start here with xeet .
2:16

been diving deep into Solstice lately...and honestly, this feels like the next stage of defi evolution on solana !! i actually spent 6+ hours researching and breaking it all down in a full detailed video > from how usx works to the ai-powered yieldvault, staking architecture, and why solstice might change the solana defi landscape. here’s what makes it stand out 👇 ================================ The Core Idea: solstice is building a self sustaining defi economy on solana, blending tradfi reliability with defi creativity. the focus? real yield, transparent onchain activity, and long term wealth creation, not hype cycles. ================================ 3 Pillars driving it all: 1. usx > solana native stablecoin fully collateralized, programmable, and scalable. more than a stablecoin, it fuels the entire solstice ecosystem. think of it as the liquidity backbone for all yield and staking strategies. 2. yieldvault > automated compounding engine ai-powered, delta-neutral strategies that generate yield in any market. capital protected, transparent, and designed for passive income. no inflated apy gimmicks. just sustainable, on-chain compounding. 3. solstice staking > institutional grade non-custodial validator network, 100% renewable energy, 99.99% uptime. over $1b in staked assets already powering solana. built for both individual stakers and large protocols. ================================ Why it matters: while most defi projects chase trends, solstice is building infrastructure that scales - for users, investors, and institutions. it’s aiming to onboard the next billion into defi by keeping things fast, clean, and reliable. ================================ How your capital grows here: • mint or hold $USX - always fully backed • deposit into yieldvault - earn stable returns through delta-neutral ai strategies • stake in the validator network - earn yield while securing solana • reinvest and compound - every token works, every second counts ================================ Key advantages: ✅ built on solana - instant txs + ultra-low fees ✅ yield from real onchain activity, not emissions ✅ cross-integrated products that reinforce each other ✅ powered by renewable energy ✅ transparent analytics + verifiable smart contracts ================================ this isn’t “degen defi” it’s infrastructure for the next wave of sustainable onchain finance. if you’re into yield, stability, and scalable defi... keep an eye on Solstice. the future of defi might just start here with xeet .

ANNABEL❤️

14,216 views • 11 months ago

📣🤔Why Flare ☀️ announcement of tailored DeFi Money Market for #Flare native assets & #FAssets is significant? #FAsset decentralized trustless cross chain collateral system will have a tailored built for #Flare Lending and Borrowing market alongside it on #Flarenetwork 🛡️A battle tested Money Market protocol is a key foundational 🏗️cornerstone to support a robust DeFi ecosystem on #Flarenetwork Kinetic.Market☀️ is tailor built ⚒️ for Flare ☀️ ecosystem. Integrating #FAssets will provide minters ability to earn real Yield🤑with their #FAssets by lending them to Kinetic.Market☀️ decentralized money market protocol. (Based off Compound contracts with numerous enhancements) #FAsset lenders will receive interest paid by borrowers in a decentralized manner. #FAssets/#Layercake Assets & #Flare native issued ERC20 tokens +stablecoins + $wFLR will likely all be available for lending into & borrowing from the protocol Borrowers will need to maintain an over-collateralize position for their loans. Kinetic.Market☀️ is Built by the highly experienced team at Rome Blockchain Labs Inc. Labs who has built numerous successful DeFi protocols including BENQI🔺 on #Avalanche which launched in 2021 and currently has $500Mill in TVL(Total Value Locked) Along with other versions of lending protocols on Evmos, Moonbeam and more. These smart contracts are based Compound Labs and have been enhanced, battle tested, multi audited and tailor suited to each individual ecosystem. Kinetic on Flare will harness FTSO and state connector. “Kinetic’s collaboration with Rome Blockchain Labs provides the robust technological infrastructure essential for seamless operations, while WATCHPUG and @ImmunefiSecCU which will oversee the platform’s smart contract audits and bug bounty programs, respectively.” Testing will begin on Coston2 and launch on Flare ☀️ 2024 👉I will be releasing a video📽️ 6am EST that breaks it all down and includes some additional insights of what else to expect from #Kenetics impact on #FAsset system and partnership with Ēnosys , too! Revolutionary native token reward and incentive system🤑 Will we 👀 Rome Blockchain Labs Inc. Labs super cool next gen Dapp Terminal Hopefully integrated into Flare ☀️ in the future😉 2 specific things that are tell tale signs of how DeFi is maturing. I noticed in my research, the emphasize on the detailed data available from IntoTheBlock & #ChaosLabs of ECONOMIC “Risk Management” tools for previous Lending & Borrowing Protocols built by Rome Blockchain Labs Inc. 🔗👇Economic Risk Radar 👇🔗 BENQI🔺 Rome Blockchain Labs Inc. Labs 🧐 The 2nd being Kinetic.Market☀️ numerous mentions of “devising a strategy” something I have been saying for past two years once the 2nd wave of a more mature DeFi ecosystem develops and built on foundation that’s been designed on a network like Flare ☀️ that offers multiple native yield streams at the network layer. #XRPL xls30d AMM’s will bring some of that ability to native #XRP but not at the level #Flare will once #FAsset system and #Layercake are live. Harnessing #Flarenetwork FTSO price feeds, the industries most decentralized & accurate Oracle system. The fact that #Flare has this system built into the network natively with close to ~100 community and professional Data/Infrastructure providers providing continuous price feeds removes the MAJOR RISK of having to integrate an external centralized oracle system like every other lending & borrowing protocol does on other networks. Having the FTSO system embedded natively into #Flare allows for any DeFi Dapp to easily integrate FTSO price feeds directly into Dapps avoiding complex external oracle integrations Exciting times ahead for Flare ☀️ with Kinetic.Market☀️ tailor built money market alongside #Fasset System will offer numerous opportunities for users pand Devs to build 🏗️Dapps on top of 🚀🚀 🔗 📽️Sneak Peak👇#1
1:28

📣🤔Why Flare ☀️ announcement of tailored DeFi Money Market for #Flare native assets & #FAssets is significant? #FAsset decentralized trustless cross chain collateral system will have a tailored built for #Flare Lending and Borrowing market alongside it on #Flarenetwork 🛡️A battle tested Money Market protocol is a key foundational 🏗️cornerstone to support a robust DeFi ecosystem on #Flarenetwork Kinetic.Market☀️ is tailor built ⚒️ for Flare ☀️ ecosystem. Integrating #FAssets will provide minters ability to earn real Yield🤑with their #FAssets by lending them to Kinetic.Market☀️ decentralized money market protocol. (Based off Compound contracts with numerous enhancements) #FAsset lenders will receive interest paid by borrowers in a decentralized manner. #FAssets/#Layercake Assets & #Flare native issued ERC20 tokens +stablecoins + $wFLR will likely all be available for lending into & borrowing from the protocol Borrowers will need to maintain an over-collateralize position for their loans. Kinetic.Market☀️ is Built by the highly experienced team at Rome Blockchain Labs Inc. Labs who has built numerous successful DeFi protocols including BENQI🔺 on #Avalanche which launched in 2021 and currently has $500Mill in TVL(Total Value Locked) Along with other versions of lending protocols on Evmos, Moonbeam and more. These smart contracts are based Compound Labs and have been enhanced, battle tested, multi audited and tailor suited to each individual ecosystem. Kinetic on Flare will harness FTSO and state connector. “Kinetic’s collaboration with Rome Blockchain Labs provides the robust technological infrastructure essential for seamless operations, while WATCHPUG and @ImmunefiSecCU which will oversee the platform’s smart contract audits and bug bounty programs, respectively.” Testing will begin on Coston2 and launch on Flare ☀️ 2024 👉I will be releasing a video📽️ 6am EST that breaks it all down and includes some additional insights of what else to expect from #Kenetics impact on #FAsset system and partnership with Ēnosys , too! Revolutionary native token reward and incentive system🤑 Will we 👀 Rome Blockchain Labs Inc. Labs super cool next gen Dapp Terminal Hopefully integrated into Flare ☀️ in the future😉 2 specific things that are tell tale signs of how DeFi is maturing. I noticed in my research, the emphasize on the detailed data available from IntoTheBlock & #ChaosLabs of ECONOMIC “Risk Management” tools for previous Lending & Borrowing Protocols built by Rome Blockchain Labs Inc. 🔗👇Economic Risk Radar 👇🔗 BENQI🔺 Rome Blockchain Labs Inc. Labs 🧐 The 2nd being Kinetic.Market☀️ numerous mentions of “devising a strategy” something I have been saying for past two years once the 2nd wave of a more mature DeFi ecosystem develops and built on foundation that’s been designed on a network like Flare ☀️ that offers multiple native yield streams at the network layer. #XRPL xls30d AMM’s will bring some of that ability to native #XRP but not at the level #Flare will once #FAsset system and #Layercake are live. Harnessing #Flarenetwork FTSO price feeds, the industries most decentralized & accurate Oracle system. The fact that #Flare has this system built into the network natively with close to ~100 community and professional Data/Infrastructure providers providing continuous price feeds removes the MAJOR RISK of having to integrate an external centralized oracle system like every other lending & borrowing protocol does on other networks. Having the FTSO system embedded natively into #Flare allows for any DeFi Dapp to easily integrate FTSO price feeds directly into Dapps avoiding complex external oracle integrations Exciting times ahead for Flare ☀️ with Kinetic.Market☀️ tailor built money market alongside #Fasset System will offer numerous opportunities for users pand Devs to build 🏗️Dapps on top of 🚀🚀 🔗 📽️Sneak Peak👇#1

Mickey_B_Fresh☀️🪝

51,371 views • 2 years ago