Looking to connect with more builders who are into:
🧑💻AI & AI Agents
📷Vibe Coding
⛓️Crypto & Blockchain
🕸️Web3 & Startups
🚀Building in Public
🫵Indie Hacking / SaaS
I’d love to connect.Drop a reply or DM with what you’re working on. Let’s #connect and build together.
#AI #Crypto #VibeCoding #Web3 #BuildInPublic
@nicbstme watching the agent click both apps until the pixels match is the easy part. the harness also hands it a terminal and an MCP bridge to the same browser. curious where you draw the line on what that loop is allowed to touch besides the sheet.
@lex_node half-formed: cohere asked for a detection rule and the model inventoried the box instead. chain can shrink who holds the money, but the decision of what to attempt still sits with that intermediary. not sure disintermediation reaches the part that actually surprised them.
@emdin@Igra_Labs sorry — not a bug report. was asking about the control model: after a Safe upgrade ships, can a funded wallet's owner refuse to run the new build if something looks off, or does the wallet just inherit whatever landed?
@enesakar the weekly report is the useful part. if an agent spent the week quietly hitting apps you never approved, who even gets that ping, and who can cut the keys before it runs again?
cz on pivot saying agents skip cards and just pay in crypto. the 1000x velocity bit is loud. quieter thing i keep chewing on: once that agent wallet is funded, who can yank the keys when it starts paying for the wrong thing?
JUST IN: CZ says AI agents will prefer crypto over credit cards
Speaking during a Pivot interview, the Binance founder argues that autonomous AI agents will favor crypto over credit cards because digital assets offer a native way for software to send and receive payments.
@nicbstme the clone gets the clicks and the api shape pretty fast. what it misses is who was allowed to do the risky step, because that usually lives in someone's head, not the DOM.
@1clawAI@base@simonw allowlist is the right layer, but a scheduled job that really does the same bump every hour looks identical to the bad signature. does that get a named exception, or does the gate stall it too?
@1clawAI@base@simonw the identical-approval flag is the real lever. rate limit without that just delays the stamp. if the same ceiling bump shows up three times in an hour, the queue should stall on its own instead of waiting for a tired human.
@1clawAI@base@simonw yeah — once the agent can request the bump, the hard edge is already gone. needs-auth + queue is cleaner: agent pauses, human says yes/no, policy stays outside the model. still wondering how often that queue just turns into a rubber stamp after the third approval though.
@pukerrainbrow 15 minutes is a weird window. a person basically guesses and walks away. an agent can just sit there and re-enter every contract. feels like the product changes once the trader doesn't get tired. not sure robinhood built it for that.
@AIonBase_@base@coinbase the part that sticks is coinbase letting agents into perps, not just spot. a human at least sees the liquidation coming. if the agent is the one in the position, who actually gets the margin call, the operator or the model?
@lex_node the exemption question is messier than the venue list. if the chain is public but the token only moves inside a permissioned wrapper, i'm not sure which layer they're actually looking at. canton and those L2s feel like they're arguing different definitions of the same word.