Don't trust the provider — verify the machine.

TensorCash publishes the verifier open source: given a proof, anyone can replay it and confirm which model did the work. Trust is earned by a checkable machine, not granted to an incumbent.

Verify it yourself: https://tensorcash.org/build/#verifiers

AI turns electricity into intelligence. Crypto turns it into value. TensorCash does both at once: one real forward pass answers a prompt *and* mints the coin — the same joules become an answer and a block. Here's how to point a GPU at it. 👇

https://tensorcash.org/blog/how-to-mine/

Two protocol upgrades hit TensorCash mainnet at block 8,000 (~15 July). TIP‑3 binds every proof to the prompt it answered — tighter security, and lower‑entropy inference workloads can now mine. TIP‑2: fully arbitrary CFDs on chain. Update your miner, node, and verifier. 👇

https://tensorcash.org/blog/tip-2-tip-3-mainnet-activation/

⚠️ Node operators: set spv-min-cumulative-tick-per-block=0 in bitcoin.conf and restart before block 11,000, or your node will stop syncing (headers advance, blocks stall). Fix ships in v1.0.4 later today; drop the override after upgrading.

https://tensorcash.org/

Classic proof-of-work burns electricity to prove electricity was burned. TensorCash points the same work at a real forward pass — the proof is just a by-product of answering a real prompt. Same chain security; the joules do a job. 👇

https://tensorcash.org/blog/pow-vs-useful-pow/

TensorCash v1.0.4 is out. VDF cumulative tick self-heals with full RPC visibility, plus amber adjudication semantics, wallet fixes and Linux desktop builds. Operators: upgrade — on v1.0.3 defaults, keep the tick-floor override until you do. 👇

https://github.com/tensorcash/tensorcash/releases/tag/v1.0.4

TensorCash v1.0.5 is out — setting up has never been easier. Prebuilt, public Docker images for GPU mining workers (Hopper + Blackwell) and the full node, plus Linux node builds and macOS (Apple Silicon) miner binaries. No more building from source. 👇

https://github.com/tensorcash/tensorcash/releases/tag/v1.0.5

TensorCash mainnet, six weeks in: implied throughput has climbed from ~27 to 100,900 tok/s, and difficulty has retargeted up step by step to keep pace. Our version of hashrate is measured in tokens per second of real inference, not wasted hashes. 👇

https://tensorcash.org/explorer

Your wallet shouldn't ask someone's server what you own. The TensorCash wallet is a full node with a GUI — balances and assets verified locally, not fetched from a backend. Prebuilt for Linux; runs anywhere with Docker (VNC console: off by default, password-gated). 👇

https://tensorcash.org/blog/how-to-run-the-wallet/

⚠️ Wallet setup note: the AI-proof check needs a verifier, and the wallet doesn't come pointed at one — you set it yourself. Run the open-source verifier on your own GPU, or point your node at a verification service you trust: VALIDATOR_HTTP_URL=https://your-verifier 👇't ask someone's server what you own. The TensorCash wallet is a full node with a GUI — balances and assets verified locally, not fetched from a backend. Prebuilt for Linux; runs anywhere with Docker (VNC console: off by default, password-gated). 👇

https://tensorcash.org/blog/how-to-run-the-wallet/#wiring-up-verification-it-has-to-be-real

Meet COMPUTE — the first asset issued on TensorCash. Real AI inference is the work that secures the chain, so as compute grows, difficulty becomes a live on-chain tracker of AI-inference activity. COMPUTE is the clearest way to see the asset-issuance platform in action. 👇

https://tensorcash.org/blog/tokenised-difficulty-options/

A miner ran the committed model at fp8 on a smaller GPU and submitted the proof as bf16. Full verification reran the model at bf16: the p-values collapsed, both blocks were assigned zero work, and the chain never extended them. Trust in action. 👇

https://tensorcash.org/blog/catching-a-quantized-miner/

On 28 July, in mainnet block 19,978, a tokenised difficulty option changed owner and native TSC moved the other way — both legs inside the *same* transaction.

There was no exchange account, no deposit or withdrawal, no escrow agent and no custodian. Two people running the TensorCash desktop wallet found each other over a bulletin board, negotiated directly, and settled on chain.

The interesting part is the guarantee. Because both legs live in one transaction, there is no ordering and no "who sends first". The chain has no way to accept half a transaction, so either both sides settle or neither does — not because anybody behaved well, but because there is no state in between.

Getting two strangers to co-sign that transaction is the actual work. Their wallets opened an encrypted peer-to-peer session, each proved on-chain ownership of what it was offering with BIP-322, and each verified the other's contribution input by input before signing anything. Nonces were exchanged before any signature was seen, and every adaptor signature was checked against the exact transaction on the table.

To the network the result looks like an ordinary Taproot spend. No escrow output, no multisig, no hash-preimage, no timelocked refund branch — none of the machinery costs block space.

The write-up includes the part most announcements leave out: one available protection, a lock-step reveal of the final signatures, was negotiated off in this run. It is a fair-exchange refinement rather than a custody hole — the worst reachable outcome was a stall — and we would rather document that than imply it happened.

Technical demonstration, not an offer or solicitation.

https://tensorcash.org/blog/first-otc-trade-fully-on-chain/

⛏️ TensorCash is at 600-second blocks.

Difficulty retargeted at block 20,160 (+3.72×) and blocks have averaged 605.7s since — right on target. Early miners rode blocks arriving 4–6× faster than target, and those rewards went to the people who showed up first. Thank you.

The network is doing ~7.7M tokens/sec of real model inference — 4.6 billion tokens every block. More powerful commercial models are on the way, and our position on that upside is simple: it belongs to the miners.

Mining rewards already reach 2,700+ distinct addresses within two hops. More hashrate is very welcome.

Also coming: better wallets, a community verification service TIP, and cross-chain transfers in the Qt wallet — where we would love community help finalising it. ⚡

https://explorer.tensorcash.org

🔐 Post-quantum spending is live on TensorCash — since block zero, not a someday migration.

You opt in by funding a new address type: tc1z…

• Taproot v2, key path disabled by consensus. A tc1z is an ordinary 32-byte Taproot output, but consensus permits only script-path spends — so there is no secp256k1 key-path signature to attack. What the leaf requires is up to the script; the standard wallet template makes it a single ML-DSA check, so the prefix alone proves the key path is off, not that the policy is ML-DSA-only.

• ML-DSA (NIST FIPS 204), via liboqs. Three parameter sets — 44 / 65 (TensorCash default) / 87 — for NIST categories 2 / 3 / 5. No Shor-like quantum attack is known against its module-lattice problem.

• Holds coin and assets. Native TSC always, and issued assets too. Already on mainnet: block 20,246 moved COMPUTE Index option units into a tc1z output — held in Witness v2; an ML-DSA spend out of one reveals the leaf later.

• Fees: free to receive (that block-20,246 tx paid just 363 sats), larger to spend — a default ML-DSA-65 spend runs ~10× a standard one, since the ~3.3 KB signature only enters the witness when you spend.

Before you use it: sign on hardware you control (liboqs warns against production use for sensitive data), back up every key (no seed-phrase derivation yet), and use a fresh address per receive.

No migration, no exposed legacy balance to rotate. Whether a coin sits on the PQ rail is your choice of address.

https://tensorcash.org/blog/post-quantum-is-on-tensorcash/

📢 TensorCash v1.1.0 — coordinated network upgrade at block 20,440, expected today.

v1.1.0 moves the difficulty algorithm from the 2,016-block retarget to ASERT: difficulty adjusts every block based on how far the chain is ahead of or behind its 600-second schedule. The old rule needed weeks to respond when mining throughput changed abruptly — the cause of the recent slow blocks.

⚠️ UPGRADE BEFORE BLOCK 20,440 — nodes still on older versions may FORK off the network at activation. Expected around 19:15 BST today (block times vary). Nodes, miners, pools, and any service that validates headers must run v1.1.0 before then. Balances and history are untouched; only the difficulty rule changes.

What to expect:
• At block 20,440 ASERT starts from a bootstrap difficulty calibrated to the hashrate observed over the last two days; block times may deviate from 10 minutes briefly while it settles.
• The reset is not a giveaway: if the mining throughput seen before the last retarget returns in full, ASERT brings difficulty back to today’s level in roughly two days (~48 h).
• A fast 12-hour half-life applies until block 46,738 (~6 months), then the standard 48-hour aserti3-2d configuration (used on BCH since 2020) takes over permanently. Block 120,440 is a review point, not an automatic reversion.
• Contracts referencing block difficulty now see per-block fixings.

⛏️ Miner note: blocks carrying low VDF ticks are relayed lazily and can be orphaned — low ticks don’t cost you mining performance, but carry enough ticks that your blocks propagate promptly.

🔁 Source mirror on GitLab: https://gitlab.com/tensorcash-org/tensorcash/-/tags/v1.1.0 (downloads on the main release link).

https://git.tensorcash.org/tensorcash/tensorcash/releases/tag/v1.1.0