Bitcoin Forum
July 11, 2026, 10:16:48 PM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 »  All
  Print  
Author Topic: [ANN] CivicNet (CIVIC) - CivicLight PoW | Mainnet is LIVE! | CPU-Only  (Read 197 times)
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 12:14:15 AM
 #1

CivicNet (CIVIC)
The Decentralized Community Grid — Built for Everyone, Powered by Any CPU

[GitHub Source] | [Wallets & Miners] | [Block Explorer] | [Official Pool]



💡 Why CivicNet?

Most proof-of-work coins today have quietly become a game for whoever owns the biggest ASIC farm. CivicNet takes a step toward a different path, built on a custom algorithm called civiclight, designed to keep mining accessible on ordinary CPU hardware rather than requiring specialized rigs.

Real Talk About ASIC Resistance:
To be upfront, civiclight is not currently ASIC-proof by design. It is a lightweight, hash-based algorithm rather than a memory-hard one. A dedicated ASIC-resistant redesign (memory-hard, similar in spirit to RandomX/Argon2) is on our roadmap for a future upgrade. For now, mining is CPU-friendly and low-barrier in practice. We believe in being honest about where the project stands technically rather than overclaiming.



🚀 Key Features

  • CPU-friendly PoW — The civiclight algorithm (SHA256d → SHA256 → XOR 0x5A → SHA256) is intentionally lightweight, keeping mining highly accessible to regular hardware today.
  • Fast Blocks — 1-minute block time ensures rapid network confirmations.
  • Fair Emission — 77 CIVIC per block, halving every 2,100,000 blocks (~4 years).
  • Fixed Supply — Hard capped around 315,000,000 CIVIC. No inflation loopholes.
  • Proven Architecture — Built on the battle-tested Bitcoin/Litecoin Core v0.21 codebase.
  • Modern Standards — Native SegWit and Bech32 address formats (civc1q...) from day one.


📊 Technical Specifications

Algorithmciviclight (custom, CPU-friendly)
Block Time1 minute
Block Reward77 CIVC (Halving every 2,100,000 blocks)
Coinbase Maturity50 confirmations (~50 minutes)
Total Supply~315,000,000 CIVC
Address FormatBech32 (civc1q...)
P2P / RPC Ports9333 / 9332



💎 Tokenomics & Transparency

CivicNet allocates a 1% developer premine (3,150,000 CIVIC), minted transparently in Block 1. This fund is strictly locked for ongoing core development, infrastructure maintenance (seed nodes, explorer, pool hosting), and community bounty initiatives.

Every other single coin in circulation is earned exactly the same way — through open, fair mining. There are no hidden VC allocations, no private sales, and no stealth mining. We believe in complete transparency from day one.



🛠️ Getting Started

1. Get the Node & Wallet
Download CivicNet Core (daemon + CLI + wallet tools) for your platform from our official GitHub releases.

2. Get the Miner
Our custom CPU miner binaries (Windows & Linux) with native civiclight optimization are available on the same releases page. Just extract and run.

3. Start Mining

Solo Mining (Direct to your local node):
Code:
cpuminer.exe -a civiclight -o http://YOUR_NODE_IP:9332 -u RPC_USER -p RPC_PASS --coinbase-addr=civc1qYOUR_ADDRESS

Pool Mining (Join the official public pool):
Code:
cpuminer.exe -a civiclight -o stratum+tcp://103.180.165.99:3032 -u civc1qYOUR_ADDRESS -p x

Full setup documentation (node configuration, wallet commands, security/backup best practices) is bundled in the USAGE.md and MINER_USAGE.md files within every release package.



🔗 Official Links

Source Code: https://github.com/CivicLight/CivicNet
Wallet & Mining Tools: https://github.com/CivicLight/CivicNet/releases
Block Explorer: http://103.180.165.99:3001/
Mining Pool: stratum+tcp://103.180.165.99:3032



📌 Current Project Status
CivicNet is in an early, active development stage. The core node architecture, wallet system, optimized CPU miner, and public block explorer are fully built, tested, and online. The dedicated public stratum mining infrastructure is actively spinning up. This is a true ground-floor community launch. We are building this entirely in the open and welcome all technical feedback, stress-testing, and community suggestions.



Disclaimer: This is not financial advice. Cryptocurrency mining and participation involve inherent technical and market risks. Do your own research before dedicating hardware or participating in any blockchain project.
gall00tech
Newbie
*
Offline

Activity: 32
Merit: 0


View Profile
Today at 12:41:18 AM
 #2

¿Is this mainnet?

Explorer  is not showing blocks.
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 05:11:20 AM
 #3

Thanks for flagging this — completely fair question to ask.

Yes, this is genuine live mainnet. The block explorer had a syncing issue on our end (missing txindex configuration on the node, which we've now fixed) — it wasn't showing data properly for a bit after this thread went up. That's now resolved.

You can verify directly here: http://103.180.165.99:3001

You'll see real block heights, transaction hashes, and block rewards being produced continuously. Appreciate the patience — and appreciate you checking rather than just assuming the worst, that's exactly the kind of scrutiny a new project should get.
Hashrateoptions
Newbie
*
Online Online

Activity: 125
Merit: 0


View Profile
Today at 05:31:40 AM
Last edit: Today at 05:45:47 AM by Hashrateoptions
 #4

There is no miner for linux. I see only for windows.
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 06:45:40 AM
 #5

Good news — a native Linux CPU miner build is now available.

Download: Check the Releases page on GitHub — civicnet-miner-linux-x86_64.tar.gz

Quick start:
Code:
tar -xzvf civicnet-miner-linux-x86_64.tar.gz
cd civicnet-miner-linux
chmod +x cpuminer
./cpuminer -a civiclight -o stratum+tcp://POOL_ADDRESS:POOL_PORT -u YOUR_CIVC_ADDRESS -p x

Built for a generic x86-64 baseline, so it should run on most 64-bit Linux distros (Ubuntu, Debian, Fedora, etc.) without extra dependencies beyond libcurl (usually already installed).

Full usage instructions (solo mining, pool mining, troubleshooting) are bundled in MINER_USAGE_LINUX.md inside the download.

Let me know if you hit any issues getting it running.
Hashrateoptions
Newbie
*
Online Online

Activity: 125
Merit: 0


View Profile
Today at 06:51:38 AM
 #6

czeck also explorer it is not working
BoozyTalking
Newbie
*
Offline

Activity: 384
Merit: 0


View Profile
Today at 08:05:25 AM
 #7

Where is windows wallet?
chn520
Newbie
*
Offline

Activity: 33
Merit: 0


View Profile
Today at 08:22:39 AM
 #8

./civicnet-node: error while loading shared libraries: libboost_filesystem.so.1.90.0: cannot open shared object file: No such file or directory
sdnz
Newbie
*
Offline

Activity: 64
Merit: 0


View Profile
Today at 09:29:59 AM
 #9

Is there any Discord channel?
Or can you point what node is available to join?
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 11:22:08 AM
 #10

Discord: Not set up yet — we're a small team focused on getting the core infrastructure solid first (node, pool, explorer, wallets) before spreading across more channels. It's on the list. For now, this thread is the best place to reach us.

Node to connect to: Our public node is running at:
Code:
103.180.165.99:9333

If you're running your own civicnet-node, you can add it as a peer:
Code:
addnode=103.180.165.99
in your civicnet.conf, then restart.

Mining pool: Also live, at:
Code:
stratum+tcp://103.180.165.99:3032

It's a young pool — still just us and a handful of early testers so far — but fully functional (PPLNS payouts, 0.01 CIVC minimum payment, live stats at http://103.180.165.99:8080). If you connect and hit anything weird, let us know here, we're actively watching this thread.
vostokzyf
Newbie
*
Offline

Activity: 35
Merit: 0


View Profile
Today at 11:59:48 AM
 #11

./civicnet-node: error while loading shared libraries: libboost_filesystem.so.1.90.0: cannot open shared object file: No such file or directory
Sparks60
Newbie
*
Offline

Activity: 50
Merit: 0


View Profile
Today at 12:04:57 PM
 #12

./civicnet-qt
./civicnet-qt: symbol lookup error: ./civicnet-qt: undefined symbol: _ZN3fmt3v107vformatB5cxx11ENS0_17basic_string_viewIcEENS0_17basic_format_argsIN S0_20basic_format_contextINS0_8appenderEcEEEE

./civicnet-node
./civicnet-node: symbol lookup error: ./civicnet-node: undefined symbol: _ZN3fmt3v107vformatB5cxx11ENS0_17basic_string_viewIcEENS0_17basic_format_argsIN S0_20basic_format_contextINS0_8appenderEcEEEE
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 12:17:15 PM
 #13

Thanks for reporting these - both are missing/mismatched shared library issues, common with dynamically-linked binaries. Here's how to fix each:

1. libboost_filesystem.so.1.90.0 missing:
Your system doesn't have the matching Boost version installed. Install it via your distro's package manager:

Debian/Ubuntu:
Code:
sudo apt install libboost-all-dev

Fedora:
Code:
sudo dnf install boost-devel

Arch:
Code:
sudo pacman -S boost

2. civicnet-qt: undefined symbol fmt::v10::vformat:
Your system has an older version of libfmt than what civicnet-qt was built against. Update it:

Debian/Ubuntu:
Code:
sudo apt update && sudo apt install libfmt-dev

If your distro's repo still has an older libfmt version even after updating, you may need a newer one from a backports repo, or build libfmt from source (https://github.com/fmtlib/fmt).

If neither works: tell us your distro + version (e.g. "Ubuntu 20.04", "Debian 11") and we'll give you exact package names/versions.

We're aware dynamic linking like this can cause friction for less technical users — we're looking at building more portable (statically-linked) binaries in a future release to avoid this entirely. Appreciate you flagging it.
vostokzyf
Newbie
*
Offline

Activity: 35
Merit: 0


View Profile
Today at 12:42:13 PM
 #14

./civicnet-node: error while loading shared libraries: libfmt.so.10: cannot open shared object file: No such file or directory
   rinima
scorpio18
Copper Member
Legendary
*
Offline

Activity: 1946
Merit: 1000


Admin of CoinMiners Pools


View Profile WWW
Today at 12:52:09 PM
 #15

From my point of view, this coin looks pretty questionable right now. Here's why:

  • I compiled the wallet from source and added the node to the configuration file. The wallet connects successfully, but the node immediately drops the connection.
  • The project doesn't even have its own domain name, whitepaper, or any proper documentation.
  • Even the main mining pool doesn't have a dedicated domain.

The node IP appears to be located in Indonesia. You can verify it yourself using SeoPer IP Information.

Also, the main pool displays the message: "Welcome to sha256-mining.go.ro", which is a Romanian domain redirecting to a camera thing.

At this point, I honestly don't know what's going on with the developer. Does he actually know what he's doing?

So i'm out.

Sparks60
Newbie
*
Offline

Activity: 50
Merit: 0


View Profile
Today at 12:52:56 PM
 #16

2. civicnet-qt: undefined symbol fmt::v10::vformat:
Your system has an older version of libfmt than what civicnet-qt was built against. Update it:

its other way around, i have fedora 44 with version 11, and it wants 10
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 01:07:15 PM
 #17

This is fair criticism and I appreciate you taking the time to check things out rather than just assuming. Let me address each point honestly:

"Welcome to sha256-mining.go.ro" + the MYT logo:
You caught something real. We built our pool software on top of an existing open-source pool template (sha256-nomp), and missed replacing some of the original template author's leftover branding in a couple of secondary template files that we hadn't fully audited yet. This has now been fixed - the pool site shows correct CivicNet branding throughout now, no leftover template text or logos. This was carelessness on our part, not anything intentional or malicious - but you were right to flag it, and it's a fair thing to be suspicious of. Feel free to refresh and check.

No domain name / whitepaper / documentation:
Also fair. We're currently running on the VPS's raw IP for node/pool/explorer, and don't have a formal whitepaper yet. We've prioritized getting the actual infrastructure (node, mining pool, block explorer, wallets) working and tested first, rather than polishing marketing materials before the core software was even solid. That's a legitimate sequencing choice we made, but we recognize it makes the project look less "finished" to someone evaluating it today. A domain and proper docs are on our list.

Node dropping your connection:
We haven't been able to reproduce this yet - can you share more detail? What OS/distro, what exact config you added, and any error output from your node's debug.log around the time it disconnected? We want to actually fix this, not just wave it away.

IP located in Indonesia:
Correct, that's just where our VPS is hosted - no issue there, just wanted to confirm it's accurate.

We're a small, early-stage project being transparent about being early-stage. Appreciate you holding us to a real standard - that's exactly the kind of scrutiny that keeps projects honest. If you're open to it, we'd genuinely like to figure out the connection issue you hit.
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 01:19:49 PM
 #18

2. civicnet-qt: undefined symbol fmt::v10::vformat:
Your system has an older version of libfmt than what civicnet-qt was built against. Update it:

its other way around, i have fedora 44 with version 11, and it wants 10

Apologies, my earlier advice assumed the wrong direction on this - thanks for the correction.

You're right, this isn't "old vs new" in a simple sense. libfmt uses inline versioned namespaces (fmt::v10, fmt::v11, etc.) specifically because they don't guarantee ABI compatibility across major versions - even though v11 is technically "newer," it's not a drop-in binary replacement for v10. Our civicnet-qt binary was linked against fmt v10 specifically (via our build's dependency pinning), so it's looking for v10 symbols that don't exist in your v11 install, even though v11 is present and otherwise perfectly fine.

Practical options on your end:
1. Build libfmt v10 from source alongside your system's v11 (they can coexist since the versioned namespace prevents symbol conflicts): https://github.com/fmtlib/fmt/releases - grab the 10.x branch
2. Check if Fedora has a compat package (unlikely, but worth a "dnf search fmt" just in case)

Longer term, this is really on us to fix properly - the correct solution is for us to build future releases as statically-linked binaries, so this kind of external ABI dependency goes away entirely and the binary just works regardless of what version anyone has installed. That's something we're actively looking at for the next release.

Sorry for the friction, and thanks for pushing back on the wrong fix.
CivicLight (OP)
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
Today at 02:52:15 PM
 #19

CivicNet (CIVC) — Major Update: Windows Release + Bug Fixes



Since the initial announcement, we've been heads-down fixing real issues and shipping the tools people actually asked for. Here's what's new:



NEW: Full Windows Release

Previously we only had a Windows CPU miner. Now the full toolkit is available for Windows, all in one package — no installation, no extra DLLs required:

  • civicnet-qt.exe — Graphical wallet. Point and click, no command line needed.
  • civicnet-node.exe — Full node/daemon
  • civicnet-cli.exe — Command-line control interface
  • civicnet-wallet.exe — Command-line wallet tool
  • civicnet-tx.exe — Transaction utility
Full setup instructions are bundled in USAGE.md inside the download.



Bugs Found & Fixed

We'd rather list these out than pretend they didn't happen:

  • Block explorer wasn't indexing data — missing txindex on the node, plus a wallet-supply calculation method mismatched for a PoW coin. Both fixed; explorer now shows accurate live block/transaction data with auto-sync every 2 minutes.
  • Pool statistics were never being recorded — a deeper issue in our fork of the pool software meant miner stats (hashrate, worker counts) weren't being tracked at all, even though mining itself worked. Rewritten and fixed — live stats now work correctly at the pool dashboard.
  • Leftover template branding — a community member caught old branding text/logo from the open-source pool template we built on top of, still present in a couple of secondary pages we hadn't audited. Fixed, and we appreciate the catch.
  • Wallet search feature was non-functional — the per-address mining stats page existed but was silently broken across several layers (wrong API wiring, missing dependencies). Now fully working.



    Where Things Stand

    Node + CLI + walletLinux & Windows
    GUI walletLinux & Windows
    CPU minerLinux & Windows
    Block explorerLive, auto-syncing
    Mining poolLive, stats working

    Links:
    Source & releases: https://github.com/CivicLight/CivicNet
    Block explorer: http://103.180.165.99:3001
    Mining pool: http://103.180.165.99:8080



    What's Still Missing

    Being upfront, same as always: no dedicated domain yet (running on the VPS's raw IP), no whitepaper, no Discord/Telegram community yet, and civiclight is not currently ASIC-resistant by design (that's a planned future upgrade, not a current guarantee). We're prioritizing working software over polish, but we know these gaps matter for how the project is perceived, and they're on our list.



    This is not financial advice. Cryptocurrency involves risk. Do your own research before participating in any project, including this one.
Sergick2023
Newbie
*
Offline

Activity: 17
Merit: 0


View Profile
Today at 05:25:29 PM
 #20

Wallet not sync on Windows(
Pages: [1] 2 »  All
  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!