Verify — Dolphin Tools

Addresses

Everything Dolphin Tools reads, and nothing it writes. There are no Dolphin Tools contracts, because Dolphin Tools has no contracts.

What	Where
Chain	Robinhood Chain, id 4663
RPC	`https://rpc.mainnet.chain.robinhood.com`
Registry / beacon	0xe10b6f6B…1b00
Shared implementation	0xb35490d6…5aE2
Event topic	`0x2205df4534432b2f6065…`
Dolphin Tools contracts	none

The topic hash was not copied from a signature database and then trusted. It was pulled out of the implementation's own runtime bytecode as a PUSH32 constant, then matched back to UIMultiplierUpdated(uint256,uint256,uint256). The last command on this page repeats that.

Recompute the numbers

Six commands. Between them they reproduce every figure published on this site from a public RPC, with no dependency on this site. Every one was run before it was published here. If any of them disagrees with what is published, what is published is wrong.

1. The action count on the landing page

expect 18

curl -s -X POST https://rpc.mainnet.chain.robinhood.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getLogs","params":[{
        "fromBlock":"0x0","toBlock":"latest",
        "topics":["0x2205df4534432b2f60654a3fdb48737ffdaf3e9edb1a498bd985bc026b15b055"]}]}' \
  | jq '.result | length'

2. The most recent action, decoded by hand

expect 1.000000000000 -> 1.000145502866

curl -s -X POST https://rpc.mainnet.chain.robinhood.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionReceipt",
       "params":["0x17717969d77a298b876c0c3c735b6367ee1f75e1906f67953a6a30dc35cc442e"]}' \
| python3 -c '
import sys, json
T = "0x2205df4534432b2f60654a3fdb48737ffdaf3e9edb1a498bd985bc026b15b055"
for log in json.load(sys.stdin)["result"]["logs"]:
    if log["topics"][0] != T: continue
    d = log["data"][2:]
    w = [int(d[i:i+64], 16) for i in (0, 64, 128)]
    print("old %d.%018d" % divmod(w[0], 10**18))
    print("new %d.%018d" % divmod(w[1], 10**18))
'

3. A live multiplier, straight from the token

expect 1.005101770003 for SGOV

cast call 0x92FD66527192E3e61d4DDd13322Aa222DE86F9B5 \
  'uiMultiplier()(uint256)' --rpc-url https://rpc.mainnet.chain.robinhood.com

4. The registry's whole log

expect 274

curl -s -X POST https://rpc.mainnet.chain.robinhood.com \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getLogs","params":[{
        "fromBlock":"0x0","toBlock":"latest",
        "address":"0xe10b6f6B275de231345c20D14Ab812db62151b00"}]}' | jq '.result | length'

5. The published feed, rebuilt from the chain

expect an empty diff

npm i -g dolphin-tools
eco actions --limit 100 --json > local.json
curl -s https://echocalls.vercel.app/api/actions > published.json

diff <(jq -S 'map({txHash,kind,newMultiplier})|sort_by(.txHash)' local.json) \
     <(jq -S '.actions|map({txHash,kind,newMultiplier})|sort_by(.txHash)' published.json)

The CLI reads the chain itself and shares no code path with the indexer that produced /api/actions. If the two agree, the published feed is what the chain says.

6. The topic hash, recovered from bytecode

expect 0x2205df4534432b2f6065…

cast code 0xb35490d6f9163DE4F80d88dc75c3516eb64C5aE2 --rpc-url https://rpc.mainnet.chain.robinhood.com \
  | grep -o '7f[0-9a-f]\{64\}' | cut -c3- | sort -u \
  | while read h; do
      curl -s "https://api.openchain.xyz/signature-database/v1/lookup?event=0x$h&filter=true" \
        | jq -r --arg h "$h" '.result.event["0x"+$h][]?.name | "0x\($h) \(.)"'
    done

What is not verified

There is no audit. There is nothing to audit: Dolphin Tools holds no funds and deploys no code to any chain. What could still be wrong is the classification — a future action landing between +2.1486% and +100% would sit in a gap this threshold has never had to resolve. If that happens, the honest answer is that the label is a guess, and the raw multipliers are the part to trust.

The set of tracked tokens is also not provably complete. It starts from a registry snapshot of 47 tokens and adds every address that has emitted the event, which is 53 today. A token that exists and has never had a corporate action may be missing from the token list — but it cannot be missing from the action feed, because the feed is indexed by topic across the whole chain rather than by walking a list.

Read at block 53,682,814 on 2026-09-03 20:06Z.

Check the numbers