Bitcoin Forum
September 23, 2026, 03:43:48 AM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [PRE-ANN] Zecnero (ZMR) | Zcash-derived privacy | RandomX CPU mining | No premin  (Read 86 times)
KaitoArisaka (OP)
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
September 21, 2026, 09:46:53 PM
Last edit: September 22, 2026, 10:13:35 PM by KaitoArisaka
 #1

Zecnero (ZMR)
Shielded payments from Zcash. RandomX mining for the computer you already own.

PRE-ANNOUNCEMENT · No testnet yet · No launch date set

Website | Protocol Specification | GitLab | Discord | X



What this is

Zecnero is a fork of Zebra, the Rust node for Zcash. It keeps the Sapling and Orchard shielded pools and swaps Equihash for RandomX, the CPU-oriented proof of work that has secured Monero since 2019.

The goal is narrow. No machine class should hold a large efficiency edge per watt over a normal desktop CPU. Farms can still win on scale. They can't win by owning better hardware, because better hardware for RandomX looks like the CPU you already have.

This thread exists so the design gets picked apart before launch, while changing it is still cheap.



Allocation

PremineNone
ICO / presale / token saleNone
Dev fund / treasuryNone
Blocks reserved for anyoneNone
Founder stream3% of each block subsidy, from block 1 until the first halving at block 1,680,000

The founder stream totals 314,999.8125 ZMR, which is 1.5% of total supply. Consensus enforces it. Every block pays it regardless of who mined that block, and it stops permanently at the first halving. It goes to a P2SH multisig script published before launch.

I will also mine at launch with the same public software everyone else uses, from addresses published in advance, so anyone can measure my share of early blocks.



Specifications

TickerZMR
Proof of workRandomX-Zecnero: RandomX v1 reference configuration, only the Argon2 salt changed
Block time75 seconds
DifficultyASERT (aserti3-2d), 2 hour half-life, anchored at genesis
Block reward6.25 ZMR
HalvingEvery 1,680,000 blocks (about 4 years)
Total supply20,999,993.5652 ZMR. Issuance ends after 30 halvings. No tail emission.
PrivacyTransparent, Sapling and Orchard pools. Sprout removed.
TransactionsVersion 5 only
Coinbase maturity100 blocks
Max reorg depth20 blocks



Design choices worth arguing about

  • A private RandomX salt. Monero's RandomX hardware and the rigs on rental markets can't mine Zecnero at launch. Anyone can add the variant to a miner later, and the design doesn't depend on keeping them out. Every other parameter stays at the audited defaults.
  • Orchard circuit fix from NU6.2 applied at block 1. Zecnero's rules follow Zcash NU6, except for the NU6.2 Orchard soundness fix and the canonical proof size rule, which apply from the first block.
  • Genesis commits to a recent Bitcoin block hash. The genesis timestamp is the public release time. Blocks mined before release would show up against the difficulty schedule.
  • 20 block reorg limit plus checkpoints. A small new chain is cheap to attack with rented CPU. Running nodes refuse deep reorganizations. A hashrate-independent finality layer is planned before any exchange listing.
  • No tail emission. Same shape as Bitcoin and Zcash. The tradeoff is a fee-only security budget in the long run, and it's open for debate.


Mining

The miner is a fork of XMRig with an rx/zecnero algorithm, built for Linux and Windows. Solo mining goes through a small bridge between the node and XMRig. A pool comes with launch, and a P2Pool-style decentralized pool is planned afterward.

Reference benchmark: about 8,200 H/s on an i7-13700KF at 16 threads, Windows, huge pages and MSR mod on, VBS enabled. RandomX wants roughly 2 MB of L3 cache per thread, so running every thread is often slower.

Windows Defender flags the miner as Program:Win32/Contebrew. It flags stock XMRig the same way. Verify the release SHA-256 and add a folder exclusion. Don't turn off your antivirus.

Hashrate earns its share of blocks. Nothing more is promised. Nobody should buy hardware to mine this.



Status

Protocol specificationDraft published
Node: chain identity and issuanceIn progress
Node: RandomX proof of workNext
Node: difficulty, reorg limit, founder streamPlanned
Miner (XMRig fork)Working, verified against test vectors
Node to miner bridgeBuilt
DNS seeder, Docker, installersBuilt, waiting on a node binary
Public testnetNot started
MainnetNot scheduled

The RandomX-Zecnero hash has been checked across four separate implementations (reference C++, the Rust binding, XMRig on Linux, XMRig on Windows), which agree on all 17 published test vectors.

A public testnet runs for several weeks before any mainnet date gets set. The launch date will be announced here at least a week ahead, together with the founder addresses and the genesis parameters.



Known risks

  • A new chain has little hashrate. Majority attacks are cheap until it grows.
  • CPU-friendly proof of work also suits botnets and stolen cloud accounts.
  • Sapling depends on the Zcash Sapling trusted setup. Orchard needs none, and wallets should default to it.
  • The node modifies consensus code. It needs outside review before mainnet, and review is welcome now.
  • Privacy coins face delisting pressure in several jurisdictions.



Looking for

  • Review of the protocol specification, the consensus changes in particular
  • Rust developers with Zebra or Zcash experience
  • Testnet miners on any hardware, especially older machines and ARM
  • People willing to run seed nodes

Criticism in this thread is useful. Posting it before launch costs nobody anything.



Links

Websitezecnero.org
Discorddiscord.gg/jphuzAXgd8
X@zecnero_org
GitLabgitlab.com/zecnero
Project emailzecnero@proton.me
Direct contactkaitoarisaka@proton.me
PGP keyzecnero.asc, fingerprint FFFC8AC02BF7B4B450B43B1F653209A344E75767

Security issues go to zecnero@proton.me privately, before any public post.

Zecnero has no price, no market, and no token on any other chain. Any "Zecnero" token you find elsewhere belongs to someone else.
KaitoArisaka (OP)
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
September 21, 2026, 10:15:41 PM
Last edit: September 22, 2026, 10:11:45 PM by KaitoArisaka
 #2

Reserved for updates

Zecnero project signing key

Fingerprint: FFFC8AC02BF7B4B450B43B1F653209A344E75767

Also published at zecnero.org/zecnero.asc and used to sign the code on GitLab. If those ever disagree with this post, trust none of them.

Code:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: User ID: zecnero <zecnero@proton.me>
Comment: Valid from: 9/19/2026 12:40 PM
Comment: Type: 255-bit EdDSA (secret key available)
Comment: Usage: Signing, Encryption, Certifying User IDs
Comment: Fingerprint: FFFC 8AC0 2BF7 B4B4 50B4  3B1F 6532 09A3 44E7 5767


mDMEaq67ARYJKwYBBAHaRw8BAQdAPPAYHc+Eep6d+p1zS3LypG+BWxgBQGMRkea4
DpwzPj+0G3plY25lcm8gPHplY25lcm9AcHJvdG9uLm1lPoivBBMWCgBXFiEE//yK
wCv3tLRQtDsfZTIJo0TnV2cFAmquuwEbFIAAAAAABAAObWFudTIsMi41KzEuMTIs
MiwxAhsDBQsJCAcCAiICBhUKCQgLAgQWAgMBAh4HAheAAAoJEGUyCaNE51dnL0sA
/1As3HtllJCcjejp2xd+9DuWLLx9hTSnUSw6ELrycA8KAQDdXzP/+yAxuuWh6QD2
dCa32OkpcDUn6EYPBEbM4MayB7g4BGquuwESCisGAQQBl1UBBQEBB0DEooQVfkdD
TibibpLEln7uHuERwthV3xxB/D/39GObTgMBCAeIlAQYFgoAPBYhBP/8isAr97S0
ULQ7H2UyCaNE51dnBQJqrrsBGxSAAAAAAAQADm1hbnUyLDIuNSsxLjEyLDIsMQIb
DAAKCRBlMgmjROdXZyOrAPoCI//0w/Ajtqlgy+CvihVwsytgAo0DCi1ySe8nSUGE
EgEAzxgHzl7mXOfjp6DeSW7PmjDwayXrpkiGt9aukAnaLg4=
=8MCI
-----END PGP PUBLIC KEY BLOCK-----


Signed statement tying this account to the key:

Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I am KaitoArisaka on bitcointalk.org, author of the Zecnero (ZMR) ANN thread.
This is the Zecnero project signing key.
Fingerprint: FFFC8AC02BF7B4B450B43B1F653209A344E75767

Launch parameters, founder addresses and release checksums will be signed
with this key. Anything claiming to be one of those without a valid signature
from it is not from the project.

2026-09-22
-----BEGIN PGP SIGNATURE-----

iJEEARYKADkWIQT//IrAK/e0tFC0Ox9lMgmjROdXZwUCarL8RRsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDEACgkQZTIJo0TnV2cjbQEA/TF9LtA1Z+bzDeuT/LWk
Wfn6unUyLbvQxfahWPNGQOMBALaFL8FISCqcj5kzJy1DB8rtIb6YAt4DqrW6/k6U
t4QI
=uKLT
-----END PGP SIGNATURE-----

Updates will follow below.
lightbit
Member
**
Offline

Activity: 473
Merit: 89


View Profile WWW
September 22, 2026, 01:08:43 AM
 #3

Interesting... will follow via discord.

CHAINQUIRY — Discover, Research & Verify Crypto Projects
Free Project Listings | Official Thread
KaitoArisaka (OP)
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
September 22, 2026, 01:24:01 AM
 #4

Thanks, see you in there. Discord is where the day-to-day happens for now, and testnet details will go out there first.

If you plan to mine it, mention what hardware you have when you join. Older and lower-end machines are the ones I most want numbers from before launch.
BoozyTalking
Newbie
*
Offline

Activity: 393
Merit: 0


View Profile
September 22, 2026, 06:38:22 AM
 #5

Older and lower-end machines are the ones I most want numbers from before launch.

What numbers do you want, you didn't change anything and use standard pow algo, all hashrate
numbers for cpu you can find with google.
KaitoArisaka (OP)
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
September 22, 2026, 08:55:05 PM
 #6

Older and lower-end machines are the ones I most want numbers from before launch.

What numbers do you want, you didn't change anything and use standard pow algo, all hashrate
numbers for cpu you can find with google.

Fair point on hashrate. rx/zecnero is RandomX v1 with a different Argon2 salt, so the cost structure is identical and a given CPU does the same H/s it does on Monero. What I need from testers is whether the build runs correctly on hardware I don't own, older CPUs and ARM especially. A build that computes wrong hashes still looks like it's mining, which is why the 17 test vectors exist and I need to ensure my binaries didn't tarnish the H/s. Reusing the audited RandomX configuration is the whole point.
 
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!