[ANN][NCTI] Noctari - Keyless Privacy PoS L1 | Fair Launch | CPU-Mineable NOW

[noctari]

https://noctari.xyz/downloads/noctari-banner.png

NOCTARI ($NCTI)
A private, fair-launched Proof-of-Stake Layer-1 with no admin key.
noctari.xyz  •  Explorer  •  GitHub  •  Discord  •  Whitepaper

⛏ The fair-launch CPU window is OPEN

Noctari is mining right now. Blocks 1–20,159 (~7 days) are a one-time Quark CPU proof-of-work distribution window — no premine, no presale, no insider allocation, no GPU or ASIC edge. At block 20,160 the chain hard-locks to pure Proof-of-Stake, forever. If you want to mine the launch, this is the window. Guide: MINING.md. Quickstart at the bottom of this post.


What Noctari is

• Keyless — no admin key, ever. The spork (governance) key is the empty string. Every consensus rule is frozen at genesis. No party — including the developers — can change emission, the reward split, or the privacy rules after launch. The only way anything changes is a new client release that node operators voluntarily adopt.
• Private payments by default. Sapling zk-SNARK shielded transactions hide amount, sender and receiver. Proofs are generated client-side on your own CPU. Transparent and shielded both supported, with shield / unshield between them.
• Anti-whale masternode economy. Deterministic masternodes in four tiers. Block rewards are flat within a tier and step up across tiers, so stacking a bigger single position doesn't buy proportionally more steady income.
• Stakeable Vault. Lock coins for a fixed term and they keep staking for block rewards AND earn a share of a 10% interest pool on top.
• Rollover jackpot. 5% of every block feeds a perpetual, collateral-weighted jackpot that pays an un-grindable winner about twice a day. Locking more collateral = better odds.
• Perpetual tail, no hard cap. A small 5-NCTI/block tail funds stakers and masternodes forever, so security never runs out of budget.
• Open source, MIT. A PIVX v5 fork (which descends from Bitcoin Core). All consensus is in the public repo.

Specs

Code:

Consensus         Quark CPU-PoW window (blocks 1–20,159) → pure PoS
Block time        30 seconds
PoS activation    height 20,160 (~1 week of PoW)
Emission          50 NCTI → 5 NCTI tail (−5 every ~86,400 blocks); no hard cap
Premine           none (zero)
PoS reward split  Masternodes 60% / Stakers 20% / Dev 5% / Jackpot 5% / Vault 10%
Dev treasury      5%, two disclosed fixed addresses, consensus-enforced, non-redirectable
Masternode tiers  Shade 100 (tx-fees only) / Specter 1,000 (w1) / Wraith 10,000 (w3) / Reaper 100,000 (w5)
Vault lock terms  30 / 90 / 180 / 365 days
Privacy           Sapling / SHIELD zk-SNARK shielded payments
Governance        keyless — spork key empty; rules frozen at genesis
Ports             P2P 52472  •  RPC 52473
Client            Noctari Core 5.6.99

Wallets & downloads

• Web wallet + dashboard: noctari.xyz (nothing to install)
• Android APK: download
• Desktop (Linux AppImage / .deb, full node built in): AppImage
• Node / miner (Linux): tarball or build from source
• Block explorer: noctari.xyz/explorer

All wallets are non-custodial — keys are generated and stay on your device.


Mine it in 3 steps

1. Copy a receive address (starts with N) from your Noctari wallet.

2. Get the node and start it — it connects on its own:

Code:

wget https://noctari.xyz/downloads/noctari-node-1.0.0-linux-x86_64.tar.gz
tar xzf noctari-node-1.0.0-linux-x86_64.tar.gz && cd noctari-node
./start.sh -daemon

3. Mine to your address (one loop per CPU core, or ./mine.sh YOUR_ADDRESS 4):

Code:

while true; do ./noctari-cli generatetoaddress 1 YOUR_ADDRESS >/dev/null; done

Full guide, including multi-core: MINING.md


Roadmap

• Now: Quark CPU-PoW fair-launch window open (~7 days).
• Block 20,160: pure Proof-of-Stake activates — staking, deterministic masternodes, the Vault, and the jackpot all go live.
• After: masternode onboarding (from 100 NCTI), community channels, exchange conversations.

Why fair launch matters here

There is no key that can change the rules, no premine to dump, and no insider unlock. What you see in the code is what the network will always enforce. The PoW window exists so the initial coins go to whoever shows up and mines — not to a treasury. That's the whole point. Come mine.

noctari.xyz • github.com/noctari-core/noctari

[weesdr]

Dev mined from block 1 and is currently mining and getting most of the blocks

[visibleplayer]

Where is full source code?

[weesdr]

Any pool?

[noctari]

Where is full source code?

Full source is on GitHub — the complete node (C++, all consensus) and the wallets, MIT licensed:
https://github.com/noctari-core/noctari

Build instructions are in the README. There's also a prebuilt node/miner tarball and the desktop/Android wallets under Downloads on the site if you don't want to compile.

Dev mined from block 1 and is currently mining and getting most of the blocks

It's fully open source and free to mine — no dev fee during the PoW window, no premine, no presale, no insider allocation. Same public code, same network, same rules for everyone; every coin from block 1 is mined in the open.

Yes, the launch nodes started at block 1 — a new chain needs someone producing the first blocks. But there's no protocol edge to be had, and the field's already competitive: external miners are pulling the majority of recent blocks (~90% of the last 50), and it shifts constantly as more people join. That's the entire point of an open window.

If the distribution bothers you, the fix is in your hands and open to everyone equally — point some hashrate at it. Guide: https://github.com/noctari-core/noctari/blob/main/MINING.md

[SwampSwagga]

Discord?

[noctari]

Discord?

https://discord.gg/7bQTwtZWRQ

[bogdan198]

Where is full source code?

Full source is on GitHub — the complete node (C++, all consensus) and the wallets, MIT licensed:
https://github.com/noctari-core/noctari

Build instructions are in the README. There's also a prebuilt node/miner tarball and the desktop/Android wallets under Downloads on the site if you don't want to compile.

Dev mined from block 1 and is currently mining and getting most of the blocks

It's fully open source and free to mine — no dev fee during the PoW window, no premine, no presale, no insider allocation. Same public code, same network, same rules for everyone; every coin from block 1 is mined in the open.

Yes, the launch nodes started at block 1 — a new chain needs someone producing the first blocks. But there's no protocol edge to be had, and the field's already competitive: external miners are pulling the majority of recent blocks (~90% of the last 50), and it shifts constantly as more people join. That's the entire point of an open window.

If the distribution bothers you, the fix is in your hands and open to everyone equally — point some hashrate at it. Guide: https://github.com/noctari-core/noctari/blob/main/MINING.md

Title: [BUG] Repository is missing several build-system components — does not build from a clean checkout
Hello,
I tried building noctarid from source (git clone https://github.com/noctari-core/noctari, then core/autogen.sh) on a clean Ubuntu 22.04, and ran into several issues that appear to indicate part of the repository simply wasn't committed:

core/src/secp256k1/Makefile.am uses CPPFLAGS_FOR_BUILD and CFLAGS_FOR_BUILD via += inside if USE_ECMULT_STATIC_PRECOMPUTATION, without a prior = initialization. With automake 1.16.5 (Ubuntu 22.04) this is a fatal error during autoreconf.
core/build-aux/m4/ is missing entirely (17 files: bitcoin_qt.m4, ax_boost_*.m4, bitcoin_find_bdb48.m4, l_atomic.m4, l_socket.m4, etc. — present in the upstream PIVX-Project/PIVX). configure.ac declares AC_CONFIG_MACRO_DIR([build-aux/m4]) and uses the BITCOIN_QT_CHECK / BITCOIN_QT_CONFIGURE / BITCOIN_QT_FAIL macros from bitcoin_qt.m4. Without it, calls to PKG_CHECK_MODULES, AC_CHECK_LIB, AC_CHECK_HEADER wrapped inside BITCOIN_QT_CHECK(...) don't get expanded by m4, and autoconf 2.71 fails with "possibly undefined macro".
core/depends/Makefile is missing, and core/depends/builders/ is missing entirely (darwin.mk, default.mk, linux.mk) — because of this, make in depends/ doesn't even start ("No targets specified and no makefile found").

It looks like this entire part of the repository existed only locally on the author's machine and was left out of git add — which is why the build worked for the author, but breaks immediately, before the compilation stage even starts, for anyone cloning the repo from scratch.
I reproduced the issue and confirmed a fix: I copied the missing files from PIVX-Project/PIVX (current upstream) — after that, autogen.sh runs cleanly, configure is generated, and depends/make starts and proceeds normally through the dependency list.
I suggest adding to the repository:

core/build-aux/m4/
core/depends/Makefile
core/depends/builders/

and checking src/secp256k1/Makefile.am for compatibility with automake >= 1.16.

And you dare call this a working project or code? You couldn't even fork the project right.