Bitcoin Forum
October 07, 2026, 05:08:12 AM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN][TESTNET][PoW] (TNR)Tenero | matmulhash v2 | Privacy coin | 60 second block  (Read 39 times)
zad112 (OP)
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile WWW
October 06, 2026, 04:06:38 AM
 #1

TENERO (TNR)
GPU-FOCUSED PROOF-OF-WORK CRYPTOCURRENCY

PUBLIC ALPHA TESTNET IS LIVE

GitHub Repository |
Downloads / Releases |
GitHub Discussions

Reddit |
Discord


🟢 Mainnet launch: 1 November 2026
🟡 Public Alpha Testnet: LIVE


Mine the testnet, run a node, benchmark your GPU, and help prepare for mainnet.



An experimental proof-of-work cryptocurrency built around modern GPU hardware, with a long-term goal of Monero-style privacy.


DISCLAIMER

Tenero is currently an experimental alpha testnet.

The project is developed by one person and has not received independent cryptographic, security, or hardware review. It should not be considered a finished cryptocurrency.

Nothing on the Tenero test network has monetary value.

The network may be reset during development, and testnet coins may be lost.

The current proof-of-work is new and has not been independently analyzed for ASIC resistance.

Tenero is inspired by CryptoNote and Monero, but it is not affiliated with, endorsed by, or part of the Monero project.



1. WHAT IS TENERO?

Tenero is an open-source proof-of-work cryptocurrency written in Rust.

The project focuses on two main areas:

  • GPU-oriented proof-of-work*
    *
  • Monero/CryptoNote-inspired transaction privacy
The first public alpha is mainly for testing the blockchain, mining algorithm, networking, and wallet software.

The goal at this stage is not to present a finished currency. The goal is to build the system, test it, find problems, and improve it.



2. PROOF-OF-WORK: MATMULHASH V2

Tenero currently uses a proof-of-work algorithm called matmulhash v2.

The algorithm is built around operations that are highly parallel and well suited to modern GPUs.

Each mining attempt:

  • Uses the block header and nonce as input*
*
  • Generates a 64 × 8192 INT8 matrix with ChaCha20
  • Selects a 16 MiB slice from the proof-of-work dataset*
    *
  • Performs exact integer matrix multiplication against that slice
  • Folds the result into the final proof-of-work hash

Current dataset parameters:

Code:
Dataset size:        4 GiB
Number of slices:    256
Slice size:          16 MiB
Matrix:              64 × 8192 INT8
Epoch length:        100 blocks

The dataset uses a data-dependent construction and must be generated sequentially.

The intended workload combines:

GPU compute throughput and memory bandwidth

The design is aimed at modern GPUs with high memory bandwidth and hardware optimized for matrix operations.



3. ASIC RESISTANCE

Tenero does not claim that matmulhash v2 is ASIC-proof.

The current design is testing the following idea:

Quote
If each mining attempt requires a large memory read as well as substantial matrix computation, a specialized miner may still need a large amount of high-bandwidth memory and compute hardware to outperform commodity GPUs.

Each mining attempt reads a complete 16 MiB dataset slice.

At the current measured GPU performance, this represents hundreds of GB/s of equivalent dataset reads.

On an RTX 5070 Ti, the current CUDA implementation has measured approximately:

Code:
~33,000–36,000 attempts/sec
~550–590 GB/s equivalent slice reads

These figures come from one GPU and one system. They are not proof of ASIC resistance.

The project welcomes criticism, FPGA implementations, hardware analysis, and attempts to find more efficient ways to perform the computation.



4. NETWORK AND CONSENSUS

Block target: approximately 60 seconds

Difficulty adjustment: per block using a weighted LWMA-style calculation over the previous 30 blocks

Starting reward: 20 TNR

Halving interval: 525,600 blocks

Main emission: 20,000,000 TNR

Tail emission: 0.5 TNR per block

Premine: none

The alpha genesis block creates no premine. Coins on the network are created through proof-of-work mining.

Block size uses a dynamic median-based model with a penalty for oversized blocks, following design ideas used by Monero.



5. PRIVACY

The long-term privacy design is inspired by CryptoNote and Monero.

The planned transaction system includes:

  • CLSAG ring signatures*
*
  • Ring size 16
  • Pedersen commitments*
*
  • Bulletproofs+
  • Hidden transaction amounts

The current alpha wallet is not Monero-level private.

It currently uses an interim CryptoNote-style output scheme while development continues toward the planned privacy architecture.

The current implementation does not yet provide all of the protections intended for the final design.

The cryptographic implementation is also unaudited.



6. NETWORKING

Tenero uses a peer-to-peer network for blocks and transactions.

Peer communication currently uses an encrypted channel based on the Noise protocol.

The alpha network includes a built-in seed server for peer discovery.

The long-term goal is to support multiple independently operated seed nodes and a more decentralized network bootstrap process.

The current alpha network is small and experimental.



7. SOFTWARE

The current release includes:

  • tenerod — Tenero full node*
    *
  • tenero-miner — GPU/CPU miner
  • tenero-wallet — command-line wallet*
    *
  • tenero-wallet-gui — graphical wallet
  • tenero-seedcheck — seed verification utility
The GPU miner currently supports NVIDIA GPUs through CUDA.

The GPU implementation uses CUDA, NVRTC, and cuBLASLt.

AMD GPU mining is not currently implemented. Alternative miner implementations are welcome.



8. CURRENT TEST STATUS

The project currently includes:

  • Rust node and blockchain implementation*
*
  • GPU and CPU mining
  • CLI and GUI wallets*
*
  • Encrypted P2P networking
  • Independent Python reference implementation*
*
  • Consensus test vectors
  • Fuzzing targets*
*
  • Approximately 900+ automated tests

The Rust implementation is checked against the independent Python reference implementation for bit-for-bit agreement on the relevant consensus and proof-of-work calculations.

The current alpha network has been run across Windows and Linux nodes, with proof-of-work being produced and independently verified by the nodes.

The network is still very small and has not been subjected to large-scale testing.



9. HARDWARE AND MINING REQUIREMENTS

GPU mining:

NVIDIA GPU

CUDA Toolkit 13.x

Approximately 4 GiB of GPU dataset storage is required. Additional memory is used by the mining process.

Only a limited number of GPU configurations have been tested, so compatibility with other cards should be considered experimental.

CPU mining:

CPU mining is supported but is currently impractical compared with GPU mining.

Tenero is intended as a GPU-focused proof-of-work experiment.



10. DOWNLOAD

Latest releases:


https://github.com/zad112/Tenero/releases


The releases currently provide Windows and Linux packages.

The binaries are not code-signed.

Verify the SHA-256 checksum before running downloaded binaries.

Users who prefer to verify the code themselves can build the project from source.

Source:


https://github.com/zad112/Tenero




11. BUILD FROM SOURCE

Tenero is written in Rust.

Basic source build commands:

Code:
cargo build --release
cargo test --workspace

The repository contains the consensus specification, test vectors, benchmark information, threat model, network documentation, and testing documentation.



12. ROADMAP

CURRENT: PUBLIC ALPHA TESTNET

The current phase is focused on public testing of the node, miner, wallets, networking, consensus, and proof-of-work.

The alpha period is intended to identify and fix issues before the permanent network launches.

NOVEMBER 1, 2026: PERMANENT MAINNET

The current plan is to launch the permanent Tenero mainnet on November 1, 2026.

The mainnet launch is intended to mark the transition from the experimental alpha network to the permanent Tenero network.

Before launch, the priorities are:

  • Expand public network testing*
*
  • Test additional GPU architectures
  • Improve mining performance and stability*
*
  • Improve peer discovery and network resilience
  • Continue consensus and security testing*
*
  • Expand documentation
  • Resolve known critical issues*
*
  • Prepare the permanent mainnet genesis and network parameters

Longer-term development

  • Replace the interim wallet output system with the planned Carrot-based design*
*
  • Continue privacy development
  • Expand independent node and seed infrastructure*
*
  • Encourage third-party miners and alternative implementations
  • Pursue independent cryptographic and proof-of-work review

The November 1, 2026 mainnet date is the current target and may change if a critical security or consensus issue is discovered before launch.



13. COMMUNITY AND DISCUSSION

GitHub Discussions:


https://github.com/zad112/Tenero/discussions


Reddit: r/Tenero


https://www.reddit.com/r/Tenero/


Discord:


https://discord.gg/QzfqaGDVcm


Use the community channels for:

  • Mining benchmarks*
*
  • Hardware testing
  • Bug reports*
*
  • Technical questions
  • Protocol discussion*
*
  • Suggestions
  • Development discussion

For security vulnerabilities, use the repository's private vulnerability reporting instead of publicly posting sensitive exploit details.



14. LINKS

GitHub:


https://github.com/zad112/Tenero


Releases:


https://github.com/zad112/Tenero/releases


GitHub Discussions:


https://github.com/zad112/Tenero/discussions


Reddit:


https://www.reddit.com/r/Tenero/


Discord:


https://discord.gg/QzfqaGDVcm


Consensus specification:


https://github.com/zad112/Tenero/blob/main/docs/CONSENSUS.md


Benchmarks:


https://github.com/zad112/Tenero/blob/main/docs/BENCHMARKS.md


Threat model:


https://github.com/zad112/Tenero/blob/main/docs/THREAT_MODEL.md




TESTNET → MAINNET

PUBLIC ALPHA TESTNET

Current phase: testing, benchmarking, bug fixing, and network development.




PERMANENT MAINNET — NOVEMBER 1, 2026



Nothing on the current testnet has monetary value.

The testnet may be reset.

The software is unaudited.

The proof-of-work is experimental.

There is no premine and no coin sale.

Do not treat the current testnet as an investment.



The current objective is simple:

Build it. Mine it. Test it. Break it. Improve it.

Then, if the network is ready:

Launch it.

Feedback, benchmarks, criticism, code review, hardware analysis, and bug reports are welcome.


zad112 (OP)
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile WWW
October 06, 2026, 05:27:04 AM
 #2

# 📦 Tenero `v0.1.0-alpha.4` is out

**Download:** https://github.com/zad112/Tenero/releases/tag/v0.1.0-alpha.4
Windows zip and Linux tar.gz. Check your file against `SHA256SUMS` before you run it.

**What changed**
One fix, found by running alpha.3 on the real network:
• A node that the seed connects to now asks the seed for addresses, and refreshes that link every 30 minutes until it has three outbound peers that aren't seeds. In alpha.3, a reachable node could end up stuck on the seed with no peers of its own, which is what alpha.3 was meant to prevent.
• Nothing else changed in the programs.

**Do I have to upgrade?**
No. The network, chain, rules and wire protocol are the same. alpha.1 to alpha.4 nodes are on the same chain and work together. Upgrade if you run a node that accepts inbound connections ("Let other nodes connect to me").

**Honest limits**
• The fix is covered by the program's own tests but has **not been tried on the real network**.
• GPU-tested by the author on one machine only (RTX 5070 Ti, about 34,000 attempts/s). Nothing is known about other cards.
• Linux: only the node has been run by hand. The Linux miner, wallet and wallet app have not been run.
• Your antivirus may flag `tenero-miner` as a coin miner. It is a miner, and nothing mines unless you start it. Check the checksum.

**Still a test release.** Unaudited, one developer, no value, and the network can be reset.
Official notices: only the pinned GitHub issue #1 (https://github.com/zad112/Tenero/issues/1). Anything claiming to be a notice elsewhere is not from the project.
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!