Bitcoin Forum
March 12, 2026, 03:20:43 PM *
News: Latest Bitcoin Core release: 30.2 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN][NXF] Nexaflow - A ledger with confidential transactions and upcoming IPO  (Read 96 times)
anythingtechpro (OP)
Newbie
*
Offline Offline

Activity: 39
Merit: 0


View Profile
February 28, 2026, 04:27:13 AM
Last edit: March 03, 2026, 01:08:20 AM by anythingtechpro
 #1

NexaFlow (NXF)
Privacy-First Digital Ledger · Confidential Transactions · Decentralized Exchange

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🌐 Website  ·  📄 White Paper  ·  💻 GitHub  ·  💬 Discord
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━


What is NexaFlow?

NexaFlow is a cryptocurrency I built from scratch in Python and Cython. The whole thing was designed around a pretty simple idea — what you do with your money shouldn't be anyone else's business.

Every transaction on the network is confidential by default. Privacy wasn't something we tacked on later or threw into a "shielded mode" toggle. It's baked into the protocol itself. Transaction amounts are hidden with Pedersen commitments, senders are mixed using ring signatures, and recipients get one-time stealth addresses. There's no opt-in, no special wallet mode. It just works that way, every time.

The whole codebase is open source on GitHub. Go read it. I'd rather people trust the code than trust me.



How It Works (The Technical Stuff)

▸ Confidential Transactions

Amounts never show up on the ledger in plaintext. We use Pedersen commitments — basically C = v·G + b·H — to lock in a value cryptographically without exposing it. Then bulletproof-style range proofs verify that the committed amount isn't negative or overflowed, all without revealing what the number actually is.

If you've looked at how Monero handles this, it's a similar concept, though our implementation is our own.

▸ Ring Signatures (LSAG)

When you sign a transaction, your key gets mixed in with a bunch of decoy keys pulled from the ledger. We use Linkable Spontaneous Anonymous Group signatures for this. From the outside, you can't tell which key in the ring actually signed — that's the whole point. Key images handle double-spend prevention so we don't sacrifice security for privacy.

▸ Stealth Addresses

Every time someone sends you NXF, a brand new one-time address gets generated on the fly using ECDH. Even if your public address is known, nobody can look at the ledger and connect incoming payments to you. We also use view tags so your wallet can scan for your own transactions efficiently without leaking info.

▸ Consensus (RPCA / BFT)

We went with a Byzantine Fault Tolerant consensus mechanism inspired by Ripple's RPCA. Blocks close roughly every 10 seconds. No mining, no PoW energy waste, no PoS centralization games. Validators agree and move on.

I know some people are going to ask "why not Nakamoto consensus" — honestly, for what we're doing, BFT gives us faster finality and a simpler validator model. It's the right fit.

▸ Cython Under the Hood

The hot paths — consensus logic, ledger operations, the privacy crypto, transaction processing — are all written in Cython and compile down to native C extensions. So yeah, it's a Python project, but the parts that matter run at near-C speed. Best of both worlds IMO.



Features

  • ECDSA / secp256k1 — same curve Bitcoin uses, for wallet keys and signing
  • Built-in DEX — on-chain order book, no middlemen, trades happen natively on the network
  • Staking — lock NXF and earn interest, rates go from 2% APY (flexible) up to 15% APY (365-day lock)
  • Trust Lines — multi-asset support through controlled relationships between accounts
  • Double-Spend Prevention — sequence numbers + key images, belt and suspenders
  • REST API — full programmatic access to node functions, everything's documented
  • mTLS P2P — node-to-node comms are encrypted with mutual TLS, not just regular TLS
  • Encrypted Wallets — private keys sit behind AES-256 at rest
  • Docker — `docker-compose up` and you have a node running, that's it



Tokenomics

TickerNXF
Max Supply100,000,000,000 (100B)
ConsensusRPCA (BFT)
Block Time~10 sec
Account Reserve20 NXF
Min Fee0.00001 NXF
InflationNone — no block rewards, nobody can mint
Fee ModelFees get burned permanently

There are no block rewards. No inflation. The only new NXF that enters circulation comes from staking interest, and that gets offset by fees burning constantly. Net effect: supply shrinks over time.



Staking Tiers

Pretty straightforward — longer lock, better rate.

TierLockAPY
FlexibleNone2%
30-Day30 days5%
90-Day90 days8%
180-Day180 days12%
365-Day365 days15%

There's also a demand multiplier that adjusts based on how much of the network is staking. Get in early and you'll see better returns.



⭐ IPO

March 15, 2026 — IPO Opens
March 31, 2026 — Mainnet Launch

Price: 1 sat = 1 NXF

Starting March 15th you can buy NXF on our exchange with Bitcoin. 1 satoshi gets you 1 NXF. Flat price, no tiers, no presale, no VC rounds, no "strategic partner" allocations. Same price for everyone.

March 31st the chain goes live — transfers, staking, DEX trading, the whole thing.

🎗️ 100% of IPO proceeds go to St. Jude Children's Research Hospital

All of it. Every sat raised during the IPO gets donated to St. Jude. I didn't build this to cash out — I built it because I wanted to build it, and if the IPO can help kids with cancer then that's worth more than a dev fund. There's no founder allocation, no team tokens, none of that.

🔥 Unsold coins get burned

Whatever doesn't sell during the IPO is gone. Permanently. No treasury sitting in a multisig somewhere slowly unlocking over 4 years. No surprise dilution. Unsold = destroyed.



Roadmap

Q1 2026
  • IPO opens March 15
  • Mainnet live March 31
  • Exchange open for NXF/BTC
  • Staking from day one

Q2 2026
  • Mobile wallet (iOS + Android)
  • Getting listed on other exchanges
  • Dev SDK + proper docs

Q3-Q4 2026
  • Smart contracts
  • Cross-chain bridges (BTC, ETH to start)
  • Hardware wallet support (Ledger, Trezor)
  • On-chain governance



Links




MIT License. Code's on GitHub. PRs welcome.

Questions? Come hang out in the Discord.
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!