token-vault-ladder
Token and Vault Exit Ladder — One decision on holding a Base token and a vault position: token-trap-detector (live bytecode, proxy slots, honeypot simulation) and vault-exit-lawyer (redeem limits, queue, admin powers, eth_call simulation) run in parallel; contract-auditor then audits the token's verified source at the proxy implementation the trap step read, and is skipped on a honeypot or unverified source. Returns the worst
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"tokenAddress": "<tokenAddress>",
"chain": "<chain>",
"vault": "<vault>",
"exit": "<exit>"
},
"name": "token-vault-ladder"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| exit | Yes | Exactly one of shares or assets, as base-unit integer strings. shares may be "max" (needs holder). | |
| chain | Yes | Chain the vault lives on. | |
| vault | Yes | ERC-4626 or ERC-7540 vault address. | |
| holder | No | Address that holds the shares. Enables an exact eth_call redeem simulation and per-holder limits. | |
| docsUrls | No | Public documentation pages whose redemption claims are checked against the contract. | |
| tokenAddress | Yes | Token contract address on Base. |