VEYA: sealed execution now live via SDK and MCP
VEYA shipped a sealed execution flow with AES-256-GCM encrypted strategy notes, BLAKE3-verified public records, and SDK plus MCP access for agents.
VEYA | Sealed Runs Are Now Working Through SDK & MCP Yesterday, we shipped a working sealed execution flow so agents can process sensitive strategy notes without exposing them in the stored record, while keeping public execution data verifiable. Here’s what we implemented: → AES-256-GCM encryption for strategy_notes; execution details remain public. → BLAKE3 fingerprints to verify the public execution record. → 2-of-3 validator consensus, with fail-closed behavior when checks fail. → SDK + MCP support for developers to run protected executions. → Wallet-controlled Mainnet settlement—VEYA prepares unsigned transaction data; you sign it yourself. → Explicit failure handling for unavailable sealed nodes, invalid requests, and duplicate runs. We’ve tested the flow, including proof matching and failure cases. It’s a working implementation—not just a roadmap item. Want to integrate sealed execution into your agent? Explore the SDK: https://www.npmjs.com/package/@veyanet/sdk Private where it matters. Provable everywhere else. $veya