Notifications
Clear all
Topic starter
12/06/2026 9:09 pm
TL;DR: Onchain AI agents that route prompts, invoke tools, and execute multi-step actions through smart contracts shift control from off-chain APIs to verifiable blockchain workflows, according to Venice. The security question is no longer just model quality, but who can govern access, execution, and accountability when agent behaviour is embedded in onchain infrastructure.
NHIMG editorial — based on content published by Venice: AI agents, onchain execution, and the Warden Protocol partnership
Questions worth separating out
Q: How should teams govern AI agents that can execute blockchain transactions?
A: Treat them as executing identities, not simple integrations.
Q: What breaks when AI agents are allowed to act through permissionless infrastructure?
A: Centralised enforcement becomes weaker.
Q: Why do onchain AI agents expand identity risk beyond normal application access?
A: Because the agent can combine reasoning, tool selection, and execution in one runtime path.
Practitioner guidance
- Map delegated agent actions to explicit privilege boundaries Break each agent workflow into the exact actions it can perform, then assign separate authorization and review rules for routing, tool invocation, and transaction execution.
- Require execution provenance for chain-linked decisions Log the prompt, model choice, tool call, and transaction outcome for each agent action so investigators can reconstruct the full path of execution.
- Define containment points outside the platform operator Assume a permissionless design may limit your ability to pause activity centrally, then build alternative controls such as scoped delegation, immutable audit records, and contract-level kill paths where appropriate.
What's in the full article
Venice's full article covers the product and partnership detail this post intentionally leaves for the source:
- How Venice models are embedded into Warden App and Warden Studio workflows
- The article’s own explanation of onchain inference and why it is presented as verifiable
- Examples of crypto-native use cases such as swaps, transfers, DAO governance, and dynamic NFT generation
- The partnership narrative around censorship resistance, deplatforming risk, and multi-chain execution
👉 Read Venice's analysis of onchain AI agents and Warden Protocol →
Onchain AI agents and the governance gap teams are missing?
Explore further
12/06/2026 11:02 pm
Onchain AI agents are an identity governance problem before they are an AI problem. The article describes agents that reason, invoke tools, and execute blockchain transactions, which means the identity subject is not just a model but an acting runtime. That moves the discussion from content control to delegated authority, execution traceability, and permission scope. For practitioners, the key conclusion is that onchain agents should be governed as executable identities, not treated as ordinary application middleware.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%), according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: Who is accountable when an AI agent executes an onchain action incorrectly?
A: The accountable party is the organisation that granted the delegation and failed to bound it, not the blockchain itself. Practitioners should define ownership for agent policy, execution review, incident response, and revocation before deployment. If no one can explain who can stop the agent, governance is already incomplete.
👉 Read our full editorial: Onchain AI agents change the governance model for access and control
