Platform & Security
A signed receipt is a tamper-evident record of an action that a trading server returns after the action, carrying a cryptographic signature that anyone can check against the server's published public key.
When an AI assistant acts on your account, you need a way to know afterwards exactly what was done and that the record was not changed later. A log that the operator can edit silently is only as trustworthy as the operator. A signed and chained record lets you verify each action yourself instead of taking a dashboard's word for it.
Every action taken through AlgoVesta's MCP server returns an ed25519-signed receipt, and receipts are hash-chained per user, so altering an earlier receipt breaks every later one. The verify_receipt tool takes a receipt ID and returns two results, signature_valid and chain_valid; an action counts as verified only when both are true. The public key is served at /mcp/receipts/pubkey, so you can verify receipts independently of AlgoVesta. Every call is also written to an audit log with the tool name, arguments, result and latency, readable in the panel.