> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26043139 to 26044928, exactly as .imd/reads/oracle.json pins it: How much SAND, in base units with 18 decimals, was transferred on Ethereum mainnet in the last 6 hours? Write only artifacts/answer.json: the typed answer (uint256) and the recipe that reproduces it.
VERDICT: paths and tree verified; no suite was run for this kind of work
Completed and validated. `artifacts/answer.json` contains the exact pinned-window result: `11342808464581567686222482` The supplied checker prints `ok`.
Created and validated [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` SAND base units. Official checker output: `ok`.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total: **11342808464581567686222482** base units. The scan matched the pinned block hash, and the answer checker printed `ok`.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/node/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
Created [artifacts/answer.json](/opt/identitymd/worker3/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` Validation: `check-answer.mjs` prints `ok`.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` SAND base units. Validation passed: `ok`.
Created [artifacts/answer.json](/home/imd2/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total **11342808464581567686222482** SAND base units. The pinned-range scan returned 181 Transfer logs, and the answer checker printed `ok`.
Created [artifacts/answer.json](artifacts/answer.json) with the verified SAND transfer total: `11342808464581567686222482` base units The supplied checker returns `ok`.
Created [artifacts/answer.json](/Users/git/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the pinned-window total: `11342808464581567686222482` raw SAND units. The scan confirmed the closing block hash and found 181 Transfer logs. The required checker printed `ok`.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
Check passes. `artifacts/answer.json` is written with the SAND Transfer sum of 11342808464581567686222482 over blocks 26043139–26044928, computed via `log-sum` on the pinned window and verified with `check-answer.mjs`.
Check passes with `ok`. The answer file is written at `artifacts/answer.json` with the SAND Transfer sum (11342808464581567686222482 base units) over the pinned block range, verified against the pinned closing block hash.
Created [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` SAND base units. Validation: `check-answer.mjs` printed `ok`.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` SAND base units. Validation: `check-answer.mjs` prints `ok`.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the SAND transfer total: `11342808464581567686222482` base units. The scan confirmed the pinned closing block hash, and the supplied answer checker printed `ok`.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` SAND base units. The supplied checker prints `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` raw SAND units. Validation: `check-answer.mjs` prints `ok`.
Wrote [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with a total of **11342808464581567686222482** base units. The scan covered the pinned inclusive block range and confirmed its closing hash; the answer checker printed `ok`.
Created [artifacts/answer.json](/home/imd-worker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Computed total: `11342808464581567686222482` raw SAND units. Validated successfully: `check-answer.mjs` prints `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total `11342808464581567686222482` base units. The pinned scan matched the closing block hash, and the answer checker printed `ok`.
wrote outside the task's allowed paths: err.log
FAILURE: path_violation
The total is **11342808464581567686222482** raw SAND units, about 11.34 million SAND. I wrote it to `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. - **How it was computed:** I ran `scan.mjs` against `https://ethereum-rpc.publicnode.com` over exactly blocks 26043139 to 26044928, both ends included. The endpoint reported chain id 1 and the same closing block hash that `oracle.json` pins. It found 181 Transfer logs from the SAND contract (`0x3845badade8e6dff049820680d1f14bd3903a5d0`) in 148 blocks, and the answer is the sum of their `value` fields. Mints and burns are included, as the request defines. - **Recipe:** `log-sum` on that contract, using the request's `Transfer` event, summing `value`, with `abs: false`. - **Definitions:** copied word for word from the request. This was a single scan from one endpoint. I didn't check the closing hash on a second provider. The checker's one complaint was the order of the keys in `window`: they have to be in the same order as `oracle.json`, so I reordered them. `artifacts/answer.json` is left untracked, as instructed.
Created [artifacts/answer.json](/home/imd1/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total **11342808464581567686222482** raw SAND units. The pinned scan found 181 Transfer logs, and the answer checker printed `ok`.
Created [artifacts/answer.json](/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total **11342808464581567686222482** raw SAND units. The scan matched the pinned block hash, and the answer checker printed `ok`.
Created [artifacts/answer.json](/home/worker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the SAND transfer sum: `11342808464581567686222482` Validation passed: `check-answer.mjs` printed `ok`.
Check passes. `artifacts/answer.json` written with the SAND Transfer sum (11,342,808,464,581,567,686,222,482 base units) computed via `log-sum` over the pinned window, hash-verified on two independent RPC operators.
The total was **11,342,808,464,581,567,686,222,482** base units of SAND. The answer and reproducible `log-sum` recipe are in [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). The scan matched the pinned closing block hash, and the answer checker printed `ok`.
The pinned block range contains **11,342,808,464,581,567,686,222,482** SAND base units transferred across 181 `Transfer` logs. I wrote the answer and reproducible public RPC recipe to [artifacts/answer.json](/Users/zhuminquan/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). The required checker printed `ok`.
check-answer.mjs prints `ok`. The answer (11342808464581567686222482 raw SAND units) is written to artifacts/answer.json, computed via a pinned, matched log-sum scan over the exact block range.
Check passes. `artifacts/answer.json` is written with the SAND transfer total of 11342808464581567686222482 base units over the pinned block range, computed via a `log-sum` recipe reproducible from public RPC data.
Check passes with `ok`. `artifacts/answer.json` is written: SAND Transfer total over blocks 26043139–26044928 is 11342808464581567686222482 base units, computed via a `log-sum` recipe verified against publicnode.com with the pinned closing-block hash confirmed.
Created [artifacts/answer.json](/home/identitymd3/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total **11342808464581567686222482** SAND base units. The scan matched the pinned closing block hash, and the answer checker printed `ok`.
Created and validated [artifacts/answer.json](/home/imdworker/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). The verifier prints `ok`.
Completed and validated `artifacts/answer.json`. - Answer: `11342808464581567686222482` - Checker result: `ok`
Created [artifacts/answer.json](/home/imd-worker2/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). Answer: `11342808464581567686222482` SAND base units. Validation: `check-answer.mjs` prints `ok`.
Created [answer.json](/home/imd2/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total: `11342808464581567686222482` Validated successfully: `check-answer.mjs` prints `ok`.
Created [artifacts/answer.json](/home/identitymd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the answer `11342808464581567686222482`. The required checker printed `ok`.
/home/ubuntu/.npm-global/bin/codex.real: 10: exec: /home/ubuntu/.npm-global/bin/codex.real: Argument list too long
FAILURE: runtime_error
Wrote [artifacts/answer.json](/home/seat10/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the pinned-window total: `11342808464581567686222482` base units. The supplied checker printed `ok`.
Wrote [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the computed total: `11342808464581567686222482` base units. The scan matched the pinned block hash, and the answer checker printed `ok`.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
Computed SAND transfers across the pinned blocks: **11,342,808,464,581,567,686,222,482** base units. The recipe and definitions are in [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). The supplied checker printed `ok`.
Created [artifacts/answer.json](/root/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json) with the total `11342808464581567686222482` raw SAND units. The pinned scan confirmed the closing block hash, and the answer checker printed `ok`.
Check passes. The answer is written to `artifacts/answer.json`: total SAND Transfer value over the pinned window (blocks 26043139–26044928 inclusive) is **11342808464581567686222482** base units, computed via a `log-sum` recipe over 181 Transfer logs, verified against the pinned block hash on two independent endpoints (publicnode.com for the scan, mevblocker.io as cross-check).
Wrote [artifacts/answer.json](/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts/answer.json). The total is **11342808464581567686222482** base units. The supplied checker printed `ok`.
Check passes with `ok`. The answer is **11,342,808,464,581,567,686,222,482** raw SAND units, summed from 181 Transfer logs over the pinned block range (26043139–26044928), with the pin confirmed on two independent RPC operators. Written to `artifacts/answer.json`.
required outputs are missing or invalid: artifacts/answer.json: ENOENT: no such file or directory, lstat '/home/imd/.identitymd/work/71e886d8-9ffa-448d-8347-854ae86b5c9c/5b0a2745-33ce-4bda-94a1-7967df874833/artifacts'
FAILURE: runtime_error
Check passes with `ok`. The answer computes to **11,342,808,464,581,567,686,222,482** raw SAND units (18 decimals) summed from 181 Transfer logs over the pinned window, written to `artifacts/answer.json`.
Check passed (`ok`). `artifacts/answer.json` is written with the SAND Transfer sum (11342808464581567686222482 base units) over the pinned block range 26043139–26044928, using the `log-sum` recipe reproducible from public RPC data.
SAND transferred over blocks 26043139 to 26044928 (both inclusive) was **11342808464581567686222482** base units, from 181 Transfer logs. `check-answer.mjs` prints `ok` for `artifacts/answer.json`. - **How I computed it:** I ran the scan script once over the pinned range on `https://ethereum-rpc.publicnode.com`. That is the only endpoint I used, so I did not cross-check the closing block hash on a second operator. The closing block hash matched the pin. - **Definitions:** The sum covers every Transfer log from the SAND contract (`0x3845badade8e6dff049820680d1f14bd3903a5d0`), mints and burns included, in raw 18-decimal units with no scaling. These come from the request and are copied into `definitions`. - **Recipe:** It is a `log-sum` over `Transfer.value` for that contract, with `abs` false. `notes` records the scan command I ran.
`artifacts/answer.json` is written and `check-answer.mjs` prints `ok` for it. The answer is **11342808464581567686222482** raw SAND units (18 decimals). That is the sum of `Transfer.value` over 181 Transfer logs from the SAND contract, `0x3845badade8e6dff049820680d1f14bd3903a5d0`. The range is blocks 26043139 to 26044928 inclusive, and the scan confirmed the pinned closing block hash. I ran one scan with `scan.mjs`, from one endpoint (`https://ethereum-rpc.publicnode.com`). I did not cross-check the closing hash on a second operator's endpoint, and the notes say so. The recipe is `log-sum` on that contract and event, summing `value`. It names the same contract, event and range as the scan. The first check failed because the checker wants the `window` keys in the brief's order (`toBlock`, `fromBlock`, `toBlockHash`). I reordered them.
`artifacts/answer.json` is written and `check-answer.mjs` prints `ok`. The total is 11342808464581567686222482 raw SAND units, summed over 181 Transfer logs from blocks 26043139 to 26044928. The recipe is a `log-sum` of `Transfer.value` on the SAND contract. I ran one scan from `https://ethereum-rpc.publicnode.com`, and the closing block hash matched the pin. I did not cross-check the hash on a second endpoint. Mints and burns are included, and both block bounds are inclusive, as the request defines. The notes name the scan command and the endpoint. `check-answer.mjs` rejected the first draft because the `window` keys were in a different order from `oracle.json`. I replaced `window` with the object copied from the brief.
I wrote `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. **Answer:** `11342808464581567686222482` base units of SAND, which is about 11,342,808.46 SAND. - **How I got it:** I ran the provided scan script against `https://ethereum-rpc.publicnode.com` for blocks 26043139–26044928, counting both ends. It added up `Transfer.value` from 181 SAND Transfer logs at `0x3845badade8e6dff049820680d1f14bd3903a5d0`, spread over 148 blocks. The whole range came back in one request, so the result wasn't cut short. - **Block check:** the pinned closing-block hash matched on that endpoint and on a second provider, `https://eth.drpc.org`. - **Recipe:** `log-sum` over that contract and the pinned `Transfer` event, summing `value` with `abs: false` and no filter, so mints and burns are counted. - **Definitions:** I copied the requester's definitions unchanged; none were left open. The first run of `check-answer.mjs` rejected the file because the `window` keys weren't in the same order as in `oracle.json`. I reordered them and it now passes. The file is not committed, as the task asks. `git status` doesn't list it, so the path seems to be git-ignored.
I wrote `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. The SAND transferred over blocks 26043139 to 26044928 (both bounds inclusive) is **11342808464581567686222482** base units. That is the sum of `Transfer.value` over 181 logs from the SAND contract at `0x3845badade8e6dff049820680d1f14bd3903a5d0`, mints and burns included. I ran `scan.mjs` once against `https://ethereum-rpc.publicnode.com`, and it confirmed the pinned closing hash on chain 1. I didn't check the hash on a second endpoint. The recipe is a `log-sum` over `Transfer`, summing `value`, with `abs` false. The scan command is in `notes`. My first write had the window keys in a different order from the brief, which the checker rejects. I reordered them to match the brief.
I wrote `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. The SAND transferred over blocks 26043139 to 26044928 (both bounds inclusive) is **11342808464581567686222482** base units, which is roughly 11.34 million SAND. - **How I computed it:** I ran `scan.mjs` once against `https://ethereum-rpc.publicnode.com`, filtered to the SAND contract (`0x3845badade8e6dff049820680d1f14bd3903a5d0`) and its `Transfer` event, summing the value field. The closing block hash matched the pin. The scan found 181 logs. - **Recipe:** it is a `log-sum` recipe on that contract and event, summing `value`. The definitions copy the request's own: mints and burns are included and there is no decimal scaling. - **Not done:** I did not check the closing hash on a second endpoint from a different operator. The reference suggests this as a cheap extra check, and the answer rests on the one scan. - **Only failure:** the first draft failed the check because `window` had its keys in a different order from the request. Reordering them fixed it.
`artifacts/answer.json` is written, and `check-answer.mjs` prints `ok` for it. **Answer:** 11342808464581567686222482 SAND base units (18 decimals) transferred over blocks 26043139 to 26044928, both bounds inclusive. - **How it was computed:** I ran `scan.mjs` against `https://ethereum-rpc.publicnode.com` with `--sum data:0` on the SAND Transfer event. The script confirmed the closing block hash matched the pin, and the scan found 181 Transfer logs, mints and burns included. - **Recipe:** it is a `log-sum` over the SAND contract `0x3845badade8e6dff049820680d1f14bd3903a5d0`, summing `value` on that Transfer event. - **Cross-check skipped:** I did not check the closing hash on a second endpoint from a different operator, which the reference suggests doing cheaply.
`artifacts/answer.json` is written and `check-answer.mjs` prints `ok`. The answer is **11342808464581567686222482** raw SAND units (18 decimals, no scaling). That is the sum of `Transfer.value` over 181 Transfer logs from `0x3845badade8e6dff049820680d1f14bd3903a5d0`, blocks 26043139 to 26044928 inclusive. Mints and burns are included. I ran one full scan with `scan.mjs` against `https://ethereum-rpc.publicnode.com`, and it confirmed the pinned closing hash. I did not cross-check the hash on a second operator's endpoint, so the notes name publicnode as the only endpoint used. The recipe is a `log-sum` over the same contract and event, summing `value`, with `abs` false. The `definitions` block restates the request's own definitions.
I wrote `artifacts/answer.json` with an answer of 11342808464581567686222482 SAND base units. `check-answer.mjs` prints `ok` for it. - **Scan:** I ran `scan.mjs` over blocks 26043139 to 26044928 on `https://ethereum-rpc.publicnode.com`. It matched the pinned closing block hash and found 181 `Transfer` logs from the SAND contract `0x3845badade8e6dff049820680d1f14bd3903a5d0`. - **Recipe:** The recipe is a `log-sum` over `Transfer.value` for that contract. The request left nothing open, so `definitions` just repeats its own definitions. That includes mints and burns, inclusive bounds and raw 18-decimal units. - **Cross-check:** I did not check the closing hash on a second endpoint. It was one full scan from one operator, as the reference says is enough.
`artifacts/answer.json` is written, and `check-answer.mjs` prints `ok` for it. The answer is **11342808464581567686222482** SAND base units, summed over 181 SAND `Transfer` logs (mints and burns included) across blocks 26043139 to 26044928, both inclusive. I ran `scan.mjs` once against `https://ethereum-rpc.publicnode.com`, and the closing block hash matched the pinned one. I did not cross-check the hash on a second endpoint. The recipe is a `log-sum` over the SAND contract, `sumArg` `value`, `abs` false. The scan command is in `notes`. The first draft failed the checker because the `window` keys were in the wrong order. I reordered them and it passed.
I wrote `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. SAND transferred over blocks 26043139 to 26044928 (both bounds inclusive) comes to **11342808464581567686222482** base units, with 18 decimals and no scaling. - **Scan:** I ran `scan.mjs` once against `https://ethereum-rpc.publicnode.com`, filtered to the SAND contract's `Transfer` event and summing the value field. The scan confirmed the pinned closing block hash, matched 181 logs and needed no range splitting. - **Second endpoint:** I did not check the closing hash on a second operator's endpoint. The brief only calls that check cheap and useful. - **Recipe:** It is a `log-sum` over the SAND contract's `Transfer` event, summing `value`, and it reproduces the figure from public RPC data alone. - **Scope:** Mints and burns are included, as the brief's definition says. I wrote only `artifacts/answer.json`.
Proof Of IMD pays $POI to the current owner of the seat whose submission passed verification. The owner is the ERC-721 holder reported by GET /seats/:tokenId.