Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Recreation challenge of Parse/Error 's piece. Made possible with Three.js and custom glsl shaders, running online in real-time. Live link 🔴👉 Code repo 📖👉 Code breakdown coming soon #threejs #glsl #npm #ts #nextjs

Marius Ballot

1,222 subscribers

16,762 просмотров • 2 лет назад •via X (Twitter)

#threejs #glsl #npm #ts #nextjs

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Draw GLSL flowers with your cursor! 🌺 One full-screen plane, two render targets, and a bit of shader magic Live demo & source code: Made with Three.js Hosted on CodePen.IO Special thanks to The Book of Shaders #webgl #glsl #threejs #shader #drawingtool

Draw GLSL flowers with your cursor! 🌺 One full-screen plane, two render targets, and a bit of shader magic Live demo & source code: Made with Three.js Hosted on CodePen.IO Special thanks to The Book of Shaders #webgl #glsl #threejs #shader #drawingtool

Ksenia Kondrashova

28,620 просмотров • 3 лет назад

If I had to choose one thing to do, it would be just coding WebGL flowers It's a GLSL shader, a full-screen plane, and 2 render targets to swap on each frame Live demo & source code: Made with Three.js Hosted on CodePen.IO Special thanks to The Book of Shaders

If I had to choose one thing to do, it would be just coding WebGL flowers It's a GLSL shader, a full-screen plane, and 2 render targets to swap on each frame Live demo & source code: Made with Three.js Hosted on CodePen.IO Special thanks to The Book of Shaders

Ksenia Kondrashova

51,837 просмотров • 3 лет назад

I built a custom TradingView indicator with Claude Code & Fable 5. It's called the Storm Gauge and is built off a real quant trading strategy. I open-sourced the full code on GitHub. Free to install, free to fork, yours to improve. Here's how to install a quant indicator on your TradingView chart: What it actually is The Storm Gauge is a live implementation of the GARCH model, a Nobel Prize-winning volatility framework that real quant desks run daily. It forecasts how "violent" tomorrow's market could be by combining three inputs: an asset's baseline volatility, yesterday's shock, and where volatility was already sitting before that shock happened. It doesn't predict market direction. Instead, it measures risk, in real time, on your actual chart. How to install it Method 1. Plugin command Open the GitHub repo: Find the installation section, copy the command, and paste it into Claude Code. It runs the plugin install automatically. Method 2. Manual config Open garchmethod.md in the repo, copy the entire file, and paste it into Claude Code. It fetches the skill files directly and verifies the strategy for you. (you only need one method; I'm just showing both) Getting it onto your TradingView chart Inside the repo, there's a Pine Script folder. Open it, copy the entire file. Go into TradingView's Pine Editor, paste it in, hit Enter, and refresh. That's it. The Storm Gauge now runs live on your chart as a real number. Once it's installed, just talk to it: → "What's the volatility forecast on Bitcoin?" → "Explain what the current volatility forecast means on $BTC and how it should impact my position sizing" → "Help me size my S&P500 position according to current market volatility" Does it actually work? I backtested the same EMA cross strategy two ways across 15 years of BTC data. Same entries, same exits. → Fixed position sizing: $17,957 final equity → Storm Gauge (GARCH) sizing: $21,205 final equity Fewer drawdowns, less risk, better result. Full breakdown of the entire build process in my recent article - pinned on my profile.

Miles Deutscher

56,355 просмотров • 1 месяц назад

LayerAI Works with DeepSeek to Supercharge the LayerAI Product Suite 🌐 LayerAI integrates DeepSeek by leveraging several of its features and capabilities, focusing on areas where DeepSeek's strengths align with LayerAI's objectives. 👉 Learn more about our work with DeepSeek: - Model Deployment: DeepSeek-V3 & Coder-V2 for superior code generation, debugging, and language tasks. - DeepSeek-Coder-V2: Coding in 338 languages with a 128K context for complex structures. - Efficient Inference: Enhanced performance with DeepSeek's MLA & MoE tech. - IDE Assist: Real-time coding help, error catch, and auto-complete. - GitHub Sync: Better collab with seamless version control and reviews. This integration elevates our AI tools, making coding, learning, and teamwork smarter. More:

LayerAI Works with DeepSeek to Supercharge the LayerAI Product Suite 🌐 LayerAI integrates DeepSeek by leveraging several of its features and capabilities, focusing on areas where DeepSeek's strengths align with LayerAI's objectives. 👉 Learn more about our work with DeepSeek: - Model Deployment: DeepSeek-V3 & Coder-V2 for superior code generation, debugging, and language tasks. - DeepSeek-Coder-V2: Coding in 338 languages with a 128K context for complex structures. - Efficient Inference: Enhanced performance with DeepSeek's MLA & MoE tech. - IDE Assist: Real-time coding help, error catch, and auto-complete. - GitHub Sync: Better collab with seamless version control and reviews. This integration elevates our AI tools, making coding, learning, and teamwork smarter. More:

LayerAI | AI2Earn

47,905 просмотров • 1 год назад

Still using AI tools that can’t turn your ideas into real apps? Most tools can write bits of code but fail when it’s time to actually build something complete. That’s where Replit ⠕ changes everything. I just asked Replit: “can you redesign this website in professional way.." In minutes, it built the entire website— clean design, full logic, animations, and dark/light mode included. No setup. No debugging. Just pure vibe coding. Here’s why Replit stands out 👇 ✅ Build with plain English – Describe what you want, Replit builds it. ✅ All-in-one platform – Code, AI help, hosting, database, and auth in one place. ✅ Create anywhere – Use the Replit mobile app on iOS or Android. ✅ Instant integrations – Connect to Notion, Slack, Google Drive, Dropbox, and more. ✅ From design to live app – Import from Figma and launch in minutes. No chaos. No micromanaging. Just you, your idea, and Replit doing the hard work. 👉 Try it now: 🎁 Get $10 credit when you purchase Replit Core via my link: #Replit #VibeCoding #AIApps #NoCode #BuildWithReplit #AItools #ReplitCore

Still using AI tools that can’t turn your ideas into real apps? Most tools can write bits of code but fail when it’s time to actually build something complete. That’s where Replit ⠕ changes everything. I just asked Replit: “can you redesign this website in professional way.." In minutes, it built the entire website— clean design, full logic, animations, and dark/light mode included. No setup. No debugging. Just pure vibe coding. Here’s why Replit stands out 👇 ✅ Build with plain English – Describe what you want, Replit builds it. ✅ All-in-one platform – Code, AI help, hosting, database, and auth in one place. ✅ Create anywhere – Use the Replit mobile app on iOS or Android. ✅ Instant integrations – Connect to Notion, Slack, Google Drive, Dropbox, and more. ✅ From design to live app – Import from Figma and launch in minutes. No chaos. No micromanaging. Just you, your idea, and Replit doing the hard work. 👉 Try it now: 🎁 Get $10 credit when you purchase Replit Core via my link: #Replit #VibeCoding #AIApps #NoCode #BuildWithReplit #AItools #ReplitCore

Fakhr

24,152 просмотров • 9 месяцев назад

🚨 THE ESX BLOCKCHAIN EXPLORER IS NOW LIVE! 🚨 Hey EstateX Family! 👋 Big news from the tech front! After some serious work by our incredible dev team (shoutout to our superstar CTO Graham and our design and dev team 💪), we’re thrilled to announce the launch of the initial version of the ESX Testnet Block Explorer! 🔍 What can you do with it? - Easily track transactions - Watch the ESX token price and movements in real time. - Monitor block production live - Dive into transaction data from the team and our testing partners - ⁠And much more This is just the beginning! Over the coming weeks, we’ll be rolling out even more features, making the explorer smarter, faster, and packed with insights. Oh, and stay tuned... we’ll soon be revealing the first wave of projects building on the ESX chain 👀 👉 Check it out here: Very exciting time, family!

🚨 THE ESX BLOCKCHAIN EXPLORER IS NOW LIVE! 🚨 Hey EstateX Family! 👋 Big news from the tech front! After some serious work by our incredible dev team (shoutout to our superstar CTO Graham and our design and dev team 💪), we’re thrilled to announce the launch of the initial version of the ESX Testnet Block Explorer! 🔍 What can you do with it? - Easily track transactions - Watch the ESX token price and movements in real time. - Monitor block production live - Dive into transaction data from the team and our testing partners - ⁠And much more This is just the beginning! Over the coming weeks, we’ll be rolling out even more features, making the explorer smarter, faster, and packed with insights. Oh, and stay tuned... we’ll soon be revealing the first wave of projects building on the ESX chain 👀 👉 Check it out here: Very exciting time, family!

EstateX

124,350 просмотров • 1 год назад

💬 We get asked Can I manage my strategies without clicking through the platform? ❕ Answer from a GT App Top Trader: Yes, and it’s a total game-changer. I’ve started using the GT Protocol MCP server to connect the platform directly to my AI agent. 🔸 Fast Integration Grab the MCP server from the GT Protocol GitHub and follow the repo guide, it’s a quick setup that only takes a couple of minutes. Once it’s ready, you can connect Claude, Cursor, or Claude Code to your account. Just tell your agent to authenticate, and your tokens will be saved automatically. 🔸 Trading via conversation Now, I use natural language for everything. For example, I just ask for a backtest, get the win rate in seconds, and deploy to a demo account with one command. 🔸 Instant monitoring I don't click around anymore. I just ask "What’s running right now?" to get a full breakdown of active bots and profits delivered straight into the chat. No more forms or clicking, just pure AI-driven trading! 👉 Get the MCP Server

💬 We get asked Can I manage my strategies without clicking through the platform? ❕ Answer from a GT App Top Trader: Yes, and it’s a total game-changer. I’ve started using the GT Protocol MCP server to connect the platform directly to my AI agent. 🔸 Fast Integration Grab the MCP server from the GT Protocol GitHub and follow the repo guide, it’s a quick setup that only takes a couple of minutes. Once it’s ready, you can connect Claude, Cursor, or Claude Code to your account. Just tell your agent to authenticate, and your tokens will be saved automatically. 🔸 Trading via conversation Now, I use natural language for everything. For example, I just ask for a backtest, get the win rate in seconds, and deploy to a demo account with one command. 🔸 Instant monitoring I don't click around anymore. I just ask "What’s running right now?" to get a full breakdown of active bots and profits delivered straight into the chat. No more forms or clicking, just pure AI-driven trading! 👉 Get the MCP Server

GT Protocol

36,479 просмотров • 4 месяцев назад

WORST NIGHTMARE OF CONgress COMES TRUE! HISTORIC UCC BILL ROCKS ASSAM ASSEMBLY🔥 BENGAL NEXT WITHIN 6 MTHS! TRIPURA NEXT! BJP MOVING TOWARDS PM .Narendra Modi JI'S 'DEMOGRAPHIC MISSION' IN FULL SWING IN BANGLADESH BORDERING STATES. Features of Assam UCC: 🔥Uniform rules on marriage (incl minimum age) (No Child Marriages allowed) 🔥Ban on polygamy 🔥Uniform Provisions for divorce, inheritance, and adoption 🔥Compulsory registration of marriages and live-in relationships 🔥Focus on women’s rights, child welfare, and ending practices like child marriage Explained in detail: 👉One Nation, One Rule on Marriage: Uniform marriage laws for all, including a strict minimum age to crush child marriages once and for all. 👉Polygamy BANNED: No more multiple wives – a direct death blow to regressive customs. Direct hammer on 'specific' population exploration & deliberate Demographic Composition Change. 👉Divorce, Inheritance & Adoption Overhauled: Clear, modern, and equal rules replacing chaotic personal laws. Male dominated personal laws in gutter. 👉Compulsory Registration: Every marriage and live-in relationship must be registered – ending secret exploitation. Love Jih@d hammered. 👉Women & Children First: Heavy focus on protecting women’s rights, safeguarding child welfare, and wiping out exploitative traditions. Big Exemption: Tribal communities are completely kept out to safeguard their unique customs and cultural identity. This is Assam saying loud and clear: Enough is enough. Time to end vote-bank politics, gender discrimination, and parallel legal systems. A bold, fiery step towards real equality and national integration! The battle for a Uniform Civil Code has officially begun. Assam is leading from the front. Now add flavour of Deportation of illegal Bangladeshis & Rohingyas in all 3 States and then you know why Piddis, CIA & ISI are badly hurt by BJP State Govts in all these 3 States with Modi Sarkar at Centre. (Source: Assam Legislative Assembly YT)

WORST NIGHTMARE OF CONgress COMES TRUE! HISTORIC UCC BILL ROCKS ASSAM ASSEMBLY🔥 BENGAL NEXT WITHIN 6 MTHS! TRIPURA NEXT! BJP MOVING TOWARDS PM .Narendra Modi JI'S 'DEMOGRAPHIC MISSION' IN FULL SWING IN BANGLADESH BORDERING STATES. Features of Assam UCC: 🔥Uniform rules on marriage (incl minimum age) (No Child Marriages allowed) 🔥Ban on polygamy 🔥Uniform Provisions for divorce, inheritance, and adoption 🔥Compulsory registration of marriages and live-in relationships 🔥Focus on women’s rights, child welfare, and ending practices like child marriage Explained in detail: 👉One Nation, One Rule on Marriage: Uniform marriage laws for all, including a strict minimum age to crush child marriages once and for all. 👉Polygamy BANNED: No more multiple wives – a direct death blow to regressive customs. Direct hammer on 'specific' population exploration & deliberate Demographic Composition Change. 👉Divorce, Inheritance & Adoption Overhauled: Clear, modern, and equal rules replacing chaotic personal laws. Male dominated personal laws in gutter. 👉Compulsory Registration: Every marriage and live-in relationship must be registered – ending secret exploitation. Love Jih@d hammered. 👉Women & Children First: Heavy focus on protecting women’s rights, safeguarding child welfare, and wiping out exploitative traditions. Big Exemption: Tribal communities are completely kept out to safeguard their unique customs and cultural identity. This is Assam saying loud and clear: Enough is enough. Time to end vote-bank politics, gender discrimination, and parallel legal systems. A bold, fiery step towards real equality and national integration! The battle for a Uniform Civil Code has officially begun. Assam is leading from the front. Now add flavour of Deportation of illegal Bangladeshis & Rohingyas in all 3 States and then you know why Piddis, CIA & ISI are badly hurt by BJP State Govts in all these 3 States with Modi Sarkar at Centre. (Source: Assam Legislative Assembly YT)

BhikuMhatre

104,278 просмотров • 3 месяцев назад

Introducing a new tool called "SideChannel". A secure alternative to OpenClaw. Utilizes signal for communication and has Claude integration. I built SideChannel, an open-source Signal bot that connects Claude AI to your entire development workflow. End-to-end encrypted. From your pocket. The real power is autonomous development. Send one message like "Build a REST API with auth, pagination, and tests" and SideChannel will: - Generate a full PRD with stories and atomic tasks. - Dispatch up to 10 parallel workers (each running Claude). - Independently verify every task with a separate Claude context. - Run quality gates to catch regressions - Auto-fix failures. - Send you progress updates via Signal as work completes. Every piece of code is reviewed by a separate AI context using a fail-closed security model. If it detects security issues, backdoors, or logic errors — the code gets rejected automatically. No rubber stamps. It also has memory that actually works. Conversations are stored with vector embeddings for semantic search. Claude remembers your project conventions, past decisions, and what's been tried before. It gets smarter about your codebase over time. Other things I'm proud of: - Plugin framework for extending with custom commands. - Multi-project support with per-user scoping. - Rate limiting, path validation, phone allowlist. - Git checkpoints before every task, atomic commits after. - Stale task recovery, circular dependency detection. - Works on Linux and macOS, one-command install. It also integrates into OpenAI or Grok (optional) for more Generative AI response for simple things like "Whats the weather in New York City right now?".

Introducing a new tool called "SideChannel". A secure alternative to OpenClaw. Utilizes signal for communication and has Claude integration. I built SideChannel, an open-source Signal bot that connects Claude AI to your entire development workflow. End-to-end encrypted. From your pocket. The real power is autonomous development. Send one message like "Build a REST API with auth, pagination, and tests" and SideChannel will: - Generate a full PRD with stories and atomic tasks. - Dispatch up to 10 parallel workers (each running Claude). - Independently verify every task with a separate Claude context. - Run quality gates to catch regressions - Auto-fix failures. - Send you progress updates via Signal as work completes. Every piece of code is reviewed by a separate AI context using a fail-closed security model. If it detects security issues, backdoors, or logic errors — the code gets rejected automatically. No rubber stamps. It also has memory that actually works. Conversations are stored with vector embeddings for semantic search. Claude remembers your project conventions, past decisions, and what's been tried before. It gets smarter about your codebase over time. Other things I'm proud of: - Plugin framework for extending with custom commands. - Multi-project support with per-user scoping. - Rate limiting, path validation, phone allowlist. - Git checkpoints before every task, atomic commits after. - Stale task recovery, circular dependency detection. - Works on Linux and macOS, one-command install. It also integrates into OpenAI or Grok (optional) for more Generative AI response for simple things like "Whats the weather in New York City right now?".

Dave Kennedy

49,427 просмотров • 6 месяцев назад

If you think this is just another silly demo made with AI, read this post. You might change your mind, because this demo is about MATH. What you see on the screen is not a render from Blender (obviously, it’s not that good). It’s a three.js app built with Toolcraft. Available on the web and rendered in real time(link in the comments). But Blender still has a lot to do with it. Blender has Geometry Nodes - a powerful node-based system for creating and manipulating procedural geometry. In other words, it’s math. And math is a universal language. And who do you think is pretty good at math? >>> AI. Now you can download or buy Blender files from marketplaces, and when they contain Geometry Nodes for procedural animations, objects, surfaces, or effects, you can transfer that logic to the web. Make it real-time, make it interactive. Materials are a separate story, of course. They can still suck unless you use the right tricks: PBR, HDRIs, material blending, displacement, and faked surface relief. So why is Blender important here? Blender is open source, and many tools around it are open source too. An AI trained on their code. That means it can translate the math from one environment to another quite accurately. If you’ve been struggling to reproduce some idea with AI that you had in your head or seen in some references, and it has something to do with Geometry Nodes, and you can find that idea or a close one in the Blender ecosystem - it means you can transfer it to the web. Thank me later.

If you think this is just another silly demo made with AI, read this post. You might change your mind, because this demo is about MATH. What you see on the screen is not a render from Blender (obviously, it’s not that good). It’s a three.js app built with Toolcraft. Available on the web and rendered in real time(link in the comments). But Blender still has a lot to do with it. Blender has Geometry Nodes - a powerful node-based system for creating and manipulating procedural geometry. In other words, it’s math. And math is a universal language. And who do you think is pretty good at math? >>> AI. Now you can download or buy Blender files from marketplaces, and when they contain Geometry Nodes for procedural animations, objects, surfaces, or effects, you can transfer that logic to the web. Make it real-time, make it interactive. Materials are a separate story, of course. They can still suck unless you use the right tricks: PBR, HDRIs, material blending, displacement, and faked surface relief. So why is Blender important here? Blender is open source, and many tools around it are open source too. An AI trained on their code. That means it can translate the math from one environment to another quite accurately. If you’ve been struggling to reproduce some idea with AI that you had in your head or seen in some references, and it has something to do with Geometry Nodes, and you can find that idea or a close one in the Blender ecosystem - it means you can transfer it to the web. Thank me later.

Alex Barashkov

28,300 просмотров • 1 месяц назад

How to build a viral Web3 app in an afternoon using the ChainGPT AI skill for Claude Code. No coding experience required. I built Roast My Wallet. Paste any Ethereum wallet address, get a savage AI-generated roast of your trading history, a Degen Score out of 100, an on-chain report card, and three AI-generated NFT portraits. Here's exactly how it came together. Setup (3 minutes): 🔸Install Claude Code at 🔸Run /plugin install ChainGPT-org/chaingpt-claude-skill 🔸Get an API key at 🔸Type /chaingpt and describe what you want to build What the skill actually does: The ChainGPT skill doesn't just give you starter code. It knows the entire API. Every endpoint, every parameter, every credit cost, every error code. When I asked it to build the roast feature, it knew to call the LLM endpoint, how to stream the response back to the browser in real time, and how to handle errors automatically. I didn't look up a single thing. How it works under the hood: 1. Pulls real ETH balance and transaction count from the Ethereum blockchain 2. Feeds those numbers into ChainGPT's LLM and streams the roast back live 3. Calculates a Degen Score from your tx count vs balance ratio 4. Generates a report card with letter grades across Trading, Patience, Risk, Diamond Hands, and NGMI 5. Uses the roast text to generate three custom NFT portraits in parallel via VeloGen 6. Packages everything into a downloadable PNG card ready to post 7. Every feature came from describing what I wanted: 8. "Make the API key server-side." Done. 9. "Add an animated arc gauge for the degen score." Done. 10. "Generate NFT portraits using the roast text as context." Done. I never wrote a function or debugged an API response. I described outcomes. The ChainGPT skill handled the rest. If you can describe what you want to build, you can build it. Get your API key. Install the skill. /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT AI!

How to build a viral Web3 app in an afternoon using the ChainGPT AI skill for Claude Code. No coding experience required. I built Roast My Wallet. Paste any Ethereum wallet address, get a savage AI-generated roast of your trading history, a Degen Score out of 100, an on-chain report card, and three AI-generated NFT portraits. Here's exactly how it came together. Setup (3 minutes): 🔸Install Claude Code at 🔸Run /plugin install ChainGPT-org/chaingpt-claude-skill 🔸Get an API key at 🔸Type /chaingpt and describe what you want to build What the skill actually does: The ChainGPT skill doesn't just give you starter code. It knows the entire API. Every endpoint, every parameter, every credit cost, every error code. When I asked it to build the roast feature, it knew to call the LLM endpoint, how to stream the response back to the browser in real time, and how to handle errors automatically. I didn't look up a single thing. How it works under the hood: 1. Pulls real ETH balance and transaction count from the Ethereum blockchain 2. Feeds those numbers into ChainGPT's LLM and streams the roast back live 3. Calculates a Degen Score from your tx count vs balance ratio 4. Generates a report card with letter grades across Trading, Patience, Risk, Diamond Hands, and NGMI 5. Uses the roast text to generate three custom NFT portraits in parallel via VeloGen 6. Packages everything into a downloadable PNG card ready to post 7. Every feature came from describing what I wanted: 8. "Make the API key server-side." Done. 9. "Add an animated arc gauge for the degen score." Done. 10. "Generate NFT portraits using the roast text as context." Done. I never wrote a function or debugged an API response. I described outcomes. The ChainGPT skill handled the rest. If you can describe what you want to build, you can build it. Get your API key. Install the skill. /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT AI!

ChainGPT

29,316 просмотров • 3 месяцев назад

Meta just shipped the official Ads CLI 🤯 The first time you can plug Claude Code directly into your Meta ad account without a third-party connector or (allegedly) getting your account banned. Plug it into Claude Code and Claude can pull live performance data, build dashboards, and analyze creative fatigue, all from one prompt. Here's what's possible inside Claude Code: → Pull last 30 days of campaign performance into a styled HTML dashboard → Find every ad with frequency over 3.0 or CTR drops over 20% week-over-week → Generate weekly client reports written in your brand voice → Run anomaly detection on spend, CPM, and conversions → Build creative fatigue alerts that flag dying ads before CPAs blow up The biggest difference from every third-party Meta MCP that's been floating around: This one is built and maintained by Meta themselves. Most folks running Meta ads won't touch third-party connectors because the ban risk is real. The official CLI (mostly) eliminates that. It's your token, your app, your direct connection to Meta's API. I put together the complete playbook: → The exact 15-minute setup: Meta Developer App, system user, asset assignment, token generation → 20+ prompt templates for reporting, fatigue detection, opportunity scoring, and anomaly analysis → A weekly operating cadence: Monday performance pull, Wednesday creative review, Friday exec brief → Rate limit guardrails so you don't trip Meta's automated enforcement → The 5 prompts to run first Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

35,635 просмотров • 3 месяцев назад

One year ago, our X account disappeared. No warning. No explanation. Just gone. With no way to explain what had happened, fear, uncertainty, and disbelief started to spread. People questioned what was happening. People assumed the worst. Silence filled the gaps. At the time, we didn’t even know why we’d been suspended. We attempted to create other accounts, but they were also taken down. That’s when it became clear this wasn’t random. We had to dig, investigate, and piece it together ourselves, with no X channel to explain anything publicly. I won’t pretend it didn’t hurt. It did. But instead of reacting, we had an internal conversation that changed everything. We made a simple decision: If we couldn’t talk, we would build. If we couldn’t defend ourselves in public, we would let the tech do it for us. So we went quiet. And we went all in. 💪 Day after day. No noise. No hype. Just execution. Over that year: • Final testnet phase completed • Mainnet went live • The routing layer started breathing, live on • Real workloads began moving • Nosana integrated directly into our execution layer • Strategic partnerships formed, including with Ozak AI • Relay launched to bridge Web2 enterprises into what we’ve actually built: attempted to create other accounts, but they were also taken down⚡️ Most people never saw it happen. And that’s okay. The people who mattered did. Getting our X back today isn’t about a social account. It’s symbolic. It closes a very difficult chapter. And opens the one we’ve been preparing for all along. 🚀 Now the outside world finally gets visibility into what’s already real. Not promises. Not decks. Not theory. Live infrastructure. ✅ Live routing. ✅ Live execution. ✅ The new website will be live very soon. The whole stack is finally coming together, and we can’t wait to show it to the world. This isn’t incremental. It’s a fundamental shift in how compute is routed. 2025 was about resilience and building through silence. 2026 is about adoption, scale, and making some serious waves. The internet routes data. We route compute. It’s good to be back. ❤️ Here’s a preview of the hero video from our new website, coming very soon. $OGPU

One year ago, our X account disappeared. No warning. No explanation. Just gone. With no way to explain what had happened, fear, uncertainty, and disbelief started to spread. People questioned what was happening. People assumed the worst. Silence filled the gaps. At the time, we didn’t even know why we’d been suspended. We attempted to create other accounts, but they were also taken down. That’s when it became clear this wasn’t random. We had to dig, investigate, and piece it together ourselves, with no X channel to explain anything publicly. I won’t pretend it didn’t hurt. It did. But instead of reacting, we had an internal conversation that changed everything. We made a simple decision: If we couldn’t talk, we would build. If we couldn’t defend ourselves in public, we would let the tech do it for us. So we went quiet. And we went all in. 💪 Day after day. No noise. No hype. Just execution. Over that year: • Final testnet phase completed • Mainnet went live • The routing layer started breathing, live on • Real workloads began moving • Nosana integrated directly into our execution layer • Strategic partnerships formed, including with Ozak AI • Relay launched to bridge Web2 enterprises into what we’ve actually built: attempted to create other accounts, but they were also taken down⚡️ Most people never saw it happen. And that’s okay. The people who mattered did. Getting our X back today isn’t about a social account. It’s symbolic. It closes a very difficult chapter. And opens the one we’ve been preparing for all along. 🚀 Now the outside world finally gets visibility into what’s already real. Not promises. Not decks. Not theory. Live infrastructure. ✅ Live routing. ✅ Live execution. ✅ The new website will be live very soon. The whole stack is finally coming together, and we can’t wait to show it to the world. This isn’t incremental. It’s a fundamental shift in how compute is routed. 2025 was about resilience and building through silence. 2026 is about adoption, scale, and making some serious waves. The internet routes data. We route compute. It’s good to be back. ❤️ Here’s a preview of the hero video from our new website, coming very soon. $OGPU

OpenGPU Network

10,979 просмотров • 7 месяцев назад

I spent 48 hours running AI from my phone. Here are 11 things that turned out to be possible and 3 that almost cost me money Forgot my laptop at home and thought the day was lost. Opened a terminal from my phone and decided to see how long I could last Lasted 2 days. Not just lasted but made $840 What works from a phone: 1. Set up Claude Code through SSH in 10 minutes while riding the subway 2. Get Telegram pushes every time a wallet enters a position 3. Copy a trade with 1 tap without taking out my earbuds 4. Launch scripts by voice through Shortcuts 5. Monitor 3 wallets simultaneously without a single lag 6. Get a morning report at 7 AM as a regular message 7. Rebuild the bot when it crashed while sitting in a cab 8. Check PnL without opening a browser 9. Add a new wallet to tracking in 30 seconds 10. Set up auto-copying without confirmation on verified wallets 11. Get a full strategy breakdown of a wallet through Claude Code in a regular chat And here is what almost killed the deposit: 1. My finger slipped and I entered at twice the planned size. Did not notice for 20 minutes. Got lucky that the position ended up in profit but it could have gone very differently 2. My phone died at 2 AM. Missed the exit signal and the position dropped $110 while I slept. By morning I realized that a power bank is just as much a part of the strategy as the bot itself 3. The delay when copying was 40 seconds. On a 15-minute market that is an eternity. The price moved from 8 cents to 23, and instead of a 12x return I got a 4x. Still profit but you feel the difference immediately Total for 48 hours: +$840. Screen time on the phone: 47 minutes. Never needed the laptop The entire time I was following the same wallet. That is the 1 that was sending me signals at 2 AM: The phone turned out to be a fully functional control panel. But this control panel has no safety switch. And that is worth remembering every time you are tapping with 1 hand in the coffee line

I spent 48 hours running AI from my phone. Here are 11 things that turned out to be possible and 3 that almost cost me money Forgot my laptop at home and thought the day was lost. Opened a terminal from my phone and decided to see how long I could last Lasted 2 days. Not just lasted but made $840 What works from a phone: 1. Set up Claude Code through SSH in 10 minutes while riding the subway 2. Get Telegram pushes every time a wallet enters a position 3. Copy a trade with 1 tap without taking out my earbuds 4. Launch scripts by voice through Shortcuts 5. Monitor 3 wallets simultaneously without a single lag 6. Get a morning report at 7 AM as a regular message 7. Rebuild the bot when it crashed while sitting in a cab 8. Check PnL without opening a browser 9. Add a new wallet to tracking in 30 seconds 10. Set up auto-copying without confirmation on verified wallets 11. Get a full strategy breakdown of a wallet through Claude Code in a regular chat And here is what almost killed the deposit: 1. My finger slipped and I entered at twice the planned size. Did not notice for 20 minutes. Got lucky that the position ended up in profit but it could have gone very differently 2. My phone died at 2 AM. Missed the exit signal and the position dropped $110 while I slept. By morning I realized that a power bank is just as much a part of the strategy as the bot itself 3. The delay when copying was 40 seconds. On a 15-minute market that is an eternity. The price moved from 8 cents to 23, and instead of a 12x return I got a 4x. Still profit but you feel the difference immediately Total for 48 hours: +$840. Screen time on the phone: 47 minutes. Never needed the laptop The entire time I was following the same wallet. That is the 1 that was sending me signals at 2 AM: The phone turned out to be a fully functional control panel. But this control panel has no safety switch. And that is worth remembering every time you are tapping with 1 hand in the coffee line

Blaze

93,477 просмотров • 5 месяцев назад

This is the most hilarious thing I saw and did today Ran gemma-4-12B-coder-fable5-composer2.5-v1-GGUF locally with 8 GB VRAM at 20+ tok/sec Anthropic's Claude Fable 5 launched June 9. By June 12 it was banned. I can't access it. You can't either. But here's the twist: I'm running a model trained on its chain of thought at 20 tok/s on my RTX 4060 8GB. Locally. Offline. No cloud. No export control. Enter: Gemma4-12B-Coder GGUF (Q4_K_M) Base: Google's gemma-4-12B-it Fine-tuned on verifiable Python CoT data: - Primary: Composer 2.5 real reasoning traces (only passing solutions kept) - Auxiliary: Fable 5 used to redo the hard cases Composer missed. Every training example's reasoning led to code that actually ran. No hallucinated logic. Llama.cpp flags: -m gemma4-coding-Q4_K_M.gguf -cnv -ngl 44 -c 64000 -v (huggingface model link in comments) Flag breakdown: -ngl 44 → offload 44 layers to GPU (tune this for your VRAM) -c 64000 → 64K context window -cnv → conversation/chat mode -v → verbose output The irony writes itself. Anthropic spent weeks telling the world Fable 5 (mythos) is too powerful to release. Then released it. Then got banned from serving it, including their own researchers. Meanwhile: a Gemma 4 12B fine tune, trained on Fable 5's reasoning, runs fully offline on my mid range consumer GPU No API. No cloud. Just me and llama.cpp. This is why local AI matters. Check out the model's link in the comments. How's your experience been with this model?

This is the most hilarious thing I saw and did today Ran gemma-4-12B-coder-fable5-composer2.5-v1-GGUF locally with 8 GB VRAM at 20+ tok/sec Anthropic's Claude Fable 5 launched June 9. By June 12 it was banned. I can't access it. You can't either. But here's the twist: I'm running a model trained on its chain of thought at 20 tok/s on my RTX 4060 8GB. Locally. Offline. No cloud. No export control. Enter: Gemma4-12B-Coder GGUF (Q4_K_M) Base: Google's gemma-4-12B-it Fine-tuned on verifiable Python CoT data: - Primary: Composer 2.5 real reasoning traces (only passing solutions kept) - Auxiliary: Fable 5 used to redo the hard cases Composer missed. Every training example's reasoning led to code that actually ran. No hallucinated logic. Llama.cpp flags: -m gemma4-coding-Q4_K_M.gguf -cnv -ngl 44 -c 64000 -v (huggingface model link in comments) Flag breakdown: -ngl 44 → offload 44 layers to GPU (tune this for your VRAM) -c 64000 → 64K context window -cnv → conversation/chat mode -v → verbose output The irony writes itself. Anthropic spent weeks telling the world Fable 5 (mythos) is too powerful to release. Then released it. Then got banned from serving it, including their own researchers. Meanwhile: a Gemma 4 12B fine tune, trained on Fable 5's reasoning, runs fully offline on my mid range consumer GPU No API. No cloud. Just me and llama.cpp. This is why local AI matters. Check out the model's link in the comments. How's your experience been with this model?

Alok

572,538 просмотров • 2 месяцев назад

🚨 CHINA'S NIGHTMARE IS ALREADY HERE AND IT'S HEADED TO AMERICA FAST: In China, a vast network of hundreds of millions of surveillance cameras with facial recognition doesn't just watch; it controls. You can't freely leave your neighborhood zone... You can't buy online or pay without successful biometric authentication... Fail the algorithm? You're digitally imprisoned. No walls needed. Just code. A young woman repeatedly failed facial authentication... She was trapped... unable to exit her designated zone. Not by force, but by silent machines deciding her freedom. Now hear Ye Gu (叶古 ): "For years I've failed online facial recognition authentication. Evil forces control the system; I can't buy a single thing online!" This isn't dystopian fiction... It's the CCP's technocratic order: Skynet/Sharp Eyes projects, integrated with social trust blacklists that restrict travel, loans, jobs, and daily life for the "untrustworthy." Facial data links everything; payments, movement, speech. And it's coming to America soon. TSA is rolling out touchless facial recognition at 65+ airports by spring 2026 (PreCheck "Touchless ID"). REAL ID full enforcement is live. Digital driver's licenses in Apple/Google Wallet are being accepted nationwide. CBP is expanding facial scans to nearly all non-citizens at borders (no kid/senior exemptions). Proposals for biometric alternatives to physical IDs. IRS and others already use facial verification for services. What starts as "convenience" and "security" (faster lines, fraud prevention) becomes a permission-based society: one failed scan, one flagged "risk score," and your movement, purchases, or access gets restricted. History warns us: Authoritarian regimes test total surveillance abroad, then export the tools and logic. Democracies adopt the tech under "safety" pretexts, then the mission creeps. We are sleepwalking into digital confinement. Your face is becoming your passport... revocable at any time by algorithm or bureaucrat. Resist now. Demand alternatives. Reject mandatory biometrics. Protect bodily autonomy and free movement. This isn't left vs right. It's free humanity vs. the machine-state. Let me know your thoughts, and Share if you refuse to live in a world where your face is a login that can be denied.

🚨 CHINA'S NIGHTMARE IS ALREADY HERE AND IT'S HEADED TO AMERICA FAST: In China, a vast network of hundreds of millions of surveillance cameras with facial recognition doesn't just watch; it controls. You can't freely leave your neighborhood zone... You can't buy online or pay without successful biometric authentication... Fail the algorithm? You're digitally imprisoned. No walls needed. Just code. A young woman repeatedly failed facial authentication... She was trapped... unable to exit her designated zone. Not by force, but by silent machines deciding her freedom. Now hear Ye Gu (叶古 ): "For years I've failed online facial recognition authentication. Evil forces control the system; I can't buy a single thing online!" This isn't dystopian fiction... It's the CCP's technocratic order: Skynet/Sharp Eyes projects, integrated with social trust blacklists that restrict travel, loans, jobs, and daily life for the "untrustworthy." Facial data links everything; payments, movement, speech. And it's coming to America soon. TSA is rolling out touchless facial recognition at 65+ airports by spring 2026 (PreCheck "Touchless ID"). REAL ID full enforcement is live. Digital driver's licenses in Apple/Google Wallet are being accepted nationwide. CBP is expanding facial scans to nearly all non-citizens at borders (no kid/senior exemptions). Proposals for biometric alternatives to physical IDs. IRS and others already use facial verification for services. What starts as "convenience" and "security" (faster lines, fraud prevention) becomes a permission-based society: one failed scan, one flagged "risk score," and your movement, purchases, or access gets restricted. History warns us: Authoritarian regimes test total surveillance abroad, then export the tools and logic. Democracies adopt the tech under "safety" pretexts, then the mission creeps. We are sleepwalking into digital confinement. Your face is becoming your passport... revocable at any time by algorithm or bureaucrat. Resist now. Demand alternatives. Reject mandatory biometrics. Protect bodily autonomy and free movement. This isn't left vs right. It's free humanity vs. the machine-state. Let me know your thoughts, and Share if you refuse to live in a world where your face is a login that can be denied.

Noah B. Price

32,700 просмотров • 4 месяцев назад

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot *resume* the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which *would've* hit the breakpoint, *if* it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because *generally* you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) *cannot apply* to some module's debug info - more quickly than doing a *full* PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume *knowing* that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot resume the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which would've hit the breakpoint, if it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because generally you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) cannot apply to some module's debug info - more quickly than doing a full PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume knowing that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

Ryan Fleury

17,527 просмотров • 1 год назад

The week has been a great one with lots of updates on different scales and different events altogether, but that doesn't also rule out the fact that there's still sense to make out in all of these. Here are a few of the projects I have my eyes on and their recent updates; - Cysic (mainnet arc) has announced their token standards. $CYS and $CGT; 2 tokens with a single mission, to make Compute-Fi as seamless as possible. $CYS serves as the network token for paying gas and keeping the chain running, while $CGT serves as the governance token to give holders a voice. This just gives out more hints that Mainnet might just be close. - The KYC Verification and subscription went live in preparation for $MMT community offering launching very soon on Buidlpad. This is all in line with the MomentumⓂ️Ⓜ️T sale community offering coming soon. The KYC & subscription ended on the 25th, while the contribution window commences on the 27th. If you wish to be a part of the sale, ensure you didn't forget to KYC and subscribe. - After weeks of shrouding in mystery, the integra. team finally discloses what they had been building all along in silence. A chain that plans to bring in over $12B+ in untapped value across major RWAs to make trading them as seamless as possible. Integra is the chain made for Real Estate, Real World Assets and all that surrounds it. - Anichess has finally taken the snapshot for their official NFT collection; the Ethernals. The snapshot was completed on Ethereum Mainnet Block #23638874. The snapshot for the collection was done to reward holders of the NFTs a 10% supply of the Anichess's $CHECK token distribution at TGE. Solid holders IMO as I saw no sell pressure on the NFT collection even after the snapshot had been taken unlike regular collections out there. - One of my big bags and long term conviction partners; 0G Labs (Home of Infinite AI) has been steadily innovating with more and more updates rolled out daily. ZeroStack (FLGC); one of the finest storage banks and 0G's treasury just secured its second $0G purchase of over $1.9M+in value, bringing the total holding to 123.4M $0G tokens. Price has been stable and the community impeccable. There's more to come on 0G, I'll advice you position accordingly. - Lastly, I saved the best for the last because it was definitely worth it. We have become too shrouded with Kaito that we failed to realize a hidden potential right under our nose. Wallchain Quacks; another advancement of info-fi has proven to be more than an excellent choice to reward and incentivize its community. Limitless recently had their TGE and over 2,500,000.00 $LMTS tokens were distributed to the top 250 Quackers (Yappers equivalent). Innovations are happening, and we'll continue to see many more advancements as we progress. You just have to stay positioned and look out for the projects built on WallChain. Stay informed guys. Goodluck and a happy weekend once again

The week has been a great one with lots of updates on different scales and different events altogether, but that doesn't also rule out the fact that there's still sense to make out in all of these. Here are a few of the projects I have my eyes on and their recent updates; - Cysic (mainnet arc) has announced their token standards. $CYS and $CGT; 2 tokens with a single mission, to make Compute-Fi as seamless as possible. $CYS serves as the network token for paying gas and keeping the chain running, while $CGT serves as the governance token to give holders a voice. This just gives out more hints that Mainnet might just be close. - The KYC Verification and subscription went live in preparation for $MMT community offering launching very soon on Buidlpad. This is all in line with the MomentumⓂ️Ⓜ️T sale community offering coming soon. The KYC & subscription ended on the 25th, while the contribution window commences on the 27th. If you wish to be a part of the sale, ensure you didn't forget to KYC and subscribe. - After weeks of shrouding in mystery, the integra. team finally discloses what they had been building all along in silence. A chain that plans to bring in over $12B+ in untapped value across major RWAs to make trading them as seamless as possible. Integra is the chain made for Real Estate, Real World Assets and all that surrounds it. - Anichess has finally taken the snapshot for their official NFT collection; the Ethernals. The snapshot was completed on Ethereum Mainnet Block #23638874. The snapshot for the collection was done to reward holders of the NFTs a 10% supply of the Anichess's $CHECK token distribution at TGE. Solid holders IMO as I saw no sell pressure on the NFT collection even after the snapshot had been taken unlike regular collections out there. - One of my big bags and long term conviction partners; 0G Labs (Home of Infinite AI) has been steadily innovating with more and more updates rolled out daily. ZeroStack (FLGC); one of the finest storage banks and 0G's treasury just secured its second $0G purchase of over $1.9M+in value, bringing the total holding to 123.4M $0G tokens. Price has been stable and the community impeccable. There's more to come on 0G, I'll advice you position accordingly. - Lastly, I saved the best for the last because it was definitely worth it. We have become too shrouded with Kaito that we failed to realize a hidden potential right under our nose. Wallchain Quacks; another advancement of info-fi has proven to be more than an excellent choice to reward and incentivize its community. Limitless recently had their TGE and over 2,500,000.00 $LMTS tokens were distributed to the top 250 Quackers (Yappers equivalent). Innovations are happening, and we'll continue to see many more advancements as we progress. You just have to stay positioned and look out for the projects built on WallChain. Stay informed guys. Goodluck and a happy weekend once again

OHJAY ⭕️ || 🇬🇧

20,919 просмотров • 10 месяцев назад

📣 Puffer UniFi V2 testnet is now live! 🐡 The UniFi V2 testnet is officially live, and we’re inviting builders to explore the stack and join the next phase of Ethereum-native infrastructure. With the advancement of based rollup technology, UniFi offers a practical path forward to address Ethereum’s fragmentation and foster ecosystem growth. UniFi-OP enables Ethereum builders and users to avoid choosing a “winning” L2 or giving up revenue. Based sequencing keeps rollups, appchains, and general-purpose chains fully composable with Ethereum. Thanks to UniFi AVS, rollup owners can now share priority fees and MEV with validators. This upgrade was made possible in collaboration with Gattaca, , Automata Network, and Ethereum. ⚒️ What Builders Get • Governance‑optional rollups 🗳️ • Custom fee markets (subsidize, burn, or share) • KYC‑gated or fully permissionless chains 💆 What Users Feel • Sub‑10 ms confirmations ⚡ • One‑click exits to L1 (no 7‑day wait) • Seamless L1 interaction—AMMs, CLOBs, RWAs “just work” 📈 Economic Win‑Win Based sequencing ≠ giving up MEV and Priority fees. Rollup owners, gateways, and L1 proposers share MEV & congestion fees through @puffer_unifiAVS. Alignment without sacrifices. 🧩Pragmatic Composability How composable is UniFi V2? • L2 → L1 withdrawal supported • EIP‑7702 smart‑wallet standard baked in • Atomic withdrawals in the same block (no more 7 day wait) 🛡️Trust‑Minimized, Real‑Time Proving Real time proving is a must have to achieve composability and security that a rollup needs. We came up with a trust minimized pragmatic approach with TEEs for the first phase. In collaboration with Automata Network we now have: • Multi‑TEE provers (Intel TDX + AMD SEV) attest each block in less than 1s. • Hardware diversity = reduced trust assumptions. 🏎️UniFi AVS (Gateway Registry) For Preconfimrations (preconfs), we take advantage of delegated proposing to gateways to bring the speed. This service requires shared security. 🏗️Built on : • Validators opt in and delegate proposer rights. • They earn extra yield for serving preconfs. • Restaking validators solve the cold‑start problem. 💻 Preconf Phases • Centralized gateways at launch. • Progressive onboarding → many independent gateways for decentralization. • Proposer‑delegated based sequencing (speed). 🗺️Roadmap • ✅ Hybrid Based‑OP stack with TEE proving & fast gateways • 🔜 ZK proving • 🔜 Universal Registry Contract (URC) by ****@fabric_ethereum for slashing • 🔜 Commit boost Commit-Boost 📻 🕶️ 🦇🔊 integration • 🔜 Native L1 ↔ L2 ↔ L2 calls All upgrades are backward‑compatible and shipped incrementally. ⚔️Security Model at a Glance • Restaked ETH → slashable backing • Multi‑vendor TEEs → hardware redundancy • ZK fallback → cryptographic safety net No single point of failure. 🎯Metrics That Matter The KPI moves from TVL to transaction volume & speed. High‑frequency order‑flow is real revenue—and UniFi lets dApps capture it instead of donating it to someone else’s sequencer. 🧑‍💻Code & Collaboration UniFi V2 extends the open work by Gattaca on Gattaca‑OP. Dive into the repos and contribute. 📚TL;DR • Pragmatic composability with atomic withdrawals from the L2. • Trust‑minimized, real‑time proving • UniFi AVS bootstrapped by EigenLayer • Based rollups that share income 🪖Builders: stop choosing between UX, composability, and revenue. DM us or visit to spin up your Based Appchain and join the UniFi Based Rollup testnet—or fork the stack and run it yourself. 👷‍♂️ Build with us: 🪙 Faucet: 🌍Ecosystem resources:

📣 Puffer UniFi V2 testnet is now live! 🐡 The UniFi V2 testnet is officially live, and we’re inviting builders to explore the stack and join the next phase of Ethereum-native infrastructure. With the advancement of based rollup technology, UniFi offers a practical path forward to address Ethereum’s fragmentation and foster ecosystem growth. UniFi-OP enables Ethereum builders and users to avoid choosing a “winning” L2 or giving up revenue. Based sequencing keeps rollups, appchains, and general-purpose chains fully composable with Ethereum. Thanks to UniFi AVS, rollup owners can now share priority fees and MEV with validators. This upgrade was made possible in collaboration with Gattaca, , Automata Network, and Ethereum. ⚒️ What Builders Get • Governance‑optional rollups 🗳️ • Custom fee markets (subsidize, burn, or share) • KYC‑gated or fully permissionless chains 💆 What Users Feel • Sub‑10 ms confirmations ⚡ • One‑click exits to L1 (no 7‑day wait) • Seamless L1 interaction—AMMs, CLOBs, RWAs “just work” 📈 Economic Win‑Win Based sequencing ≠ giving up MEV and Priority fees. Rollup owners, gateways, and L1 proposers share MEV & congestion fees through @puffer_unifiAVS. Alignment without sacrifices. 🧩Pragmatic Composability How composable is UniFi V2? • L2 → L1 withdrawal supported • EIP‑7702 smart‑wallet standard baked in • Atomic withdrawals in the same block (no more 7 day wait) 🛡️Trust‑Minimized, Real‑Time Proving Real time proving is a must have to achieve composability and security that a rollup needs. We came up with a trust minimized pragmatic approach with TEEs for the first phase. In collaboration with Automata Network we now have: • Multi‑TEE provers (Intel TDX + AMD SEV) attest each block in less than 1s. • Hardware diversity = reduced trust assumptions. 🏎️UniFi AVS (Gateway Registry) For Preconfimrations (preconfs), we take advantage of delegated proposing to gateways to bring the speed. This service requires shared security. 🏗️Built on : • Validators opt in and delegate proposer rights. • They earn extra yield for serving preconfs. • Restaking validators solve the cold‑start problem. 💻 Preconf Phases • Centralized gateways at launch. • Progressive onboarding → many independent gateways for decentralization. • Proposer‑delegated based sequencing (speed). 🗺️Roadmap • ✅ Hybrid Based‑OP stack with TEE proving & fast gateways • 🔜 ZK proving • 🔜 Universal Registry Contract (URC) by ****@fabric_ethereum for slashing • 🔜 Commit boost Commit-Boost 📻 🕶️ 🦇🔊 integration • 🔜 Native L1 ↔ L2 ↔ L2 calls All upgrades are backward‑compatible and shipped incrementally. ⚔️Security Model at a Glance • Restaked ETH → slashable backing • Multi‑vendor TEEs → hardware redundancy • ZK fallback → cryptographic safety net No single point of failure. 🎯Metrics That Matter The KPI moves from TVL to transaction volume & speed. High‑frequency order‑flow is real revenue—and UniFi lets dApps capture it instead of donating it to someone else’s sequencer. 🧑‍💻Code & Collaboration UniFi V2 extends the open work by Gattaca on Gattaca‑OP. Dive into the repos and contribute. 📚TL;DR • Pragmatic composability with atomic withdrawals from the L2. • Trust‑minimized, real‑time proving • UniFi AVS bootstrapped by EigenLayer • Based rollups that share income 🪖Builders: stop choosing between UX, composability, and revenue. DM us or visit to spin up your Based Appchain and join the UniFi Based Rollup testnet—or fork the stack and run it yourself. 👷‍♂️ Build with us: 🪙 Faucet: 🌍Ecosystem resources:

Puffer Finance 🐡

158,083 просмотров • 1 год назад

IMPORTANT: Instead of giving the liars and frauds engagement, Here are the facts about me & Ed Krassenstein 1) We've never run a p-rn site of any kind—gay, straight, or otherwise. Not that there’s anything wrong with it if it’s legal, but it simply isn’t true in our case. 2) We never scammed anyone in our lives. Not a single “victim” has ever accused us of doing so. We’ve never been arrested, charged or convicted of a crime. 3) Yes, between 2001 and 2011, we operated a massive domain name brokerage and parking business. At one point, we owned over 15,000 domains, acquired in two ways: - Bulk Purchases: We’d buy entire portfolios (sometimes over 500 domains at once) and park them for ad revenue from type-in traffic. - Automation: We developed our own code to register dropped domain names with traffic, which we then parked. - Important Clarification: Some of these domains were adult-oriented (less than 0.2%), but they were either part of large portfolios we bought or were automatically acquired from dropped domain lists. Most of these were immediately dropped as soon as we were able to. None of them were EVER developed into websites or p-rn sites. You can check the internet archives to confirm that none of these domains were adult websites during the time we owned them. 4) Yes we made a post once saying that we were buying websites and message boards aimed towards teens and young adults. The post was made approximately 20 years ago when we were either teenagers or in our early 20's and when we were running fan-club websites for musicians, entertainers and college students. We owned some of the largest internet forums related to music, school and entertainment on the internet in the early 2000’s. 5) No one pays us to Post political comments on X besides X. We have been approached by multiple PACs over the years and have always refused. The video floating around showing us claim that “we are paid by the higher ups” is an edited clip of a parody video we made. The full video is online for anyone to watch and see that it was a clear joke. 6) We did NOT buy our Twitter accounts. Both of our accounts have always been owned solely by us. We did rename them several times over the past 14 years. We still have the original emails that Twitter sent us when we created these names. It’s easy for conspiracy theorists to cobble together random bits from the internet over 20+ years and spin false narratives, but the truth is clear when you know the facts. Don’t fall for the lies—rely on the truth.

IMPORTANT: Instead of giving the liars and frauds engagement, Here are the facts about me & Ed Krassenstein 1) We've never run a p-rn site of any kind—gay, straight, or otherwise. Not that there’s anything wrong with it if it’s legal, but it simply isn’t true in our case. 2) We never scammed anyone in our lives. Not a single “victim” has ever accused us of doing so. We’ve never been arrested, charged or convicted of a crime. 3) Yes, between 2001 and 2011, we operated a massive domain name brokerage and parking business. At one point, we owned over 15,000 domains, acquired in two ways: - Bulk Purchases: We’d buy entire portfolios (sometimes over 500 domains at once) and park them for ad revenue from type-in traffic. - Automation: We developed our own code to register dropped domain names with traffic, which we then parked. - Important Clarification: Some of these domains were adult-oriented (less than 0.2%), but they were either part of large portfolios we bought or were automatically acquired from dropped domain lists. Most of these were immediately dropped as soon as we were able to. None of them were EVER developed into websites or p-rn sites. You can check the internet archives to confirm that none of these domains were adult websites during the time we owned them. 4) Yes we made a post once saying that we were buying websites and message boards aimed towards teens and young adults. The post was made approximately 20 years ago when we were either teenagers or in our early 20's and when we were running fan-club websites for musicians, entertainers and college students. We owned some of the largest internet forums related to music, school and entertainment on the internet in the early 2000’s. 5) No one pays us to Post political comments on X besides X. We have been approached by multiple PACs over the years and have always refused. The video floating around showing us claim that “we are paid by the higher ups” is an edited clip of a parody video we made. The full video is online for anyone to watch and see that it was a clear joke. 6) We did NOT buy our Twitter accounts. Both of our accounts have always been owned solely by us. We did rename them several times over the past 14 years. We still have the original emails that Twitter sent us when we created these names. It’s easy for conspiracy theorists to cobble together random bits from the internet over 20+ years and spin false narratives, but the truth is clear when you know the facts. Don’t fall for the lies—rely on the truth.

Brian Krassenstein

416,947 просмотров • 2 лет назад