Reference

FAQ

How long does a verification take? Quick and Quick-Smell: a few seconds. Full: about 10 seconds of GPU time plus whatever is queued ahead of it; poll at the interval the 202 suggests. A block already on the chain is usually answered at once.

Can I use one key from several servers? Yes. A key is not tied to an address. The limits are per key, so if two servers share one key they share its quota; give each server its own key (an account holds five) if you want separate quotas.

How do I rotate a key? Create a new key on the Keys page, switch your servers to it, then revoke the old one. Revocation takes effect within 30 seconds and cannot be undone.

Is testnet supported? No. The service verifies TensorCash mainnet only; /v1/… and /net/tensor-main/v1/… are the same routes.

Does it cost anything? No. The service is free during launch, with the per-key limits in Limits and errors. If they are too low for your pool, ask us through the portal's contact address.

How do I verify shares rather than blocks? Send the share target in X-Target-Override on the Full (or Quick-Smell) submit route and poll with the same header. Your key needs the verify:share-mode scope, granted on request. See Verifying shares.

I submitted a block and got 200 at once. Was it verified? Yes, earlier: the reply came from an existing result ("cached": true). Blocks already on the chain usually need no new run.

Which reply format should I use? For blocks, the scoped format (X-Verify-Result-Contract: scoped/1): the result is keyed by everything it was judged under, so a result computed for another height or ruleset can never answer your question. For shares, the plain format (no header). Nodes handle this themselves.

My Quick result is Quick_OK but the node rejected the block. Why? Quick checks structure, proof-of-work and parameter bounds; it does not replay the model. Only Full says whether the model ran, and a node applies its own consensus rules on top of any verifier.

Where do I get a ValidationRequest to send? A TensorCash node builds one for every block it validates; pools build the same message for their candidates. The schema is shared-utils/fb-schemas/validation.fbs in the TensorCash repository. There is no JSON form.

Why did my key stop working? It was revoked, or it is not the key you think (keys are shown once; compare the first eight characters with the Keys page). Both cases answer 401.

Can I see how many requests my key made? The portal shows each key's state and last use, accurate to about a minute. There are no per-request counters.

Who do I contact? Account, key and portal questions: the contact address on the portal. Questions about verdicts or the verifier software: the TensorCash project.

Updated 2026-10-07