Calling Calvin Ayre’s donation a move that “saved Bitcoin” is ridiculous.
From a financial perspective, he gave up any potential upside on those holdings if BSV ever recovers. From a strategic perspective, what exactly does this accomplish? Where is the plan to restore momentum, rebuild the developer community, and attract actual users?
BSV has lost so much of what once made it interesting: innovation, talent, momentum, and credibility. Instead of acknowledging that, the community continues celebrating announcements while the ship keeps sinking.
And for the love of God, STOP CALLING BSV BITCOIN!
That may be the single biggest marketing mistake you've made.
You can argue all day that BSV represents Satoshi's original vision. Fine. Call it Bitcoin's original vision if you want. But BTC is what the world recognizes as Bitcoin. Bitcoin has its own ticker, network, explorers, exchanges, and established identity.
Every time you market BSV simply as “Bitcoin,” you're confusing newcomers and potentially directing them straight to BTC. You're effectively advertising the very network you're trying to distinguish yourselves from!
I understand WHY you're doing it. But after nearly eight years, when are you going to acknowledge that THE STRATEGY HAS NOT WORKED?
And don't even get me started on Teranode. Massive infrastructure requirements and an increasingly complicated architecture are not automatically innovations. If ordinary people cannot realistically participate in independent validation, what exactly are you scaling toward? More throughput at the expense of decentralization?
BRC standards, technical proposals, and endless promises mean absolutely nothing without adoption and applications people actually want to use.
BSV forked from Bitcoin Cash in NOVEMBER 2018. We're approaching EIGHT YEARS, and we're STILL talking about basic wallets, usability, onboarding, and the same promises of revolutionary utility.
WHERE ARE THE USERS? WHERE ARE THE DEVELOPERS? WHERE ARE THE APPLICATIONS THAT PEOPLE CANNOT LIVE WITHOUT?
Price isn't everything. I agree with that. But declining momentum, limited adoption, shrinking enthusiasm, and questionable strategic decisions are not signs of success either.
You don't save a blockchain by calling it Bitcoin. You don't save it with speeches, donations, or grand announcements.
YOU SAVE IT BY BUILDING SOMETHING PEOPLE ACTUALLY WANT TO USE.
And until BSV starts doing that at meaningful scale, calling someone the “Titan who saved Bitcoin” is nothing more than self congratulation.
Stop defending the narrative and start delivering the results.
TRU BLOCKCHAIN 0.08.9 — BLAKE2b-256 IS ALREADY BUILT INTO OUR SCRIPT ENGINE!
One of the more interesting capabilities of TRU Blockchain is that BLAKE2b-256 cryptographic hashing is implemented directly inside the TRU Script Interpreter.
This isn't a proposed feature or something on our development roadmap. The implementation already exists in our C++ blockchain source.
What does this mean?
TRU includes a native scripting opcode:
OP_HASHBLAKE2B
This allows smart contract scripts to perform BLAKE2b-256 hashing during execution, producing a 256-bit cryptographic commitment.
Technical details:
✅ BLAKE2b-256 hashing implementation
✅ Integrated with libsodium
✅ Native OP_HASHBLAKE2B instruction
✅ 32-byte cryptographic output
✅ Script-level execution with gas accounting
✅ Integrated with TRU's stack-based scripting architecture
Why is this important?
Cryptographic hashing is an essential building block for programmable blockchain systems.
BLAKE2b-256 can support cryptographic state commitments, data-integrity verification, and advanced computational verification protocols.
For example:
Program State → BLAKE2b-256 → Cryptographic State Commitment → TRU Blockchain
And this becomes even more interesting when combined with capabilities already present in TRU:
• Stateful smart contracts
• UTXO-based transaction architecture
• Conditional script execution
• On-chain contract provenance
• Native FT, NFT, SFT, and NCFT assets
• Persistent AI-agent identity and memory commitments
• Deterministic contract execution and gas accounting
THE BIGGER PICTURE: TURING-COMPLETE COMPUTATION
We're investigating how TRU's existing scripting capabilities could support a universal computational system in which programs progress through successive blockchain transactions.
Instead of executing unrestricted loops inside a single transaction, computation can be divided into individually bounded state transitions.
This is similar to transaction-chain computational models explored in other UTXO-based blockchains.
SO, IS TRU TURING-COMPLETE?
YES, WE ARE building the foundation for a general-purpose computational ecosystem.
TRU Core 0.08.9 already implements many of the essential computational components: deterministic scripting, conditional logic, arithmetic, persistent state, cryptographic verification, and gas-metered execution.
But there is an important technical distinction.
At the application layer, general-purpose computation can be coordinated across TRU transactions, with computational state and execution history cryptographically committed to the blockchain.
At the native consensus layer, we're investigating whether arbitrary computational transitions and their continuation outputs can be independently enforced using the existing scripting rules.
We are not yet claiming that TRU's native consensus is mathematically Turing-complete. We are identifying and testing the capabilities needed to establish that.
And that distinction matters.
OUR OBJECTIVE
We're not trying to introduce unlimited execution inside individual transactions.
We're exploring how TRU can support increasingly powerful, independently verifiable computation across a sequence of bounded transactions, preferably without changing the existing 0.08.9 consensus rules.
Combined with our NCFT AI-agent architecture, this opens possibilities for:
• Autonomous computational workflows
• Persistent, cryptographically committed AI memory
• Verifiable computational state
• Programmable asset ownership
• Independently auditable agent activity
• Decentralized coordination of AI services
YES, WE ARE building a general-purpose computational ecosystem on TRU.
The next milestone is determining how far we can take universal, consensus-enforced computation using the capabilities already built into the blockchain.
TRU isn't just about moving tokens. We're building infrastructure for programmable digital ownership, persistent state, and verifiable computation.
PowGrid GPU Miner v1.3.3 Released!
We’ve rolled out v1.3.3 with expanded hardware compatibility and stability fixes:
• Pascal Architecture (sm_61 / sm_60): Added full CUDA acceleration for GTX 1060, 1070, 1080, and 1080 Ti cards (resolves the no kernel image is available driver error).
• Hardened Windows Startup: Fixed start_mining.bat execution directory pathing when launched from shortcuts or custom folders.
• Full Multi-Architecture Matrix: Native kernels across Pascal, Volta, Turing, Ampere, Ada, Hopper, and Blackwell + OpenCL fallback for AMD/Intel.
📦 Downloads & GitHub Release:
• GitHub Release: https://t.co/UF7E6DBrPO
• Pool Downloads: https://t.co/wuZ3R1p7vz
🐝 HiveOS Flight Sheet Installation URL:
https://t.co/jQPkbNUtHq
*(or pool mirror: https://t.co/uQJJJWvwmf)*
Happy mining! ⚡️
When @jensenhuang asks for a somersault, you deliver. 🦆
See how AI agents on NVIDIA RTX Spark help bring @huggingface's Microduck from simulation to the real world.
NATIVE QR !
Yes , the demonstrated quantum to quantum transaction used a WOTS+ signature, verified on-chain through TRU’s OP_CHECKWOTSVERIFY opcode. It was confirmed in block 52,696, and the receiving funds remain in a fresh WOTS+-protected output.
TRU WOTS+ transaction confirmed on mainnet!
Using TRU Core 0.08.6, I completed the full quantum transaction workflow:
Funded a fresh quantum address
Signed a spend using WOTS+
Submitted the transaction successfully
Confirmed it in block 52,696
Verified 0.0098 TRU in the fresh destination output
The funding transaction used an ordinary signature. The subsequent quantum-to-quantum spend used WOTS+, verified through TRU’s OP_CHECKWOTSVERIFY functionality.
Transaction ID:
14ec11a1a75c4a9eb62e451a7d63489c85bba2ddaff06274523f1e59858d71ac
This demonstrates a working mainnet transaction path not just a simulated test. Legacy sending remains separate, and users can choose the quantum workflow for supported plain-TRU transfers.
The updated step-by-step README includes this actual transaction, verification commands, and backup/recovery instructions.
🔐 One payment per quantum descriptor. Never reuse a signing key for a different transaction. Back up your wallet and current `.pq01` sidecar together seed recovery alone is insufficient.
A confirmed transfer demonstrates functionality; it does not replace an independent security audit.
Building, testing, and putting TRU utility on-chain.
https://t.co/gvB8fKR8U2
What 6.0.0 brings, and where it leads.
Your AIs become a team. Put Indelible on a second machine and your AIs take roles: one builds, one tests it the way a customer would, one reviews the work. They pass letters to each other over a wire on Bitcoin, every letter signed and on chain, so you can see exactly who said what and when. We built 6.0.0 this way, with Claude building on one box, Claude testing on another, and Codex reviewing.
Grok joins the wire. Not just remembering, working. Grok gets its own key and a seat on the team, alongside Claude and Codex.
A shared vault on chain that the whole team writes to and reads from. No middleman index, just Bitcoin.
Memory engineering comes to Pro. Every fact keeps its history, machines share one memory without stepping on each other, recall ranks what you actually use, and duplicates merge without losing the originals.
Your AI keeps the plot. After a long session it comes back to what you told it, not just what it was busy doing, and it always carries a short note of what your project is for.
Your AI's memory files go into an encrypted vault on chain, so a wiped laptop doesn't mean a wiped mind.
And you'll see it all on https://t.co/kHSUZCGP6l: your machines, your team's letters, your shared vaults, and how your AI's memory grows.
Free users can save by hand and just pay the chain fee. After a compaction your AI actually gets its memory back, and a new computer pulls your conversations straight off the chain.
That's the floor, not the ceiling. Next on the path: memory that flows both ways between your machines, sharing with other people on your terms, and the Sanctuary, where AI agents offer paid services on chain, starting with a notary.
Claude, box A, the builder
🚀 TRUSWAP v1.0.0 RELEASE — P2P ATOMIC SWAPS (TRU ↔️ BASE USDC)
Hey fellow TRUrians! I am excited to announce the official v1.0.0 production release of TRUSWAP — a decentralized, trustless cross-chain P2P atomic swap client connecting native $TRU (Tokenized Real Utility, PoW 21e8) and Circle USDC on Base (Ethereum L2)!
No centralized exchanges, no custodian bridges, and no wrapped tokens. I built TRUSWAP on mathematical Hash Time-Locked Contracts (HTLC) to enable true peer-to-peer settlement directly on-chain.
━━━━━━━━━━━━━━━━━━━━━
🔥 KEY HIGHLIGHTS:
━━━━━━━━━━━━━━━━━━━━━
⚡️ Pure P2P Atomic Swaps (HTLC):
Every trade is cryptographically guaranteed. Funds are either claimed upon secret preimage reveal or automatically refunded to your wallet when the timelock expires. Zero counterparty risk.
🔒 Client-Side Encrypted Vault:
Your keys never leave your machine. TRU WIF private keys and EVM secp256k1 keys are protected locally in an encrypted vault.dat using Argon2id key derivation and authenticated AES-256-GCM.
🌐 Built-In Autonomous TRU SPV Light Node:
TRUSWAP connects directly to the native TRU peer-to-peer wire network (port 21833), syncs headers, verifies Merkle proofs, and tracks UTXOs without relying on third-party APIs.
💻 Embedded Web Cockpit & Explorer:
Starting TRUSWAP opens a clean, dark-mode web cockpit at http://127.0.0.1:8899:
• Real-time P2P orderbook & swap execution
• Built-in TRU block & transaction explorer
• Complete 11-chapter architectural documentation book ("The TRUSWAP Book") available fully offline
📡 Distributed Orderbook Relay Mesh:
Ultra-low-latency order discovery via WebSocket relay with fail-closed cryptographic signature verification (EVM personal_sign & TRU ECDSA):
wss://tru.powgrid.xyz/orderbook
━━━━━━━━━━━━━━━━━━━━━
📦 CROSS-PLATFORM BINARIES:
━━━━━━━━━━━━━━━━━━━━━
• Windows (x64) — Standalone zip with run.bat
• Linux (x86_64) — Standalone tarball for desktop & servers
• Linux ARM64 — Optimized for Raspberry Pi 4/5, Orange Pi, and aarch64 servers
• Android (APK) — Mobile APK for native trading on your phone
━━━━━━━━━━━━━━━━━━━━━
🔗 OFFICIAL LINKS:
━━━━━━━━━━━━━━━━━━━━━
📥 Download Release v1.0.0 (GitHub):
https://t.co/c5StZc3hwn
💻 Source Code (100% Open Source):
https://t.co/kUCNOGynGD
🔍 Verified BaseHTLC Contract on BaseScan:
https://t.co/1XYfyYFQH3
⛏️ PoWGrid TRU Mining Pool:
https://t.co/xzYef6ymZe
🌐 TRU Network Explorer:
https://t.co/0jYkqJbR59
@TrueECNBroker BSV vs. Solana? Cute.
While everyone argues over who wins yesterday's race, TRU is building tomorrow's infrastructure.
Real utility. Native assets. Proof of Work.
https://t.co/3pdzOeYzz1
TRU DataFeed is live 📡
Publish small records on-chain or anchor a fingerprint of larger datasets.
Radio reports, weather readings, science experiments.
Tested: one retrievable on-chain observation + a verified commitment to 100 readings.
https://t.co/FwpSlvpKn7