AskGrokWallet · for the person whose money the bot is running

You can see the balance change. You cannot see whether the rules were broken.

If you hand money to a bot or an operator — a friend's bag, a small pool, followers — a balance and a list of on-chain transactions are all you get. They answer "where did the money go", not "did it stay inside what we agreed".

Three questions you cannot answer today

What you get instead

A signed record per decision, and a monthly statement. Anyone can verify it — without trusting the operator, and without trusting us.

decision   refuse
reason     daily loss limit reached — auto-trading paused
amount     hidden from the public; disclosable to the funder or an auditor
time       2026-09-14 09:22 UTC
signature  Ed25519, key pinned inside the verifier
onchain    entry 51 · that log head sits in an Ethereum transaction

The part that matters most

Two rule-breaking requests were never broadcast at all. The wallet's nonce never moved — the limit took effect before signing, not in a log written afterwards.

Something that did not happen is stronger evidence than something that did.

Verify it yourself in 30 seconds

curl -sLO https://github.com/richard7463/askgrokwallet/releases/download/verify-receipt-v1.0.1/SHA256SUMS
curl -sLO https://github.com/richard7463/askgrokwallet/releases/download/verify-receipt-v1.0.1/verify-receipt.mjs
shasum -a 256 -c SHA256SUMS        # check the bytes BEFORE running them
node verify-receipt.mjs receipt.json

Four lines come back: ✓ proven · ✗ provably wrong · ~ not checked (never "fine").

What we do not do — said up front

The first step is small

Nothing in your current flow changes. The operator keeps the wallet and the strategy; we record alongside and hand you a monthly statement you can verify yourself.

Prove that the paper is useful first. Then decide whether the rules should move into the signing path.


See a real monthly record → · askgrokwallet.io

Unaudited developer preview. No third-party audit yet; the verifier has survived two external adversarial reviews, and both repros are kept as failing tests in the public repository.