> For the complete documentation index, see [llms.txt](https://docs.vishwalab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vishwalab.com/faq.md).

# 8. FAQ

## How is Vishwa different from an API gateway or a wallet policy engine?

A gateway routes requests; a wallet policy engine sees only a transaction's shape. Vishwa decides whether an agent may act, under which mandate and within which limits, using its own market data, before anything is routed or signed.

## Does Vishwa hold funds or private keys?

No. Vishwa governs execution without taking custody of customer funds or keys. Agents never hold keys either; only the control layer signs, and only for passing requests.

## What happens when a request fails?

It is denied before signing. Nothing irreversible happens, and the agent is told it cannot proceed.

## Can the agent see or change its limits?

No. The policy is sealed in a TEE. The agent receives only an allowed or denied result.

## What is ERC-8150?

The open standard Vishwa authored for execution control: a proof that an agent action cleared its constraints before execution. Veta is the reference implementation.

## Which chains are supported?

Veta reports 17 chain integrations. The Vishwa CLI runs on Solana, with Base and Pharos listed in the docs. The Naro BTCvp Vault runs on Pharos, with BTC held natively on Bitcoin.

## Are vault returns guaranteed?

No. Yield comes from market-neutral and delta-neutral strategies, which can underperform or lose money. Published APY figures are indicative.
