Evidence row 1034292

What was observed

{
  "count": 5,
  "tools": [
    {
      "description": "Describes the Unlock Pulse dataset itself: server version, when it was last refreshed, how many upcoming unlocks it holds and how far ahead, how many past unlocks the track record is built on, which blockchains the on-chain check covers, sources, the strength formula and thresholds, known limitations and how to cite. Use when the user asks where the numbers come from, how fresh or complete they are, or how to cite them.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "get_dataset_info"
    },
    {
      "description": "Explains the strong / medium / small rating and gives the historical record: for past unlocks of each strength, how often the token fell against Bitcoin in the week before the unlock and the average move. Use when the user asks what 'strong' means, whether unlocks move prices, or how reliable the rating is. Not a forecast for any single token.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "get_method_and_track_record"
    },
    {
      "description": "What is actually happening on-chain with a token's locked allocations: the vesting contracts and wallets holding team, investor and treasury tokens, how much they hold now, outflows (tokens leaving locked wallets), mints, burns and contract upgrades, the next unlock by the project's own documents, and our short finding (for example: unlocked but never withdrawn, tranches sent to an exchange, vesting contract has not paid out). Use for 'are team tokens moving', 'did the unlock really happen', 'who is selling'. Without a token: recent movements across all covered tokens. token accepts a ticker (preferred), a name or a slug; covered_tokens in the result lists what we track (a few dozen tokens, not the whole calendar). Movements look back at most 30 days; wallet roles marked 'our attribution' are our analysis, not the project's statement. For the unlock calendar use get_token_unlocks.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "days": {
            "default": 30,
            "description": "Look-back window for the list of recent movements (no token).",
            "maximum": 30,
            "minimum": 1,
            "type": "number"
          },
          "lang": {
            "default": "en",
            "description": "Language of the page links.",
            "enum": [
              "en",
              "ru"
            ],
            "type": "string"
          },
          "token": {
            "description": "Ticker, name or slug. Leave empty for recent movements across all covered tokens.",
            "maxLength": 60,
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "get_onchain_check"
    },
    {
      "description": "All scheduled unlocks in the next 60 days for one token, with recipients (team, investors, treasury ...), USD value, share of circulating supply, futures availability and a link to the token page. Accepts a ticker (ARB), a name (Arbitrum) or a slug (arbitrum). Returns found=0 if the token has no unlock in the next 60 days (that is not an error). If the result mentions onchain_check, call get_onchain_check to see what the locked wallets are doing. lang=ru returns Russian page links.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "lang": {
            "default": "en",
            "enum": [
              "en",
              "ru"
            ],
            "type": "string"
          },
          "token": {
            "description": "Ticker, name or slug.",
            "maxLength": 60,
            "minLength": 1,
            "type": "string"
          }
        },
        "required": [
          "token"
        ],
        "type": "object"
      },
      "name": "get_token_unlocks"
    },
    {
      "description": "Calendar of scheduled crypto token unlocks in the next N days (up to 60), each rated strong / medium / small by size relative to circulating supply. Use for questions like 'which token unlocks are coming this week', 'biggest unlocks in November', 'strong unlocks with perpetual futures'. Data refreshes hourly (data_updated_utc in the result). Results are cut to 'limit' (default 30): 'matched' says how many fit the filters. The futures filter covers KuCoin and Binance USDT perpetuals only. For one coin use get_token_unlocks; for what the rating means and past results use get_method_and_track_record; for coverage and sources use get_dataset_info. lang=ru returns Russian page links.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "days": {
            "default": 14,
            "description": "Look-ahead window in days.",
            "maximum": 60,
            "minimum": 1,
            "type": "number"
          },
          "futures": {
            "default": "any",
            "description": "Filter by perpetual futures availability.",
            "enum": [
              "any",
              "with_futures",
              "kucoin",
              "binance"
            ],
            "type": "string"
          },
          "lang": {
            "default": "en",
            "description": "Language of the page links.",
            "enum": [
              "en",
              "ru"
            ],
            "type": "string"
          },
          "limit": {
            "default": 30,
            "maximum": 100,
            "minimum": 1,
            "type": "number"
          },
          "min_strength": {
            "default": "small",
            "description": "Lowest strength to include.",
            "enum": [
              "strong",
              "medium",
              "small"
            ],
            "type": "string"
          },
          "sort": {
            "default": "date",
            "description": "date = soonest first; size = largest share of circulating supply first.",
            "enum": [
              "date",
              "size"
            ],
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "get_upcoming_unlocks"
    }
  ]
}

What the leaf hashes

{"body":"b05a8970d034cb05137a09477ea26710fef7a129a0b653c9dda6b6f13c6abae9","id":1034292,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793290456859250,"prev":997096,"subject":"cb88d6fa-0d2e-445c-9319-5511286f622c","subject_kind":"endpoint"}

Proof

Fold these into the leaf in order, hashing each sorted pair with keccak256, to reach the root of 2026-10-29 (242798 rows).

1. 0xc3cf8efa8a54236c76dfebef4d7dfd455a947fedf1104f1b456198300d56649c
2. 0xb8e7a91917c3ba50d56b9bb65ced181354f50696b3f9158b51ed124d03724230
3. 0x579652f3848ba42b19946eea31ca9d5a4699c56ec5f8e930410e38acad6d27c2
4. 0x12970b30187143657462a57e10b6043028cfdea691fea48597e6f97d7911e308
5. 0x76f1816a3c855c7ad57f2c04d2b457eb7b57476a98d497ccc2cdf57bab21987c
6. 0x13d7b82b0fc7d9197eaab35d072b513e7752c04d207306f1305a75b0752dd5fb
7. 0x872baf560aa346c724036c8d0d04d2df70e58f14888de859deac2da4ed6d9dbb
8. 0x4eb077bbd0c08881b190ee250317e221400a8c9f7a27d974d5f0cea8d88a0d04
9. 0x13f3e15b56394ad962e44e0a5b36cd196501c6656da78e463fd452c3aba44475
10. 0x3f36751974c641fb10708909744d6372e3a15de2b4d24568a1f0e79ad993fa6a
11. 0x809e25b2f4a9926998f718d6924a34c64952667689be804304b90d3bf876b9c1
12. 0x5cb842fc8ebd71381fe19a8881791924e752bffd68551649b2c4cbd8b2e7acfb
13. 0x82acf0ab79b727689a8862d5f40ebc054bfa26bd74148138aeb5de693084058a
14. 0x104600713bd70fcbdf137fa07f8136bb6c252c890776bc7cbd7b194271f8b93a
15. 0x4e4f8f228a3b7a38299ec6f2b1967c6cf4de15fdd9dc0d200e691266e51ef99d
16. 0xef5d5572aac8f06b61579b7167b369fcb479d9027d4037dc9cacff9e3a26ffd2
17. 0xa1fa2e97e71ad6e802f325afd74bb7095901f2060529c9739182a1233f8804bc
18. 0xe01539ac4c9f9cdf265a9e5c6d99c8da11e70ff0c7175fb23e402d33b9d79785

Day root

0xc050555c6b023f2aefb6536efb9f0760b92c30a0d06c572b7daf63db259ea17c

Chained

0x4cde8bae2042512e1bec11650628f0293556311cc4ea74d99ffddf02b671a7d6

Published

On Arc Testnet, block 69753317: 0x9e85c340732f416e431b111fae72f7624870125f7f379af2732eb6c2ba8cf6a1