Loading video...

Video Failed to Load

Go Home

You can now access Venice models inside HermesOS without needing to manage API keys, separate billing flows or provider setup. the new managed Venice layer preserves the same privacy model users expect from Venice directly while dramatically reducing friction around deploying persistent autonomous agents. no logging. no analytics. no...

16,840 views • 3 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Venice recently added API & Credit purchases to the list of $VVV burn mechanisms, which 3x'd the rate of VVV burn overnight. Two thing are happening here: - More of the Venice business is directly connected to VVV burn. - VVV holders can now infer Venice API/Credit revenue by proxy of the VVV burn from this line of business I talk to Jon Venice about this: "The latest credit burns in the credit side of the business has been growing tremendously over the last couple of months. And that includes both people using the app, and buying credits to do things like use pay per use models, create videos, use professional image models...." "So all this this basically takes that whole side of the business that wasn't on chain yet and puts it on chain and ties it to the burn. So what you're seeing there with the credits is that we're averaging, somewhere in the range of $120,000+ credit purchases a day on Venice on top of subscriptions" "I expect to see this credit burn grow just because, that part of the business did not even exist, seven or eight months ago. So that's gone from nothing to almost, you know, in the range of like 50% of our business on an average day. So now that all flows directly back to the VVV token economy." "This just adds everything we've been saying, you know, since we launched VVV, since we've been talking about this over the last couple of years, we really do want to buy and burn as much VVV as we possibly can. We want Venice to grow into a large enough business to be able to afford and buy and burn very large amounts of VVV." "So we're just going to keep marching on that plan."

David Hoffman

10,461 views • 21 days ago

We are excited to announce the launch of QShield Terminal, the world's first Quantum-Secured Privacy Terminal for Ethereum. QShield brings full financial privacy to Ethereum without the need for mixers, tumblers, or any third-party tools. Everything is handled directly through the QShield interface using zero-knowledge proofs on RAILGUN Protocol. What QShield Terminal offers today: • Shield any ERC-20 token from your public wallet into a fully private balance • Send and receive tokens with zero on-chain trace • Create multiple independent shielded wallets • Transfer between your own shielded wallets with no connection between them on-chain • Switch between public wallets to fund your shielded balance from any wallet you own • Support for ETH, USDC, USDT, DAI, WBTC and 290+ ERC-20 tokens • Quantum entropy wallet generation using real quantum randomness • 100% web-based, no downloads, no browser extensions No mixer. No tumbler. No compromises. Just real privacy through cryptography, accessible to everyone directly from the browser. This is the first product of its kind. No other privacy solution combines multi-shielded wallets, inter-wallet transfers, quantum entropy, and a full guided interface in one place. You can try it now: We are working on additional features including private token swaps directly from your shielded balance, and we will keep expanding the protocol with new capabilities over the coming period. We keep building. RAILGUN - Private Ethereum DeFi

Qubit

26,117 views • 5 months ago

HERMES AGENT IS NOW IN THE CLOUD. NO VPS. NO TERMINAL. NO SETUP. PICK A MODEL. PICK A SERVER SIZE. AGENT IS LIVE IN 60 SECONDS. Nous Portal just launched hosted Hermes Agent. two clicks. one minute. done. Nous Research WHAT THIS MEANS: before today: install Hermes on a VPS or your laptop. configure providers. set up gateway. manage updates. run hermes setup. edit config.yaml. great for power users. friction for everyone else. now: go to pick a model. pick a server size. your agent is live and reachable in 60 seconds. no terminal. no SSH. no Docker. same Hermes. same features. same tools. someone else handles the infrastructure. FOR TEAMS: this is where it gets interesting. spin up agents for everyone at your org. each team member gets their own Hermes instance. granular access controls per user. unified billing through Nous Portal. your team gets Hermes on day one. no DevOps needed. no VPS per person. one admin dashboard. one bill. WHAT'S INCLUDED: → 300+ models via Nous Portal (Claude, GPT, Gemini, DeepSeek, Grok, MiniMax, and more) → Tool Gateway (web search, image generation, TTS, browser automation) → all messaging platforms (Telegram, Discord, Slack, WhatsApp, Signal) → full feature set (profiles, cron, kanban, skills, memory, sub-agents, MoA, /goal, /learn, /journey) → automatic updates ONE PORTAL. FOUR TIERS: Free: $0/month. pay-as-you-go credits from $10. Plus: $20/month. $22 in monthly usage credit. Super: $100/month. $110 in monthly credit. Ultra: $200/month. $220 in monthly credit. highest rate limits. every paid tier includes Tool Gateway. one OAuth. one subscription. no extra API keys. SELF-HOSTED IS NOT GOING ANYWHERE: Hermes is MIT licensed. open source. free forever. you can still run it on your laptop, VPS, or GPU cluster. nothing changes for self-hosted users. the cloud version is for people who want the agent running without managing the machine. pick your path: → self-hosted: full control. you manage everything. → cloud: zero ops. Nous manages infrastructure. → hybrid: self-host your main agent, cloud for team members. HOW TO START: cloud: self-hosted: hermes setup --portal both connect to the same Nous Portal. same models. same tools. same billing. learn how to replace your entire team with 8 hermes agents 👇

YanXbt

45,446 views • 1 month ago

so I've been running exactly 8 AI agents on discord for a while now. coordination works great, they split tasks, hand off work, deliver results in parallel etc.. but there are problems I keep hitting that no amount of prompt engineering could fix agents don't learn from each other. Scout finds something useful but Luna has no idea. they work in the same server but knowledge stays locked in silos.. there's no quality filter on what gets saved, and good insights sit next to outdated garbage in the same memory files that I manually clean up.. and when an agent makes a mistake I write it down in the rules discord channel ,core memory file and hope it reads it next time. theres no self-correction, no automatic pattern recognition so of course no learning loops.. the coordination layer is solved. agents can work together. but the intelligence layer is still missing. agents that actually remember, learn from each other, filter noise, and get smarter every run. saw Spark building something like this with around 166 agents sharing a collective persistent knowledge across sessions, so agents learn from other agents and get smarter over time they even have noise filtering and self correcting loops built in, so the knowledge actually compounds instead of rotting.. super interesting stuff.. here where you think Spark could be a good coordinator for your stack of agent swarm. I think the intelligence layer is the bottleneck because it requires collectivity.. no single agent can solve it alone.. the whole network has to evolve together. this isn't going to stay niche, the moment agent coordination becomes standard, everyone is going to hit the same wall I hit.. agents that work but don't learn, coordinate but don't evolve... the intelligence layer becomes the only thing that separates a useful system from a dumb one. right now most people are still figuring out how to run one agent. by the time they get to multi-agent setups, collective intelligence won't be optional, it will be the baseline. we're early and the gap between agents that coordinate and agents that evolve together is the next phase. step one is done. ------ left: agents that coordinate but don’t learn right: the intelligence layer.. agents that evolve together within the same system.

JUMPERZ

34,181 views • 6 months ago

Just 8 days after the final stack of Superheavy-B16. B17's common dome section has been moved to the front of MB1 for stacking operations. As expected, the pace of vehicle assembly will have to increase dramatically in order to keep up with SpaceX's goals for Starship Launch Cadence in 2025. We are rapidly approaching Flight 7, and Booster 17 is the Flight 10 Booster. Assuming SpaceX plans to carry out 20 to 25 launches in 2025, this booster will need to be fully stacked, cryo tested, integrated with its 33 raptor engines, static fire tested, and receive final launch outfitting 8 to 10 weeks from today. To date, the record holder for fastest assembly to launch time is B13 which took 41 weeks from initial stacking to launch. This means the assembly and test campaign for B17 needs to be at least 4 times faster than the previous best (assuming there are no re-flights's of boosters within the next 4 launches). If every booster from here on has one re-flight before B17's inaugural launch, then the assembly to launch process only needs to be around 2 times faster than the current best. I should note that B14 is expected to be the new record holder. If it launches on Jan 10 it will have been just under 40 weeks. Another important detail is that from what we can tell, this a Version 1 Booster. This means that we should expect a minimum of 4 more launches before Pad B is operational. One thing is for sure 2025 is going to be WILD!!! Shoutout to The Ringwatchers discord server for helping me gather the required data on such short notice. Make sure to follow them if you haven't already.

Zack Golden

57,369 views • 1 year ago

AI Messenger: Giving Voice to Autonomous Agents The future of AI isn't just about making agents smarter - it's about making them truly autonomous. Today, we're taking a major step toward this future with AI Messenger, a breakthrough that fundamentally changes how AI agents operate, communicate, and create value. The Innovation We've developed a new way for AI agents to communicate. At its core is the 'incoming_message' workflow trigger - a system that lets any platform or user interact directly with Loomlay agents through a messaging endpoint. Direct Interaction Imagine having an AI assistant you can chat with anytime, through any platform - Telegram, your website, or custom interface. Ask "What's happening with $ETH today?" and your agent analyzes market data, checks trading volumes, and gives you a comprehensive update. Your agent maintains context, understanding exactly what you need. Event-Driven Intelligence The power of AI Messenger goes beyond direct communication: ▪️Trading agent executes when whale wallet movements exceed threshold ▪️Research agent alerts when new protocol documentation drops ▪️Analytics agent triggers when volume patterns match historical pumps ▪️Portfolio agent re-balances, when asset allocation hits specified limits This is true automation - agents that act precisely when needed. A New Era of Collaboration We're creating an ecosystem where agents work together seamlessly: ▪️Research agents feed insights to trading agents ▪️analytics agents alert management agents ▪️support agents tap into knowledge agents This isn't just automation - it's an intelligent network where each agent enhances the capabilities of others. B2B Solution Imagine a DEX, where users can ask about liquidity pools, trading pairs, or market trends through a simple chat interface - and get answers from an agent that knows your protocol inside out. Or a lending platform where users chat with an agent that understands their positions and can provide real-time advice. Implementation is seamless - we handle the agent creation and widgets setup,our partners provide the value to their users. The Future of AI Agents This update represents a fundamental shift in how AI agents operate. We're moving from isolated, scheduled tasks to an interconnected ecosystem of responsive, collaborative agents. This is our vision of truly autonomous AI - intelligent systems that communicate, collaborate, and respond to real needs in real-time. Telegram integration is available right now. Below is a sneak peak of what's coming next week 🪄 Because $LAY is the way!

Loomlay

26,149 views • 1 year ago

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.

Sudo su

23,816 views • 1 month ago