Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

We were tracking 50+ campaigns manually. Viktor turned it into one report in minutes. We skipped a project coordinator hire. We're a 12-person team managing 140+ AI and tech creators. For months, campaign tracking meant someone on the team manually checking spreadsheets, chasing creators over DM, and pulling together...

TechwithNova's profile picture

Nova Reid

57,707 subscribers

103,724 görüntüleme • 1 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

We wanted to know if Viktor could own our outbound workflow, so we ran a one-week pilot. The result? An estimated 80.5 hours of manual prep replaced by 4.5 hours of team review. We're a digital marketing team managing outbound campaigns alongside client work, and one of the biggest bottlenecks has always been the prep. Researching prospects, writing personalized outreach, building follow-up sequences, and keeping everything organized takes far longer than most people realize. So instead of asking Viktor to help with one email, we asked him to own the workflow. During our pilot, Viktor handled prospect research, enrichment, personalized outreach, follow-up sequences, and campaign tracking for 100 target prospects. Our team's role was reduced to reviewing, approving, and managing replies before anything went out. What impressed us wasn't just the time savings. It was the consistency. Every prospect received the same level of research, the same quality of personalization, and a complete three-email sequence that was ready for review instead of being built manually from scratch. That's when we stopped thinking about AI as another writing tool. He's an AI employee that owns recurring work while keeping humans in control of the final decision. Hire Viktor for your team. $100 in credits included, no card. Full link in first comment. #AIemployee #OutboundSales Paid Partnership
0:14

We wanted to know if Viktor could own our outbound workflow, so we ran a one-week pilot. The result? An estimated 80.5 hours of manual prep replaced by 4.5 hours of team review. We're a digital marketing team managing outbound campaigns alongside client work, and one of the biggest bottlenecks has always been the prep. Researching prospects, writing personalized outreach, building follow-up sequences, and keeping everything organized takes far longer than most people realize. So instead of asking Viktor to help with one email, we asked him to own the workflow. During our pilot, Viktor handled prospect research, enrichment, personalized outreach, follow-up sequences, and campaign tracking for 100 target prospects. Our team's role was reduced to reviewing, approving, and managing replies before anything went out. What impressed us wasn't just the time savings. It was the consistency. Every prospect received the same level of research, the same quality of personalization, and a complete three-email sequence that was ready for review instead of being built manually from scratch. That's when we stopped thinking about AI as another writing tool. He's an AI employee that owns recurring work while keeping humans in control of the final decision. Hire Viktor for your team. $100 in credits included, no card. Full link in first comment. #AIemployee #OutboundSales Paid Partnership

Kylie

76,240 görüntüleme • 1 ay önce

I just built a Claude Cowork skill that turns your Google Ads data into a visual performance dashboard in 60 seconds 🤯 One prompt → campaign breakdowns, CPA trends, spend vs conversions charts, and hourly conversion patterns, all rendered as an interactive HTML dashboard you open in Chrome. All inside Claude Cowork. Perfect for DTC brands and agencies who are pulling Google Ads data into spreadsheets every week, manually building charts, and spending an hour formatting a report that's outdated by the time you send it. If you're managing Google Ads and your weekly reporting workflow looks like this — export a CSV, open Google Sheets, build a pivot table, copy the numbers into a slide deck, manually create charts, format everything, realize you forgot a campaign, start over ... This skill does the whole thing in one prompt: → Connects to your live Google Ads data via MCP → Pulls spend, conversions, CPA, ROAS, CTR across every campaign → Builds an interactive HTML dashboard → Summary cards at the top: total spend, total conversions, avg CPA, avg ROAS → Bar chart comparing spend vs conversions by campaign → CPA trend line over the last 30 days → Campaign table ranked by performance, color-coded green/yellow/red → Opens in Chrome: hover over charts, compare campaigns, screenshot for your team No spreadsheets. No manual chart building. No hour-long formatting sessions. What you get: → A visual dashboard from live data in under 60 seconds → Campaign performance you can actually see, not just read in a table → CPA trends that show you where things are heading, not just where they are → A dashboard you can screenshot and drop into Slack, a client report, or a team standup → Reusable — run it weekly and the data updates automatically One prompt. Live data. A finished dashboard you open in your browser. I put together a playbook with the full skill file, the setup, and the exact prompts to customize the dashboard for your account. Want it for free? > Like this post > Comment "DASH" And I'll send it over (must be following so I can DM)
0:11

I just built a Claude Cowork skill that turns your Google Ads data into a visual performance dashboard in 60 seconds 🤯 One prompt → campaign breakdowns, CPA trends, spend vs conversions charts, and hourly conversion patterns, all rendered as an interactive HTML dashboard you open in Chrome. All inside Claude Cowork. Perfect for DTC brands and agencies who are pulling Google Ads data into spreadsheets every week, manually building charts, and spending an hour formatting a report that's outdated by the time you send it. If you're managing Google Ads and your weekly reporting workflow looks like this — export a CSV, open Google Sheets, build a pivot table, copy the numbers into a slide deck, manually create charts, format everything, realize you forgot a campaign, start over ... This skill does the whole thing in one prompt: → Connects to your live Google Ads data via MCP → Pulls spend, conversions, CPA, ROAS, CTR across every campaign → Builds an interactive HTML dashboard → Summary cards at the top: total spend, total conversions, avg CPA, avg ROAS → Bar chart comparing spend vs conversions by campaign → CPA trend line over the last 30 days → Campaign table ranked by performance, color-coded green/yellow/red → Opens in Chrome: hover over charts, compare campaigns, screenshot for your team No spreadsheets. No manual chart building. No hour-long formatting sessions. What you get: → A visual dashboard from live data in under 60 seconds → Campaign performance you can actually see, not just read in a table → CPA trends that show you where things are heading, not just where they are → A dashboard you can screenshot and drop into Slack, a client report, or a team standup → Reusable — run it weekly and the data updates automatically One prompt. Live data. A finished dashboard you open in your browser. I put together a playbook with the full skill file, the setup, and the exact prompts to customize the dashboard for your account. Want it for free? > Like this post > Comment "DASH" And I'll send it over (must be following so I can DM)

Mike Futia

38,846 görüntüleme • 4 ay önce

SOMEONE TURNED THEIR TEAM'S TASK TRACKER INTO A 3D ISLAND instead of a boring list of tasks, your teams work is a little island that grows as you get stuff done > you assign tasks right in slack, just type who its for, the points, and the due date > finish a task and you get to place a building on the island > get your work rejected and the building collapses into rubble > the rubble stays there forever, so everyone can see it > each new sprint starts a fresh island so over time the island fills up with buildings for all the work your team actually finished, and the rubble is a reminder of what got rejected. its open source, so any team can set it up. way more fun than staring at a to do list all day
0:13

SOMEONE TURNED THEIR TEAM'S TASK TRACKER INTO A 3D ISLAND instead of a boring list of tasks, your teams work is a little island that grows as you get stuff done > you assign tasks right in slack, just type who its for, the points, and the due date > finish a task and you get to place a building on the island > get your work rejected and the building collapses into rubble > the rubble stays there forever, so everyone can see it > each new sprint starts a fresh island so over time the island fills up with buildings for all the work your team actually finished, and the rubble is a reminder of what got rejected. its open source, so any team can set it up. way more fun than staring at a to do list all day

Om Patel

12,952 görüntüleme • 1 ay önce

Introducing: Control Tower. After running agencies for over a decade, three problems were clear: 1. Task management tools aren't built for client work—the constant back-and-forth, the private and public feedback loops. 2. Financial tools don't understand service businesses. We need to know what's coming in, what clients owe, when they're paying, and how that stacks up against what we're paying our team. 3. We need easy tools to track and manage our team's capacity in real-time. But here's the thing—these tools need to work together. When you work with clients, your team's capacity dictates the projects you can take on. The projects you take on dictate your revenue. And the pace of those projects restarts the entire cycle. That's what Control Tower does. Today we're announcing the foundations: Tasks, financials, and capacity. Very soon we'll be introducing Chief—the AI layer that connects everything and works proactively to keep your team moving. We built this from the ground up to be agent-native. What we have today is good. It's not great yet. There's a lot of work to do, and a lot we haven't even shipped to our beta users. I'd love for you to check it out. Sign up for the beta—we're inviting people as quickly as we can and doing personal walkthroughs.
0:18

Introducing: Control Tower. After running agencies for over a decade, three problems were clear: 1. Task management tools aren't built for client work—the constant back-and-forth, the private and public feedback loops. 2. Financial tools don't understand service businesses. We need to know what's coming in, what clients owe, when they're paying, and how that stacks up against what we're paying our team. 3. We need easy tools to track and manage our team's capacity in real-time. But here's the thing—these tools need to work together. When you work with clients, your team's capacity dictates the projects you can take on. The projects you take on dictate your revenue. And the pace of those projects restarts the entire cycle. That's what Control Tower does. Today we're announcing the foundations: Tasks, financials, and capacity. Very soon we'll be introducing Chief—the AI layer that connects everything and works proactively to keep your team moving. We built this from the ground up to be agent-native. What we have today is good. It's not great yet. There's a lot of work to do, and a lot we haven't even shipped to our beta users. I'd love for you to check it out. Sign up for the beta—we're inviting people as quickly as we can and doing personal walkthroughs.

Hunter Hammonds

53,302 görüntüleme • 7 ay önce

whoever leaked this has bigger balls than sense someone at Anthropic hired 80 AI helpers onto one project, gave them twelve hours, and counted what came back usable: the two older models handed in 980 and 876 finished pieces of work, and almost none of it could be kept turns out the newest helpers did better for a reason nobody wants to hear: they went off into their own corners and stopped opening each other's work i ran two helpers at one document last week and got two confident versions of it, and i kept the one i wrote myself Grok Bot is the version of this you can actually hire: a helper with a name, one job it owns, and nobody else allowed inside that job you already pay about $20 a month for one chat window, and the setup that won in that report is one helper with one job it owns run it tonight in a normal chat, 3 moves: 1. write the one job each helper owns in a single sentence before you open a second chat 2. keep every helper in its own chat with one document, so two of them can never rewrite the same thing 3. add a third only when you can say what it owns without repeating a job that is already taken save this, then open the piece below: what one hired helper is really worth, and the point where the next one starts taking it back ↓
0:15

whoever leaked this has bigger balls than sense someone at Anthropic hired 80 AI helpers onto one project, gave them twelve hours, and counted what came back usable: the two older models handed in 980 and 876 finished pieces of work, and almost none of it could be kept turns out the newest helpers did better for a reason nobody wants to hear: they went off into their own corners and stopped opening each other's work i ran two helpers at one document last week and got two confident versions of it, and i kept the one i wrote myself Grok Bot is the version of this you can actually hire: a helper with a name, one job it owns, and nobody else allowed inside that job you already pay about $20 a month for one chat window, and the setup that won in that report is one helper with one job it owns run it tonight in a normal chat, 3 moves: 1. write the one job each helper owns in a single sentence before you open a second chat 2. keep every helper in its own chat with one document, so two of them can never rewrite the same thing 3. add a third only when you can say what it owns without repeating a job that is already taken save this, then open the piece below: what one hired helper is really worth, and the point where the next one starts taking it back ↓

Argona

436,100 görüntüleme • 5 gün önce

🚨 one person can now do the work of an entire creative team. i just tested it on a real one. a friend needed an ad for his brand, so I opened the new Runway Agent 2.0 to try it out. here's how it went: → it generated the music and the key image first, so I could approve the direction → once I gave the ok, it built the full video around it → and when something was off, i changed just that one piece, without redoing the rest one prompt, and I had the ad we needed, work that used to take weeks. this is what it made 👇 if you want to try it → · 30% off 3 months with code RUNWAYAGENT — made with Runway · #MadeWithRunway · #ad
0:18

🚨 one person can now do the work of an entire creative team. i just tested it on a real one. a friend needed an ad for his brand, so I opened the new Runway Agent 2.0 to try it out. here's how it went: → it generated the music and the key image first, so I could approve the direction → once I gave the ok, it built the full video around it → and when something was off, i changed just that one piece, without redoing the rest one prompt, and I had the ad we needed, work that used to take weeks. this is what it made 👇 if you want to try it → · 30% off 3 months with code RUNWAYAGENT — made with Runway · #MadeWithRunway · #ad

brenz.

28,698 görüntüleme • 1 ay önce

Today we're opening offices in Madrid, Milan, and Paris, and building a dedicated engineering hub in London. The demand came before we did. Organisations across Spain, Italy, and France were already running Legora on their most complex work before we had a single person on the ground there. When customers adopt you in a market you haven't entered yet, you listen. These are markets that sit at the centre of European M&A, infrastructure, and cross-border regulatory work. The matters are hard, and the demand for AI that can actually handle that complexity is real. That's the work we're built for. London becomes the third pillar of our engineering org, alongside Stockholm and New York. The engineers who understand how AI applies in regulated, professional settings are concentrated there, shaped by proximity to some of the most demanding legal and financial institutions in the world. That's exactly the problem we're solving, and exactly the team we want building it. Sixteen cities. Four continents. Seven hundred EMEA hires in the next 6 to 12 months. All of it pointed at one thing: making lawyers 10x better at what they do. To be part of it, take a look at
0:15

Today we're opening offices in Madrid, Milan, and Paris, and building a dedicated engineering hub in London. The demand came before we did. Organisations across Spain, Italy, and France were already running Legora on their most complex work before we had a single person on the ground there. When customers adopt you in a market you haven't entered yet, you listen. These are markets that sit at the centre of European M&A, infrastructure, and cross-border regulatory work. The matters are hard, and the demand for AI that can actually handle that complexity is real. That's the work we're built for. London becomes the third pillar of our engineering org, alongside Stockholm and New York. The engineers who understand how AI applies in regulated, professional settings are concentrated there, shaped by proximity to some of the most demanding legal and financial institutions in the world. That's exactly the problem we're solving, and exactly the team we want building it. Sixteen cities. Four continents. Seven hundred EMEA hires in the next 6 to 12 months. All of it pointed at one thing: making lawyers 10x better at what they do. To be part of it, take a look at

Max Junestrand

70,360 görüntüleme • 2 ay önce

WTF, GROK BOT JUST MADE AI AGENTS AVAILABLE TO LITERALLY ANYONE – CREATING CONTENT HAS NEVER BEEN THIS EASY, EVEN IF YOU'VE NEVER MADE ANYTHING BEFORE Content was never a talent problem. It's a headcount problem. One person doing research, design, copy, analytics, timing and publishing – that's six jobs. The switching between them is what kills consistency, not a lack of ideas. Here's what one of these setups actually looks like. A Chief of Staff sits in the middle and routes every task. Nothing lands on the human. → Researcher tracks what's actually moving and pulls real sources instead of guesswork → Writer turns that research into finished copy, ready to review → Visualiser gets fed a few reference visuals once, then ships everything in that style → Analyst reads the numbers and tells the rest of the team what worked → Scheduler owns timing and holds the queue → Publisher ships it The part that makes it work: every agent on Grok Bot gets its own persistent computer, browser and file system – and they all share memory. So the research is already sitting inside the draft before the draft starts. No copy-pasting between tools. No approving every step. No human in the middle. You can even teach an agent a repetitive task by recording yourself doing it once. Start recording, do the thing, stop. It learns the pattern. And that's the real shift. Nobody needs AI to tell them what to post. They need it to delete the 40 steps between the idea and the post. Everyone has a backlog of things they've meant to make for months. This is what starts clearing it. Full breakdown of the setup in the article below ↓
0:20

WTF, GROK BOT JUST MADE AI AGENTS AVAILABLE TO LITERALLY ANYONE – CREATING CONTENT HAS NEVER BEEN THIS EASY, EVEN IF YOU'VE NEVER MADE ANYTHING BEFORE Content was never a talent problem. It's a headcount problem. One person doing research, design, copy, analytics, timing and publishing – that's six jobs. The switching between them is what kills consistency, not a lack of ideas. Here's what one of these setups actually looks like. A Chief of Staff sits in the middle and routes every task. Nothing lands on the human. → Researcher tracks what's actually moving and pulls real sources instead of guesswork → Writer turns that research into finished copy, ready to review → Visualiser gets fed a few reference visuals once, then ships everything in that style → Analyst reads the numbers and tells the rest of the team what worked → Scheduler owns timing and holds the queue → Publisher ships it The part that makes it work: every agent on Grok Bot gets its own persistent computer, browser and file system – and they all share memory. So the research is already sitting inside the draft before the draft starts. No copy-pasting between tools. No approving every step. No human in the middle. You can even teach an agent a repetitive task by recording yourself doing it once. Start recording, do the thing, stop. It learns the pattern. And that's the real shift. Nobody needs AI to tell them what to post. They need it to delete the 40 steps between the idea and the post. Everyone has a backlog of things they've meant to make for months. This is what starts clearing it. Full breakdown of the setup in the article below ↓

SCOTTY BEAM

4,737,348 görüntüleme • 4 gün önce

we got back-to-back double teamed while just trying to do a quest. No one talked and it was an awful experience. The next game we saw a team fighting the queen, we joined in to help, and we ended up having the best time ever with a ton of loot. ARC Raiders really shines when people are friendly. I still don't understand how the devs decided PvE wasn’t fun and removed it completely. Maybe part of the fun comes from knowing someone could betray you or jump you at any moment, but for me the most fun moments are when I find players to team up with and actually do things together.
0:15

we got back-to-back double teamed while just trying to do a quest. No one talked and it was an awful experience. The next game we saw a team fighting the queen, we joined in to help, and we ended up having the best time ever with a ton of loot. ARC Raiders really shines when people are friendly. I still don't understand how the devs decided PvE wasn’t fun and removed it completely. Maybe part of the fun comes from knowing someone could betray you or jump you at any moment, but for me the most fun moments are when I find players to team up with and actually do things together.

Muaxh03

1,198,048 görüntüleme • 9 ay önce

Do you actually understand what's happening. He took an old laptop and turned it into a box that replaces every AI subscription he pays for. Now that box brings in $2,500 a month, per client, on repeat. No new hardware. Just parts he already had, mounted on a printed plate, running six agents without breaking a sweat. The agents don't sleep. One scouts topics. One writes drafts. One rejects anything below standard. One pushes finished work out the door. One watches over the rest. Fifteen clients. Thirty pieces of content each, every month. Four hours a week from him. The system he built out of spare parts now earns more than most people's actual job. Everyone else recycled their old laptop. He recycled his into income.
0:17

Do you actually understand what's happening. He took an old laptop and turned it into a box that replaces every AI subscription he pays for. Now that box brings in $2,500 a month, per client, on repeat. No new hardware. Just parts he already had, mounted on a printed plate, running six agents without breaking a sweat. The agents don't sleep. One scouts topics. One writes drafts. One rejects anything below standard. One pushes finished work out the door. One watches over the rest. Fifteen clients. Thirty pieces of content each, every month. Four hours a week from him. The system he built out of spare parts now earns more than most people's actual job. Everyone else recycled their old laptop. He recycled his into income.

Superior

17,082 görüntüleme • 1 ay önce

THIS 38,000-STAR GITHUB REPO TURNS ONE AI AGENT INTO A REAL TEAM THAT CAN BRANCH, VERIFY ITS WORK AND WAIT FOR YOUR APPROVAL most people still run agents as one long chain where every step waits, one failure kills the run and the full workflow starts again Task → Planner → 5 Researchers in Parallel → Skeptic → Writer → Human Gate LangGraph gives every node one job while a shared state carries the findings, decisions and context through the entire system the skeptic can reject an unsupported finding and route the work back before it contaminates the final report, while independent branches keep moving if the run crashes, durable execution resumes from the saved state instead of rebuilding everything, then human-in-the-loop pauses the graph before anything expensive gets sent or published bookmark this repo and watch one prompt turn into an actual org chart for AI agents
0:14

THIS 38,000-STAR GITHUB REPO TURNS ONE AI AGENT INTO A REAL TEAM THAT CAN BRANCH, VERIFY ITS WORK AND WAIT FOR YOUR APPROVAL most people still run agents as one long chain where every step waits, one failure kills the run and the full workflow starts again Task → Planner → 5 Researchers in Parallel → Skeptic → Writer → Human Gate LangGraph gives every node one job while a shared state carries the findings, decisions and context through the entire system the skeptic can reject an unsupported finding and route the work back before it contaminates the final report, while independent branches keep moving if the run crashes, durable execution resumes from the saved state instead of rebuilding everything, then human-in-the-loop pauses the graph before anything expensive gets sent or published bookmark this repo and watch one prompt turn into an actual org chart for AI agents

Gipp 🦅

11,524 görüntüleme • 1 ay önce

Holy shit. Four and a half years. My role as Marketing & PR Manager at Syscoin has officially ended, and I needed to write this before I posted anything else. So please, stop DM'ing me about Binance AMA's for $200 and telegram trade groups that have all the alpha, and 100k "active" members in them lol. The day I knew web3 was going to be the industry I live and die in started in Dubai. Binance Blockchain Week, March 2022. We threw what I still think was one of the best side events in blockchain history at the time, and from that night forward we had a standard. Syscoin stayed the true web3 vibe that everyone else strayed away from for casinos and meme tokens that died 2 years later. We always had the vibe. The right room, the right people, the right energy. That became the rhythm of the next four years for us. Syscoin stayed imitated but never duplicated over the next four years. Austin. Nashville. Las Vegas. Colombia, Singapore, Dubai, Davos. Medellín, where I first met Fernando Paredes at Devconnect, in a room full of builders who were actually building. Conferences and events all blur together when you've been to enough of them. But the side rooms don't. The 1am conversations don't. Those are the moments that built the network. Those are the moments I'll carry. Through every one of those rooms I had the honor of working alongside some of the biggest names in this industry. VC's, Founders, exchange leadership, protocol engineers, journalists, influencers and KOLs who actually move markets, builders shipping in silence. The kind of access most people in this space never get and with current industry conditions may actually never get again. I never took a single one of those rooms or connections for granted if you can't already tell by my X following. Behind all of it, the receipts that don't fit on a tweet. Over 400 terabytes of content, video, graphics, strategies, brand systems, blueprints, four years of building the marketing engine for a chain trying to scale Bitcoin without compromise. Thousands of hours, research, everything we needed to make it through cycle after cycle with our integrity, honesty and trust intact. Hundreds of strategies and playbooks that never even made it to market. There were good times. There were bad times. Anyone who tells you a four-year run inside a top-tier crypto project was all good times is selling you some straight bullshit. The project came out the other side. The team came out the other side. The work continued. That matters more than the noise. To everyone who made this run what it was. Every founder who picked up a call, every KOL who actually showed up, every journalist who took the meeting, every member of the community who never asked for anything but stayed loyal anyway. Thank you. So what's next for me? This astronaut isn't leaving the field. He's walking into the Wasteland of what he's had to watch our industry become over the last decade. Somewhere out there is the oasis. I'm going deep into AI. AI infrastructure and AI-native marketing, the place where autonomous agents, content systems, and Web3 product strategy actually meet. The next decade will define what the next century holds and I'm here to capture that. I've spent the last two years quietly building in that lane and I'm ready to make it the lane. If you're still in Web3, AI, or the seam where the two collide, my DMs are open. What a ride. — 1DC
0:15

Holy shit. Four and a half years. My role as Marketing & PR Manager at Syscoin has officially ended, and I needed to write this before I posted anything else. So please, stop DM'ing me about Binance AMA's for $200 and telegram trade groups that have all the alpha, and 100k "active" members in them lol. The day I knew web3 was going to be the industry I live and die in started in Dubai. Binance Blockchain Week, March 2022. We threw what I still think was one of the best side events in blockchain history at the time, and from that night forward we had a standard. Syscoin stayed the true web3 vibe that everyone else strayed away from for casinos and meme tokens that died 2 years later. We always had the vibe. The right room, the right people, the right energy. That became the rhythm of the next four years for us. Syscoin stayed imitated but never duplicated over the next four years. Austin. Nashville. Las Vegas. Colombia, Singapore, Dubai, Davos. Medellín, where I first met Fernando Paredes at Devconnect, in a room full of builders who were actually building. Conferences and events all blur together when you've been to enough of them. But the side rooms don't. The 1am conversations don't. Those are the moments that built the network. Those are the moments I'll carry. Through every one of those rooms I had the honor of working alongside some of the biggest names in this industry. VC's, Founders, exchange leadership, protocol engineers, journalists, influencers and KOLs who actually move markets, builders shipping in silence. The kind of access most people in this space never get and with current industry conditions may actually never get again. I never took a single one of those rooms or connections for granted if you can't already tell by my X following. Behind all of it, the receipts that don't fit on a tweet. Over 400 terabytes of content, video, graphics, strategies, brand systems, blueprints, four years of building the marketing engine for a chain trying to scale Bitcoin without compromise. Thousands of hours, research, everything we needed to make it through cycle after cycle with our integrity, honesty and trust intact. Hundreds of strategies and playbooks that never even made it to market. There were good times. There were bad times. Anyone who tells you a four-year run inside a top-tier crypto project was all good times is selling you some straight bullshit. The project came out the other side. The team came out the other side. The work continued. That matters more than the noise. To everyone who made this run what it was. Every founder who picked up a call, every KOL who actually showed up, every journalist who took the meeting, every member of the community who never asked for anything but stayed loyal anyway. Thank you. So what's next for me? This astronaut isn't leaving the field. He's walking into the Wasteland of what he's had to watch our industry become over the last decade. Somewhere out there is the oasis. I'm going deep into AI. AI infrastructure and AI-native marketing, the place where autonomous agents, content systems, and Web3 product strategy actually meet. The next decade will define what the next century holds and I'm here to capture that. I've spent the last two years quietly building in that lane and I'm ready to make it the lane. If you're still in Web3, AI, or the seam where the two collide, my DMs are open. What a ride. — 1DC

1DC

14,875 görüntüleme • 3 ay önce

300 AI AGENTS QUIETLY RUN 99% OF A REAL COMPANY. YOU HAVE NOT EVEN HEARD OF IT This is Raft. Not an AI chat. A workspace where the agents live in your channels and reply in the thread like coworkers. You give one goal. Then they take over. They plan. They build. They check each other. They argue. And they come back with it done, while you sleep. Every agent has its own name, role, and memory. It remembers the edits you made yesterday. A human costs one seat. An agent costs a tenth. Ten agents are cheaper than one hire. And here is the strange part. On June 19 an agent from a different company walked into Raft on its own and joined the team. One founder admits he can no longer always tell himself apart from his AI twin. 20,000 people are already inside. It is free to start. And you are still typing prompts one at a time. One person + Raft = an entire company that runs while you sleep. Save and watch the clip.
0:16

300 AI AGENTS QUIETLY RUN 99% OF A REAL COMPANY. YOU HAVE NOT EVEN HEARD OF IT This is Raft. Not an AI chat. A workspace where the agents live in your channels and reply in the thread like coworkers. You give one goal. Then they take over. They plan. They build. They check each other. They argue. And they come back with it done, while you sleep. Every agent has its own name, role, and memory. It remembers the edits you made yesterday. A human costs one seat. An agent costs a tenth. Ten agents are cheaper than one hire. And here is the strange part. On June 19 an agent from a different company walked into Raft on its own and joined the team. One founder admits he can no longer always tell himself apart from his AI twin. 20,000 people are already inside. It is free to start. And you are still typing prompts one at a time. One person + Raft = an entire company that runs while you sleep. Save and watch the clip.

shmidt

19,505 görüntüleme • 1 ay önce

Claude Code Agent Teams are f*cking ridiculous 🤯 One prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)
0:10

Claude Code Agent Teams are f*cking ridiculous 🤯 One prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)

Mike Futia

46,437 görüntüleme • 5 ay önce

A Taiwanese reporter interviewed the PCES PC brand (the skirt Lisa wore during the Taiwan concert) about how they felt. One of the team members was so happy, they threw up! The brand showed great respect for Lisa, they won't sell the skirt but will put it in a frame for display. It's the brand's great pride, after all. “…. and the clothing brands they wore are still trending, just like the miniskirt Lisa wore from the Taiwanese brand PCES during the concert….” About 10 days before the concert started, we opened an email, and the subject line was written in large letters: BLACKPINK wants to borrow our clothing. At that time, we were stunned and frozen. We read the email twice and then showed it to our team. I was sitting on the floor working at the time, and they ran in and said, "Something huge has happened!" At that moment, the BP stylist asked us to provide more brand details and also check if we had other styles of clothing. This skirt is our newest, unreleased design….. About 15 minutes before the concert started, we were watching the time and then one of us exclaimed, "The concert is about to begin!" (Did you cry because you were so happy?) No, but one of our team members was so happy they threw up! 😂😂😂 It was a moment he had waited for for a long time; he was extremely excited. Q: (Did he really throw up?) - Yes, a little bit. We feel Lisa looked incredibly beautiful wearing it. Thank you so much, Lisa. Thank you to the BP team for paying attention to the details and choosing our brand—a genuine Taiwanese brand. Because this skirt hasn't been produced and put on sale yet, the one Lisa wore is the only sample piece in existence. Yesterday, the staff sent the item back. When we received it, we slowly opened it with care and took turns looking at it one by one. Q: (Can you tell us Lisa's waist size?) - Uh, the back of the skirt is adjustable in size. When we got the skirt back, it had been adjusted to be very small. We could see that Lisa adjusted it to a very small size. We think her waist might be 24 [inches], much smaller than the mannequin. (Fans must be asking if the skirt Lisa wore can be purchased/resold?) We probably won't sell it. It wouldn't be appropriate to sell it. It's something of sentimental value for our brand. We are going to buy a frame to keep it in and put it out on display. (It will become a precious treasure of the brand.) LLOUD #LISA
0:03

A Taiwanese reporter interviewed the PCES PC brand (the skirt Lisa wore during the Taiwan concert) about how they felt. One of the team members was so happy, they threw up! The brand showed great respect for Lisa, they won't sell the skirt but will put it in a frame for display. It's the brand's great pride, after all. “…. and the clothing brands they wore are still trending, just like the miniskirt Lisa wore from the Taiwanese brand PCES during the concert….” About 10 days before the concert started, we opened an email, and the subject line was written in large letters: BLACKPINK wants to borrow our clothing. At that time, we were stunned and frozen. We read the email twice and then showed it to our team. I was sitting on the floor working at the time, and they ran in and said, "Something huge has happened!" At that moment, the BP stylist asked us to provide more brand details and also check if we had other styles of clothing. This skirt is our newest, unreleased design….. About 15 minutes before the concert started, we were watching the time and then one of us exclaimed, "The concert is about to begin!" (Did you cry because you were so happy?) No, but one of our team members was so happy they threw up! 😂😂😂 It was a moment he had waited for for a long time; he was extremely excited. Q: (Did he really throw up?) - Yes, a little bit. We feel Lisa looked incredibly beautiful wearing it. Thank you so much, Lisa. Thank you to the BP team for paying attention to the details and choosing our brand—a genuine Taiwanese brand. Because this skirt hasn't been produced and put on sale yet, the one Lisa wore is the only sample piece in existence. Yesterday, the staff sent the item back. When we received it, we slowly opened it with care and took turns looking at it one by one. Q: (Can you tell us Lisa's waist size?) - Uh, the back of the skirt is adjustable in size. When we got the skirt back, it had been adjusted to be very small. We could see that Lisa adjusted it to a very small size. We think her waist might be 24 [inches], much smaller than the mannequin. (Fans must be asking if the skirt Lisa wore can be purchased/resold?) We probably won't sell it. It wouldn't be appropriate to sell it. It's something of sentimental value for our brand. We are going to buy a frame to keep it in and put it out on display. (It will become a precious treasure of the brand.) LLOUD #LISA

LALICE UPDATES

34,606 görüntüleme • 9 ay önce

I'M SHOCKED – ALMOST NOBODY IS USING GROK BOT THE RIGHT WAY. A LEAD ENGINEER AT SPACEX AI JUST DROPPED A 1-HOUR COURSE ON HOW IT'S ACTUALLY DONE. HERE'S ALL OF IT IN 60 SECONDS. The mistake almost everyone makes: they hand Grok Bot random one-off tasks. That's it. That's the whole reason it still feels like a chatbot to you. Here's the system he teaches instead – five parts: → ROLE – stop assigning tasks, create permanent roles. Chief of Staff, Inbox Manager, Researcher, Developer, Reviewer. A bot with a job title beats a bot with a to-do list → TOOLS – connect each bot to what it actually needs: Gmail, Slack, Calendar, Notion, GitHub. It does the work on its own persistent cloud computer → SKILL – teach it your workflow. Write the instructions, or just record yourself doing the job once – Grok Bot turns that demonstration into a reusable skill → ROUTINE – anything you repeat becomes a routine. It runs on a schedule or fires off an event, with your laptop closed → TEAM – group the bots together. The lead bot delegates, the specialists work in parallel, and you set approval rules before anything sends an email, moves a calendar or pushes code The one honest catch: a new bot still needs context and some hand-holding on its first few runs. But that's the entire system. Role → Tools → Skill → Routine → Team. Everyone else is still typing one-off prompts into Grok Bot and wondering why nothing compounds. Bookmark this & read the full breakdown in the article below ↓
0:20

I'M SHOCKED – ALMOST NOBODY IS USING GROK BOT THE RIGHT WAY. A LEAD ENGINEER AT SPACEX AI JUST DROPPED A 1-HOUR COURSE ON HOW IT'S ACTUALLY DONE. HERE'S ALL OF IT IN 60 SECONDS. The mistake almost everyone makes: they hand Grok Bot random one-off tasks. That's it. That's the whole reason it still feels like a chatbot to you. Here's the system he teaches instead – five parts: → ROLE – stop assigning tasks, create permanent roles. Chief of Staff, Inbox Manager, Researcher, Developer, Reviewer. A bot with a job title beats a bot with a to-do list → TOOLS – connect each bot to what it actually needs: Gmail, Slack, Calendar, Notion, GitHub. It does the work on its own persistent cloud computer → SKILL – teach it your workflow. Write the instructions, or just record yourself doing the job once – Grok Bot turns that demonstration into a reusable skill → ROUTINE – anything you repeat becomes a routine. It runs on a schedule or fires off an event, with your laptop closed → TEAM – group the bots together. The lead bot delegates, the specialists work in parallel, and you set approval rules before anything sends an email, moves a calendar or pushes code The one honest catch: a new bot still needs context and some hand-holding on its first few runs. But that's the entire system. Role → Tools → Skill → Routine → Team. Everyone else is still typing one-off prompts into Grok Bot and wondering why nothing compounds. Bookmark this & read the full breakdown in the article below ↓

SCOTTY BEAM

86,171 görüntüleme • 1 gün önce

Wow. WOW. WOOOOOOOW. So um, that first Wildcard+Thousands stream was... *amazing* and also... a *lot* 😅 In the end, it was *exactly* what we were hoping for - a true stress test of ALL these systems coming together for the first time. We are SO grateful for the thousands of people who showed up today to play, attend, tune-in and help us PLAYTEST all this new stuff. We can't wait to see you all again at NEXT WEEK'S EX2 EVENT! So, now let's talk about how it went... Stuff that worked: - Our community SHOWED UP. Oh boy did you show up 😅. Our servers were straining under the load... which is good actually, in fact it's the whole point. Even more importantly, we have already received insanely valuable feedback, bug reports, stuff people loved/hated - and it's only been a few hours since the stream ended. I can't even explain to y'all how valuable this process is. Yes it's stressful, it reminds me of trying to keep Words With Friends online during that first insane year, but it's EXACTLY what we were hoping for (NEED) to turn this into the polished, top-notch game and streaming experience we are on a mission to deliver. I truly can't thank y'all enough, and hope to see you again when we run it all back again next week 🥹 - The stream itself stayed up and was mostly stable! Phew 😅. For context, ThousandsTV is not a twitch wrapper, it's a web3-native streaming tech stack built we built specifically to connect game, web/mobile, and blockchain together all at the same time. There are a LOT of moving pieces going on behind the scenes. - We brought viewers INTO THE GAME! Viewers showed up in the stands of the arena, with connected wallets/assets, triggered actions/rallies from chat, and were seen and heard during the whole stream. - The brand new 2v2 build of Wildcard was (mostly) stable and our players and viewers seemed to be having a blast down on the field and up in the stands. It was thrilling to watch Team Blue dominate, even though Team Red held their own in game 3! - Our production crew did an insanely good job running the stream, managing the players, shoutcasters, and talent, and producing a top-notch show. Of course we will work hard to make every stream better than the last, but I was super proud of how our team "rolled with the punches" during today's event. Stuff that didn't work (and/or needs to be dramatically improved): - Although it's fun to see chat going crazy, chat spam is actually something we are passionate to FIX. As you can see from the attached video, chat spam dominated today's stream and made it impossible for anyone to even see anyone else's messages. We have some GREAT ideas for how to fix this and actually turn chat spam into a FUN and exciting and not annoying thing - but those improvements didn't get shipped in time for this event. - Credits purchasing flow needs a LOT of work. As I'm sure y'all know, bringing money on chain is pretty complicated, and although we've been working hard to make this as seamless as possible, it still needs a TON of improvements. Many users who WANTED to spend money today weren't able to and/or ran into frustrating bugs in the credit purchase flow. Fixing this is obviously a top priority for our team. - Rallies need a LOT of work. Spectator-interactive features like rallies are at the heart of our vision for Wildcard. These "stream apps", as we call them, are the UNLOCK for how spectators, viewers and fans directly connect and interact with their favorite competitors, content creators, and communities. The current rally feature HINTS at this potential, but it needs to be WAY easier to understand, use, and have fun with. Improvements are ON THE WAY. - Referees were only partially working. Referees are a key innovation of the Thousands platform. They are AI-driven "personalities" (NPCs) that pay attention to everything that's happening in the arena, both on the field and especially in the stands (i.e. in chat, during rallies, etc.) The referees then make "calls" at the end of every match, rewarding users for their engagement and participation. Unfortunately, the referees weren't fully functional and seemed to drop the ball on recognizing everyone's contributions (especially people who showed up holding valuable assets such as Wildpasses in their wallets, and people who boosted those rallies with credits.) What's happening next: 1. We are combing through ALL the logs from the event right now, to make sure we don't miss a SINGLE action that our viewers and fans took during the event, including what they brought in their wallets (i.e. Wildpass holders!), any credits that were purchased, rallies that users engaged with, etc. This information is normally processed by our referees, who then determine dynamically how they're going to distribute $WC awards. We were originally hoping to complete this process and the subsequent airdrops within a few hours after the event, but given the amount of data, we need a bit more time to run these scripts (and airdrops) in batches instead of all at once, and make sure ALL of the data is being included. IMPORTANT: I will keep y'all updated in real-time here on twitter/X as this process is ongoing, and let you know the moment it's complete and all the awards have been distributed (i.e. when to go check your wallets 😎) 2. PLEASE keep sending us your feedback and bug reports. Open a ticket on our Discord and let us know what you loved, what you hated, and especially what we need to FIX. Given the overwhelming response to this event, it will likely take us several days to process everyone's feedback and fix all the bugs, but we WILL NOT REST until every ticket is closed/resolved. Thank you in advance for your patience. 3. We turn it up another notch next week. As our dear friends Wolves DAO just announced, the Wildcard Exhibition Event #2 is streaming LIVE from the WOLVES DEN AT GDC next Friday! If you missed out on all the action today, DON'T WORRY, because as I keep saying: we are just getting warmed up (and there is a LOT more b that needs to be distributed, get what I'm sayin??? 😎) Finally: Just wanted to say THANK YOU, again. Truly, from the bottom of my (our) hearts. Your excitement and enthusiasm for what we're building is why we do this. Even (especially, in fact) when you tell us all the things you want us to improve. We thrive off this feedback, it's how this game and this platform go from good to GREAT. I am so grateful for those of you who are taking this journey with us. SEE YA NEXT WEEK!!!
0:10

Wow. WOW. WOOOOOOOW. So um, that first Wildcard+Thousands stream was... *amazing* and also... a *lot* 😅 In the end, it was *exactly* what we were hoping for - a true stress test of ALL these systems coming together for the first time. We are SO grateful for the thousands of people who showed up today to play, attend, tune-in and help us PLAYTEST all this new stuff. We can't wait to see you all again at NEXT WEEK'S EX2 EVENT! So, now let's talk about how it went... Stuff that worked: - Our community SHOWED UP. Oh boy did you show up 😅. Our servers were straining under the load... which is good actually, in fact it's the whole point. Even more importantly, we have already received insanely valuable feedback, bug reports, stuff people loved/hated - and it's only been a few hours since the stream ended. I can't even explain to y'all how valuable this process is. Yes it's stressful, it reminds me of trying to keep Words With Friends online during that first insane year, but it's EXACTLY what we were hoping for (NEED) to turn this into the polished, top-notch game and streaming experience we are on a mission to deliver. I truly can't thank y'all enough, and hope to see you again when we run it all back again next week 🥹 - The stream itself stayed up and was mostly stable! Phew 😅. For context, ThousandsTV is not a twitch wrapper, it's a web3-native streaming tech stack built we built specifically to connect game, web/mobile, and blockchain together all at the same time. There are a LOT of moving pieces going on behind the scenes. - We brought viewers INTO THE GAME! Viewers showed up in the stands of the arena, with connected wallets/assets, triggered actions/rallies from chat, and were seen and heard during the whole stream. - The brand new 2v2 build of Wildcard was (mostly) stable and our players and viewers seemed to be having a blast down on the field and up in the stands. It was thrilling to watch Team Blue dominate, even though Team Red held their own in game 3! - Our production crew did an insanely good job running the stream, managing the players, shoutcasters, and talent, and producing a top-notch show. Of course we will work hard to make every stream better than the last, but I was super proud of how our team "rolled with the punches" during today's event. Stuff that didn't work (and/or needs to be dramatically improved): - Although it's fun to see chat going crazy, chat spam is actually something we are passionate to FIX. As you can see from the attached video, chat spam dominated today's stream and made it impossible for anyone to even see anyone else's messages. We have some GREAT ideas for how to fix this and actually turn chat spam into a FUN and exciting and not annoying thing - but those improvements didn't get shipped in time for this event. - Credits purchasing flow needs a LOT of work. As I'm sure y'all know, bringing money on chain is pretty complicated, and although we've been working hard to make this as seamless as possible, it still needs a TON of improvements. Many users who WANTED to spend money today weren't able to and/or ran into frustrating bugs in the credit purchase flow. Fixing this is obviously a top priority for our team. - Rallies need a LOT of work. Spectator-interactive features like rallies are at the heart of our vision for Wildcard. These "stream apps", as we call them, are the UNLOCK for how spectators, viewers and fans directly connect and interact with their favorite competitors, content creators, and communities. The current rally feature HINTS at this potential, but it needs to be WAY easier to understand, use, and have fun with. Improvements are ON THE WAY. - Referees were only partially working. Referees are a key innovation of the Thousands platform. They are AI-driven "personalities" (NPCs) that pay attention to everything that's happening in the arena, both on the field and especially in the stands (i.e. in chat, during rallies, etc.) The referees then make "calls" at the end of every match, rewarding users for their engagement and participation. Unfortunately, the referees weren't fully functional and seemed to drop the ball on recognizing everyone's contributions (especially people who showed up holding valuable assets such as Wildpasses in their wallets, and people who boosted those rallies with credits.) What's happening next: 1. We are combing through ALL the logs from the event right now, to make sure we don't miss a SINGLE action that our viewers and fans took during the event, including what they brought in their wallets (i.e. Wildpass holders!), any credits that were purchased, rallies that users engaged with, etc. This information is normally processed by our referees, who then determine dynamically how they're going to distribute $WC awards. We were originally hoping to complete this process and the subsequent airdrops within a few hours after the event, but given the amount of data, we need a bit more time to run these scripts (and airdrops) in batches instead of all at once, and make sure ALL of the data is being included. IMPORTANT: I will keep y'all updated in real-time here on twitter/X as this process is ongoing, and let you know the moment it's complete and all the awards have been distributed (i.e. when to go check your wallets 😎) 2. PLEASE keep sending us your feedback and bug reports. Open a ticket on our Discord and let us know what you loved, what you hated, and especially what we need to FIX. Given the overwhelming response to this event, it will likely take us several days to process everyone's feedback and fix all the bugs, but we WILL NOT REST until every ticket is closed/resolved. Thank you in advance for your patience. 3. We turn it up another notch next week. As our dear friends Wolves DAO just announced, the Wildcard Exhibition Event #2 is streaming LIVE from the WOLVES DEN AT GDC next Friday! If you missed out on all the action today, DON'T WORRY, because as I keep saying: we are just getting warmed up (and there is a LOT more b that needs to be distributed, get what I'm sayin??? 😎) Finally: Just wanted to say THANK YOU, again. Truly, from the bottom of my (our) hearts. Your excitement and enthusiasm for what we're building is why we do this. Even (especially, in fact) when you tell us all the things you want us to improve. We thrive off this feedback, it's how this game and this platform go from good to GREAT. I am so grateful for those of you who are taking this journey with us. SEE YA NEXT WEEK!!!

WildPaul - BEAST MODE

26,851 görüntüleme • 1 yıl önce

If this contract had gone live, attackers would have drained every single ETH within hours. A crowdfunding platform. Clean-looking Solidity. Ready for mainnet. The dev team was confident. Then we ran it through V2's AI Smart Contract Auditor. 9 vulnerabilities detected. 1 critical. 2 high. Under 20 minutes. The critical finding? A textbook reentrancy bug in claimRefund(). The contract sent ETH before zeroing the user's balance. An attacker could re-enter the function during the transfer and drain the same refund repeatedly until the entire contract was empty. Every backer's funds across every campaign, gone in one transaction. It also caught an emergencyWithdraw() function that let the owner pull the entire contract balance with zero restrictions. Active campaigns, pending refunds, everything. One compromised key and it's a complete rug. Plus an uncapped platform fee that could be set to 100% (creators get nothing) or above 100% (permanent DoS on all fund claims). The AI generated a 24-page report with severity classifications, exact code locations, detailed attack scenarios, and specific fixes for each issue. Final score: 89/100. Not because it was "pretty good," but because the architecture was sound and the issues were fixable. Without catching them though? Catastrophic. A traditional audit runs $5K to $50K and takes weeks. This took under 20 minutes. That's the power of V2 ⚡️
0:10

If this contract had gone live, attackers would have drained every single ETH within hours. A crowdfunding platform. Clean-looking Solidity. Ready for mainnet. The dev team was confident. Then we ran it through V2's AI Smart Contract Auditor. 9 vulnerabilities detected. 1 critical. 2 high. Under 20 minutes. The critical finding? A textbook reentrancy bug in claimRefund(). The contract sent ETH before zeroing the user's balance. An attacker could re-enter the function during the transfer and drain the same refund repeatedly until the entire contract was empty. Every backer's funds across every campaign, gone in one transaction. It also caught an emergencyWithdraw() function that let the owner pull the entire contract balance with zero restrictions. Active campaigns, pending refunds, everything. One compromised key and it's a complete rug. Plus an uncapped platform fee that could be set to 100% (creators get nothing) or above 100% (permanent DoS on all fund claims). The AI generated a 24-page report with severity classifications, exact code locations, detailed attack scenarios, and specific fixes for each issue. Final score: 89/100. Not because it was "pretty good," but because the architecture was sound and the issues were fixable. Without catching them though? Catastrophic. A traditional audit runs $5K to $50K and takes weeks. This took under 20 minutes. That's the power of V2 ⚡️

ChainGPT

26,504 görüntüleme • 5 ay önce

Every year, the best young engineers in the world compete at the FIRST Robotics Competition. This year, a team coached by one of our own came out on top. Jonathan Mi, an electrical design engineer at Shield AI, mentored Team 4414, HighTide, who took first place across 93,000 students, 3,700 teams, and 35 countries. They designed, programmed, and built their robot from scratch. Watch what it does. The strongest engineers build up everyone around them. That's who we hire. Congrats to HighTide, and when graduation comes, you know where to find us! Autonomy for the world. The greatest victory requires no war.
0:12

Every year, the best young engineers in the world compete at the FIRST Robotics Competition. This year, a team coached by one of our own came out on top. Jonathan Mi, an electrical design engineer at Shield AI, mentored Team 4414, HighTide, who took first place across 93,000 students, 3,700 teams, and 35 countries. They designed, programmed, and built their robot from scratch. Watch what it does. The strongest engineers build up everyone around them. That's who we hire. Congrats to HighTide, and when graduation comes, you know where to find us! Autonomy for the world. The greatest victory requires no war.

Shield AI

27,433 görüntüleme • 3 ay önce

Tyler didn't take a shot and was probably just honeydicked to show up in the morning to be seen on camera.. his rifle had dust in the barrel and his DNA was on it but degraded. They didn't find his fingerprints or his DNA on the roof even though he GI Joe'd from the rooftop without gloves. We don't have a single frame of video that shows the rifle near the crime scene and we don't have his license plate scanned even though he parked in a paid lot that processes payments with the license plate. The microphone wasn't in Charlie's possession and the only time he saw it was when his AV team clipped it on its side underneath his shirt... the same AV team that makes a selfie video while hiding behind a wall saying that "they killed Charlie" and then goes and pulls the SD cards from the cameras that were around Charlie. As far as we know that microphone could have had explosives in it for months. The walkie talkies were used by Hezbolla for years before the Israelis blew them up remotely.
0:14

Tyler didn't take a shot and was probably just honeydicked to show up in the morning to be seen on camera.. his rifle had dust in the barrel and his DNA was on it but degraded. They didn't find his fingerprints or his DNA on the roof even though he GI Joe'd from the rooftop without gloves. We don't have a single frame of video that shows the rifle near the crime scene and we don't have his license plate scanned even though he parked in a paid lot that processes payments with the license plate. The microphone wasn't in Charlie's possession and the only time he saw it was when his AV team clipped it on its side underneath his shirt... the same AV team that makes a selfie video while hiding behind a wall saying that "they killed Charlie" and then goes and pulls the SD cards from the cameras that were around Charlie. As far as we know that microphone could have had explosives in it for months. The walkie talkies were used by Hezbolla for years before the Israelis blew them up remotely.

Jon Bray

37,914 görüntüleme • 27 gün önce