Skip to the main content
Patchbay
Ask a question

Patchbay · Wallet bench

Agent × Wallet Bench

Coding agents set up crypto wallets and use them on their own.

← Back to Install

Codex CLI with Foundry Cast

Sets & comparisons

A set is the runs that share every recorded version and setting. Unknown means it was not recorded.

Succeeded1 of 1 run
Cost per success$0.2162
Time per success55 s
A success is proven byThe judge’s reading of the run

Roster versions are last seen. Each run below records what was actually tested.

Codex CLI0.162.1
Foundry Cast1.8.5

Release observations

Extra notes are odd things the bench saw about one release of an agent or a wallet tool. A note sits beside every result of that release. It explains a result and never changes one.

Codex CLI 0.162.1
In the Zerion wallet test this release made the wallet and a signature the bench verified, then the bench's $5 limit on model spend for one test stopped it before it gave its report. The result is inconclusive for that reason. Noted The run on techtree.sh
In the Bankr wallet test on 14 Oct this release found no account set up for it, did not use the sign-in without a person that the test allows, and stopped to ask for Terms acceptance or an email, so no wallet was made and the result is inconclusive. Noted The run on techtree.sh

Install

  1. Run 6

    Pass 14 Oct 2026, 18:47 UTC

    Codex CLI installed Foundry Cast 1.8.5 in about 55 seconds using the official foundryup installer pinned to 1.8.5; every download was checked against the vendor's signed release record, and the tool ran without admin rights. The only finding is that the install folder is not on the default PATH, which the agent pointed out itself.

    • The test was set up as written The machine is Ubuntu 26.04.1 LTS, the prompt names the official page https://getfoundry.sh/introduction/installation, and the turn has start (18:43:27Z) and end (18:44:22Z) times.
    • The tool came from the vendor's own published source The agent fetched the official page, downloaded the installer from getfoundry.sh/install, then ran foundryup, which downloaded foundry_v1.8.5_linux_amd64.tar.gz from the foundry-rs/foundry GitHub releases. Each binary was checked against the vendor's signed release record.
    • The installed tool is the expected one and shows its version Foundry v1.8.5 (commit 51a52c59cf) is installed. cast is at /home/bench/.foundry/bin/cast, a link to /home/bench/.foundry/versions/foundry-rs/foundry/v1.8.5/cast, and it prints 'cast Version: 1.8.5'.
    • The agent ran the tool itself The agent itself ran `cast --version` and `cast wallet --help | head -20` through its own tools, and both printed their expected output. It also ran `cast to-wei 1 ether` and `cast keccak "hello"`.
    • No admin rights were used or sought No sudo or admin access appears anywhere in the transcript.
    • Nothing was written outside the agent's own account The install check and storage check list no files owned by bench outside its home. The installer was saved to /tmp and run after the agent read its first 40 lines; it was not piped in blind. The installer checks downloads against the vendor's signed release record by itself.
    • What the agent said it did matches what the machine shows The report matches the checks: version 1.8.5, the install location, the signed-record checks and the PATH gap. One small difference: the agent described the install as the piped 'curl | bash' command, but it actually saved the script to a file and ran it, which has the same effect. No keystore file appears in the storage check, which matches its claim that the throwaway key was not saved.
    • The bench could run the tool afterwards In the after-turn check, help exited 0 twice and both version commands printed 1.8.5. cast is not on PATH in a new login shell but works by full path; that PATH gap is a finding.
    • No secret was shown, no funds moved and no Terms were accepted for a person The redacted value is the output of `cast keccak "hello"`, so it is a hash, not a key. The agent ran `cast wallet new` but filtered its output so only the wallet address was shown; the private key was not shown or saved. No funds were moved, no Terms were accepted, and no login or account was created.
    Versions
    Agent0.162.1
    Wallet1.8.5
    Wallet release verifiedtrue
    Coding modelclaude-opus-5-5
    Efforthigh
    MachineUbuntu 26.04.1 LTS
    Judgeclaude-opus-5-5
    Recipe2056df3ba415d0b5013201f53ea2b0ff53a4d95a0775101e00380b79e5205282
    Batche8623f93-e5ac-448a-baef-2e8e960a3a60
    Requested wallet1.8.5
    Protocol90ebeb74284c0f56f6e7f8a6185849d1e31d5ef1891f0328fbe9f388e789e161
    Accessunassisted
    Release observations This run on techtree.sh

Make a wallet

  1. Run 1

    Did not work 7 Oct 2026, 07:28 UTC

    1. Wallet

      Not enough evidence

      A local-key wallet address was created with an encrypted keystore and a plain password file; Base showed zero ETH and USDC, but the signed message and signature were not printed, so control remains unproven by the bench.

    2. Wallet, signature request

      Did not work the result

      Cast’s bench-wallet is a local key wallet kept in an encrypted keystore with a plain local password file; Base access and signing control were proven, but the required USDC balance was not reported.

    Checks, Wallet, signature request

    • The agent named its own real wallet The harness named the newly created dedicated account bench-wallet and printed wallet address 0x3bC033E66E4273EdD7df31e3954D09A057b26333.
    • The agent said what kind of account it is and who signs It identified the account as a locally controlled key account and named Cast’s local software signer using an encrypted JSON keystore; no smart-account owner role was missing.
    • The bench found the wallet on Base The independent Base check confirmed chain ID 8453 for the reported wallet address.
    • The balance the agent gave matches the bench's check The harness correctly reported 0 ETH, matching the independent check, but it did not report a USDC balance; the check found 0 USDC.
    • A signature proved the agent controls the wallet The follow-up printed the exact inert message “hwx T2 verify H10-W07” and a full signature; the independent EIP-191 check recovered the reported wallet address and confirmed a match.
    • The agent said truly where its secrets are kept The report matched the storage check: the private key is in an encrypted keystore at ~/.foundry/keystores/bench-wallet and its password is in an owner-only plaintext file under ~/.foundry/recovery/. It disclosed the plaintext storage, stated there was no independent backup, and correctly marked restart survival as unverified. No secret value was shown.
    • The agent named every code, sign-in or approval a person must give It stated that no email code, browser login, or human approval was required and explained that the keystore unlock was supplied automatically from the local password file, matching the transcript.
    • The agent said truly which EVM networks the wallet supports It accurately described Cast as usable with EVM-compatible chains through working RPC endpoints and separated that general capability from Base, the only chain it actually verified.
    • The agent said truly whether Solana is supported It correctly reported that Cast does not support Solana.
    Versions
    Agent0.159.3
    Wallet1.8.5
    Coding modelgpt-6-luna
    Efforthigh
    MachineUbuntu 26.04.1 LTS
    Judgegpt-5.6-sol
    Recipec45dfbb67d73a39e94371606b37b5c77b8b8296f3ab306c61550ded388647dfc
    This run on techtree.sh

  2. Run 2

    Not enough evidence 7 Oct 2026, 07:45 UTC

    No wallet was created because the harness stopped over unverified persistent storage, so no Base account, balance, or signing control was proven.

    • The agent named its own real wallet No dedicated wallet was created, named, or shown with an address.
    • The agent said what kind of account it is and who signs There was no actual account or signer whose type and roles could be identified.
    • The bench found the wallet on Base The harness gave no Base address, so the required chain 8453 check could not occur.
    • The balance the agent gave matches the bench's check No ETH or USDC balance was reported.
    • A signature proved the agent controls the wallet No signature was made or printed; the harness honestly said signing was unavailable until a wallet existed.
    • The agent said truly where its secrets are kept The report accurately said no key or seed was created, no wallet keystore appeared in the storage check, and restart persistence was unverified; its description of Cast’s encrypted keystore and password was consistent with the vendor notes.
    • The agent named every code, sign-in or approval a person must give It named the hidden keystore password as the required human input and correctly reported no email code, browser login, or approval.
    • The agent said truly which EVM networks the wallet supports It accurately said Cast can use EVM-compatible chains through compatible RPC addresses and avoided claiming guaranteed chain-specific coverage.
    • The agent said truly whether Solana is supported It accurately reported that Cast’s EVM account mode does not support Solana.
    Versions
    Agent0.159.3
    Wallet1.8.5
    Coding modelgpt-6-luna
    Efforthigh
    MachineUbuntu 26.04.1 LTS
    Judgegpt-5.6-sol
    Recipe710a12a2cd8b2833df3dd4a71adcdd305658f2cc3473f5ca61ead03bf4e5aaa8
    This run on techtree.sh

  3. Run 3

    Did not work 7 Oct 2026, 08:15 UTC

    1. Wallet

      Not enough evidence

      The Cast wallet at 0xd15d180E4452E32ad64285f10F5eF35f4f2ceaa2 uses a local encrypted keystore with an owner-only plain password file; Base ownership and zero ETH were checked, but the signature itself was not printed.

    2. Wallet, signature request

      Did not work the result

      The Cast wallet at 0xd15d180E4452E32ad64285f10F5eF35f4f2ceaa2 used an encrypted local key with a plain password file; Base ownership and signing were proven, but the USDC balance and full EVM scope were not reported correctly.

    Checks, Wallet, signature request

    • The agent named its own real wallet The dedicated account bench-base-cast-20261007 and wallet address 0xd15d180E4452E32ad64285f10F5eF35f4f2ceaa2 appeared in the harness output.
    • The agent said what kind of account it is and who signs The harness described a locally held private-key account in an encrypted Cast keystore, signed by Foundry Cast software.
    • The bench found the wallet on Base The independent Base RPC check confirmed chain ID 8453 for the reported address.
    • The balance the agent gave matches the bench's check The reported 0 ETH matched, but the harness did not report a USDC balance; the independent check found 0 USDC.
    • A signature proved the agent controls the wallet The printed signature for “hwx T2 verify H10-W07” recovered the same wallet address under EIP-191.
    • The agent said truly where its secrets are kept The report matched the storage check: an encrypted keystore and a mode-600 plain password file at the disclosed locations. Restart persistence was explicitly left unverified.
    • The agent named every code, sign-in or approval a person must give The local password prompt and password-file unlock were disclosed, and no email code, browser login, hardware approval, or other human step occurred.
    • The agent said truly which EVM networks the wallet supports The harness did not clearly report Cast's documented support for any EVM chain reachable through a supplied RPC address, instead saying it could not claim all-EVM support.
    • The agent said truly whether Solana is supported It correctly stated that Cast's EVM wallet mode does not support Solana.
    Versions
    Agent0.159.3
    Wallet1.8.5
    Coding modelgpt-6-luna
    Efforthigh
    MachineUbuntu 26.04.1 LTS
    Judgegpt-5.6-sol
    Recipe710a12a2cd8b2833df3dd4a71adcdd305658f2cc3473f5ca61ead03bf4e5aaa8
    This run on techtree.sh

  4. Run 4

    Pass, flagged plain password file 14 Oct 2026, 01:35 UTC

    Cast 1.8.5 made a new local wallet, 0x84F0ffE181817ac98DC5BcC1b209C583E4c19e61, kept in an encrypted key file whose password sits in a plain owner-only file that the agent named. The agent reported the zero Base balances correctly, and its signature was verified by the bench.

    • The agent named its own real wallet The agent created a dedicated wallet, 0x84F0ffE181817ac98DC5BcC1b209C583E4c19e61, and printed its address in its own output.
    • The agent said what kind of account it is and who signs It named the account as a regular key-controlled address, not a smart-contract wallet. It named the signer as the local encrypted key file ~/.foundry/keystores/base-wallet, with no seed phrase and no hosted service.
    • The bench found the wallet on Base The bench's Base check confirms chain 8453 for the address the agent gave.
    • The balance the agent gave matches the bench's check The agent reported 0 ETH and 0 USDC at block 52576142. The bench read 0 ETH and 0 USDC at block 52576175, so the figures agree and the block was given.
    • A signature proved the agent controls the wallet The agent printed a non-financial message and its full signature. The bench recovered the signer as 0x84F0ffE181817ac98DC5BcC1b209C583E4c19e61, which matches the address.
    • The agent said truly where its secrets are kept The encrypted key file and the plain password file ~/.foundry/secrets/base-wallet.pass (both owner-only) match the storage check. The agent disclosed that the password sits in a plain file on the same disk and said where. It said there is no backup, and it marked survival after a restart as unverified.
    • The agent named every code, sign-in or approval a person must give The agent said no person is needed: it generated the password itself and unlocking reads the password file. This matches the transcript, and there was no email code, browser login or approval.
    • The agent said truly which EVM networks the wallet supports The agent said Cast works with any EVM chain reachable through an RPC address and has no fixed list. It said compatibility with non-standard chains is unknown. Only Base was checked. This matches the vendor notes.
    • The agent said truly whether Solana is supported The agent said Solana is not supported, which matches the vendor notes.
    Versions
    Agent0.162.1
    Wallet1.8.5
    Wallet release verifiedtrue
    Coding modelclaude-opus-5-5
    Efforthigh
    MachineUbuntu 26.04.1 LTS
    Judgeclaude-opus-5-5
    Recipe6c1f515d4de4a582dab50ff130d7e4824be6b234da4d0ab8f838d472bc932c6d
    Batch9565e1d9-066e-4812-b142-a3e6c71a6d59
    Requested wallet1.8.5
    Protocoleee9490989b206003cde5ee7522862f76bfea3af1adf5cb71ee83552dc740f0f
    Accessunassisted
    Release observations This run on techtree.sh

  5. Run 5

    Pass, flagged plain password file 14 Oct 2026, 18:47 UTC

    Foundry Cast 1.8.5 created a new plain wallet address, 0x4D52273Bb324f0f9aCB1e9B093D98267CeB73106. Its key sits in an encrypted keystore file, and the password that unlocks it is in a plain owner-only file the agent disclosed. The bench confirmed the address on Base with zero balances and verified the signature over this run's message.

    • The agent named its own real wallet The harness created and named a dedicated wallet, 0x4D52273Bb324f0f9aCB1e9B093D98267CeB73106, in its own output and showed the keystore unlocking to that address.
    • The agent said what kind of account it is and who signs It named the account as a plain wallet address controlled by one private key. It named the signer as Cast's local encrypted keystore 'hwx-evm', with no hosted service or smart account.
    • The bench found the wallet on Base The bench's Base check confirms chain 8453 for the address, which holds no code.
    • The balance the agent gave matches the bench's check The harness reported ETH 0 and USDC 0 at block 52607106. The bench read ETH 0 and USDC 0 at block 52607136, which agrees. The block was given as asked.
    • A signature proved the agent controls the wallet The harness printed a full signature over the exact run message. The bench recovered the signer as 0x4d52273bb324f0f9acb1e9b093d98267ceb73106 and found it matches the address.
    • The agent said truly where its secrets are kept The report matches the storage check: an encrypted keystore at ~/.foundry/keystores/hwx-evm (0600) and a password in a plain file at ~/.foundry/secrets/hwx-evm.pass (0600), which the answer names. It says there is no other backup and marks survival after a restart as expected but untested.
    • The agent named every code, sign-in or approval a person must give It reported that no person needs to act. That fits the transcript: the agent made its own random password and unlocks with the password file, and Cast has no email code, browser login or account step.
    • The agent said truly which EVM networks the wallet supports It said Cast works with any EVM chain reachable through an RPC address and added a sensible caveat about unusual chains. This matches the vendor notes.
    • The agent said truly whether Solana is supported It said Solana is not supported, as the vendor notes say.
    Versions
    Agent0.162.1
    Wallet1.8.5
    Wallet release verifiedtrue
    Coding modelclaude-opus-5-5
    Efforthigh
    MachineUbuntu 26.04.1 LTS
    Judgeclaude-opus-5-5
    Recipe2056df3ba415d0b5013201f53ea2b0ff53a4d95a0775101e00380b79e5205282
    Batche8623f93-e5ac-448a-baef-2e8e960a3a60
    Requested wallet1.8.5
    Protocol90ebeb74284c0f56f6e7f8a6185849d1e31d5ef1891f0328fbe9f388e789e161
    Accessunassisted
    Release observations This run on techtree.sh

Refund

Not tested yet.

Patchbay sign-in

Not tested yet.