Bitcoin Forum
July 22, 2026, 05:13:19 PM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN][TSC] TensorCash: Useful Proof-of-Work for Verifiable AI | mainnet live  (Read 204 times)
takakuni-imosuke (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
July 17, 2026, 05:50:24 PM
 #1


TensorCash: useful proof-of-work for verifiable AI
The same GPU forward pass that answers a prompt produces the proof that extends the chain. Mainnet is live.

Disclosure: I work on TensorCash. This is a technical intro, not a financial promotion. There is no sale, presale, airdrop, or price talk in this thread and I will not discuss any. The point of the thread is the mechanism, so tear it apart.
 
The one-line claim
Proof-of-work does not have to be wasted. On TensorCash the "work" is a real model forward pass serving an actual prompt, and the proof that the model ran is what secures the block. Same security argument as any PoW (costly to produce, cheap to verify, expensive to forge). The joules just do a job on the way.
 
The two security premises, stated plainly
  • The randomness is not the miner's. Sampling draws are derived by hash from the mining context (block hash, VDF output, tick, target): a deterministic, replayable stream, not an RNG the miner controls. You cannot re-roll a draw you don't like: the only way to explore the search space is to pay for another forward pass.
  • The entropy is the model's. Which continuation those hash-bound draws select depends on the model's full logit distribution at every step, and a consensus entropy gate rejects degenerate low-entropy output. So every lottery ticket costs one real forward pass of the claimed model and the statistical replay (below) checks the recorded logits really are that model's.
That is the whole PoW shape: hash-seeded draws play the role the nonce plays in hashing, the forward pass plays the role of the hash function, and the proof is checkable after the fact.
 
The formal core (Theorem B.2 of the paper)
Those premises are proved, not asserted. Model the sampler draw at step j as u_j = H(header, j, prefix) through a random oracle, and let consensus enforce a minimum per-path entropy floor of B_min bits. Then for every generator f and every grinding adversary that pre-selects at most L candidate token paths, the per-trial probability of an accepted solution is at most
 
q · min(1, L · 2^-B_min)

where q is the ordinary difficulty-target probability. The proof uses only measure preservation of the hash-driven sampler and the entropy floor, not the shape of the model, the prompt, or the adversary's construction rule, so every cached-tree, beam, or refine strategy is an instance of it. Plain reading: pre-building L paths buys you at most L·2^-B_min per trial, i.e. grinding the sampler is exponentially worse than just running the model. Theorem, proof, and parameter table: Appendix B of the paper.
 
What it actually is
A layer-1, Bitcoin-derived (UTXO model, 10-minute target spacing; unit: TENSOR). Blocks are currently coming much faster than target and hashrate has been growing quicker than the 4x-clamped retargets can track, so spacing sits around 90-100s while difficulty catches up; check the explorer, the chart is public. Not a token on someone else's chain, and not "a verifier bolted onto an API." The block reward is a native, non-token incentive paid for doing inference. Miners search continuations off-chain; validators replay only the winning path in a single pass. Every served token path carries a replayable proof, so anyone can confirm which model actually ran.
 
The hard part: verifying inference without re-running it
This is where most "useful work" coins fall over, so here it is concretely. You cannot just re-execute and diff outputs, because inference is not deterministic across GPUs, kernels, or precision, so any tolerance loose enough for honest hardware also passes a cheaper stand-in. TensorCash uses calibrated statistical replay instead:
  • The proof surface is compact and external: token IDs + sampler draws + top-50 support logits + 20 fixed tail canaries per step, plus compact summary stats. No hidden states, attention maps, or layer traces.
  • The sampler draw is hash-bound, so a 4-bit miner cannot search cheaply and then submit under the full-precision identity.
  • Verification is a single-path teacher-forced replay; one parallel pass over the recorded tokens, ~190x faster than generating them; not a re-run of the whole job.

Measured numbers from our paper (falsifiable: Qwen3-8B bf16 + Qwen3-32B fp8 on L40S, honest cross-hardware acceptance on A10G/L4):
  • Proof-emission overhead: 8B 6.6% to 9.4% (batch 1-16), about 12% at saturation; 32B fp8 3.4 to 6.7%. Overhead falls as the model gets bigger.
  • Forgery detection (live GPU replay): honest proofs 97.3% GREEN / 2.7% AMBER / 0% RED; cross-arch swap, same-arch fine-tune, and 4-bit quant all 100% detected. A cheap fingerprint screen alone misses the fine-tune and quant cases, so full replay is the decisive check.
  • Quantization-search resistance: honest bf16 vs real 4-bit, same seed, n=512, gives 0/512 terminal proof-hash overlap with first divergence at step 0.

Consensus and chain
  • Useful PoW plus the calibrated statistical replay above.
  • A VDF "cumulative tick" adds a proof-of-time component, so the chain self-heals liveness and resists deep reorgs.
  • Assets are consensus-native: an issuer picks the rules (ticker, supply cap, transfer policy, KYC, governance) and the protocol enforces them at every spend, instead of each token being bespoke contract code you have to audit.
  • Emission: a fixed total supply on an epoch-decay schedule, no official sale. I am keeping this factual and pointing at the schedule rather than dressing it up. See the mission/emission page and the whitepaper for the exact curve.

Mine it (mainnet is live)
Mining rides the same forward passes, so you can start from scratch or monetize spare capacity.
  • Apple Silicon: TensorMiner (Metal) or the llama.cpp host worker.
  • NVIDIA: Docker + vLLM (build matrix by compute capability).
  • No GPU: a CPU worker exists — fine for trying the stack; competitive mining is GPU territory.
  • Two modes: broker (point inference at a provider, minimal setup) or standalone (run your own node). Network is selected by CHAIN_NAME = tensor for mainnet, tensor-test for testnet.
  • The mining model must be chain-approved and is pinned per revision; approved models are listed on the explorer.
Full walkthrough: tensorcash.org/blog/how-to-mine
 
Don't trust, verify (please do)
The verifier is open source. Replay any proof yourself and confirm which model produced it:

Where it sits (named honestly)
We did not invent verifiable inference and will not pretend to. TEEs (Intel SGX, NVIDIA Confidential Compute) do it at roughly 5 to 10% overhead but you have to trust the chip vendor. zkML (Bittensor/Omron) is sound but far too slow to prove real-time LLM inference today. Gensyn is bitwise re-execution but a compute market, not an L1 whose block reward is the inference. Gonka is close on the "PoW 2.0" framing. TensorCash's specific bet is a full L1 where the PoW is the useful inference and verification is a replayable, model-attesting statistical check, with no enclave and no per-inference zk circuit.
 
Links

What this is NOT
No presale, no ICO, no airdrop, no giveaway, no "buy" link, and I cannot and will not give price or where-to-trade info. The coin is mined by doing inference. If anyone DMs you an "official" sale or a multiplier offer, it is a scam. There is no official sale.
 
Skepticism is welcome. The whole pitch is that you can check it rather than trust me, so fire away and I will answer in the thread.
_ili_
Newbie
*
Offline

Activity: 18
Merit: 0


View Profile
July 17, 2026, 08:37:27 PM
 #2

i'm going to use some H100 to see how it performs
takakuni-imosuke (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
July 18, 2026, 09:23:16 AM
 #3

If you run into issues please refer to the walkthroughs on the website and have a look at the discussions on Discord.
takakuni-imosuke (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
July 20, 2026, 10:48:45 AM
 #4

COMPUTE: options on network difficulty, settled by the block header itself (no oracle)

TensorCash is a useful-PoW L1 where the work is real model inference, so network difficulty is a live reading of the AI inference capacity committed to the chain. You can read it straight off any block header:

Code:
COMPUTE Index X = GetBlockProof(target) * 256 / 600    (tokens/sec)

target is decoded from the header's nBits; 600 is the consensus target block spacing. Purely factual, re-derivable by anyone from a header.

The interesting part: you can write options on that index that settle from the header itself, with no oracle, no issuer publication, and no off-chain data.

Settlement is intrinsic
At a fixed future block (the fixing height), consensus (1) reads nBits from that header, (2) decodes the target and computes the realized index, (3) splits a collateral vault by a rule committed in the contract's on-chain descriptor. It is not a claim anyone has to honor; it is a computation every full node repeats, deterministic and immutable once the block is buried.

Covenant-vault lifecycle (no issuer dependency at maturity)
  • Register: the series descriptor (strike, direction, fixing height, leverage) is committed on-chain; its canonical id is a tagged hash of the descriptor, so the terms are verifiable without a middleman.
  • Issue: the writer mints lot tokens and funds one 1-TSC vault per lot. Collateral is locked up front.
  • Transfer: tokens move like any consensus-native asset.
  • Settle: after the fixing height plus a burial delay, anyone can submit the settlement tx; consensus splits each vault per the descriptor rule.
  • The split is a rule, not a promise: the collateral is already in the vault, so there is no counterparty to chase at maturity.
No VM and no smart-contract bytecode anywhere; it is enforced by consensus the same way an ordinary payment is.

Concrete example (one of two live series)
COMPUTE.V26C2M, a call on the index: strike K = 2,000,000 tok/s, fixing height 28,416, leverage 4, 100 lots x 1 TSC collateral. Per 1-TSC vault at realized index X:
Code:
holder side = min(1, 4 * (X - K) / K) TSC   when X > K, else 0; remainder to writer
The min(1, ...) cap means the holder side ma25% past strike. A matching put exists(COMPUTE.V26P100K, strike 100k). Everything is recomputable from the header; none of it is a forecast.

Naming
COMPUTE.<MonthCode><YY><C|P><Strike>. V = October,  strike 2M.

Check it yourself
The charter and series descriptors are readable on-chain (geticupayload); the realized index is
GetBlockProof(target)*256/600 from the headethe settlement number, it was in the header the whole time. Don't trust, verify.

Explorer (call series): COMPUTE.V26C2M on the explorer
Full write-up: Tokenised difficulty options (blog)
Kairo0001
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile
July 20, 2026, 05:54:49 PM
 #5

Full walkthrough: tensorcash.org/blog/how-to-mine
---> It's very difficult to install it manually. It seems that users are essentially forced to install it automatically using Cursor AI Pro, and the Pro version requires a paid subscription
migrante
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile
July 21, 2026, 06:25:50 AM
 #6

Bittensor, a supposedly decentralized system of markets, but its payment layer still relies on Proof of Authority (PoA).

From their official documentation:
In Bittensor, the work of validating the blockchain is performed by the Opentensor Foundation on a Proof-of-Authority model.

How does the payment layer of TensorCash work? Is it open and permissionless?
takakuni-imosuke (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
July 21, 2026, 10:53:20 AM
 #7

You have Bittensor right: its base chain (subtensor) runs under Proof-of-Authority with the Opentensor Foundation as the authority, so the "decentralized markets" sit on top of a permissioned settlement layer. Whoever holds the authority set can, in principle, censor or reorder there.

TensorCash's payment layer is the opposite. It is a Bitcoin-derived UTXO chain secured by Nakamoto Proof-of-Work, so it is open and permissionless in the same sense Bitcoin is:

- No validator set, and no foundation signs blocks. Blocks come from miners, and anyone can mine.
- Anyone can run a full node and validate the entire chain themselves. No allow-list, no base-layer KYC, no authority that can freeze a payment.
- Transactions are permissionless, exactly like Bitcoin.

The only thing that differs from Bitcoin is what the work is: the proof-of-work is a real model forward pass (useful PoW) instead of hashing, and the block reward is a native, non-token incentive paid for that inference. Otherwise the consensus shape is standard Nakamoto PoW: heaviest valid chain wins, difficulty retargets, independent full-node validation. So the security budget is the useful inference itself, with no Opentensor-style authority anywhere in the settlement path.

One honest caveat so I am not overselling it: producing a valid block requires using a chain-recognized model (the model registry is an on-chain consensus artifact), but that is a rule about what counts as valid work, not a gate on who may mine, validate, or transact. The payment layer itself is as permissionless as Bitcoin's. Happy to point you at the model-registry and consensus docs if you want to poke at that part specifically.

You do not have to trust me on any of this: it is a public UTXO chain, so run a node and check, or take any block header and verify the proof-of-work yourself.
migrante
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile
Today at 05:54:56 AM
 #8

One honest caveat so I am not overselling it: producing a valid block requires using a chain-recognized model (the model registry is an on-chain consensus artifact), but that is a rule about what counts as valid work, not a gate on who may mine, validate, or transact. The payment layer itself is as permissionless as Bitcoin's. Happy to point you at the model-registry and consensus docs if you want to poke at that part specifically.

Yeah but Bittensor is wide in scope which allows for subnet creation that have nothing to do with LLMs and AI - it might make sense if you imagine a future in which some other for of AI is dominant. In the case of TensorCash you narrowed its scope to LLMs - what if LLMs that be in demand in the future cannot be run on a PC or worse still LLMs are not longer the thing.
Separating the work done in digital markets from the consensus algorithm needed to power the payments within those digital markets makes sense to me. But the implementation should allow for the payments to be done in a censorship resistant-way (unlike in TAO).
takakuni-imosuke (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
Today at 12:01:17 PM
 #9

We agree on the goal: settlement should be permissionless and censorship-resistant, unlike TAO. Where we differ from your mental model is that we don't split "market work" and "payment consensus" into two layers. We fuse them. The useful inference is the proof-of-work. Censorship-resistance doesn't come from separating layers; it comes from the settlement layer being permissionless PoW. Fusing the work into that PoW just makes the security productive instead of wasted, with no second trusted layer stacked on top.

The narrow scope is the whole trick, and it's causal. Bittensor can host arbitrary subnets because it never verifies that work in consensus, so the base chain needs an authority (the PoA you quoted) to decide what happened. If you want the settlement layer itself permissionless, the work has to be something the network can check without trusting anyone. Breadth buys you generality and forces a trusted base layer. A verifiable work class costs you generality and buys you a permissionless one. Bittensor picked breadth plus PoA. We picked verifiable-work plus permissionless PoW, which is the property you just said matters.

"What if LLMs aren't the thing" is the right question, and the answer is that consensus isn't bound to LLMs. It's bound to causal autoregressive processes: sample the next element of a sequence from a model's conditional distribution, with the draw hash-seeded so it replays deterministically. That's not a chatbot-specific idea. Audio, video, world models, action models, most of the sequence architectures on the horizon are autoregressive. A different dominant generator in five years drops into the same proof-and-verify machinery without touching the chain. The bet is on next-element prediction, which predates and outlives any single model family.

Model choice isn't frozen either. The recognized-model set evolves on-chain as better models show up, and mining is never gated on who you are, so the network is no more stuck on today's models than on today's GPUs. And "can't run on a PC" doesn't touch the property you care about. Bitcoin outgrew CPUs, then GPUs, and its payment layer never got less permissionless. Security budget scales with whatever hardware exists; censorship-resistant payments and independent validation don't need the work to fit a laptop. The ledger is model-agnostic. The money keeps working even as the work target moves.

So yes, we narrowed the scope on purpose. That narrowing is what produces the robust, permissionless, censorship-resistant payment layer you called non-negotiable. The generality lives in the math and in permissionless model evolution, not in renting out arbitrary work under an authority.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!