Urgent.News

What's breaking now, across hundreds of outlets.

Tech

My Agent Signs Real Transactions. I Don't Trust It — I Verify It.

Written for the zkVerify Agent Games Creator Track (#AgentGames). Every claim below has a receipt: a transaction hash, a score, or a rule I can point to. The question no one asks until money moves My AI agent moves real money. Not in a demo, not on a slide — on BNB Smart Chain, from a wallet I own, through the Binance Agentic Wallet. It mints NFTs, swaps tokens, and sends funds. And the first…

The wire material for this story discusses the importance of verification in AI agent transactions. The author uses their own experience with an AI agent to demonstrate the need for a verification process. They describe a hard rule their agent follows: before executing any transaction, the agent must show a decoded preview of the exact contract, function, arguments, and value.

The agent only executes the transaction after the human confirms the preview. The author explains that this delay is intentional, as it prevents the agent from executing actions without the human's explicit approval. They also mention that the agent's addresses are sourced from the human's address book rather than transaction history to prevent funds from being sent to the wrong recipients.

The author emphasizes that verifiable records, such as transaction hashes, scores, and rule compliance, are essential for confirming that the AI agent acted as claimed. They argue that trust should not be based on the agent's word alone, but rather on verifiable evidence produced by the agent's actions. The author concludes by stating that verification cuts both ways, proving both successes and losses, and that the pattern of preview, proof, and verification applies to any scenario where an AI agent acts with real-world consequences.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Building a Fully Automated CI/CD Pipeline on AWS with Docker, ECR, CodeBuild, CodePipeline and ECS Fargate

Introduction Shipping software by hand is one of the quickest ways to introduce mistakes. Someone builds an image on their laptop, pushes it to a registry, logs into a console and clicks through a…

  • CI/CD pipeline automates software release process on AWS
  • CodePipeline extracts latest code from GitHub on code push
  • ECS Fargate deploys updated container without manual intervention

Estimating Popularity Without Collecting a Single Answer

The board is a model, not a poll A trivia game that scores you on how popular your answer is has an obvious implementation problem: popularity is data, and data implies collecting it from players.

  • Scoring remains consistent throughout the day for honest comparisons.
  • Unexpectedly popular answers omitted from the board.
  • Trade-off between comparability and recognizing unexpected success.

More from Saturday 21 November →